From bernardino.lopez at gmail.com Mon Feb 5 11:26:06 2007 From: bernardino.lopez at gmail.com (Dino Lopez) Date: Mon, 5 Feb 2007 10:26:06 -0600 Subject: [Masterview-users] Multiple Skin / Theme / Layout repository for Masterview on Rail Applications.... Message-ID: <4209097b0702050826i33f7012n80fec7d23ba1a653@mail.gmail.com> I saw a Master_View screencast at: http://podcast.sdruby.com/ , and I think is very very cool. That bring me to the main site: http://masterview.org/ the Flash screencast looks great, I can't wait to try it on my computer. Maybe I'm asking something silly, I'm very new on Master_View, but I wonder if there is some kind of Theme / Skin Gallery something like: http://www.oswd.org/ http://www.csszengarden.com/ How cool would it be to select the theme that U like to use in your site or your page ???, If a repository is created it can be by name then use it as the default theme.... For starters the Themes can be just change the Skin color... later extra imagery can be added just like zengarden. The question would be how to manage the download and use of the theme repository. Best Regards Dino. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070205/c70d639b/attachment.html From jeff.barczewski at gmail.com Mon Feb 5 12:06:42 2007 From: jeff.barczewski at gmail.com (Jeff Barczewski) Date: Mon, 5 Feb 2007 11:06:42 -0600 Subject: [Masterview-users] Multiple Skin / Theme / Layout repository for Masterview on Rail Applications.... In-Reply-To: <4209097b0702050826i33f7012n80fec7d23ba1a653@mail.gmail.com> References: <4209097b0702050826i33f7012n80fec7d23ba1a653@mail.gmail.com> Message-ID: <19cda190702050906na1b9595kd98be75098c2aef3@mail.gmail.com> On 2/5/07, Dino Lopez wrote: > > I saw a Master_View screencast at: http://podcast.sdruby.com/ , and I > think is very very cool. > > That bring me to the main site: http://masterview.org/ the Flash > screencast looks great, I can't wait to try it on my computer. > > Maybe I'm asking something silly, I'm very new on Master_View, but I > wonder if there is some kind of Theme / Skin Gallery something like: > > http://www.oswd.org/ > http://www.csszengarden.com/ > > How cool would it be to select the theme that U like to use in your site > or your page ???, If a repository is created it can be by name then use it > as the default theme.... For starters the Themes can be just change the Skin > color... later extra imagery can be added just like zengarden. The question > would be how to manage the download and use of the theme repository. > > Best Regards Dino. > > _______________________________________________ > Masterview-users mailing list > Masterview-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/masterview-users > > Thanks for writing Dino! I agree what you are suggesting would be wonderful! It would be great to have a library of themes similar to the oswd and csszengarden. I have used both of these as inspiration for my own sites. For instance you can take the oswd design and simply sprinkle MasterView tags in and you are done. However it would be even better if it was easier than that. We'll brainstorm about this and see what we can come up with. Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070205/978542b7/attachment.html From Lea.Viljanen at iki.fi Fri Feb 16 12:15:11 2007 From: Lea.Viljanen at iki.fi (Lea Viljanen) Date: Fri, 16 Feb 2007 19:15:11 +0200 Subject: [Masterview-users] FYI: Masterview admin pages visibility, webrick and radrails Message-ID: <45D5E69F.7060101@iki.fi> I had weird problem where I could not see the masterview admin page at all. Web server kept on saying: Initializing MasterView configuration (2007-02-16 18:59) Program name = -e => Rails application started on http://0.0.0.0:3001 => Ctrl-C to shutdown server; call with --help for options [2007-02-16 18:59:42] INFO WEBrick 1.3.1 [2007-02-16 18:59:42] INFO ruby 1.8.5 (2006-12-25) [i686-linux] [2007-02-16 18:59:42] INFO WEBrick::HTTPServer#start: pid=27462 port=3001 Now, everybody FAMILIAR with Masterview would instantly know that Webrick is not actually running the Masterview code at all. However, installing and running Masterview for the first time I did not even realize this before I read http://rubyforge.org/pipermail/masterview-users/2006-October/000083.html. The problem turned out to be a problem/feature in Eclipse Radrail plugin, which spawns Webrick using a lot of "-e some_code_here". And this causes the program name to be set to "-e" and Masterview code would not run. The solution is to define a new set of web servers via the "External tools" mechanism instead of relying on the default generated web servers. I though this ought to be documented somewhere, it took me some hours to debug. From jeff.barczewski at gmail.com Fri Feb 16 12:31:17 2007 From: jeff.barczewski at gmail.com (Jeff Barczewski) Date: Fri, 16 Feb 2007 11:31:17 -0600 Subject: [Masterview-users] FYI: Masterview admin pages visibility, webrick and radrails In-Reply-To: <45D5E69F.7060101@iki.fi> References: <45D5E69F.7060101@iki.fi> Message-ID: <19cda190702160931j21b4b176h11c96505cdbd6e51@mail.gmail.com> Lea, Thank you for posting this. I will see what I can do to resolve the issue when running with RadRails. Blessings, Jeff On 2/16/07, Lea Viljanen wrote: > > I had weird problem where I could not see the masterview admin page at > all. Web server kept on saying: > > Initializing MasterView configuration (2007-02-16 18:59) > Program name = -e > => Rails application started on http://0.0.0.0:3001 > => Ctrl-C to shutdown server; call with --help for options > [2007-02-16 18:59:42] INFO WEBrick 1.3.1 > [2007-02-16 18:59:42] INFO ruby 1.8.5 (2006-12-25) [i686-linux] > [2007-02-16 18:59:42] INFO WEBrick::HTTPServer#start: pid=27462 port=3001 > > Now, everybody FAMILIAR with Masterview would instantly know that > Webrick is not actually running the Masterview code at all. However, > installing and running Masterview for the first time I did not even > realize this before I read > http://rubyforge.org/pipermail/masterview-users/2006-October/000083.html. > > The problem turned out to be a problem/feature in Eclipse Radrail > plugin, which spawns Webrick using a lot of "-e some_code_here". And > this causes the program name to be set to "-e" and Masterview code would > not run. The solution is to define a new set of web servers via the > "External tools" mechanism instead of relying on the default generated > web servers. > > I though this ought to be documented somewhere, it took me some hours to > debug. > _______________________________________________ > Masterview-users mailing list > Masterview-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/masterview-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070216/33d4b6f8/attachment.html From Lea.Viljanen at iki.fi Fri Feb 16 12:46:21 2007 From: Lea.Viljanen at iki.fi (Lea Viljanen) Date: Fri, 16 Feb 2007 19:46:21 +0200 Subject: [Masterview-users] How come app/views/ is empty? Message-ID: <45D5EDED.8040002@iki.fi> Apart from the webrick problem documented previously, I had a puzzling problem: views/controller directory would stay empty after doing "script/generate model controller". Script would say everything is OK, but I would get a "Missing template script/../config/../app/views/foo/list.rhtml" error in the browser on trying to get to the controller. The problem is that I don't know what fixed this. When I got the webrick problem sorted out, the generator suddenly started working as well. But as the problems probably weren't related, I'd like to know if anybody else has seen this? What was the solution? BTW, Masterview would need better support for merging it with existing plain Rails projects. I don't think I'm the only one realizing halfway into coding that something like Masterviews would be needed. Or at least better documentation how to do it... I'm willing to help, but with about 8 hours of Masterview experience I'm not the ideal candidate. From jeff.barczewski at gmail.com Fri Feb 16 12:59:07 2007 From: jeff.barczewski at gmail.com (Jeff Barczewski) Date: Fri, 16 Feb 2007 11:59:07 -0600 Subject: [Masterview-users] How come app/views/ is empty? In-Reply-To: <45D5EDED.8040002@iki.fi> References: <45D5EDED.8040002@iki.fi> Message-ID: <19cda190702160959s2f81a64erdccae02ecd7049b4@mail.gmail.com> On 2/16/07, Lea Viljanen wrote: > > Apart from the webrick problem documented previously, I had a puzzling > problem: views/controller directory would stay empty after doing > "script/generate model controller". Script would say everything is OK, > but I would get a "Missing template > script/../config/../app/views/foo/list.rhtml" error in the browser > on trying to get to the controller. Hmm. Sounds like there was an exception happening in the generate that was not actually letting the code succeed to create the files. Unfortunately many of these rails commands eat the exception by default so we don't always see the output, sometimes you can get more output by adding a command line option. The problem is that I don't know what fixed this. When I got the > webrick problem sorted out, the generator suddenly started working as > well. But as the problems probably weren't related, I'd like to know > if anybody else has seen this? What was the solution? I'm guessing that somehow you resolved the original exception and things started working again. We'll try to indicate in our docs how one can get more useful output if you are having problems. BTW, Masterview would need better support for merging it with existing > plain Rails projects. I don't think I'm the only one realizing halfway > into coding that something like Masterviews would be needed. Or at least > better documentation how to do it... I'm willing to help, but with about > 8 hours of Masterview experience I'm not the ideal candidate. Yes, while you can currently mix and match using MasterView with an existing project, others have also suggested interest in being able to import existing rhtml into the MasterView templates would really help. I agree that this would be a nice feature to have, but I haven't quite worked through all the technical details to be able to make this happen. It is on our todo list. Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070216/f6a8f6ca/attachment.html From bernardino.lopez at gmail.com Mon Feb 19 12:33:43 2007 From: bernardino.lopez at gmail.com (Dino Lopez) Date: Mon, 19 Feb 2007 11:33:43 -0600 Subject: [Masterview-users] Can Masterview work with RestFul Applications... Message-ID: <4209097b0702190933w189c485bwf9f588e9770fbbc8@mail.gmail.com> I have some simple jukebox restful application working, try to use with Masterview. and the applications just seem to quit working. I did override all the files to let jukebox take control over the look & feel, but seems like something did not worked nice. Any advise about how to make Masterview work in a Restful environment ??? Best Regards Dino. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070219/9f1e3ded/attachment.html From jeff.barczewski at gmail.com Mon Feb 19 12:48:07 2007 From: jeff.barczewski at gmail.com (Jeff Barczewski) Date: Mon, 19 Feb 2007 11:48:07 -0600 Subject: [Masterview-users] Can Masterview work with RestFul Applications... In-Reply-To: <4209097b0702190933w189c485bwf9f588e9770fbbc8@mail.gmail.com> References: <4209097b0702190933w189c485bwf9f588e9770fbbc8@mail.gmail.com> Message-ID: <19cda190702190948q2b3a0765qb221c352dad10da8@mail.gmail.com> Dino, I am using MasterView with a REST application (a hybrid, some REST, some traditional) and things work fine, however I found that there were areas that could be improved. I would also like to offer have a generator that generates REST style app as well. I am planning on making some enhancements in the next month or so to accommodate these enhancements. However you can get things working with REST today. So back to your issues, can you give us more specifics on what happened and what stopped working? Any log files? We'll do our best to help. Jeff On 2/19/07, Dino Lopez wrote: > > I have some simple jukebox restful application working, try to use with > Masterview. and the applications just seem to quit working. I did override > all the files to let jukebox take control over the look & feel, but seems > like something did not worked nice. > > Any advise about how to make Masterview work in a Restful environment ??? > > Best Regards Dino. > > _______________________________________________ > Masterview-users mailing list > Masterview-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/masterview-users > -- Jeff Barczewski, MasterView core team Inspired Horizons Ruby on Rails Training and Consultancy Next Ruby on Rails plus JRuby workshop Feb 22-24 St. Louis, MO http://inspiredhorizons.com/training/rails/index.html -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070219/ead7ee4d/attachment.html From Lea.Viljanen at iki.fi Tue Feb 20 08:30:04 2007 From: Lea.Viljanen at iki.fi (Lea Viljanen) Date: Tue, 20 Feb 2007 15:30:04 +0200 Subject: [Masterview-users] "generate masterview model controller" produces 0 length HTML files Message-ID: <45DAF7DC.4000505@iki.fi> Why are the Masterview HTML templates empty after the following sequence: lea at migrox:~/src/swaram/app$ cd .. lea at migrox:~/src/swaram$ script/generate masterview license admin Initializing MasterView configuration (2007-02-20 15:09) Program name = script/generate dependency model exists app/models/ exists test/unit/ exists test/fixtures/ skip app/models/license.rb skip test/unit/license_test.rb skip test/fixtures/licenses.yml exists app/controllers/ exists app/helpers/ exists app/views/admin exists public/stylesheets/masterview exists app/masterview exists app/masterview/extra exists test/functional/ overwrite app/controllers/admin_controller.rb? [Ynaqd] n skip app/controllers/admin_controller.rb overwrite test/functional/admin_controller_test.rb? [Ynaqd] n skip test/functional/admin_controller_test.rb identical app/helpers/admin_helper.rb create admin/list.html create admin/destroy.html create admin/show.html create admin/new.html create admin/edit.html identical public/stylesheets/masterview/style.css overwrite public/stylesheets/masterview/sidebox.css? [Ynaqd] n skip public/stylesheets/masterview/sidebox.css overwrite public/stylesheets/masterview/color-scheme.css? [Ynaqd] n skip public/stylesheets/masterview/color-scheme.css identical app/masterview/extra/mvpreview.js identical app/masterview/extra/show_only_new.css identical app/masterview/extra/show_only_edit.css identical app/masterview/extra/show_only_show.css identical app/masterview/extra/show_only_list.css identical app/masterview/extra/show_only_destroy.css lea at migrox:~/src/swaram$ lea at migrox:~/src/swaram$ cd app/views/admin/ lea at migrox:~/src/swaram/app/views/admin$ ls -al total 120 drwxr-xr-x 4 lea lea 4096 2007-02-20 15:09 . drwxr-xr-x 12 lea lea 4096 2007-02-17 00:13 .. -rw-r--r-- 1 lea lea 0 2007-02-20 15:09 destroy.html -rw-r--r-- 1 lea lea 0 2007-02-20 15:09 edit.html ... To recap, I am in the process of converting an existing application to use Masterview, so I actually do have a model called license and a controller called admin. And no, I'm not willing to totally overwrite them, just generate the HTML, thank you. With the previous two controllers I converted, I just copied the existing HTML files using the Admin GUI without using the generator, so I haven't had this particular problem before. Or is it intended that the generator is used only when running MV for the first time and then everything is copied through the admin web? If so, a hint towards this in the documentation would be nice. -- Lea 'LadyBug' Viljanen Independent security consultant. ladybug at iki.fi http://www.lavsecurity.fi/ From Lea.Viljanen at cs.helsinki.fi Tue Feb 20 06:54:20 2007 From: Lea.Viljanen at cs.helsinki.fi (Lea Viljanen) Date: Tue, 20 Feb 2007 13:54:20 +0200 Subject: [Masterview-users] How to get :confirm and :post functionality with a mv:link_to? Message-ID: <45DAE16C.3080100@cs.helsinki.fi> I have a link in the form of: <%= link_to 'Destroy', { :action => 'destroy', :id => component }, :confirm => 'Are you sure?', :post => true %> in an application I'm converting to use Masterview. However, I haven't found a way to achieve exactly this with mv:link_to. Note, that in my original application, the :confirm and :post get converted by Rails framework to a piece of onclick= javascript, but Masterview just adds the :confirm and :post parameters to the link URL. I could go through a separate destroy form/page, but I prefer it this way, it gives direct feedback to user instead of jumping between pages. Any hints appreciated, - Lea -- Lea 'LadyBug' Viljanen Independent security consultant. ladybug at iki.fi http://www.lavsecurity.fi/ From jeff.barczewski at gmail.com Tue Feb 20 11:26:34 2007 From: jeff.barczewski at gmail.com (Jeff Barczewski) Date: Tue, 20 Feb 2007 10:26:34 -0600 Subject: [Masterview-users] "generate masterview model controller" produces 0 length HTML files In-Reply-To: <45DAF7DC.4000505@iki.fi> References: <45DAF7DC.4000505@iki.fi> Message-ID: <19cda190702200826i1deed2am395d972d8d9fa697@mail.gmail.com> On 2/20/07, Lea Viljanen wrote: > > Why are the Masterview HTML templates empty after the following sequence: > > lea at migrox:~/src/swaram/app$ cd .. > lea at migrox:~/src/swaram$ script/generate masterview license admin > Initializing MasterView configuration (2007-02-20 15:09) > Program name = script/generate > dependency model > exists app/models/ > exists test/unit/ > exists test/fixtures/ > skip app/models/license.rb > skip test/unit/license_test.rb > skip test/fixtures/licenses.yml > exists app/controllers/ > exists app/helpers/ > exists app/views/admin > exists public/stylesheets/masterview > exists app/masterview > exists app/masterview/extra > exists test/functional/ > overwrite app/controllers/admin_controller.rb? [Ynaqd] n > skip app/controllers/admin_controller.rb > overwrite test/functional/admin_controller_test.rb? [Ynaqd] n > skip test/functional/admin_controller_test.rb > identical app/helpers/admin_helper.rb > create admin/list.html > create admin/destroy.html > create admin/show.html > create admin/new.html > create admin/edit.html > identical public/stylesheets/masterview/style.css > overwrite public/stylesheets/masterview/sidebox.css? [Ynaqd] n > skip public/stylesheets/masterview/sidebox.css > overwrite public/stylesheets/masterview/color-scheme.css? [Ynaqd] n > skip public/stylesheets/masterview/color-scheme.css > identical app/masterview/extra/mvpreview.js > identical app/masterview/extra/show_only_new.css > identical app/masterview/extra/show_only_edit.css > identical app/masterview/extra/show_only_show.css > identical app/masterview/extra/show_only_list.css > identical app/masterview/extra/show_only_destroy.css > lea at migrox:~/src/swaram$ > lea at migrox:~/src/swaram$ cd app/views/admin/ > lea at migrox:~/src/swaram/app/views/admin$ ls -al > total 120 > drwxr-xr-x 4 lea lea 4096 2007-02-20 15:09 . > drwxr-xr-x 12 lea lea 4096 2007-02-17 00:13 .. > -rw-r--r-- 1 lea lea 0 2007-02-20 15:09 destroy.html > -rw-r--r-- 1 lea lea 0 2007-02-20 15:09 edit.html > ... > > To recap, I am in the process of converting an existing application to > use Masterview, so I actually do have a model called license and a > controller called admin. And no, I'm not willing to totally overwrite > them, just generate the HTML, thank you. > > With the previous two controllers I converted, I just copied the > existing HTML files using the Admin GUI without using the generator, so > I haven't had this particular problem before. Or is it intended that the > generator is used only when running MV for the first time and then > everything is copied through the admin web? If so, a hint towards this > in the documentation would be nice. > > -- > Lea 'LadyBug' Viljanen Independent security consultant. > ladybug at iki.fi http://www.lavsecurity.fi/ > > Lea, The generator is designed to get a person up and running as quickly as possible with a CRUD application in MasterView. It can be run with an existing project or a new project. However like you said, if you already have a working controller and model, then you will probably want to tell the generator to not override those files. You will want to make sure that your controller method names match up with the templates being generated (both name wise and that the appropriate instance variables are being created for the views to use). Another thing you could do to help this process is to create another rails app and generate it there to see what the controller it creates looks like and you can then update yours appropriately. Alternatively you can update the views. The generator isn't the only way to proceed, though it is one of the quickest. The other option is to simply take some html representing what you want to end up with and then sprinkly the MasterView directives into it, to make it real. We are planning to prepare more info and videos about how to do this second process. I hope this helps some. If you have trouble we'll try to help however we can. Blessings, Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070220/10fbe6a1/attachment.html From jeff.barczewski at gmail.com Tue Feb 20 11:31:45 2007 From: jeff.barczewski at gmail.com (Jeff Barczewski) Date: Tue, 20 Feb 2007 10:31:45 -0600 Subject: [Masterview-users] How to get :confirm and :post functionality with a mv:link_to? In-Reply-To: <45DAE16C.3080100@cs.helsinki.fi> References: <45DAE16C.3080100@cs.helsinki.fi> Message-ID: <19cda190702200831s151597a0t666c5a6fa34b2eeb@mail.gmail.com> On 2/20/07, Lea Viljanen wrote: > > I have a link in the form of: > > <%= link_to 'Destroy', { :action => 'destroy', :id => component }, > :confirm => 'Are you sure?', :post => true %> > > in an application I'm converting to use Masterview. However, I haven't > found a way to achieve exactly this with mv:link_to. Note, that in my > original application, the :confirm and :post get converted by Rails > framework to a piece of onclick= javascript, but Masterview just adds > the :confirm and :post parameters to the link URL. > > I could go through a separate destroy form/page, but I prefer it this > way, it gives direct feedback to user instead of jumping between pages. > > Any hints appreciated, > - Lea > > -- > Lea 'LadyBug' Viljanen Independent security consultant. > ladybug at iki.fi http://www.lavsecurity.fi/ > I will take a look and see whether it is a syntax issue or defect. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070220/90567959/attachment.html From jeff.barczewski at gmail.com Tue Feb 20 13:14:49 2007 From: jeff.barczewski at gmail.com (Jeff Barczewski) Date: Tue, 20 Feb 2007 12:14:49 -0600 Subject: [Masterview-users] How to get :confirm and :post functionality with a mv:link_to? In-Reply-To: <19cda190702200831s151597a0t666c5a6fa34b2eeb@mail.gmail.com> References: <45DAE16C.3080100@cs.helsinki.fi> <19cda190702200831s151597a0t666c5a6fa34b2eeb@mail.gmail.com> Message-ID: <19cda190702201014s5b83d02kd402b0361325b08@mail.gmail.com> Lea, I just added a test to confirm this and it appears to work in the trunk. So double check your syntax with the test code below and see if maybe it was a typo. Otherwise maybe it was something that was recently fixed. I am planning to push out a new release today so if the below syntax does not work for you on your version, then the new version should fix it. def test_link_to_with_post_and_confirm template = <<-END END expected = { 'foo/bar' => "
<%= link_to( 'Destroy', { :action => 'destroy', :id => component }, :confirm => 'Are you sure?', :post => true ) %>
" } assert_template_result expected, template end Blessings, Jeff On 2/20/07, Jeff Barczewski wrote: > > On 2/20/07, Lea Viljanen wrote: > > > > I have a link in the form of: > > > > <%= link_to 'Destroy', { :action => 'destroy', :id => component }, > > :confirm => 'Are you sure?', :post => true %> > > > > in an application I'm converting to use Masterview. However, I haven't > > found a way to achieve exactly this with mv:link_to. Note, that in my > > original application, the :confirm and :post get converted by Rails > > framework to a piece of onclick= javascript, but Masterview just adds > > the :confirm and :post parameters to the link URL. > > > > I could go through a separate destroy form/page, but I prefer it this > > way, it gives direct feedback to user instead of jumping between pages. > > > > Any hints appreciated, > > - Lea > > > > -- > > Lea 'LadyBug' Viljanen Independent security consultant. > > ladybug at iki.fi http://www.lavsecurity.fi/ > > > > > I will take a look and see whether it is a syntax issue or defect. > -- Jeff Barczewski, MasterView core team Inspired Horizons Ruby on Rails Training and Consultancy Next Ruby on Rails plus JRuby workshop Feb 22-24 St. Louis, MO http://inspiredhorizons.com/training/rails/index.html -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070220/00ffbf2c/attachment.html From jeff.barczewski at gmail.com Tue Feb 20 13:28:07 2007 From: jeff.barczewski at gmail.com (Jeff Barczewski) Date: Tue, 20 Feb 2007 12:28:07 -0600 Subject: [Masterview-users] problem with mv:attr and erb evaluated code. In-Reply-To: <3df642dd0701310236s148564fbs70c21167a4175d5b@mail.gmail.com> References: <3df642dd0701310236s148564fbs70c21167a4175d5b@mail.gmail.com> Message-ID: <19cda190702201028oc0f3ea3qb35589bb2f89a1db@mail.gmail.com> On 1/31/07, Ed Howland wrote: > > I ran into this before, but I can't find any email from me about it. > Sorry if this is a repeat, but the problem persists in MV 0.3.1 > > If you have a helper method that you want to evaluate in a construct like: > >
> > it legitimately renders it so: >
> > But if you increase the argument count to more than 1, e.g.: >
> > It renders: >
I have tested this in the trunk and it is resolved. (We had fixed one of the parsing functions) So you can get this with the next release, which is due out any time now. It's also available in the trunk. I added this test to insure that it works def test_attr_eval_helper_with_multi_params template = <<-END
foo bar
END expected = { 'foo/bar' => "
\">foo bar
" } assert_template_result expected, template end Blessings, Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070220/d996067b/attachment-0001.html From ed.howland at gmail.com Tue Feb 20 14:11:26 2007 From: ed.howland at gmail.com (Ed Howland) Date: Tue, 20 Feb 2007 13:11:26 -0600 Subject: [Masterview-users] problem with mv:attr and erb evaluated code. In-Reply-To: <19cda190702201028oc0f3ea3qb35589bb2f89a1db@mail.gmail.com> References: <3df642dd0701310236s148564fbs70c21167a4175d5b@mail.gmail.com> <19cda190702201028oc0f3ea3qb35589bb2f89a1db@mail.gmail.com> Message-ID: <3df642dd0702201111s4cecf872y146bdce300b19798@mail.gmail.com> On 2/20/07, Jeff Barczewski wrote: > On 1/31/07, Ed Howland wrote: > > I ran into this before, but I can't find any email from me about it. > > Sorry if this is a repeat, but the problem persists in MV 0.3.1 > > > > If you have a helper method that you want to evaluate in a construct like: > > > >
> > > > it legitimately renders it so: > >
> > > > But if you increase the argument count to more than 1, e.g.: > >
> > > > It renders: > >
> > I have tested this in the trunk and it is resolved. (We had fixed one of the > parsing functions) > > So you can get this with the next release, which is due out any time now. > > It's also available in the trunk. > > I added this test to insure that it works > > def test_attr_eval_helper_with_multi_params > template = <<-END >
> foo > bar >
> END > expected = { > 'foo/bar' => "
%>\">foo bar
" > } > assert_template_result expected, template > end > Jeff, are the escapes of the curly-braces needed for all double-quated string evals? Does that need to be documented somewhere? Ed > > Blessings, > > Jeff > > _______________________________________________ > Masterview-users mailing list > Masterview-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/masterview-users > -- Ed Howland http://greenprogrammer.blogspot.com From jeff.barczewski at gmail.com Tue Feb 20 14:24:11 2007 From: jeff.barczewski at gmail.com (Jeff Barczewski) Date: Tue, 20 Feb 2007 13:24:11 -0600 Subject: [Masterview-users] problem with mv:attr and erb evaluated code. In-Reply-To: <3df642dd0702201111s4cecf872y146bdce300b19798@mail.gmail.com> References: <3df642dd0701310236s148564fbs70c21167a4175d5b@mail.gmail.com> <19cda190702201028oc0f3ea3qb35589bb2f89a1db@mail.gmail.com> <3df642dd0702201111s4cecf872y146bdce300b19798@mail.gmail.com> Message-ID: <19cda190702201124u45ffe793v9fe6ad2c3c4a967c@mail.gmail.com> On 2/20/07, Ed Howland wrote: > > > Jeff, are the escapes of the curly-braces needed for all double-quated > string evals? Does that need to be documented somewhere? > > Actually no, you don't need to do anything like that. This was only necessary because the here doc (<<) in my test case tries to eval things. You don't need to do that in your templates. Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070220/d3c6e9ea/attachment.html From Lea.Viljanen at iki.fi Tue Feb 20 14:35:06 2007 From: Lea.Viljanen at iki.fi (Lea Viljanen) Date: Tue, 20 Feb 2007 21:35:06 +0200 Subject: [Masterview-users] How to get :confirm and :post functionality with a mv:link_to? In-Reply-To: <19cda190702201014s5b83d02kd402b0361325b08@mail.gmail.com> References: <45DAE16C.3080100@cs.helsinki.fi> <19cda190702200831s151597a0t666c5a6fa34b2eeb@mail.gmail.com> <19cda190702201014s5b83d02kd402b0361325b08@mail.gmail.com> Message-ID: <45DB4D6A.5040200@iki.fi> Jeff Barczewski wrote: > I just added a test to confirm this and it appears to work in the trunk. > So double check your syntax with the test code below and see if maybe it > was a typo. Duh, I had tried different combinations with the closing quotes and braces but apparently not the exactly correct one. So, it works now, thanks! - Lea From jeff.barczewski at gmail.com Wed Feb 21 12:25:41 2007 From: jeff.barczewski at gmail.com (Jeff Barczewski) Date: Wed, 21 Feb 2007 11:25:41 -0600 Subject: [Masterview-users] [ANN] MasterView rails-optimized (x)html friendly template engine - Release 0.3.2 Message-ID: <19cda190702210925w7a3f77bcof399218f1349d012@mail.gmail.com> 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. Releae 0.3.2 is primarily a maintenance release to fix a minor incompatibility with Rails 1.2.2 which was causing a blank screen on a view compile error rather than the normal debug output. Also there was a defect in the parameter parsing when using multiple parameters that was corrected. Finally the authorization mechanism for accessing the MasterView admin pages was made customizable by allowing a user configurable module to be used. Tested with Rails 1.2.2 Release 0.3.1 was a maintenance release addressing an issue with ruby 1.8.5(wrong number of arguments 1 for 2 during scaffold generation), fixing a problem with the deprecated/directive_base used for custom directives, updating a few out of date docs, and accomodating a change to the API of the Rails 1.2 generator. Release 0.3.0 was a major release for MasterView with an emphasis on refactoring and simplifying the API for building directives. A DSL syntax was chosen to greatly simplify the creation of directives to both help the core team with directive development as to also enable developers to create their own custom directives easily. MasterView has been constructed to allow directives to be shared amongst the community and this refactoring will enable custom development. To further enhance sharing and prevent collisions, this release introduces custom namespaces to the directives allowing users to create their own namespaces to prevent conflict. Namespaces as well as many other metadata about directives can now be configured at both the app-level and installation-level providing flexibility. Video A short video which demos the basic operation is available at http://masterview.org/videos/demo_short.html Screenshots and illustrations http://masterview.org/media_list.html MasterView is released under MIT open source licensing. Main site: http://masterview.org/ Rubyforge Project site: http://rubyforge.org/projects/masterview Goals - Create/extend a template engine for rails that would be XHTML friendly and thus could be edited/styled with a WYSIWYG HTML editor even late in development without breaking template. - Keep it simple. DRY. No extra config files, simple syntax with ruby flavor. - Design it specifically for ruby and rails. Use the full power and not be limited in its capabilities over what can be done with ERb (rhtml) - Work nicely with layouts, partials, and rails html helpers. - Reduce complexity, work with existing rails code, no extra view logic or hashes than what is used by ERb (rhtml). Scaffold generate initial templates or work from existing html prototype. Make scaffolds nicely styled and easily useable for production with minor changes. - Reduce the numbers of files, simplifying editing. Define partials and layouts naturallyl right in the template, no need to go to another file. - Preview in browser without running an app. Allow for dummy data in the template so that the page can be viewed and styled independently of the application. - Performance equal to ERb (rhtml) Release Notes: == Recent changes (Release 0.3.2 - Maintenance release plus custom admin auth) This release addresses a compatibility problem with Rails 1.2 where a view syntax error would not display the normal debug output but instead displayed only a blank screen. Also fixed a parsing problem with multiple parameters in some directives. Added the ability to use custom mixin for authorization to MasterView admin screens. Changed the MasterView generator to use request, flash, and params rather than deprecated @request, @flash, and @params. Tested with Rails 1.2.2 == Recent changes (Release 0.3.1 - Maintenance release This release addresses an issue with ruby 1.8.5, fixes a problem with the deprecated/directive_base used for custom directives, updates a few out of date docs, and accomodates a change to the API of the Rails 1.2 generator == Recent changes (Release 0.3.0 - Major update - refactoring of directive API (for developing directives) The directive API for creating directives has been refactored and simplified. This will enable directives to be developed more easily by both core developers and MasterView users. The end goal is to make it extremely simple for anyone to create their own custom directives and to share those with the community, and thus the project can live and grow into many specialty areas. The directive API refactoring is one more step towards those goals. The old directive_base.rb which provided the API for directives has been deprecated and moved to deprecated/directive_base.rb, MasterViewdevelopers which have developed custom directives should upgrade those directives to the new API as soon as possible. During the transition period one can use the original API by requiring the deprecated/directive_base.rb file and changing their directive to inherit from DirectiveBaseOld rather than DirectiveBase. == Recent changes (Release 0.2.5) Fix AdminPage compatibility with Rails 1.1.5+ which uses safe_load_paths to find controllers Fix rake mv:view_rhtml RHTML=foo/_bar.rhtml was not able to find partials Visit the online documentation page at http://masterview.org/ for screenshots, illustrations, complete installation and usage information. We would love to hear your feedback and ideas around this project! Visit the rubyforge project to join the users mailing list or to add yourself to the announce list to receive future announcements. Check out the videoto see MasterView in action! Thanks for your time!! MasterView Development Team Jeff Barczewski and Deb Lewis -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-users/attachments/20070221/1807b9cf/attachment.html