On 3/18/07, Nicolas Roard <[EMAIL PROTECTED]> wrote:
Here's a quick summary of the audio conf we had this evening... Participants were Yen-Ju, Jesse, David, Quentin and me.1/ We'll use a stable branch + trunk As a developer, you put the code you think is stable in it. Basically you put your code in trunk as currently, but when you have a version that you think is stable enough, you copy it in the stable branch. Users can then check that branch, not trunk, if they want a (hopefully) working release of étoilé :-) That way, users can safely report bugs against the stable branch, while not bothering developers with the trunk branch, which by definition is bleeding edge (as in, you'll cut yourself). For releases, it's also much easier for us -- we just need to copy the current stable code to a specific branch for the release (as the code in stable is supposed to work).
I created /etoile/stable and can build all of them with a single 'make'. -stable is supposed to make life easier. So whenever there is a bug report to -stable, the best solution is to fix in -trunk, then copy to -stable. If -trunk is too unstable for the moment, it is best to fix both in -trunk and in -stable. If you only fix in -stable, but still developing in -trunk, you may encounter merge conflict in the future. In short, treat -stable as a frozen state of -trunk. And I would encourage people to put your work-in-progress in trunk instead on your hard disk.
2/ Stable components that will go into that branch
I would like to add AZDock and AZBackground soon. It will be great that people can test them in trunk and report problems. Thanx. Another thing I would like to have is the Login.app, but it depends on Nicolas. (Nicolas, if you are busy, you can send me the code and I can upload it.) So in my mind, the main focus of next release is on all these system stuffs. (Except Grr, we don't really have any new and great user application). [snip]
5/ Space vs GWorkspace Quentin has a prototype for a filemanager, Space, in his branch. Space uses the Io bridge and UKDistributedView. We decided to wait for Quentin to fix the io bridge and commit Space on trunk and use it for the live cd for the étoilé account, as for the live cd we do not need a fully working filemanager -- a simple application launcher / disk browser is enough. Also there's a lot of problems with using GW (see point 4, and the fact that we'd have two competing session management: System and GW...), and... it would be better to start working on our own filemanager after all :) The fact that Space is based on io isn't a problem as we can replace parts of it by Objective-C objects when/if needed, and using io is ideal for prototyping/fast development anyway. Quentin will hopefully write a small tutorial explaining how to replace part of an objc program by io parts and vice-versa.
I just gave Space.app a try. First, Io has its own issue. I tried the official Io, the unstable in the branch and the stable one in -stable. None of them works well. Some do not even run the Calc.app. The official Io can not build ObjcBridge due to some errors. So even though it may sound too criticizing and I am apologizing for it, we should consider to rewrite Space into Objective-C now when the code base is still small in order to meet the deadline. Otherwise, we are fighting on two sides: one is to keep Io working, the other is to write a file manager. I looked at the code of Space. Besides using DistributedView and other views, the interesting part is to treat files and directories as objects. It is a good idea and we can keep it in Objective-C. If people are not objecting this idea, we can have a short list of what is supposed to work by deadline, either in Space.app or an objective-c version. I guess it belongs to another thread. Yen-Ju
7/ System will be splitted into a framework and an application, so that other apps can use System services without duplication
I have plan to add freedesktop to NSWorkspace as what System does through WorkspaceCommKit. For example, gnome and kde come with desktop entry for their applications. It is very similar to GNUstep's application bundle, but the application, icon and property list is scattering on the FHS. I plan to extend NSWorkspace so that it will work on these applications, say [-launchApplication: @"firefox"] will launch firefox, and [-appIconForApplication: @"gimp"] will return an image of gimp. Anyway, it will not meet 0.2 release, but is in my future plan. Finally, I think it is fun to have this conference. Never thought we can do thing like this. :D Yen-Ju
8/ Release date for the livecd and planning. We expect to release the 0.2 version for the 1st of May. Quentin hopes to have a working version of the io bridge / space filemanager in a couple of weeks. We'll have another audio conf in 3 weeks to see where we are. ... As a final note, I'll thanks all the participants to this audio conf (hopefully we'll have other devs on board next time), and while it was the first time we tried that, it didn't go too bad I think ;) Next audio conf same time (19hGMT), planned currently for the 8th of april. -- Nicolas Roard "La perfection, ce n'est pas quand il n'y a plus rien à ajouter, c'est quand il n'y a plus rien à retrancher." -- Antoine de St-Exupéry _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
_______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
