[Gimp-developer] What's up with the list archives?
Does anybody know what is happening with the archives of the various GIMP mailing lists? I tried to have a look at them while I had no direct e-mail access during my long week-end, but the archives were 4 days late. On Sunday, they only contained the messages sent on Thursday morning. As of this writing, the last message archived for this list is a message sent by Sven on Friday afternoon. Take a look at these links: http://lists.xcf.berkeley.edu/lists/gimp-developer/2003-June/date.html http://lists.xcf.berkeley.edu/lists/gimp-user/2003-June/date.html http://lists.xcf.berkeley.edu/lists/gimp-web/2003-June/date.html This is unusual. Two weeks ago, the archives were not suffering from such a big delay. -Raphaël ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] what's up
Hi, "Branko Collin" <[EMAIL PROTECTED]> writes: > On 20 Dec 2001, at 12:23, Sven Neumann wrote: > > > a lot of you folks will go into XMas holidays soon and I thought it > > might be nice to give a status report on the current development so > > you have something to think about. So here's a short summary made up > > from the ChangeLog entries since 1.3.1 was released (about four weeks > > ago): > > [snippety-snip] > > There were more changes and most probably even a few important ones > > that I forgot. If you care, why don't you read the ChangeLog > > yourself? > > Thanks. As you said, though, most of that info is in the changelog. I'm not sure if this kind of mail is of interest to anyone. I thought a short summary might help since it's not too easy to read the ChangeLog sometimes. > Does GIMP 1.3. build? Is it useful for anything? What do you feel are > the major things to do before the first users will start using 3.x? > What do you feel are the major things to do before the first users > will be right in using 3.x? ;-) In other words: how far have you come > and how far do you still have to go? it builds. I can only remember a few hours during the last month when gimp from CVS would not build for some reason or another. Useability? I'd say there are still too many problems to use it for real work. It works fine for the occasional open/scale/save session or something similar. The target is still developers only I'd say. I won't give you any numbers. I'm doing this for too long now to know that giving people release dates at this early stage is a mistake. To get an impression on what needs to be done before we consider the code cleanup finished, take a look into the app directory in the source. When everything but main.c has gone, we are finished. As you can see we have already come very far (80-90 %). There are a few tasks beside the code cleanup that have already been started or are planned to start soon. I'd like to get them all into TODO.xml during the next weeks. Once we have collected the things we absolutely want to see for 1.4, we should declare a tentative feature freeze and try to stick to the task mentioned in TODO.xml. BTW, the file I'm talking about is the one used to generate this page: http://developer.gimp.org/gimp-todo.html So, if you have plans, suggestions, want to take a task from the TODO or whatever; now is the time to speak up. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] what's up
On 20 Dec 2001, at 12:23, Sven Neumann wrote: > a lot of you folks will go into XMas holidays soon and I thought it > might be nice to give a status report on the current development so > you have something to think about. So here's a short summary made up > from the ChangeLog entries since 1.3.1 was released (about four weeks > ago): [snippety-snip] > There were more changes and most probably even a few important ones > that I forgot. If you care, why don't you read the ChangeLog > yourself? Thanks. As you said, though, most of that info is in the changelog. Does GIMP 1.3. build? Is it useful for anything? What do you feel are the major things to do before the first users will start using 3.x? What do you feel are the major things to do before the first users will be right in using 3.x? ;-) In other words: how far have you come and how far do you still have to go? > If you are in middle europe between XMas and the end of the year, why > don't you visit Mitch, Simon and me at the Chaos Communication > Congress 18C3 where we hope to get some nice GIMP hacking done. Check > the website for more infos: http://www.ccc.de/congress/2001/. I'll be in Barcelona by that time. Give my regards to Paul Wouters if you see him. -- branko collin [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] what's up
Hi, a lot of you folks will go into XMas holidays soon and I thought it might be nice to give a status report on the current development so you have something to think about. So here's a short summary made up from the ChangeLog entries since 1.3.1 was released (about four weeks ago): Bex did a lot of message proofreading. Daniel optimized and cleaned up the paint-funcs system. He also fixed some problems with our Makefiles. Guillermo helped finishing the task of switching all dialog buttons over to the button ordering for GTK+-2.0. Kelly did something to the undo and pixel-region systems that will hopefully just work since anyone else is afraid to touch this code. Mitch started a massive cleanup of the tools and display subsytems. The whole image <-> display coordinates calculation does happen in the display layer now and tools don't need to care. Mitch also exposed a lot of hidden tool options in the tool options dialogs and gave them a nicer look and feel. Mitch did some menu reorganization. This needs more thought and work. Mitch reenabled brush pipes which used to be broken in the 1.3 tree. Mitch did this and Mitch did that ... I have started a rewrite of the gimprc code and it's already pretty mature but still unused. The idea of the new system is to have an interface for object serialization and deserialization that can easily be implemented by any object. The easiest way is to define everything that needs to be de/serialized as object properties and use the default implementation from GimpConfig. The file format written and parsed is still sexpressions (the thing with lots of brackets) because I think it is a well-suited format for our config files and Glib has a nice parser for it (GScanner). Some stuff needs still to be done, but I hope to be able to remove gimprc.[ch] from the app directory soon. I have started to change our internally used enums so they use a GIMP namespace just as their counterparts in the libgimp API do. This involved touching lots of files, but the actual changes were minimal. Other contributors: David Neary, David Odin, Roger Leigh, Ville Pätsi. There were more changes and most probably even a few important ones that I forgot. If you care, why don't you read the ChangeLog yourself? It looks as if the GTK+ folks are preparing the 1.3.12 release and we will try to get GIMP 1.3.2 out shortly after. If you are in middle europe between XMas and the end of the year, why don't you visit Mitch, Simon and me at the Chaos Communication Congress 18C3 where we hope to get some nice GIMP hacking done. Check the website for more infos: http://www.ccc.de/congress/2001/. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
