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. 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'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. Thanks, Jacob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
