Thank you rob for your answer.
1) For documentation, I was meaning that a complete identical structure is better, even if for some plugins, topics are 'NA' or do not need samples. (it's also a roadmap for people completing the wiki)
Today, even for senior developpers (like me : C, C++, C#, ...) it's
really hard to get into Fabrik, because you don't see clearly :
- for what, some objects are really intended to,
- the logic of Fabrik
I'm really believing Fabrik is the killing CCK, but since I watch it for 2 years, I didn't get concrete results, compared to regular Joomla Components !
A great documentation topic would be : an 'application life cycle' explaining (ex : for your contact sample), all the logical steps :
- database design / List & Elements
- plugins logic and IN/OUT parameters, PHP specific treatments
- Forms
- How to have contextual form elements
- How to template
With a such 'roadmap' everybody should then understand how to adapt it to its needs.
I'm sorry, but today I'm still in the fog and ask stupid basic questions in forums, as I don't know
the best way to implement things (Fabrik is rich)...
2) For MySQL, I was meaning 5.1 needed by Joomla 3. (I edit it in my posts)
My problem is that my hoster has updates that works only on their original distribution. Unix experts advised me to stay like this,
as I do not want to spent my time on Unix administration. As I'm alone on my projects,
I want to focus on web and Joomla.
And soon my hoster will have a new version, so I wait (and Joomla 3 is not too mature)...
3) For my J2.5/F3.0.8 problems, I'm really stucked with this one :
http://www.fabrikar.com/forums/index.php?threads/return-pb-in-php-validation-plugin.35340/
Regards