On Mon, Oct 5, 2009 at 9:25 AM, Kevin <[email protected]> wrote: > On Mon, Oct 5, 2009 at 5:30 AM, Hans <[email protected]> wrote: >> >> Great! >> >> I use page 'site' all the time, as it gives a nice listing of all >> important pages for admin. > > I use 'site' all the time myself. > > As for action=skin, I don't use that at all. > > I created a new site over the weekend and found that I bypassed it > completely going right to snippets to make those changes. I then created a > code.style code.skin etc... directly. > > The difference now, is I knew where and what controlled this stuff now. A > new user won't.
Of course if you were going to make the skin available to others, you would want to rename them code.skin.myname and code.style.myname. Then reset the skin: myname in site.config. It also has the advantage of you being able to revert to the default skin if needed, or even shuffle between different skins. And as for action.skin you are right. It is not necessary. But for a new user, and to make things easy to modify, it does add some nice pizzazz. It would be great if every skin available as a plugin either took advantage of features in action.skin and/or had a custom action.skin.myskin page. create child is I think Hans creation. Not in core. I've thought of adding it, but I wasn't sure what to call it. :) If we ever get our code examples section going, that would be a good place to put markup for something like this. Cheers, Dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
