On 3/16/10, Markus <[email protected]> wrote:
> On Mar 16, 1:41 pm, The Editor <[email protected]> wrote:
>
> > * Added a wildcard search feature allowing you to search for
> > text=bolt* and match words like BoltWire!
>
> Wow, that was fast. Thanks. Next time I'll ask for something more
> challenging like regular-expression search and replace on-site.
Actually, on my version of TREE, I have that already, though it may
not be on the publically available plugin. Of course, in the core you
already have:
[(find group=test* regex=/.../)]
You can also have it look for all the instances of a certain markup
rule by markup=order:rule or even string='some string'
If you fed that through a template with a function that did a simple
replace--you are good to go. I just warn you--it is very slow. For
this reason, I'm likely to remove this function from the core and make
it a plugin instead. BOLTcms will almost surely have a full powered
tree module included.
> 3.4.7:
>
> 1) Visit "site" and have a look at the bullets.
I think I have that fixed now. Just a slight change in the box markup...
> 2) I get pages of whitespace above this table:
>
> [t]
> [(search fmt="[r][c][[{+p}|+]]")]
> [t]
It seems when the <div class=search> feature is removed this works
properly. Seems I'm now mostly just removing hacks that are no longer
needed. That's a VERY good sign...
> PS: As blues I wonder if a default search class is of any benefit.
My real reason for introducing this was to solve a linespacing problem
with templates and fmts displaying differently. All Blues arguments
against it were valid, and evidently some of the other things we've
fixed along the way solved the original problems. So this feature is
now gone. :)
--
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.
