On Thu, Feb 06, 2003 at 09:17:20AM +0100, Philippe Ney wrote: > > > > If this effort is to succeed, we would like to ask all developers > > > > who have a few hours to help out. If Micah and I are to do this > > > > alone, it will take more time than you are probably willing to wait > > > > ;-) > > > > > > Is there a tasklist to choose from? > > > > Yes, in the page I posted: > > http://picogui.org/wiki/view/Main/PicoGUI1dot0 > > (or you can pick some task that is not in the list but you want to see > > in 1.0) > > Is there already something written in the page? I have only the wiki title > and a blank page...
The sfwiki is very flaky... you usually have to reload several times to get it to work right :( Some time we should replace it with phpwiki or moinmoin. > > > The list is not too big now, but some items need to be expanded in > > sub-items and some still need discussion. Specially, WidgetFoundry is > > our "GUI layout tool" (comparable to glade); we want it "complete" for > > 1.0 but we don't yet know what "complete" means. > > Is this point really important? > It's like waiting for a stable version of glade before releasing gtk, > isn't it? > I see the WidgetFoundry as a PicoGUI tool and not as a part of > the PicoGUI ~ui toolkit~. > In comparison with themetools that is needed to customise the look of > your application, the WidgetFoundry is not necessary to create it. Well, it could be used for either. Now that XWTs are usable, and even more so when widget foundry is, you can create the entire app's layout using widget templates. > > Maybe PicoGUI have to be split in something like : > > * picogui-uitoolkit (server + clients) > * picogui-themec (theme compiler, example, extra-themes) > * picogui-widgetfoundry (The WidgetFoundry) > > with some dependences between the packages. I think the current separation of widget foundry into apps and themec into themetools is good enough. Reorganizing things is hard in CVS, so unless there's a good reason I'd rather not move anything. In the new design however, the directory structure will be much better. Using SVN instead of CVS, we can move things around easily. You can look at the repository's contents at the moment to see what I have in mind for the new layout. > > Just my own vision of the project... > -philippe > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Pgui-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/pgui-devel -- Only you can prevent creeping featurism! ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Pgui-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/pgui-devel
