[TYPO3-project-formidable] XML version check against installed version

[Jerome Schneider]

Hi Adrian,

Yes, minVersion and maxVersion act effectively like the EM's constraints.

It would be excellent to have this version information in the reference 
for each feature. I'll have a look to see what can be done to determine 
this.


Greetings from Strasbourg,
Jerome

Adrian Föder a écrit :
> Hi Jerome,
> 
> would it then be possible to omit one of the both minVersion and 
> maxVersion tags?
> I think one kind of version definition element should be mandatory to 
> force the version check to work. That means the developer of an 
> Formidable XML has to take care for what version his work is intended or 
> at least to declare which version the XML is developed against.
> 
> With minVersion and maxVersion, you think about some kind of the 
> ext_emconf's "constraints", right?
> 
> 
> If the version check is implemented, it would be very nice to add an 
> information at the XML reference 
> (http://formidable.typo3.ug/reference.html) where is noted from what (or 
> until, when obsolete) version the respective element works.
> 
> Best,
> 
> adrian
> 
> 
> Jerome Schneider wrote:
>> Hi Adrian,
>> That's a good idea, and you'll have such a feature in revision 2.0.319 
>> and above.
>>
>> one may now define /minVersion="X.XX.XXX" and /maxVersion="X.XX.XXX" 
>> on the /formidable xml-tag
>> if a condition is not met, Formidable displays a mayday screen
>>
>> I think that it's better to use new tags than the /version one to 
>> avoid future version-locking. So that if the XML has to be tied to a 
>> specific range of Formidable version, he'll have the ability to do so, 
>> but by default it will be executed anyway.
>>
>> What do you think ?
>>
>> Jerome
>>
>> Adrian Föder a écrit :
>>> Hi there @all,
>>>
>>> I just ran into "indiscoverable non-functionality" when gambling with 
>>> some examples from the web page.
>>> The simple reason was: I didn't have the version installed that the 
>>> example was made for. The required version stands in the root element 
>>> "formidable", e.g.
>>>
>>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>>> <formidable version="2.0.296">
>>>
>>> </formidable>
>>>
>>> Wouldn't it be useful when the formidable engine throws a mayday or 
>>> something like this when it discovers a version string newer then the 
>>> installed one?
>>>
>>>
>>> [AND: I'm, as you surely already noted, new to the project, so please 
>>> excuse when there is a bugtracker available where such feature 
>>> requests should better be posted or it has already been. The BT @ 
>>> bugs.typo3.org has the project "formidable", but it seems a bit 
>>> outdated and not really used...]
>>>
>>>
>>> Thank you very much and
>>> have a nice weekend!
>>>
>>> -adrian
>> _______________________________________________
>> TYPO3-project-formidable mailing list
>> TYPO3-project-formidable at lists.netfielders.de
>> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-project-formidable 
>>
>>
>>