At the moment I'm sitting in a train going home to after a short break in the south.  The train ride is 5 hours and the lack of internet gives me a good opportunity to concentrate a little on getting stuff done on JDevTools.

For those who don't know, JDevTools is going to be an awesome set of tools to help developers create components easier. It's also my summer of code project, and right now it's not too much besides a hello world, a good base and a lot of ideas. What it will be though, is a way to automize most of the tasks connected with creating a component for example helping to create the mcv file structure and boilerplate code.

I envision the normal user experience being a four step process going something like this:

- Start screen, where the user can select between a list of different scripts or decide to create their own
- Edit screen, where the selected script is shown so the user can make modifications to it and press run
- Input screen which contains a form in case the script needs specific inputs (name of component or the like)
- Status screen, where the script lists what has been done, or any errors

It's my intent to provide premade scripts that take care of some general tasks, so most developers wont have to start learning how to script something. At the same time I want to make scripting approachable and intuitive to use for newcomers. This is why I want to show the edit screen. It gives users an entranceway to making their own scripts by letting them modify the scripts they are already using.

Not that anybody has to. But it can't hurt to have the opportunity.