General

• Define minimal components of a GUI desktop. Implement them as web services and mozilla applications.
• add some kind of dependable database abstraction layer based on URLs in style of odbc/jdbc/dbi. perhaps better. some kind of SQL_in_web_context to URL mapping.
• group blogging/aggregation/calendaring tool
• http server side API specification to support magical features:
  • web site developer just provides proper URIs on his website
  • field completions from query
  • interface to desktop search features
• XUL Icon/List view, for finder/explorer like stuff (GUI native look)

Media player

Media player component(s), included in firefox.

Make it work especially well with OGG and other free formats.

VLC seems nice, but others could be supported.

This could greatly help with platform-independant open source video. Now this requires closed source plugins (flash).

API should be powerful enough to implement SMIL.

API:

• open(url,[callback]) - starts loading URL. callback is when clip info is available. maybe there should be a blocking version also
• play(), pause(), stop()
• seek(time) and seek(percent)
• fullScreen() and fullScreen(boolean) - maybe present() would be better?
• set(variable, value), get(variable) - change component settings
• getMetainfo(variable) - get clip metadata value
• getImage() - get current frame as image
• getPosition() - get clip (time) position

Calendar

Augment calendaring application so that it can be effectively used for publishing public events (like concerts, festivals, etc...)

General considerations

• Consider central data structure: RDF? Atom?
• Implement imports and exports as javascript plugins. done already?
• Implement publishing and refresh as javascript plugins. done already?
• Combine with blogging tool / GUI view

Editor

• Interface should be fully easily keyboard operatable (no mouse)
• Interface should have 2 tabs (master-slave), list of events and the edit form. Why?
  • this prevents focus shift when new windows appear and is much less distracting
  • popup windows don't loose position and such (since editing form is permanently instanced)

• Support extended attributes on events (thru RDF?) to display in event editing form (eg. price, performers, photos)
• Support for suggestions/search/browse (for location and categories, for example)

Imports

• RDFCAL
• Atom+hCalendar
• Atom+Google data
• Import subscription list from OPML or such
• Import lists of categories and locations (venues)

Exports

• Subscription list (so you can export your list/bookmarks. perhaps use browser bookmarks?)
• Support HTTP GET/POST as well as CALDAV for publishing edits to the server. Why?
  • writing whole iCal file is non-transactional (problems with multiple editors, etc)
  • We don't know how to set up caldav with passwords properly for our web server
  • perhaps we would like to use a quick and dirty PHP skript to implement updating the calendar database
  • ical is old and ugly. RDF/XML is better.
• Support for other RPCs (SOAP, XMLRPC..., various blogs). Probably as javascript plugin.