use Perl

• templating (Score:1)

  by awwaiid (5634)

  Yeah, Continuity::Widget is just a sketch, and separate from Continuity itself on purpose. Even if I get that going the way I like, I definitely don't expect it to be The Way to use Continuity. More like a demonstration of what can be done. Well... and for my own use :)

  I unfortunately don't know the full HTML::Mason request cycle and how that all works. One thing you can do, I believe, is to just use Mason as a template engine. You could then use Mason components to organize your views, and outter Continu
• what he said (Score:1)

  by hdp (1658)

  use Mason's templating parts, not its web framework parts, like you would with Catalyst or Jifty. see the source of Catalyst::View::Mason, and the "using Mason in standalone scripts" part of HTML::Mason::Admin.
  • Re: (Score:0)

    by slanning (5049)

    (I'll be damned if I can get the code to format within <code> tags, so this is all Code format.)
    
    I actually tried installing Jifty last night because I realized it might be more what I had in mind (continuations, Mason...), but I aborted the install after about a half hour of exciting CPAN action. (Maybe I should try Catalyst I guess, but it's never really felt right to me..)
    
    Then I ended up doing just what you mentioned, using Mason as a standalone script. It wasn't very elegant, though. Unfortunately
    • Re: (Score:1)

      by awwaiid (5634)

      Yeah. In larger apps I usually end up putting $request into an instance variable so that I don't have to pass it around all the time. You can do the same thing with your Mason interpreter, I imagine your main body might look like:
      
      sub main {
          my $request = shift;
          my $app = App->new(request => $request);
          $app->run;
      }
      
      package App.pm;
      # ...
      
      sub run {
          my $self = shift;
          $self->display('/one.html');
          my $num1 = $self->param('num