I'm exploring other possibilities as well for change. I'm particularly
looking for functions/commands that work in weird or arcane ways. Or
don't really get much use. The more we can trim BoltWire down to the
most common simple straightforward functions, the better. For
example:
The data function allows you to set certain prescribed data fields on
a page using a function. Clever. But once that code is put on the
page, it tells BoltWire to resave the data variable every time it
loads the page. Highly inefficient. I think there might be some
isolated uses for it, but at the very least it could be shunted off to
a plugin or something don't you think?
What about the getline function, which allows you to retrieve line 7
of some.page? Do we really need that? I thought it was a system
function, but it doesn't seem to be used anywhere else in the code.
Possibly an action page though I can't imagine which one. Shouldn't
this be a plugin as well?
There's also a thread function. I'm not sure it is really necessary in
the core. We already have the page.# shortcut, and therefore as a
result, never really use the function form. It might be useful, but
hardly essential. I think perhaps we should move this function to a
plugin.
Overwrite and zones are also rarely used, but they do come in handy
for specific actions: plugins and zones respectively. So I guess we
will have to keep them in there. Similarly, nocache and touch, are
used in the caching system. And therefore probably should stay in the
core. Other than these four and the three mentioned above, I think the
rest are all well used and highly functional.
The commands look a little better. Nothing there too much to worry
about. We have the touch command of course, and would possibly need to
add a math command if we split the counter function into math and
counter.
I see no major changes in the conditions worth making (adding or subtracting),
Looking over the markups page I see some possibilities for improvement:
* Snippets perhaps should be in the pre group rather than vars, much
like embed is
* The various vars patterns could be rewritten so that the member vars
shortcut could be processed by BOLTvars, easily enough.
* Is anyone using wikiwords? I'd personally just as soon eliminate
support for it. Simplifies the code and goes against our strategy of
making everyrthing case insensitive. We could also put the pattern in
a plugin if we desired--just we would lose case insensitivity.
* Can't the headers pattern be rewritten so they don't need the
leading line return. Something like (not tested)
/(.*\<\;)?(!{1,6})(.*)/me'
* Can't we reduce the indent rules into one rule? Esp now that we are
requiring them to be at the beginning of a line. Should be easy
enough.
* Do we want to include hyperlinks in the bolt styles function. After
all, we already have styles allowed in regular [[links]]
There are also some awkward looking patterns, regarding bullets,
styles, spacing and lines, etc., but they are the best I can come with
at the moment. And no desire to go back in and try to rework them.
Well so much for thinking out loud. Feedback welcome...
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
-~----------~----~----~----~------~----~------~--~---
