21:36 so. what would people like to see out of a jifty plugin framework?
21:39 I'd like to see that a dispatcher plugin cannot affect an action plugin
21:43 What do you mean? I'd expect that a plugin would be able to install dispatcher rules and actions
21:43 so we could make the "EditFile" thing a plugin
21:44 I'd like to see JiftyX::EditFile::Dispatch
21:44 er Dispatcher
21:44 JiftyX::EditFile::Action
21:44 as separate namespaces (maybe inside the same EditFile.pm)
21:44 of course, JiftyX is better spelled as Jifty::Plugin
21:44 Jiftyhashi?
21:45 Java has coffee beans
21:45 maybe Jifty has tea bags
21:45 Jif::Tea::Bag
21:45 *groan*
21:46 so. about plugins
21:46 I guess there are two different things here
21:46 1) plugins for parts of jifty should be in the right namespaces
21:46 2) should a plugin be able to install dispatcher rules directly?
21:46 ie, "use this plugin and it adds rules at these trigger points"
21:48 I want "Login" and "Signup" to become plugins
21:48 so I can stop cargo culting them between apps
21:48 so sorta like rt callbacks
21:48 yeah. was thinking more like plagger's system. it looks pretty
21:48 named points. so even if they move between files, you don't lose
21:48 yup
21:49 so. this means I need to be able to:
21:49 install actions
21:49 install dispatcher rules at all stages
21:49 install static content
21:49 install templates
21:49 possibly install widgets (aka form fields)
21:49 install javascript libs and css files
21:50 (special cases of static content)
21:50 (but also hooks to add those things to the generated header)
21:50 right
21:50 what else am I missing? ;)
21:50 oh. new jifty commands?
21:51 po files are considered templates?
21:51 # ./bin/jifty fooplugin
21:51 no. pofiles are anotehr item for the list
21:51 declare dependency? (normal cpan semantics?)
21:51 another
21:51 yeah. I'd just use perl require lines
21:51 partial ordering? (run this before that)
21:52 in dispatchers?
21:52 or actions?
21:52 or what?
21:57 sorry
21:57 from callbacks
21:57 nod. I worry a little bit about the complexity. when would we want it for callbacks other than the dispatcher rules?
21:58 if all your login etc are in well known places