Deb,<br><br>I took a look through the changes. It is looking real good. A couple things I think we should do before the release:<br><br>* create sample configuration file with the available options commented out, so they can simply copy this file and uncomment anything they want to change. No mispellings and hunting for options, they would all be there. Put this in examples/config/masterview/settings.rb??
<br><br>* update README file mentioning how to customize, recommending copying the example config file to ___ location (making sure to spell out exactly what filename path). Mention how to do environment specific customization, simply by specifiying file ____, etc.
<br><br>* update init.rb to mention where to go to configure options (what config files) and where to get sample, similar to README. Existing users will be going there so they will see this and many plugin users have been accustomed to looking in there, so just want to make sure they know where to go to customize.
<br><br>* slight rewording of inializer.rb, from reading the comments it was a little unclear. I suggest we just cut to the chase and mention customize by editing file config/masterview/settings.rb and for environment (development,test,production) settings edit file config/masterview/environments/{environment}.rb (ie.
development.rb, test.rb, production.rb)<br><br>* update masterview_version <br><br>* update CHANGELOG if not already done<br>
<br>* test as a gem<br><br>I will send you a separate email with my current release steps, so if you would like to do the release you are welcome to do so.<br><br>Jeff<br><br><br><br><br><br><br><br><br><br><div><span class="gmail_quote">
On 6/6/06, <b class="gmail_sendername">Deb Lewis</b> <<a href="mailto:djlewis@acm.org">djlewis@acm.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Jeff - I'm pretty happy with the new init/config stuff now - did one more<br>polishing pass over things to today to tinker a bit more with names and<br>rework a few things that still felt awkward.<br><br>doc/configuration.html has a complete (brief) reference for all the
<br>supported config settings and a bit of intro material on how to customize<br>the config.<br><br>Also wrote some test cases to exercise basic default settings for rails and<br>non-rails usage and test loading of settings.rb
and env settings from an app<br>config dir. The test fixtures for config settings file provide example of<br>usage [need to add to the config guide doc]<br><br>Look this over one more time and let me know if you want any changes in
<br>naming or approach.<br><br>Whenever you're ready for the cutover, I'll submit the other changes that<br>need to go in to turn this on. New versions of init.rb, masterview.rb, and<br>rails_init.rb; plus a few minor changes that rippled into other files. This
<br>update will include new generated comment facility with template_path var<br>substitution.<br><br>Client impact: any existing settings customization will need to be moved out<br>of plugin init.rb into config settings files, with notation changes to
<br>convert from module var refs to setting config values. (pretty<br>straightforward).<br><br>I'll add something to changes notes for the next release when this goes in.<br><br>~ Deb<br><br><br>_______________________________________________
<br>Masterview-devel mailing list<br><a href="mailto:Masterview-devel@rubyforge.org">Masterview-devel@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/masterview-devel">http://rubyforge.org/mailman/listinfo/masterview-devel
</a><br></blockquote></div><br>