Rails - Jul 2006 - MasterView rails-optimize (x)html friendly template engine - Release 0.2.4

MasterView is a rails-optimized (x)html friendly template engine plugin that
provides another option to the existing rails view templates (rhtml and
rxml). The main idea is to provide a template engine that would provide all
the power of layouts, partials, and rails helpers but still be
editable/styleable in a WYSIWYG editor. It was also a major goal that the
syntax of these attribute directives be very similar to rails helpers so
that one could intuitively start using MasterView with little learning curve
other than knowing rails. MasterView was inspired by Amrita, Kwartz,
Tapestry, Zope/PHP TAL, Liquid, and Web Objects but designed with a fresh
approach and specifically targetted for rails users.


Release Notes

Release 0.2.4

Fixed apache2 scgi problem where masterview was not being loaded at startup.
Added Interactive template console to admin pages for testing/learning how
masterview directives work.

Release 0.2.3

Changed default development settings for enable_admin_pages and
enable_view_rhtml = true (false in production) to make it easy
for new users to get up and running. Added check_box, radio_button,
select, collection_select directives. Refactor attr_value parsing
to be more robust taking into account nested objects. Internal rework
of directive handling to support alternate namespaces for directives.
Std app directives dir at rails app/masterview/directives will be
automatically added to MasterView load path if exists.

Release 0.2.2

Fixes problem when rails encounters exception in either compiling or
involving RuntimeError in the generated rhtml. The rails TemplateError
class looks at the file system for the template contents. So when
generate_rhtml is false (no file is generated) rails was not able to
find source and was not outputting an error page. Rails TemplateError
class was extended to look at MasterView store first and then fallback
to file system.


More details, screenshots, and video at http://masterview.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://wrath.rubyonrails.org/pipermail/rails/attachments/20060726/a6539182/attachment.html

I inadvertantly did a gem update or something which installed 0.2.4.
Now, I can''t get the Admin console to work. WEBrick shows 0.2.4 for
the plugin.

The error I get when I go to http://localhost:3000/myapp/masterview is:
Routing Error
Recognition failed for "/masterview"

Can anyone help?

Is there a way to backout to the previous release? Will just
uninstalling the gem work?

Thanks

Ed

On 7/26/06, Jeff Barczewski <jeff.barczewski@gmail.com>
wrote:
> MasterView is a rails-optimized (x)html friendly template engine plugin
that
> provides another option to the existing rails view templates (rhtml and
> rxml). The main idea is to provide a template engine that would provide all
> the power of layouts, partials, and rails helpers but still be
> editable/styleablei in a WYSIWYG editor. It was also a major goal that the
> syntax of these attribute directives be very similar to rails helpers so
> that one could intuitively start using MasterView with little learning
curve
> other than knowing rails. MasterView was inspired by Amrita, Kwartz,
> Tapestry, Zope/PHP TAL, Liquid, and Web Objects but designed with a fresh
> approach and specifically targetted for rails users.
>
>
>  Release Notes
>
>  Release 0.2.4
>
>  Fixed apache2 scgi problem where masterview was not being loaded at
> startup.
>  Added Interactive template console to admin pages for testing/learning how
> masterview directives work.
>
>  Release 0.2.3
>
>  Changed default development settings for enable_admin_pages and
>  enable_view_rhtml = true (false in production) to make it easy
>  for new users to get up and running. Added check_box, radio_button,
>  select, collection_select directives. Refactor attr_value parsing
>  to be more robust taking into account nested objects. Internal rework
>  of directive handling to support alternate namespaces for directives.
>  Std app directives dir at rails app/masterview/directives will be
>  automatically added to MasterView load path if exists.
>
>  Release 0.2.2
>
>  Fixes problem when rails encounters exception in either compiling or
>  involving RuntimeError in the generated rhtml. The rails TemplateError
>  class looks at the file system for the template contents. So when
>  generate_rhtml is false (no file is generated) rails was not able to
>  find source and was not outputting an error page. Rails TemplateError
>  class was extended to look at MasterView store first and then fallback
>  to file system.
>
>
>  More details, screenshots, and video at http://masterview.org/
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
>
>

-- 
Ed Howland
http://greenprogrammer.blogspot.com

Are you sure that you didn''t mean to go to
http://localhost:3000/masterview
rather than
http://localhost:3000/myapp/masterview ??

The admin console is normally at http://localhost:3000/masterview

The other obvious thing to check is whether your
config/masterview/setting.rb or
config/masterview/environments/development.rb has enable_admin_pages
set to true.

However if that is not the obvious solution then, the answer to your
question is yes, that you can uninstall the latest gem if necessary.
It is also possible to reference a specific gem by version in the
require (using require_gem) however unininstalling the latest gem is
easiest.

I will be glad to work with you further if you find that indeed this
is bug and not simply a URL typo.

PS. Rather than take up the rails mailing list bandwidth, we can
discuss this further on the masterview-users list (and everything will
be archived for future reference).

Blessings,

Jeff






On 8/9/06, Ed Howland <ed.howland@gmail.com>
wrote:
> I inadvertantly did a gem update or something which installed 0.2.4.
> Now, I can''t get the Admin console to work. WEBrick shows 0.2.4
for
> the plugin.
>
> The error I get when I go to http://localhost:3000/myapp/masterview is:
> Routing Error
> Recognition failed for "/masterview"
>
> Can anyone help?
>
> Is there a way to backout to the previous release? Will just
> uninstalling the gem work?
>
> Thanks
>
> Ed
>
> On 7/26/06, Jeff Barczewski <jeff.barczewski@gmail.com> wrote:
> > MasterView is a rails-optimized (x)html friendly template engine
plugin that
> > provides another option to the existing rails view templates (rhtml
and
> > rxml). The main idea is to provide a template engine that would
provide all
> > the power of layouts, partials, and rails helpers but still be
> > editable/styleablei in a WYSIWYG editor. It was also a major goal that
the
> > syntax of these attribute directives be very similar to rails helpers
so
> > that one could intuitively start using MasterView with little learning
curve
> > other than knowing rails. MasterView was inspired by Amrita, Kwartz,
> > Tapestry, Zope/PHP TAL, Liquid, and Web Objects but designed with a
fresh
> > approach and specifically targetted for rails users.
> >
> >
> >  Release Notes
> >
> >  Release 0.2.4
> >
> >  Fixed apache2 scgi problem where masterview was not being loaded at
> > startup.
> >  Added Interactive template console to admin pages for
testing/learning how
> > masterview directives work.
> >
> >  Release 0.2.3
> >
> >  Changed default development settings for enable_admin_pages and
> >  enable_view_rhtml = true (false in production) to make it easy
> >  for new users to get up and running. Added check_box, radio_button,
> >  select, collection_select directives. Refactor attr_value parsing
> >  to be more robust taking into account nested objects. Internal rework
> >  of directive handling to support alternate namespaces for directives.
> >  Std app directives dir at rails app/masterview/directives will be
> >  automatically added to MasterView load path if exists.
> >
> >  Release 0.2.2
> >
> >  Fixes problem when rails encounters exception in either compiling or
> >  involving RuntimeError in the generated rhtml. The rails
TemplateError
> >  class looks at the file system for the template contents. So when
> >  generate_rhtml is false (no file is generated) rails was not able to
> >  find source and was not outputting an error page. Rails TemplateError
> >  class was extended to look at MasterView store first and then
fallback
> >  to file system.
> >
> >
> >  More details, screenshots, and video at http://masterview.org/
> > _______________________________________________
> > Rails mailing list
> > Rails@lists.rubyonrails.org
> > http://lists.rubyonrails.org/mailman/listinfo/rails
> >
> >
> >
>
>
> --
> Ed Howland
> http://greenprogrammer.blogspot.com
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>

I had already checked that. I have a bookmark/toolbar link to it so it
shouldn''t have changed. I double checked it again.

I also double checked my environment and settings.rb and they are ok,
again no change.

Both my Masterview based projects no longer work from the Rails Admin
page. The Rake tasks work ok.

It definitely still works on another computer with the previous MV gem
version. Same code checked out from the repository.

Ed


On 8/9/06, Jeff Barczewski <jeff.barczewski at gmail.com>
wrote:
> Are you sure that you didn''t mean to go to
> http://localhost:3000/masterview
> rather than
> http://localhost:3000/myapp/masterview ??
>
> The admin console is normally at http://localhost:3000/masterview
>
> The other obvious thing to check is whether your
> config/masterview/setting.rb or
> config/masterview/environments/development.rb has enable_admin_pages
> set to true.
>
> However if that is not the obvious solution then, the answer to your
> question is yes, that you can uninstall the latest gem if necessary.
> It is also possible to reference a specific gem by version in the
> require (using require_gem) however unininstalling the latest gem is
> easiest.
>
> I will be glad to work with you further if you find that indeed this
> is bug and not simply a URL typo.
>
> PS. Rather than take up the rails mailing list bandwidth, we can
> discuss this further on the masterview-users list (and everything will
> be archived for future reference).
>
> Blessings,
>
> Jeff
>
>
>
>
>
>
> On 8/9/06, Ed Howland <ed.howland at gmail.com> wrote:
> > I inadvertantly did a gem update or something which installed 0.2.4.
> > Now, I can''t get the Admin console to work. WEBrick shows
0.2.4 for
> > the plugin.
> >
> > The error I get when I go to http://localhost:3000/myapp/masterview
is:
> > Routing Error
> > Recognition failed for "/masterview"
> >
> > Can anyone help?
> >
> > Is there a way to backout to the previous release? Will just
> > uninstalling the gem work?
> >
> > Thanks
> >
> > Ed
> >
> > On 7/26/06, Jeff Barczewski <jeff.barczewski at gmail.com>
wrote:
> > > MasterView is a rails-optimized (x)html friendly template engine
plugin that
> > > provides another option to the existing rails view templates
(rhtml and
> > > rxml). The main idea is to provide a template engine that would
provide all
> > > the power of layouts, partials, and rails helpers but still be
> > > editable/styleablei in a WYSIWYG editor. It was also a major goal
that the
> > > syntax of these attribute directives be very similar to rails
helpers so
> > > that one could intuitively start using MasterView with little
learning curve
> > > other than knowing rails. MasterView was inspired by Amrita,
Kwartz,
> > > Tapestry, Zope/PHP TAL, Liquid, and Web Objects but designed with
a fresh
> > > approach and specifically targetted for rails users.
> > >
> > >
> > >  Release Notes
> > >
> > >  Release 0.2.4
> > >
> > >  Fixed apache2 scgi problem where masterview was not being loaded
at
> > > startup.
> > >  Added Interactive template console to admin pages for
testing/learning how
> > > masterview directives work.
> > >
> > >  Release 0.2.3
> > >
> > >  Changed default development settings for enable_admin_pages and
> > >  enable_view_rhtml = true (false in production) to make it easy
> > >  for new users to get up and running. Added check_box,
radio_button,
> > >  select, collection_select directives. Refactor attr_value
parsing
> > >  to be more robust taking into account nested objects. Internal
rework
> > >  of directive handling to support alternate namespaces for
directives.
> > >  Std app directives dir at rails app/masterview/directives will
be
> > >  automatically added to MasterView load path if exists.
> > >
> > >  Release 0.2.2
> > >
> > >  Fixes problem when rails encounters exception in either
compiling or
> > >  involving RuntimeError in the generated rhtml. The rails
TemplateError
> > >  class looks at the file system for the template contents. So
when
> > >  generate_rhtml is false (no file is generated) rails was not
able to
> > >  find source and was not outputting an error page. Rails
TemplateError
> > >  class was extended to look at MasterView store first and then
fallback
> > >  to file system.
> > >
> > >
> > >  More details, screenshots, and video at http://masterview.org/
> > > _______________________________________________
> > > Rails mailing list
> > > Rails at lists.rubyonrails.org
> > > http://lists.rubyonrails.org/mailman/listinfo/rails
> > >
> > >
> > >
> >
> >
> > --
> > Ed Howland
> > http://greenprogrammer.blogspot.com
> > _______________________________________________
> > Rails mailing list
> > Rails at lists.rubyonrails.org
> > http://lists.rubyonrails.org/mailman/listinfo/rails
> >
>

-- 
Ed Howland
http://greenprogrammer.blogspot.com

Well definitely try setting the config property for that to true

config.enable_admin_pages = true

in the settings or environment file and see if that turns it on. And
double check the environment file since that would override whatever
is in settings. Maybe it is disabled in there??

Sounds like a default issue or something. Let me know if that doesn''t
fix it and send me the version number of the gem you are using and a
copy of your settings.rb and environment/development.rb and I can try
and reproduce the issue.

Thanks,

Jeff


On 8/10/06, Ed Howland <ed.howland at gmail.com>
wrote:
> I had already checked that. I have a bookmark/toolbar link to it so it
> shouldn''t have changed. I double checked it again.
>
> I also double checked my environment and settings.rb and they are ok,
> again no change.
>
> Both my Masterview based projects no longer work from the Rails Admin
> page. The Rake tasks work ok.
>
> It definitely still works on another computer with the previous MV gem
> version. Same code checked out from the repository.
>
> Ed
>
>
> On 8/9/06, Jeff Barczewski <jeff.barczewski at gmail.com> wrote:
> > Are you sure that you didn''t mean to go to
> > http://localhost:3000/masterview
> > rather than
> > http://localhost:3000/myapp/masterview ??
> >
> > The admin console is normally at http://localhost:3000/masterview
> >
> > The other obvious thing to check is whether your
> > config/masterview/setting.rb or
> > config/masterview/environments/development.rb has enable_admin_pages
> > set to true.
> >
> > However if that is not the obvious solution then, the answer to your
> > question is yes, that you can uninstall the latest gem if necessary.
> > It is also possible to reference a specific gem by version in the
> > require (using require_gem) however unininstalling the latest gem is
> > easiest.
> >
> > I will be glad to work with you further if you find that indeed this
> > is bug and not simply a URL typo.
> >
> > PS. Rather than take up the rails mailing list bandwidth, we can
> > discuss this further on the masterview-users list (and everything will
> > be archived for future reference).
> >
> > Blessings,
> >
> > Jeff
> >
> >
> >
> >
> >
> >
> > On 8/9/06, Ed Howland <ed.howland at gmail.com> wrote:
> > > I inadvertantly did a gem update or something which installed
0.2.4.
> > > Now, I can''t get the Admin console to work. WEBrick
shows 0.2.4 for
> > > the plugin.
> > >
> > > The error I get when I go to
http://localhost:3000/myapp/masterview is:
> > > Routing Error
> > > Recognition failed for "/masterview"
> > >
> > > Can anyone help?
> > >
> > > Is there a way to backout to the previous release? Will just
> > > uninstalling the gem work?
> > >
> > > Thanks
> > >
> > > Ed
> > >
> > > On 7/26/06, Jeff Barczewski <jeff.barczewski at gmail.com>
wrote:
> > > > MasterView is a rails-optimized (x)html friendly template
engine plugin that
> > > > provides another option to the existing rails view templates
(rhtml and
> > > > rxml). The main idea is to provide a template engine that
would provide all
> > > > the power of layouts, partials, and rails helpers but still
be
> > > > editable/styleablei in a WYSIWYG editor. It was also a major
goal that the
> > > > syntax of these attribute directives be very similar to
rails helpers so
> > > > that one could intuitively start using MasterView with
little learning curve
> > > > other than knowing rails. MasterView was inspired by Amrita,
Kwartz,
> > > > Tapestry, Zope/PHP TAL, Liquid, and Web Objects but designed
with a fresh
> > > > approach and specifically targetted for rails users.
> > > >
> > > >
> > > >  Release Notes
> > > >
> > > >  Release 0.2.4
> > > >
> > > >  Fixed apache2 scgi problem where masterview was not being
loaded at
> > > > startup.
> > > >  Added Interactive template console to admin pages for
testing/learning how
> > > > masterview directives work.
> > > >
> > > >  Release 0.2.3
> > > >
> > > >  Changed default development settings for enable_admin_pages
and
> > > >  enable_view_rhtml = true (false in production) to make it
easy
> > > >  for new users to get up and running. Added check_box,
radio_button,
> > > >  select, collection_select directives. Refactor attr_value
parsing
> > > >  to be more robust taking into account nested objects.
Internal rework
> > > >  of directive handling to support alternate namespaces for
directives.
> > > >  Std app directives dir at rails app/masterview/directives
will be
> > > >  automatically added to MasterView load path if exists.
> > > >
> > > >  Release 0.2.2
> > > >
> > > >  Fixes problem when rails encounters exception in either
compiling or
> > > >  involving RuntimeError in the generated rhtml. The rails
TemplateError
> > > >  class looks at the file system for the template contents.
So when
> > > >  generate_rhtml is false (no file is generated) rails was
not able to
> > > >  find source and was not outputting an error page. Rails
TemplateError
> > > >  class was extended to look at MasterView store first and
then fallback
> > > >  to file system.
> > > >
> > > >
> > > >  More details, screenshots, and video at
http://masterview.org/
> > > > _______________________________________________
> > > > Rails mailing list
> > > > Rails at lists.rubyonrails.org
> > > > http://lists.rubyonrails.org/mailman/listinfo/rails
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Ed Howland
> > > http://greenprogrammer.blogspot.com
> > > _______________________________________________
> > > Rails mailing list
> > > Rails at lists.rubyonrails.org
> > > http://lists.rubyonrails.org/mailman/listinfo/rails
> > >
> >
>
>
> --
> Ed Howland
> http://greenprogrammer.blogspot.com
> _______________________________________________
> Masterview-users mailing list
> Masterview-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/masterview-users
>