[Typo3-dev] ObTS ready.

[dan frost]

> Fatal error: Call to undefined function: cobjgetsingle() in
> /var/www/testsite/typo3conf/ext/obts/tslib_content/class.tslib_cobj_stdwrap.php
> on line 1062
> 

Probably related to the piece of undisclosed, essential information: 
this is for version 3.6.. Sorry.

I'll double check this error asap.

> 
> 1. A little while ago I read something about a special TypoScript-editor
> and I realised that it would be VERY great if it could automatically show
> which properties/methods are available on the 'selected' object. This
> ObTS-thing could really assist with that, but I thought it would be wise
> to choose unique classnames then:
>>From a 'auto-complete'-point-of-view it's currently hard to tell if you're
> working on a TEXT-object in a PAGE-object, or in a TEXT-object in a
> GIFBUILDER-object. Maybe now is the time to change these classnames so
> that all image-builder-classes (gifbuilder is not very apropriate anymore
> too...) are prefixed with IMG_ or something. (The current IMG_TEXT would
> have to be renamed too I guess.)
> 
> What do you all think about this?
> 

Auto-complete, prompts for available function names, properties, 
datatypes and so on are all possible and relatively simple of ObTS.

I will, now be able to come of the snowboard tour and plan to demo how 
this is possible.

> 2. Typo can ultimately be used to generate not just HTML, but also e.g.
> WAP-pages. How could such a thing be implemented?
> One way would be to call something like setupWML() instead of setupHTML().
> I don't really need this functionality though, just being curious :)
> 
You don't need a setupWML() - you (or, rather I) just need to 
implement a better setupHTML() and perhaps rename it setupML() or 
setupOUT().

Basically, setupHtml() uses an API to a mark-up rendering objects. 
This class knows nothing about any particular mark-up/XML; that is, it 
know only about make well-formed xml, not valid (right way round, i 
think).

To implement another xml, you could do:
(a) Use setupHtml() as usual
(b) have a "mapping" function which maps between different xml. This 
works on the result of setupHtml() and is this on a per-datatype basis.

Or, (b) could happen at the mark-up rendering level. I'm not sure 
which is best yet, but will try a few.

> Thanks for ObTS!
You're welcome. Enjoy.

P.s. I am going to launch a site on how ObTS works - it makes it a bit 
easier to understand. Also, i'll add each API/program flow to it over 
time.

dan