After reading the posts of both Linly and Hans, I have to admit I was persuaded. Guess on this point we will keep the original structure unless a more compelling reason can be given for changing it.
> I think it overcomplicates thing and makes it harder to get started, > and harder to upgrade. Why would anyone wants multiple barns (systems) > ? Perhaps you for easy testing, but nobody need sit for a normal > installation. The whole philosophy is one barn, multiple fields. > Retaining the folder name is also important. At present you can just > extract a new version over the old (on a Windows system) and the > upgrade is done. The idea is having multiple barns makes it easier to upgrade one field at a time (by editing the index file) and testing for glitches. Without having to do them all at once. And then be able to downgrade just as easily if there is a problem. This doc pages discusses the issue a bit: http://www.boltwire.com/index.php?p=docs.admin.farms#another_multibarn_option This may be a bit more important in BoltWire than PmWiki because of it's rapid pace of development and more frequent glitches. However it occurred to me you could get a similar effect with the current setup (if you wanted) by always renaming the barn folder immediately overwriting the boltwire directory to barn2_44, etc. And then switching over the fields from barn2_43 to barn2_44 one at a time. Plus, you retain all the advantages of the current setup, so ably pointed out by Hans and Linly. > I also like to see folders for plugins and skins, and probably I like > the icons too if I find out what to put in there. It does not matter > that they are empty at the start. it is very helpful for knowing where > to copy add-ons later. I recommend to keep it as simple as it is. I > would even keep both skin and plugin folders. Skins and plugins are > treated separately in the site configuration (I think of page Site > here, which gives a well conceived table of links), so I like to see > that also reflected in the file folders. The icon's folder is simply for farm wide graphics, usually system icons, you might want to use on multiple sites. There are several nice free icon sets here: http://www.boltwire.com/index.php?p=solutions.icons To use them, you just put markup like this in a page: icon:img.gif or icon:subfolder/img.jpg. I'm still thinking about the difference between skins and plugins. In the future, I'm almost certain skins will be installed just like any other plugins, so it makes sense to merge the two, but having them in separate folders, even if they are installed the same way, does make for separate lists, as you mentioned. We'll have to postpone a final decision on this until I can get some time to revisit the skin installation process. Thanks for the input! I appreciate the wisdom of the larger group. Cheers, Dan P.S. I would love to see a skin or two from Hans--who does such excellent work. This is probably our weakest area at BoltWire at present. Only a handful of skins, and most of them not really finished in any real way. And yet skin development is one of the easier aspects of BoltWire to learn. I probably need to put up a step by step tutorial on skin construction... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
