On Wed, Jan 6, 2010 at 7:32 PM, riccardo <[email protected]> wrote: > On Wed, Jan 06, 2010 at 10:51:33AM -0500, The Editor wrote: > >> Thanks Richard, I'm with you on this one. Right now it is still easy >> to import text--even text with <. You just have to be careful about >> malicious code getting dumped in. If we make this switch it should be >> both easier and safer. > > There's been some comment here about the dokuwiki example. I would agree > that doku is a fine example from which one can learn a lot. A second source > of good ideas may be cmsmadesimple. Let me explain with a brief history. > > A few years ago, I originally set up a couple of my sites using dokuwiki as > a kind of cms, and I chose it because of its clean code and because of the > plain text page storage. I often edited pages directly on the server and > the system appeared entirely tolerant of this (though I suppose it would > have created difficulties if I had had need to backtrack just after one of > my direct edits). I then moved to cmsmadesimple. I chose that over drupal, > zope-and-friends, etc., because it was lighter and much simpler to > understand and to manage. I found it reasonably easy to transfer everything > I had done in dokuwiki to cmsmadesimple, and the subsequent management is > simpler. My main reason for thinking of moving on from cmsmadesimple, at > least for some uses, is the storage in mysql -- the loss of the simple text > pages. In BoltWire, I see the potential for getting most of the strengths > of both of the above in an innovative and compact system.
Thanks for the feedback. I agree with you on both goals--simple file management system, and simple code base. And yet robust. BoltWire may not have all the kinks ironed out, but you got our target clearly in mind. Changing the character encoding system to not escape < moves a step closer in both goals, by the way.. > Both dokuwiki and cmsmadesimple provide hierachical control of all aspects > of the pages, dokuwiki uses a very similar approach to BoltWire, essentially > giving precedence to the version of any system variable found closest to the > page. It is not necessary to replace the whole file AFAIR, 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. Especially if it could be combined with a hierarchical system, which does not currently exist, but could be implemented easily enough. Most things are configurable, and actually you can make the config variables configurable via config files, but there may be an easier way to centralize this--which is proving to be a nice strength of BoltWire. > For both dokuwiki and cmsmadesimple, I wrote tags for things I like to do > often -- and example being a box to insert in text that can contain either > an image or a snippet of html and which can be floated either right or left > or centred, surrounded by a frame or separated from the adjacent text by a > vertical line, and in either case can have a caption if required. This is > an item I would definitely wish to recreate for BoltWire (unless it already > exists). I quote this only as an example of the kind of flexibility I hope > will be available if I decide to use boltwire as a cms. 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 The colors don't look so great on chrome, but I recall them being brighter on IE. 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. 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.
