[E-devel] eet and updating ChangeLog: the moap tool
Hey, cedric just fixed a bug in eet, and he forgot to update the ChangeLog. I do not criticise, it can happen to everyone, including me (and it did happen to me). But, as we plan to do more releases, the ChangeLog will have to always be updated when such fixes are done, and i think that we should take the habit of updating the ChangeLog files with some tools that could help us. The gstreamer team uses a tool named 'moap' [1] (written by the previous release manager of gstreamer, btw). I use it for epdf, edvi, eps and evil, and it is quite nice regarding ChangeLog updates. To use it, go to the toplevel directory of the project, then: 1) run: moap cl prep this step modify the ChangeLog according to the modified files 2) Update the ChangeLog to add comments 3) run moap cl ci to commit the changes Note that i don't want that everyone use that tool and update always the ChangeLog files right now. I just want to mention one of the features of that tool, which can help us a lot when we will have to update the ChangeLog files in the released EFL. Finally, last remark: unfortunately, the order of the changes in the ChangeLog of eet is the reverse of the one that moap uses (currently, last cahnges are at the bottom, while moap put them at the top of the ChangeLog). Maybe we can modify the current ChangeLog and use maop for the updates Vincent [1] http://thomas.apestaart.org/moap/trac -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] eet and updating ChangeLog: the moap tool
On Fri, Jan 30, 2009 at 12:41 PM, Vincent Torri vto...@univ-evry.fr wrote: Hey, cedric just fixed a bug in eet, and he forgot to update the ChangeLog. I do not criticise, it can happen to everyone, including me (and it did happen to me). But, as we plan to do more releases, the ChangeLog will have to always be updated when such fixes are done, and i think that we should take the habit of updating the ChangeLog files with some tools that could help us. The gstreamer team uses a tool named 'moap' [1] (written by the previous release manager of gstreamer, btw). I use it for epdf, edvi, eps and evil, and it is quite nice regarding ChangeLog updates. To use it, go to the toplevel directory of the project, then: 1) run: moap cl prep this step modify the ChangeLog according to the modified files 2) Update the ChangeLog to add comments 3) run moap cl ci to commit the changes Note that i don't want that everyone use that tool and update always the ChangeLog files right now. I just want to mention one of the features of that tool, which can help us a lot when we will have to update the ChangeLog files in the released EFL. Finally, last remark: unfortunately, the order of the changes in the ChangeLog of eet is the reverse of the one that moap uses (currently, last cahnges are at the bottom, while moap put them at the top of the ChangeLog). Maybe we can modify the current ChangeLog and use maop for the updates I really dislike ChangeLog files, they predate any source control version. Now CVS/SVN/Git/Whatever nicely replaces that. So generating it automatically is the way to go. AFAIK changelogs are supposed to be the reverse order, like maop does, so changing to it is becoming more standard. -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] eet and updating ChangeLog: the moap tool
On Fri, 30 Jan 2009, Gustavo Sverzut Barbieri wrote: I really dislike ChangeLog files, they predate any source control version. Now CVS/SVN/Git/Whatever nicely replaces that. So generating it automatically is the way to go. of course I disagree. Mainly because of an experience i had with autotools: for the EFL, I had to check if I didn't use macros that were too recent, or on the contrary if they were old enough to replace them by newer ones. If I had to look at all the svn logs, i doubt that i would have finished that work today (there are a lot of macro / features in autoconf, automake and libtool). On the contrary, I just opened the ChangeLog files, did a search in it, and it was quite fast for me to find the informations. That's why I think that, if it helped me, a changeLog can help other people. Note that I agree with raster's position here: noting in a ChangeLog only the most important changes. For example, even if I had committed in eet repo (only formatting and autotools stuff, iirc), i didn't modified the ChangeLog (Well, actually, i added one entry, to mention that the compilation can be done with Visual Studio). So the ChangeLog does not grows too much and has only important cahnges in it. That's my opinion as a user of a tool. And i think that there are a lot of users who don't know how to use cvs, svn or git and are quite happy to have some ChangeLog files. Vincent -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] eflpp + ewl + ecmd
Hello, I'm sorry for the delay, but I wanted to reach my 0.1 milestone. Here is the link for the source of my ECommander application: http://smrt.is-a-geek.org/ecmd/ (screenshots + source) ECommander (ecmd) is a 2 pane file manager similar to all other commanders (total/nortan/midnight/gnome). It has the basic operations implemented (CAUTION: it is possible that some files can be lost/deleted!!!) and more is to come. See the README for info how to build and use it. (Sorry that there is no autotools config, I could grasp it:(). For a successful build you need to apply my c++ patch to efreet. The application is written in c++ and uses ewl as the widget toolkit. I've written a wrapper for ewl, to make my life easier.:) The wrapper is 30-50% complete. I've wrapped only widgets I've used. I hope the interested in ewl will give me some constructive crituque, so I can improve it. At the moment there are some problems with the wrapper: 1. The widget class has one ewl::function (boost,tr1,c++0x function class) member per possible callback, no matter if the callback is used. 2. You can have only one callback functions attached to a given type of callbacks for the widget 3. The mvc wrapping is a bit messed up. 4. some more I can't remember :) Any suggestions how to fix these issues are welcome :) Best regards, Teodor Petrov On Wed, 31 Dec 2008 09:34:09 +0100 Andreas Volz li...@brachttal.net wrote: Am Sun, 21 Dec 2008 18:11:15 +0200 schrieb fusca...@gmail.com: I'm using c++ and ewl to write a filemanager app and I think I'll use eet for the configuration files. I've also done an ewl c++ wrapper (not complete at all). And I can contribute the code to eflpp when it is more complete. I just started to wrap ETK as you see with my last commit. In parallel I liked to start with EWL. But if you yet work on it we may share our work. But the EWL wrapper you do has to fit the eflpp design. How far did you proceed? Could you show something? -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
