Plans for next versions of TinyButStrong

I'm currently working on TBS 2.02.
Contents of this version is not yet defined, but here are the points I'm working on.

---------
fea = new feature
bug = bug to fix
tec = technical enhancement
---------

[fea] multiformat available for dates (zero, null)
Status: done, tested

[bug] script='...' => protection should be set to False
Status: done, to test

[tec] $OriginalVal reviewed
Status: done, to test

[fea] htmlconv=js => convert to a JavaScript string
Status: done, to test

[bug] selected=tag doesn't work with attributes ID and NAME uppercase
Status: done, to test

[bug] selected=tag doesn't support embeded tags (ex : td will be cut on next </td>)
Status: to do

[fea] allow OpenChr and CloseChr with several char (example : '{{' '}}')
Status: still on study
Notes: it's ok for OpenChr, but CloseChr will cost time execution

[bug] GetBlockSource() and $DetailSrc delete Block Defition Tags
Status: work not yet evaluated

[bug] CacheAction() returne always false with TBS_DELETE.
Status: to do

[fea] protect even CharSet=false
Status: work not yet evaluated

[fea] support hierarchical display
Status: work not yet evaluated
Notes: big, but nice

[fea] magnet='+1c'  => deleted one char before (value can change)
Status: to do

[fea] magnet='+att' => deleted the attribut which embeds the tag (value can change)
Status: to do

[fea] htmlconv='esc2' and 'esc3', for (') and (")
Status: to do
Notes: really useful?

[fea] sub-cache for a block
Status: to do

[fea] TBS_CACHEGETAGE, TBS_CACHEGETFILENAME, TBS_CACHEISONSHOW
Status: to do

[fea] parameter 'when' for merged blocks
Status: to do
Notes:  difficulte because of time optimization

[fea] option to make MergeBlock() to display data on the fly
Status: to study

[fea] htmlspecialchar() without htmlentities()
Status: to study

[fea] frm='upper','lower','proper'
Status: to study
Notes: can be done by native database functions

yeaj for the Javascript string conversion. I asked for it ages ago :D

[fea] htmlconv='esc2' and 'esc3', for (') and (")
I don't get this one. Isn't that what the javascript conversion is going to do?

At first thougth it could be useful for some script languages, but I think you're rigth: it can be useless if we have htmlconv=js.

you could allways name the js conversion differently as it is not js specific. I guess it will also work for java and c like languages??

But on the other hand; since tbs is confined to HTML and browsers js might be a good name anyway ;)
(What does vb-script need for strings?)

Isn't vb-script dead?

don't know, I do not use it :P

But I suppose that when you are coding in asp you might extend vb-scripts into the HTML.

Like I said, js is probably not a bad name ;)

Make "max" close the last tag inside block.

<p>Results like this don't validate XHTML 1.0, XHTML 1.1, etc...

What you think about this feature?

tbs works on html specifying/being the block delimiters. If your blocks are wrong, what would tbs do??

It depends on what's wrong.
If there is no closing tag after the openning tag, then there's a TBS error message.
If there's a closing tag after the openning tag, but corresponding to another opening tag, then TBS doesn't notice the problem and take the bad tag.

True.

Tag validation in a XHTML content is a "pre-TBS" issue.

If TBS used some DOM methods then tbs would know (and be a lot slower as well I think)

it would be good if printer friendly link is also available.

DT

> it would be good if printer friendly link is also available.

I agree Deependra. I was working on a none framed version of this forum. But I will continue after the TBS 3.00 release.