There's one piece I left out in the wiki-page, namely how should the
structure for additional resources (skin/locales) look like. I'm not
sure how this should be structured. my suggestion would be that we
handle the resources with the following additional folders:
/calendar
/enterprise
/themes
/pinstripe
/winstripe
/locales
/en-US
As always, comments are welcome.
mickey.
When I suggested similar locales structures in the past, I've received
feedback from the localizers that having multiple directories they need
to check out in order to localize everything is too onerous.
As a result your locales should live in:
/calendar/locales/en-US/chrome/enterprise
and I'd suggest putting them in their own enterprise-en-US.jar
Your proposed themes structure seems in line with what currently
exists, although my preference would be to move away from having themes
directories all over the place. I haven't gotten enough consensus on
that to make it happen, but here's what I've been envisioning:
/calendar
/themes
/*instripe
/calendar (shared stuff)
/enterprise
/lightning
/sunbird
Each subdirectory would correspond to the feature's jar.
-lilmatt
mickey.
mickey.
The first feature that is about to be commited is the event dialog
proposed at http://wiki.mozilla.org/Calendar:Event_Dialog. The exact
location will be 'mozilla/calendar/prototypes/wcap'.
I'd like to make this a last call for feedback. If there're any other
suggestions/concerns, please bring them up before Monday. In case no
further comments arrive until then I'll go ahead an check the stuff in.
mickey.