I suggest discussion on this list; you'll also need to discuss on the respective application lists if you want to change their UI code.
hmm. In this respect, I was just about to make a blog on blogger to kind of document what I do as I do it without cluttering a mailing list with e-mails here and there. I'll of course put stuff through the list, but I think blogger would be a little better as this would put all the info for this project in one place, where it'd be easier to go through and create some kind of documentation. What do the [EMAIL PROTECTED] members think of this? Is there any better way to consolidate info?
To get feedback quickly and to make sure that you reach the majority of the core developers you just have to use this list. Posts on this list will be read immediately by anyone involved in this project whereas a new entry in your blog will probably not be noticed at all. We can also host documents on the gsl pages on OOo and this mailng list can be searched as well.
When designing a new chrome API please consider that the preferred way to do this would be UNO components.
Another new thing for me to learn. Ooh goody. I just finished reading the W3C CSS spec, now I get to read some more. :-P
As a starting point (after you read some of the UNO papers) you may want to have a look at the TOOLKIT project which wraps part of VCL (eg the controls) with an UNO API. However, this is currently not used in the application UI but only for form controls (controls that you can embed in a document for scripting) and controls used in BASIC dialogs (for macro programming).
Since this effort would go on over at least many months you'd need ways to synchronize your work with the master builds; which would be possible using a child workspace (CWS, see e.g. http://tools.openoffice.org/dev_docs/child_workspace_policies.html ), but probably the synch work would run out of bounds at some point, so you'd need to integrate the work already done and then create a new CWS.
I would definatly not be following the recommended 1-4 weeks deadline... I wouldn't want to integrate untiil this project is quite a ways down the road, and that won't be in 4 weeks.
Nevertheless setting up a CWS would make sense, as it allows you to easily work on your own branch and to resync to the ever changing code base of OOo. Consider you start developing today and want to integrate something in 6 months. You will have a hard time to achieve that and you're likely to have a broken version afterwards. So a simple rule is: resync as often as possible to make sure you're alwas working as close to HEAD as possible.
Stephan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
