Inline comments follow: On Wed, 02 Feb 2005 11:42:08 +0100, Philipp Lohmann - Sun Germany <[EMAIL PROTECTED]> wrote: [snip] > 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.
A wish I plan to make reality, at least eventually. As noted, this isn't a small undertaking. And besides that I'm not the best programmer in the world. I'm sure a lot of those reading this list are a lot better than me, maybe not as stupid in taking on such big projects, but a lot better than me. :D [snip] > 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? [snip] > You're talking a huge effort here. Well yah. The squeaky wheel gets the grease, and this particular thing seems to be squeeking an awful lot in my ear, so I'll give it the grease and start it rolling. > For contributing please consider that > you'll have to sign the JCA (see > http://www.openoffice.org/contributing/programming.html ). This could pose a slight problem for me. I'm a minor. Any suggestions? > 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 > 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. > Also you'd have to coordinate with the project leads of the applications > when you change the application UI code. A gotcha. Good thing to know. Thanks. > Just some thoughts, pl Thoughts are the start of ideas, and ideas rule the world. > -- > Never be afraid to try something new. Remember: > amateurs built the ark; professionals built the Titanic. > -- Autor unbekannt Thanks, Jacob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
