TBS 3.2.0 Release Candidate 1

The 3.2.0rc1 is now available for download.
Feel free to try it.

-------------

-> Fixed bugs:

* Bad HTML attribute reading when glued to bottom of tag.
  Example: <input value="xxx"/> attribute value was read as xxx"/
  Note that this is way of coding an attribute is not
  conform to the XML/XHTML syntax.

* When parameter "block=_" was put at the very beginning of a
  line, next line was added to the block.

-> Changes:

* Some Error message arranged to be clearer.

* The date format for parameter 'frm' support only (") as a string
  protector. Character (') is not a string protector for date format anymore.
  That was non sense anyway because (') is the string protector
  for TBS parameters yet.

-> New features

* TBS tags [onload.x] merges the global variable $x on LoadTemplate.
  (normal [var] fields are merged on Show).

* [var..cst.MY_CONSTANT] merges the constant MY_CONSTANT.

* If a file is not found (when defined in method LoadTemplate or parameters
  file and script) then it is quietly searched in the folder of the last
  loaded template.

* Several ope parameters are allowed.
  Example : [var.x;ope=add:10,mod:2]

-------------

Download :
http://www.tinybutstrong.com/download/download.php?file=tbs_beta.zip&sid=2

Hi SKrol29

Thanks for a new release!!!

I ran it against all of my test apps (the same ones used when testing 3.1.x series) and got NO probs !!!!

Will begin test of new featues next.

Great guns, thanks again for all your fine work.
TomH

BTW - have you given any more thoughts to being able to show the plugin version numbers from var..version  ;-)

Great.. Ill download to try . Thanks

> BTW - have you given any more thoughts to
> being able to show the plugin version numbers from var..version  ;-)

I can add a feature that display TBS version plus all installed plug-in (names and version). Does it sound goog for you ?

That is great - I will like it!!!

For backward compatibility -  please consider creating new variable name (not using var..version name)

Maybe also consider sending TinyLetter for 3.2.0rc1 and also for plugin version upgrades in future.

Why [var..cst.MY_CONSTANT] for merges the constant MY_CONSTANT. [cst.MY_CONSTANT] will not be better ?

thanks
Olivier

> Why [var..cst.MY_CONSTANT] for merges the
> constant MY_CONSTANT. [cst.MY_CONSTANT] will not be better ?

Hi Olivier,

Having constants through [cst.*] fields would require that both [cst.*] and [var.*] are searched within the template and also within some specific TBS parameters (file, script, if, then, ...). This will cause a cost for double check.

The interest of [var..*] fields is that they are preccessed in the same flow that [var.*] fields.

Great! A new toy~