Finally ... we will get an app store! You have a shop anyway, so why not. Take 30% of the price if you sell one of my skins ...
>From my wishlist: * a smoother integration of multipage editing (using "count" or similar) * having the chance to add "id" and "class" names to every element including ul/ol/li * getting ready for html5 The last two points may require to rethink the use of shortcuts for html attributes. I am happy to move on and thank you very much for your work. Greetings, Martin On Mar 16, 1:49 pm, blues <[email protected]> wrote: > On Mar 16, 2:29 pm, The Editor <[email protected]> wrote: > > > In some ways it is smarter to just maintain > > a bunch of separater plugins. Pick and choose. But in reality, it is > > easier for me to maintain them as a group. On my site, I have all > > these things (blog, forum, rss, store, email verification, passwords, > > etc.). If something breaks I fix it immediately for my site--and don't > > go back and patch every plugin involved. If I could run my site off a > > "BoltWire CMS", I patch that core and release it. And > > bingo--everything is working. So that's part of my rationale behind > > it. I'm hoping it will give folks a better user experience than trying > > a half dozen plugins that have somehow been outdated. > > i think i agree with you. > although the plugin approach is probably better, i have nothing > against a "CMS core" concept, it should be easier for you to maintain > and for the users to update. > but it should be structured so that the various parts can be disabled > if not needed, to minimize the overhead. > > blues -- 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.
