Roadmap
After a long line of 3.xx development (not to mention the 2.xx, 1.xx, beta, and alpha development releases), BoltWire is preparing for a 4.xx release. Our focus now is perfecting our 3.xx final release candidate, and easing the transition to 4.xx.
Listed below are changes that will be included in the next release, and farther down information about our 4.xx goals.
Core--Already Fixed for Next Release
Remaining goals for 3.xx series are
- Fix search outputs so they only show up on specified pages (based on nextpage).
- Multi-Page Search feature based on limit=50 or searchLimit in site.config
- Require all commands to be set as session variables to avoid problems with accidental command triggering (namespace). Notes
- Get multiple commands to be automatically renumbered so this is invisible to the user.
- Allow one to put multiple parameters in session commands, like lines=false or fieldreplace=false. Also things like[session mail to= from= subject= body=]. Very nice improvement to not be stuck in a field/value limitation.
- Get rid of boltfield system.
- Move session writing of session form inputs to one place in page generation (closing form tag)--to minimize read/write time.
- Rework form validation and merge with BOLTwire's internal filtering system.
- Rename session to command.
Revise directory structure
/boltwire
/boltwire/system
/boltwire/system/scripts
/boltwire/system/pages
/boltwire/shared
/boltwire/shared/pages (this is new)
/boltwire/shared/plugins (or scripts)
/boltwire/shared/images
/boltwire/shared/public
/boltwire/shared/looks (or skins, themes)
/site
/site/config
/site/files
/site/indexes
/site/pages
/site/stamps
- Remove math (php4) from core and simplify counter. Add a php5 plugin (the latter with try catch).
- Have all page names end in .txt for security purposes.
Software
Possible Future Features- Have a safemode feature for superadmins so only system files are used?
- Get member vars handled by BOLTvars function, drop separate markup rule
- Fully nestable conditionals. Perhaps like tables?
- Eliminate BOLT from BOLTconfig variables. Make config variables hierarchical. Perhaps a script for centralized default config values.
- Use an optional English language files for messages, delete site.messages. Remove all message "text" from core. Alternately, have site.messages.language.
- Rework BOLTprocess to allow two way variables to be sent to it, and insert various hooks into the BOLTsavepage / BOLTloadpage functions.
- Some kind of automatic system for support of external skin style sheets. Caching?
- Improve searching so can check for strings, patterns, etc, and display them highlighted. Use a match conditional and a context function, perhaps.
- Loosen vars markups so can do {p{p0}}
- Rework backup command/plugin so that lastmodified's can be checked, and only changed pages backed up.
- A BOLTstripHTML function... Perhaps also a BOLTstripMarkup function
- Allow single hyphens in indexing.
- Allow -id, -@group in site auth pages to create banlists. As in all member except Bob.
- Develop an inrange conditional, which could be used for blacklist ip blocking features.
- Make BOLTmemberships and BOLTadmin as arrays, rather than csv lists.
- Add @othergroup syntax to groups, or perhaps some limited markups.
- Things Won't be doing
- Make groups that can create forms configurable
- Make pages displayed as code configurable
- Default skin folder, not system pages, in case code.skin gets deleted.
- Add boolean search operators to "find" similar to "search"
- Carefully evaluate all url/utf conversions and try and keep everything within BoltWire consistently utf except as absolutely needed.
- Check that message box doesn't display in skin pages.
- Check for problems with nested ordered/unordered bullets.
- Check undo and history on code pages.
- Have a box skin for popups, like help
- Spruce up action.join for default groups and id's when specified as get values. Add action.join to action bar. Perhaps a plugin?
- One click login/logout?
- Math plugin for php4/php5 (the latter with try catch)