Re^2: CGI::Application, inheritance trees, and 'the right way'

that, in fact, does look like the cleanest solution.

from the perldoc, i guess my form action would just have the module name on it? like:

   <form name='add' method='post' action='/cgi-bin/index.cgi/EventMana
+ger/'>
[download]

and the hidden fields for RM would still apply?

Comment on Re^2: CGI::Application, inheritance trees, and 'the right way' Select or Download Code

Replies are listed 'Best First'.
Re^3: CGI::Application, inheritance trees, and 'the right way' by dragonchild (Archbishop) on Nov 02, 2004 at 18:23 UTC
I'm not quite sure how that works, as I've never used it myself. Try it out with a few toy classes and see what happens. Alternatively, you can ask on the CGI::Application mailing list, which is where I heard about this. Being right, does not endow the right to be rude; politeness costs nothing. Being unknowing, is not the same as being stupid. Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence. Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.	[reply]
Re^4: CGI::Application, inheritance trees, and 'the right way' by geektron (Curate) on Nov 02, 2004 at 18:46 UTC
actually, adding the `dispatch`ed class to the form method just works, which is nice. i just have to play with some of my direct links, see if i should tack on `?rm=foo`	[reply] [d/l] [select]