On Thu, Jan 07, 2010 at 08:35:09AM -0500, The Editor wrote: > On Wed, Jan 6, 2010 at 7:32 PM, riccardo <[email protected]> wrote: [...] > Thanks for the feedback. I agree with you on both goals--simple file > management system, and simple code base. And yet robust.
Perfect. [...] > > dokuwiki ... > > just placing the > > variables that are to be changed in a config file will change only them > > and > > inherit the values for all others from above. >· > This is a nice idea. I'm thinking of combining this idea with > something Danny suggested (can't recall if it was onlist or off), > about having a central config script that would keep all the default > config settings in one location.· I was going to suggest that next. IMO it's best to put all the config items in one file and include it. This is not only easier for the average user, it makes writing a configuration front-end (I guess in BW that is going to be a config form on a special page) much easier, and also simplifies trying out different combinations (by symlinking to different variations) while developing a site or while developing the engine itself. > Especially if it could be combined with a hierarchical system, which does Do you mean a hierarchy of config variables? I've seen this used elsewhere where config variables are in a two dimensional array -- makes naming easier when altering the code, and also finding the right variable easier when configuring a site. [...] > > For both dokuwiki and cmsmadesimple, I wrote tags for things I like to > > do > > often -- and example being a box ...· > > [with very variable contets and parameters] [...] >· > It's probably just a simple issue of customizing the box css style or > adding some new styles, and if you wish, some markup rules. Here are > two solutions pages you might want to look at, for ideas. >· > http://www.boltwire.com/index.php?p=solutions.css.stickynotes > http://www.boltwire.com/index.php?p=solutions.css.special Ye--es. There may be easier or just different ways of achieving what I want in BW. I'll need to find time to play a bit. But the code I wrote for doku and cmsms was a custom tag that accepted a stack of possible parameters to allow floated "bits" in a range of styles to be inserted by someone who doesn't know or want to mess with css directly, and to allow these "bits" to follow a style determined by the site css while being able to be controlled in size and position etc. I am likely to feel moved to hack something. > If you need help customizing something, post the markup you want to > use, and the html output you would like to see, and someone should be > able to whip together a markup rule and/or some css for you pronto. Thanks. As I say, I am more likely to try to do it myself, but it's good to know help is at hand. Cheers, richard
-- 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.
