Reaction setup helper (args to get working app or bare bones ?):
- create view/site.pm file
- create view/site/widget/index.pm (or something, for root action)
- create root controller with:
 - base action (loads sitelayout with args from config), 
   - sitelayout used should be reaction::ui::vp::sitelayout, unless I use alias'd my own in which case use that?
 - root action (displays new welcome-message from appropriate files)
 - static action (why do we have our own and not use the cat plugin?) - is it for decorating static data with sitelayout also?
- create share/skin/<myappname> dir and layout/web subdirs
- auto-set skin name in config in Root.pm 

Reaction to list ViewPorts/Widgets etc in catalysts start-up debug (or similar)?

schema reflecting, auto-loads/creates "Create.pm" etc, but if I add for eg:
collection_actions => { name => 'Login', base => '' },
It doesnt load/verify Login.pm for me, I have to "use" it myself

Reflecting is still wordy:
- 1 DBIC Schema to define the cols/attributes
- 1 Cat model to define the connection data and the im_class name
- 1 IM file to create the reflector and pass it about 3 args
- 1 CRUD controller to define the cat model name / collection_name its for
Can we create this lot with one script from a schema or even existing db ?
reflect_schema can get args from config? (eg the collection_actions etc)

Actions need a callback that can stop apply, and somehow stuff appropriate reasons/error messages into the correct place. Currently overridden: sync_all, can_apply and error_for_attribute.

error_for_attribute should probably be returning some sort of key that can be translated/localised at a higher level, rather than a string.

More drop-in standard controllers, eg Users (create, login, send forgotten password  etc)

Localisations more a part of Reaction?