[TYPO3-project-formidable] New SVN revision 160

[Jerome Schneider]

Hi Manuel,

Yes actually, performance problems were reported as formidable was 
loaded at *each* load, no matter if it was used or not; so by removing 
auto-loading we gained some cpu cycles :)

This change makes it a little longer to instanciate, but you can cut 
thru efforts using the PATH_formidableapi constant.

Like this: require_once(PATH_formidableapi);


PS: There are a lot of changes that happened, and I think a lot will in 
the future. We're always trying to ensure back-compat whenever it's 
possible.

Jerome


Manuel Rego Casasnovas a écrit :
> Hello,
> 
> another question about new revision.
> 
> I've noticed that since revision 149 [1], the line 86 in
> "ext_localconf.php" has been commented:
> //require_once(PATH_formidable . 'api/class.tx_ameosformidable.php');
> 
> With this change I have to make a "require_once" for each file in witch
> I want to create a FORMidable form (call to t3lib_div::makeInstance). At
> least, I have to make a "require_once= for each extension that I want to
> use FORMidable.
> 
> I think that if I have ameos_formidable installed, it's because I'm
> gonna to use FORMidable in some extension, and I'm gonna to create some
> FORMidable forms.
> 
> Any reason for this change? Is it the correct way or is better the previous?
> 
> Best regards,
>    Rego
> 
> [1]
> http://formidable.svn.sourceforge.net/viewvc/formidable/ext_localconf.php?revision=149&view=markup
>