[TYPO3-english] tesseract

Robert Wildling rowild at gmx.net
Wed May 7 07:41:45 CEST 2014


Thank you, François! Great news to read!!

Am 06.05.14 16:43, schrieb François Suter:
> Hi Nico,
>
>> Only one (fundamental) question: can you please help me
>> (and others) by briefly explaining the difference(s) with e.g. wfqbe.
>
> The main difference is that Tesseract is directed at querying the 
> TYPO3 database, whereas wfqbe aims at displaying data from external 
> databases. If you try to query TYPO3 tables with wfqbe it is quite 
> some work because you have to add all the enable field conditions 
> yourself and I don't think that it manages languages overlays either 
> (disclaimer: I haven't looked at wfqbe in ages, so things may have 
> changed in that regard; Mauro can certainly tell more).
>
> Tesseract is also very flexible because it is made of components 
> instead of being a single big extension. So what I said above is not 
> exactly true ;-) Extension "dataquery" is designed to query the TYPO3 
> database. It will handle all enable fields, language and version 
> overlays for your, even if you write SQL queries with JOINs (it does 
> quite a bit of magic in the background). But you could write an 
> extension which queries another database and feeds its results in the 
> same display mechanisms (of which there are three, each packaged as 
> separate extension; one uses "traditional" TYPO3 marker templates, one 
> uses Fluid and one straight PHP). There exists one other such "data 
> provider", extension "googlequery" which gathers data from a Google 
> Search Appliance or Google Site Search.
>
> Extension "datafilter" provides a very flexible filtering system. It 
> can take values from many sources (GET/POST, TypoScript, etc.) and 
> transfer them as conditions to the data providers. Each provider then 
> transforms those abstract conditions into the syntax they use (so 
> "dataquery" will transform the conditions to SQL, for example).
>
> HTH
>



More information about the TYPO3-english mailing list