I like the plugins, destroy, and help for generators. I also like the formatting on the commands, I should have spent a little more time on my toolbox. I found the best way to find the rails directory is using %p, too. This does not always work well for me since my komodo projects some times cover more then one rails application.
Do you plan on adding anything else to this toolbox?
I created my toolbox as I developed rails applications. I have added migration snippets and capistrano commands to my package. I am working on a set of rdoc and rhtml snippets. I was wondering if you were going to add more things because I did not want to duplicate each others efforts.
I like to start my servers from the command line but a tab for managing servers would be nice. I am learning how to create extensions but it going slow. Other then that I really like using komodo for Rails.
When you create a project based on the "Ruby on Rails" project template,
you get a set of macros and commands for each project. I picked a few
as a proof of concept -- creating and deleting the database based on
the contents of the config/database.yml file (the JS code in the template
does pseudo-yaml-parsing, but I'd rather replace it with a real component),
running a few of the generators and migrators, and launchers for running
and debugging.
My attempt was to provide a framework that makes it easy to write new
commands, add generated files to the library, etc. The advantage of
doing this through macros is you can parse the output of the commands
and act on them.
I am working on the same type of thing. http://support.activestate.com/forum-topic/ruby-on-rails-toolbox
I like the plugins, destroy, and help for generators. I also like the formatting on the commands, I should have spent a little more time on my toolbox. I found the best way to find the rails directory is using %p, too. This does not always work well for me since my komodo projects some times cover more then one rails application.
Do you plan on adding anything else to this toolbox?
Yes I was thinking of improving the macros since now we have more time.
What do you have in mind?
--
Do It Right or Don't Do It at All
I created my toolbox as I developed rails applications. I have added migration snippets and capistrano commands to my package. I am working on a set of rdoc and rhtml snippets. I was wondering if you were going to add more things because I did not want to duplicate each others efforts.
I like to start my servers from the command line but a tab for managing servers would be nice. I am learning how to create extensions but it going slow. Other then that I really like using komodo for Rails.
Stephen Becker IV
When you create a project based on the "Ruby on Rails" project template,
you get a set of macros and commands for each project. I picked a few
as a proof of concept -- creating and deleting the database based on
the contents of the config/database.yml file (the JS code in the template
does pseudo-yaml-parsing, but I'd rather replace it with a real component),
running a few of the generators and migrators, and launchers for running
and debugging.
My attempt was to provide a framework that makes it easy to write new
commands, add generated files to the library, etc. The advantage of
doing this through macros is you can parse the output of the commands
and act on them.
Interested in your feedback...