by James Britt / Neurogami http://www.neurogami.comjames@neurogami.com
Rhesus is a tool for copying over pre-built templates with optional embedded string interpolation.
It started as a way to make jump-starting Jimpanzee apps easier, but the user-defined templates need not have anything to do with any special library or programming language.
Basically, you create a skeleton of the files you want as templates in some suitably-named subdirectory of ~/.rhesus.
If any of those files contain Erb variables, they will be used to prompt the user for real values when that template is used to generate files and directories.
The same value gets applied in all cases where that variable is used. Some magic is used to handle proper casing for class and file names.
The results are copied out to a directory relative to where you invoked the 'rhesus' script.
Generates files for you to jump-start projects that have common code.
Makes assorted assumptions and needs more testing with a variety of template sources
Driven by the Works for James criteria. Feedback is welcome.
Make sure you have http://gems.neurogami.com added as a gem server source.
$ sudo gem sources -a http://gems.neurogami.com
Then install the gem:
$ sudo gem install rhesus
Or, pass the gem source as part of the command:
$ sudo gem i rhesus ––source http://gems.neurogami.com
Then run the rhesus setup option:
$ rhesus --setup
This should create a .rhesus folder in your home directory. This is where you store you templates, each in its own containing folder.
To use templates, cd to an existing project, or wherever you want to splat out the generated code. For example, start a new jimpanzee application:
$ jimpanzee cool-app $ cd cool-app
Run rhesus list to see the available templates
$ rhesus list
NOTE: This behavior might vanish, since in actual use it is pretty useless. See below.
Run rhesus gen to generate code from a template. You may optionally pass the name of a template, but if you leave that out you'll get a list to pick from.
$ rhesus gen1: jimpanzee.about2: jimpanzee.basic3: jimpanzee.midiEnter the number of the template to use:
If you pass a complete template name then that is automatically used:
$ rhesus gen jimpanzee.midi
Run rhesus stuff to have rhesus show a list of templates that match on stuff.
$ rhesus midi1: jimpanzee.midiEnter the number of the template to use:
The code assumes you have a directory .rhesus in your home directory (+~/.rhesus+)
That directory holds the template sets.
Each set is just a top-level directory containing the skeleton files and directories to use:
james@james06:~/.rhesus$ tree.|-- jimpanzee.about| `-- src| `-- about| |-- about_controller.rb| |-- about_model.rb| |-- about_ui.rb| `-- about_view.rb|-- jimpanzee.basic| `-- src| `-- klassname| |-- klassname_controller.rb| |-- klassname_model.rb| |-- klassname_ui.rb| `-- klassname_view.rb`-- jimpanzee.midi |-- com | `-- neurogami | `-- ResourceLoader.java |-- lib | |-- java | | |-- libWiiuseJ.so | | |-- libwiiuse.so | | |-- miglayout-3.6.jar | | `-- wiiusej.jar | `-- ruby | |-- README.txt | |-- wii_api_manager.rb | |-- wiimotable.rb | `-- wiimote_event_listener.rb `-- src |-- mainclass | |-- mainclass_controller.rb | |-- mainclass_model.rb | |-- mainclass_ui.rb | `-- mainclass_view.rb |-- midi.rb |-- resolver.rb |-- resource_loader.rb `-- spinner_dialog.rb
What you call these directories is up to you; there is no code in place to do anything clever with the names (such as grouping projects and templates). But something like that may be added if managing growing numbers of templates becomes an issue. So, the suggested format is project_type.template_name
Rhesus starts with some assumptions about what files might be using Erb. You can add your own file patterns (sort of) by placing a haz_vars.txt file in your .rhesus folder.
By default, the file-end patterns are: rb txt rhtml ini yml yaml Rakefile gemspec.
A recent addition, and still evolving, is the use of a .options.yaml file in the root of a template folder.
This is because you may have a large set files that do not need any template processing.
Worse, some files may be themselves Erb templates (or contain Erb markup) that should be copied over as-is, but would otherwise get preprocessed by rhesus.
a .options.yaml file can contain a hash of file patterns, like this
noparse: - /gems/gems/rack - .git/ ignore: - .git/
This tells rhesus that any file whose template path matches on any of the items listed in noparse should not be parsed for template variables, and simply copied over as-is.
The array under ignore means to ignore any files or directories that match on that substring. No parsing, no copying.
When you select a template set, Rhesus scans these files for Erb (or some alternate) variables. It then prompts you to provide values. If you use any of these variable names in file or path names then Rhesus will apply those values to the names and paths when applying the template.
You need to be sure, then, to only use the same variable name across files when you want them to all have the same value.
That is, if foo.rb and baz.ini both use <%= my_var %>, then the resulting text will have the same value used in both.
If a file in a template set is not among the file types that may have Erb (e.g., jar, dll, gif) then it will be copied over as-is.
For example:
jimpanze.basic has this structure:
jimpanzee.basic| `-- src| `-- klassname| |-- klassname_controller.rb| |-- klassname_model.rb| |-- klassname_ui.rb| `-- klassname_view.rb
The file klassname_controller.rb has Erb to define the name of the class:
class <%= klassname %>Controller < ApplicationController set_model '<%= klassname %>Model' set_view '<%= klassname %>View'
When jimpanze.basic is selected for code generation, Rhesus scans the template files and picks out variable names used inside Erb brackets (i.e., <%= this_is_the_variable %> )
When the list of all such variables in all the files is assembled, rhesus prompts for a value for each one.
Using template jimpanzee.basicValue for klassname:
The value entered will than be used for all instances of klassname in Erb. It will also be used to alter any file or folder names that contain that as well.
Assume you gave the value of Goober
Since the template directory has src/klassname, and several files with that string, the generated code will look like this
| `-- src| `-- goober| |-- goober_controller.rb| |-- goober_model.rb| |-- goober_ui.rb| `-- goober_view.rb
Inside the files, the code will also have this value:
class GooberController < ApplicationController set_model 'GooberModel' set_view 'GooberView'
Some assumptions are made in writing out the code. Variables inside files are replaces as-is.
That is, if you want Goober in your text, use Goober. If instead you want goober, use that.
However, for file and folder names, variable values are snake-cased. That's why you end up with src/goober/goober_controller.rb.
A value of FooBar, for example, would create src/foo_bar/foo_bar.rb. But the string FooBar would be used inside the generated files.
Some of the code for auto-mangling file and path names is changing. Initially the code was specific to Ruby apps, but it's really very handy for all sorts of things, such as Haskell projects.
But these other things have different conventions; code to apply appropriate conventions is being added.
Another recent evolving features is the use of "rhamaze" templating.
Suppose you have a Ramaze project template set, with some .xhtml files that contain Erb markup. You do not want Rhesus to pre-process this as Erb, but you *do* want to have some interpolated variables.
So, you need to add a leading line that contains the string RHEMAZAR and do your rhesus variables using this syntax:
<|= my_variable |>
That leading line will be skipped when processing the file.
You can add templates by just tossing them into the appropriate directory structure under ~/.rhesus.
You can also install templates from a git repository:
$ rhesus --install git@gitlandia.org:Neurogami/super.bad.template.git
or
$ rhesus --install git://gitistan.org/Neurogami/super.bader.template.git
Rhesus will do a straight-up git clone to fetch the files. If the repo name begins with rhesus. (e.g. git://gitistan.org/Neurogami/rhesus.ramaze.basic) then that leading string gets stripped from the destination folder (ramaze.basic).
This is so that repos names can have an identifiable name prefix without having the resulting template folder cluttered with that prefix.
Ruby, and a sense of adventure.
$ sudo gem i rhesus ––source http://gems.neurogami.com
(The MIT License)
Copyright (c) 2009 James Britt / Neurogami
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Feed your head.