Another pretty big release. Few new features--but lot's of bug fixes and
performance tweaks. I'd definitely upgrade if you are on an earlier version
of 4.xx. We're pretty close to the end of this development cycle.
Cheers,
Dan
>From the changelog:
- Changed <embed script> into a function, ie <(embed script)>, with the
advantage we drop one markup rule. I also fixed so I can insert parameter
like {+arg1} into the script via the function call. Very useful. It should
also recognize vars like {+p} and {+id} as well.
- I also decided to drop the new form command as I can use the include
function, with a small change to allow insertion of fields from the include
parameters, ie: {+field}.
- Finally decided what to do with the stash command: drop it. :) Can do
[(info field=id value='one | two')], or [(log 'field: one | two' page=)].
Hopefully this feature is new enough it won't affect too many people.
- Did some tinkering on the translation system to improve performance.
Ended up rewriting it and re-adding a translate function. Allows for the
following (note the cases): [(translate yellow fr)] => jaune [(translate
YELLOW language=fr)] => JAUNE [(translate Jaune language=fr reverse=true)]
=> Yellow. Still not promising languages are working fully on 4.xx. Haven't
really tested. No doubt the language packs will need to be updated.
- Did some hopefully transparent changes under the hood to improve
performance of the search function, esp when if statements are used. Won't
go into the details here, but let me know if you notice anything strange,
as something may have been broken in the process.
- Spent some time reworking the session system on the site, after
discovering some session information was not being cleared properly.
Finally got it working beautifully.
- Discovered an easy way to allow multiple commands with the same name,
ie: [command if ...][command if ...] rather than [command if_1 ...][command
if_2 ...]. I just got BoltWire to rename duplicate commands for you,
automatically. Note {=field} replacements will require you to use the
correct name--which could give you a good headache. That is, [command
source somevar][command source somevar2][command id {=source}] will bring
in somevar. You will need to use {=source_1} to get in the second one, and
{=source_2} to get a third if it existed. Still, it helps more than it
confuses things! Won't affect site already using commands like if_1 or if_2.
- Reworked the stopwatch feature. Set $BOLTstopWatch to true in
index.php and you'll get a nice report showing how long the entire page
takes to load, times for each zone. Helpful in tracking down drags on your
site. (I need to document better how those times are calculated: beginning
times for each zone are relative to the start, end times are time in each
zone. Some functions have nested times, etc).
- Finally got the auto indexing to work after the page is flushed from
the server so there's no lag time.
- Set the default to not show headers on action pages. To restore them,
put actionHeaders: true in site.config.
- Changed the BOLTargs function to allow parameter names with hyphens,
and another small change. Let me know if you notice any side effects.
- Slight tweak to how the default view action works, so can see the
action in the url for enhance possibilities.
- Significant number of small bug fixes here and there...
--
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/boltwire.
For more options, visit https://groups.google.com/d/optout.
