<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=685342316-07062006>Jeff - good points, I'll make another pass over
comments, doc, provide fullly commented-out sample of settings config files per
your suggestions.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=685342316-07062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=685342316-07062006>I'm stil finding and patching up places that have
rails-specific assumptions bolted down about templates being located in
app/views (there are several scattered around the code that I've got fixed in my
local working copy, just found yet another in tasks/masterview.rake last night
that I'm still patching)</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=685342316-07062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=685342316-07062006>Process note: committing to trunk != publishing
release. Believe we should *not* do another public release build
until useful set of new functionality is completed, committed to trunk
for development team use so we've both looked it over, and confirmed
stable after we've run with the new code base for a
while.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=685342316-07062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=685342316-07062006>[unless there's some bug fix that you need to get out
to users for some reason]</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=685342316-07062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=685342316-07062006></SPAN></FONT><FONT face=Arial color=#0000ff
size=2><SPAN class=685342316-07062006>~ Deb</SPAN></FONT></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> masterview-devel-bounces@rubyforge.org
[mailto:masterview-devel-bounces@rubyforge.org] <B>On Behalf Of </B>Jeff
Barczewski<BR><B>Sent:</B> Wednesday, June 07, 2006 4:42 AM<BR><B>To:</B>
masterview-devel@rubyforge.org<BR><B>Subject:</B> Re: [Masterview-devel] New
init/config stuff ready to be submitted<BR></FONT><BR></DIV>
<DIV></DIV>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></BODY></HTML>