in reply to Re^5: Does Catalyst Borrow from Rails?
in thread Does Catalyst Borrow from Rails?

Rails does provide chaining as well as a uri_for(). I don't remember which framework I added uri_for to - I think it was C::A - mst probably figured that one out on his own. :-)

Yes - I did mean configured routes vs. discovered routes.

Yes, I do look at the debug output to figure things out. However, it's not always as simple as just looking at some config file. The ability to use both would be nice.

I prefer Ruby's clean OO over Perl's rather verbose version. However, as tye has said before, the lack of strictures makes Ruby a second-class language, no matter what else it offers. That its syntax is closer to Javascript's would normally make it a better candidate for RIAs than Perl, but the lack of strictures is just a deal-killer.


My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

Replies are listed 'Best First'.
Re^7: Does Catalyst Borrow from Rails?
by phaylon (Curate) on Feb 09, 2007 at 12:48 UTC
    Again, what is 'configured routes vs. discovered routes'? What *are* routes?
    Yes, I do look at the debug output to figure things out. However, it's not always as simple as just looking at some config file. The ability to use both would be nice.
    Umm, what debugging information would you expect in your configuration file?

    Ordinary morality is for ordinary people. -- Aleister Crowley
      A configured route is one you laid out in a config file. A discovered route is one that comes about through inspection of the methods' metadata. In other words, Rails-style vs. Cat-style.

      As for the info, a properly laid out routes config file will provide, through inspection, a lot of information that is more difficult to find in a Cat-style layout.


      My criteria for good software:
      1. Does it work?
      2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
        Catalyst doesn't enforce you to use discovered "routes." It can discover it from your code (which can be told in several ways) but with Chained and uri_for, you can also set your paths in your configuration file. If you use uri_for the right way, all your links will still work after you reconfigured your paths, without you having to touch the templates, controllers or anything else.

        Which is why I thought and said that Catalyst is probably more flexible. It has no "style". You can use the style you need for your application.

        Ordinary morality is for ordinary people. -- Aleister Crowley