Suchfeld und Hauptnavigation überspringen, zur Unternavigation
Roadmap
For version 1.0.0
XHTML Templates
Currently cal is build up on the phpicalendar- and some quick table templates. Neither are XHTML compatible and need to be improved. Ben van t'ende has started working on that.
Administration Page
Right now we have the normal calendar view and the edit/create/delete event views, but there are more configuration views possible and already available (e.g. create cal_organizer/cal_location). To tie them all together an administration/configuration view would be nice. And this adminsistration page should be available for everyone who has at least one of those rights (of course limitted to the allowed rights).
piVar handling
Currently piVars are used in many parts of the extension. For some fe-editing views this is ok, but they are used also besides these views. PiVars should be handled in a configuration module - which has to be created. Afterwards only $conv-vars should used. This will also open the possiblity to plug into the configuration module and change settings depending on user-settings, which will be needed for personalizing the calendar.
Coding style
We have to make sure all variables are retrieved and stored through getter and setter methods.
Huge single-function classes should get divided into smaller parts (e.g. day-, week- & month-view).
FE-Editing
The way the FE-editing is programmed right now is a mess. It needs to be rewritten und structured. There should be method for each field - just like the event_service. Maybe we should think about extracting the whole fe-editing into its own extension.
Timezone handling
The way TYPO3 handles date fields is buggy. As soon as it is corrected we will start integrating timezone handling for events.
Configuration module
There should be a configuration module handling all settings through TS, flexform and piVars.
Icons
Some icons in the backend are still wrong or missing. RSS and ICS links should be displayed with an (additional) icon
Labels
Currently labels are handled through the template. Now the idea is to handle them through TS. This way we can hide labels if the value is not present.
Translations
Many translations got lost due to wrong encoding of the file :( and many new fields got added. We need translations!!!
For version 2.0.0
Personalize
This is the topic for private calendars, free-/busytime, alarm, timezones, note, todo, card. Things a fe-user can configure for himself only
div / lib
The extension will be converted to be based on the ect-extensions: div & lib
Attendee
People attending and registering for an event will come eventually. Therefore we need a attendee-model to handle this data and a attendee-service to manipulate it
A connector for tx_seminars is in progress :)
Free-/Busytime
As soon as we can create personal (private) calendars, it would be nice if a person could enable a public view to his calendar, showing every one whether he is free or busy without revealing any information about the events.
A request could be answered automatically when setting up a meeting with different attendees: “Does Mr. X have time to join the meeting?”
Note
Fe-User can create notes. These notes are similar to events with the fact that they only have description- and date/time fields and have no influence on free-/busytime
Todo
Another form of a note. But this “note” has an alarm built into itself.
Card
A vCard could be attached to an ICS export.
AJAX Interface
The interface for a fe-user dealing with any of the above mentioned configuration stuff should be intuitive. It shouldn't be much different as working on a desktop. Therefore a AJAX interface would be recommended.
Synchronization with Outlook/Sunbird
This could become a breakthrough feature: updating events using outlook/sunbird. The export of events is already possible through the generation of *.ics files.
For version 3.0.0
Partner Framework (if available)
Integrating of the upcoming partner-framework could ease dealing with fe-user, attendee, location and organizer.
Event-Management
It would be nice, if a fe-user could set up a meeting and organize the attendees. He would get feedback if any of the attendees are busy. On the other side, the attendees would get notified about the event and accept the appointment, decline the appointment, or send a reschedule request. The organizer can than handle the request and maybe reschedule the appointment..... A lot is possible here
Room-Management
Like managing people one could manage rooms to. E.g. is a room available for an appointment? Does the room have all the equipment needed? Size? And so on..... Jonas Hartmann has started working on that
Private Calendar
A private calendar is a calendar, which is only visible if a fe-user is logged in and belongs to the category user-list
One could think of extending the category by another user-list of people who have read access (shared view). So everyone in the main user-list should be able to manipulate all the events belonging to that category.
Sharing events
Sharing an event is the same as exporting a private event and someone else imports is on his calendar, with the exception, that the other person can manipulate it after importing. So sharing would mean, you are having a private event like a meeting course you are the organizer. All attendees get this event as a private-shared event. Means, they can see it, but can't manipulate it; besides removing it from THEIR view.
Skins
Just like TYPO3 all paths should be configurable to create different calendar skins, not only for public use, but for private calendars too.
