[TYPO3-ect] first clone of lib...

[Elmar Hinz]

Hi all,

for me it is a pleasure, to find a clone of lib. It shows how recognized
lib/div already is, while it is still marked as alpha. That's good
publicity.

Rene Nitzsche has different extensions in TER that use the library. He
couldn't build public extensions upon an alpha version. Could he? The
initial version is from 07-02-20, when lib wasn't much progressed.

http://typo3.org/extensions/repository/view/rn_base/0.0.1/info/ChangeLog/


Franz Koch wrote:

> 
> great - why does everybody think his private favors have to be shared in
> TER? Nothing against redesigning lib for private use - but why rubbish
> the TER with that crap.

Well, Rene could have shared his ideas with us in NG and wiki. But his main
idea is to get a smaller library. Could we downsize lib? I fear not.

His way of downsizing the complexity, did not really work. He still depends
on those objects of lib he tried to "optimize" away. Example: 

$this->_dataStore = new tx_lib_spl_ArrayObject(); 

in

http://typo3.org/extensions/repository/view/rn_base/0.0.3/info/class.tx_rnbase_configurations.php/

(Lib will drop the selfmade SPL objects, when disabling PHP4.)

Either you provide a naked controller or you provide a full framework.
Everything in between can't be satisfying. But a framework we can only
maintain as a community.

> Another indication that the average TYPO3 community isn't one at all,
> because everybody is cooking his own meal and is not able to think about
> some more corners for a greater plan.
> 

That's right. Cooperation takes a lot of time. It's a time expensive hobby.
People without time for a lot of coordination have the choice to contribute
something or contribute nothing. We have to improve the framework, in that
the single contributions automatically make the great plan. That's why a
working culture of "extending extensions" is needed. 

http://wiki.typo3.org/index.php/MVC_Framework/Extending_Extensions

Instead of many incompatible extensions, this should result in ONE
organically growing tree of extensions. 

http://wiki.typo3.org/images/c/cd/ECT-libDiv-extendingExtensions.png

We need to come to this culture.

> But this is no fault of the ECT - in my eyes it is more a false
> communication by the association - or let's better say of TYPO3 in
> general. Besides of the newsgroups, there is no real worldwide community
> of TYPO3 - only some small 'self-help-script-kiddy-groups' in certain
> countries that are not a part of a common community, are not moderated
> by association-members that teach a needed 'TYPO3 codex' or whatever.
> The documentation and information for newbies is not the best and
> doesn't teach them a hardly needed community sense in a easy way.
> 

When ECT has lib up and stable, people will listen, when we teach codex and
standards. It's called authority by competence.

Things only can be done, if there is motivation and qualification. More
community needs organization, organization is work and work needs a
befitting payment/motivation. TYPO3 isn't a community of event managers.

Little self-help-groups live because of few organizational work.
Big communities like churches live because of enough members that pay
professional organizers. The difficult size is in between. I see no easy
way.

A good motor to build community is a successfull project. Each project has a
natural size of members. A good project needs a vision. A network of
project groups is one part of the answer. The answer I can give.

> Also the extension developing tutorials don't teach such a attitude (as
> far as I can remember).

Hmm, for me contributing to TER is already an attitude. It's needs an
improvement of the system. Extending extensions. :-)

http://wiki.typo3.org/index.php/MVC_Framework/Extending_Extensions

Regards

Elmar