[snip] > > 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.
OK. Here's what I'll do. I like the idea of having a blog, because there are some nice tools to quickly post comments. So I can use the blog as a kiind of central storage place for all the information about what I'm doing. From the blogger blog I'll have a google group that e-mails will be sent to on all the changes. This group will have the [EMAIL PROTECTED] subscribed to it. I'll keep in mind when I'm writing the sections of blog that it'll be on a mailing list. Any objections, pointers, problems, comments, with this solution? Yes, you can search, but I haven't found that to be exactly the most responsive... In order for discussions to work. I think what I'd do is have a summary post every now and then to describe recent discussion and what was decided. The other option to make everything easily accessible is probably a little easier to grasp/work with. I can, instead of putting this list on another mailing list, simply use the blog and link to all the e-mails. I can post in depth progress descriptions, and then post to the mailing list whenever I think something needs discussion, or I want to run some ideas by the list. But I want to keep the blog to let people know what I'm working on when, and have a kind of place where I can keep myself on track as well. [snip] > 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). I was just looking at the toolkit... I'll definately have to read up on alot of things. That developer guide is going to take a while to read through, and then I'll have to read UNO docs. Also, I was just starting to look at some of the things mozilla has done, and wanted to know how much discussion there has been on using one of their technologies, or a derivative of them. I'm kind of liking XUL, though I don't think I'll have quite the same implementation as mozilla if I use it. There are some things I'd like with it, but others I don't. I don't want to embed the GRE, to make it usable. Also I was looking at the mozilla xpfe. I'll need to read more, but we might be able to use that... > 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. OK. Sounds good. I've called my CWS that I just set up silveronion, and I was just thinkinga about calling it silon: SILver is kind of like chrome ONions have layers so SILON will be the new chrome layer, or at least the code name, I don't know if it'll make it into the trunk as silon, but I thought it was a nifty name. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
