Hi,
Jacob Floyd wrote:
OK, not sure where else to post stuff as I work on it and find it (hmm. I should probably create a blog...)
I'm working on CVS access, and I just found this file (how nice, someone else has started the concept work, possibly gotten farther): http://gsl.openoffice.org/files/documents/16/848/Toolkit2.sxw
Any other info would be nice.
No, there is (well, to my knowledge) no further work in that direction; basically this is what we would have wanted to do if time had allowed us, but that's more or less still a wish list.
I also noticed there seems to be a lot of work on stop gap measures that seem to work around creating a new chrome layer to create widgets. I don't intend to put any effort into stop-gap measures. They bug me. Once you start using them, it's inevitable you're stuck with 'em IMO. So I'm going for the big cash prize (so to speak) I'm looking at a new chrome layer.
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.
I'll begin by creating the API I think I'll need for the chrome, and then slowly begin replacing references to VCL in the application code. As I find things in that the new chrome layer doesn't have that OOo needs, I will add those features. I believe that's the best route to take. Any suggestions otherwise would be appreciated though.
You're talking a huge effort here. For contributing please consider that you'll have to sign the JCA (see http://www.openoffice.org/contributing/programming.html).
When designing a new chrome API please consider that the preferred way to do this would be UNO components.
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.
Also you'd have to coordinate with the project leads of the applications when you change the application UI code.
Just some thoughts, pl
--
Never be afraid to try something new. Remember:
amateurs built the ark; professionals built the Titanic.
-- Autor unbekannt--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
