So, I have done a couple of things here, mostly just cleanup, and repairing a couple of issues. First on the top of the list, which is the most important. I have migrated over stuff that I have used in the IDE to the corelib for VisualRuby, that was meant to be in the corelib from the get go. What that means, is that now, from revision 8c3d394 onwards, VisualRuby will require the gem vr-corelib to be installed, before you it will properly operate.
The good thing is, I have the gem published now, so that you can actually install it by just doing gem install vr-corelib. The next thing I have done, is fixed an error in a previous commit that deals with the template for GUI Applications, when a new one was created, the project file wasn't correctly setting the proper execution line in it. This however has been fixed.
I currently foresee that I have 3 features to setup in VisualRuby, before I launch the first public gem that can be installed for the IDE. The first being finishing up the gem requirements in the project templates, so that for templates such as Rails, it will determine if you have the proper gems installed for it, and if not, tell you that they need to be installed, and there by install them for you. This will be the first half of the template creation system that needs finishing, the second half being actual implementation of using commands to create the project templates, for ones that do not have static templates.
This ties in to the fact, that I don't want to update VisualRuby's core distribution everytime Rails updates some piece of their code for templates. So, in fact, when you go into a new project, and eventually, a new file, it will use template commands to generate the project / template file for what you want.
This brings me to the second feature to implement, which is the New File dialog. Currently, when you click on a New File, you just get a blank document. I plan to expand that into a dialog, which will check what type of project your working with, and present the correct options for the new file, from a blank file, to a template file that is required for something to occur, such as with GUI Applications, a New dialog, a New Window, or a custom widget, with Rails apps, a new Model, a new View, or a new Controller.
The final feature that I will need to implement, before I release my first version of the new IDE, is the Project Properties dialog, which will allow you to actually setup Properties for the Project, such as Name of the Project, executable, if required, the version, authors, websites, and such. This will eventually lead to the final part of this two part feature, which is the creation of the Gem Specification, and actual building of a gem, that will be posted to RubyGems, and installed locally, should you want to test it out.
At this point, I will feel comfortable enough in releasing the current version of the IDE, with other features being put temporarily on back burner, for the next version, such as Git/SVN/Mercurial integration and possible restructure of Project code, an Internal GUI Designer, and even the possibility to bind code to a single executable, in similar method to ocra, or rubyscript2exe. So, more things are on the horizon for VisualRuby, and it will hopefully be something worth while. As always, comments, suggestions, help, what have you are welcome.