Beta 2 Uploaded

2003-03-06T22:47:26Z

The Beta 2 files have been uploaded to the Files page, for your downloading enjoyment. Currently all implemented features of the frontend and backend work, except for event submission from the frontend, which has broken since the last release and has yet to be fixed. New and improved instructions for installation are included.

Testing Framework Implemented

2003-03-05T21:14:31Z

A new unit testing framework has been implemented to test both the backend and frontend of the MightyCal software. It uses HttpUnit, which tests the ability to interact properly through a Web client.

MightyCal now listed on Freshmeat.net

2003-02-06T00:34:33Z

In preparation for attracting more developers to the MightyCal project, I've added a Freshmeat project listing. Freshmeat.net is the primary listing site for Open Source projects. It's often the first place that people look when searching for software to download and use, or for projects to join and help.

New documentation and screenshots

2003-02-05T23:50:08Z

The homepage at http://mightycal.sourceforge.net now has a link to a new Screenshots page. Also, updated API documentation has been created for the Backend... it's linked to via the homepage and the Sourceforge project page.

Leadup to Beta 2

2003-01-29T08:21:39Z

Beta 2 of MightyCal will be out shortly, with lots of new features. In particular, a full administration interface is implemented, web user authentication via the frontend is implemented, and a vastly improved frontend that uses the facilities of Cocoon to a much greater extent. The entire application is starting to look a lot more like a well-behaved MVC application, with the Cocoon frontend providing the View and Controller portions, and the Model implemented in the backend.

Frontend refactoring

2003-01-29T07:42:13Z

* The Cocoon frontend has been completely refactored as a separate subapplication that can be installed into an existing Cocoon installation. An Ant build script installs the MightyCal application into the main Cocoon installation.
* The new version of the Frontend has moved nearly all of the application logic into Cocoon components, by implementing custom Actions, Generators and Transformers in order to simplify the sitemap dramatically and make it more easily understandable.
* The Cocoon frontend now can handle user authentication and session tracking. The HTTP session mechanism is used to store information about the user's preferences, thereby eliminating the need to have lots of request parameters floating around and needing to be tracked.

Major refactoring in backend

2003-01-29T07:26:30Z

* Moved all modules into subpackages to clarify organization. In particular, split out the ever-increasing number of constants into individual Const.py files in each of the subpackages.
* Added new security assertion methodology; a SecurityPolicy module contains a map of permissions, and every object in the MightyCal tree gets permissions as defined in this map.
* Combined all XML-related procedure calls into two entry points; the Cocoon frontend only needs to know about these two entry points to get all the information it needs from the backend.

New data-entry handling methodology, plus refactoring

2002-11-20T00:19:06Z

Major refactoring done to the MightyCal internal structure. Constants have all been put into uppercase to distinguish them from variables. Many subpackages have been created to collect related modules together, thereby reducing confusion and increasing encapsulation. Also, an entirely new data entry methodology has been implemented: the DataEntryTransaction. The DataEntryTransaction has for its purpose the ability to provide a multi-stage event editing process, in particular the ability to return the user to editing an Event when the user's original entries/edits failed validation tests. When the user is returned to the data entry screen on a failed validation, the data entry screen will have full, informative error messages for each invalid field. This new DataEntryTransaction structure is user-agent agnostic... it will work whether the user is entering data via the Cocoon frontend, or whether the administrator is entering an event via the ZMI (Zope Management Interface). A user can also choose to "Save these values as defaults", so that future Event creation sessions for the same EventType will automatically be filled in using the values from the previous transaction.

New portal-like administration interface for Calendars

2002-11-20T00:15:46Z

New Portal-like Administrative interfaces for individual Calendars are functioning. Currently only a few panels are available for adding to the interface, but eventually the calendar Admin will be able to choose from a wide variety of status panels to add to the interface, in order to create a single-screen overview of the current happenings in their Calendar.

MightyCal goes Beta

2002-10-16T22:18:05Z

The MightyCal Beta 1 release has been made. The main changes available in Beta 1 are in the display templates available via the Cocoon frontend... MightyCal can now display calendars in HTML (List View, Month View, Event Detail and Event Edit), PDF (List View and Month View) and Avantgo/Strict HTML3.2 (List View and Month View). The Intermediate Template Language and associated Stylesheet Management interface have matured a lot, so that layout and look-and-feel are highly customizable. Event editing via the Cocoon frontend is also working. Downloads of the Frontend and Backend files are available from the "Files" area, and a basic Install document is available from "Docs".

Recent posts to news