Weekend Coding
So lately I’ve been doing little to no work on gIDE, which while it is not unusual it is a little disappointing as I had hoped to have made at least one release by now. With that in mind and the fact that I don’t have anything planned for this weekend I sat down and listed all of the features that I needed and wanted to have before I made an initial release. The plan is to sit down this weekend and knock as many of these things out before the weekend is over and make a release, will I hold true to this? I do not know, my track record of promises similar to this (which you should be able to find in the archives of this blog) is not stellar. Heres hoping I follow through on it this time. Now onto the important part of this post the lists:
Needs
- Find/Replace
- File Rename
- File Move
- Build System
Wants
- Move from vte to vtemm
- Document Split view
Of the things that is on these lists the one that I am not really sure about is the moving from vte to vtem, while vtemm would fit in better with the rest of the application it is currently not packaged with any of the major distros. This leads to the problem which is more important the design of the application or the ability of people to run the software? I’m sure I will have some comments about this in the next couple of days.
All going well I should hopefully make a blog post after I finish each feature, or for a couple of less screenshot worthy features I might just save them until a screenshot worthy one is finished before making a posting.
Latest libvtemm (it’s 0.20) is already on svn.gnome.org. Earlier versions wrapping earlier versions of vte will be put soon there also, as I only know where (branches/tags).
Being not packaged in any major distribution is a stopper – it’s true. There are no projects which have libvtemm as a dependency (I won’t be mad if, for example, Nemiver switch to libvtemm. 
). On the other side – your project also doesn’t seem to be packaged (well, I didn’t checked it thoroughly, only Fedora, Ubuntu and Debian distros). Probably when your gIDE reach quite mature status, libvtemm will be already packaged. I suppose I’ll have to see to it. Debian packaging seems complicated at first glance.
It’s good to see that libvtemm looks like it is gaining momentum, that does help with my decision. It’s true that gIDE is not packaged for any ditro yet – this is largely because I’m not at the stage of feeling that it is ready for a release, when I do make a release I should be providing at least a rpm and a debian package. As you might be able to tell I haven’t done much of what I posted up there, I largely blame this on the Firefly boxset I picked up that weekend it seemed to sap all my productivity out of me