[TYPO3-ect] Voting: Classnames for BETA

[Johnny Peck]

+1  -- I agree completely with Joerg on this.  I have not seen anyone 
really bring up this issue as to whether 5.0 should be such a focus for 
lib/div.  Migration for those that use lib/div will be simpler than for 
any other simply because we are using strong enough OO patterns for 
development by using the libraries.  We would also very likely wish to 
adjust our extensions anyhow to take advantage of improvements 
introduced by 5.0.  Attempting to create an aura of migration to 5 via 
lib/div may be short sighted since we have no verified public release of 
such and we have been misplacing the point that our use of lib/div in 
the first place is to use better programming practices anyhow, which 
*should* be commonplace when developing or migrating to TYPO3 5.0 anyhow.

I also don't want to change too much of my current work code to comply 
with Beta though I will if needs be.  I honestly like the class.*.php 
way and am not really that excited about the 5.0 naming though I am sure 
I can get used to it just fine.  Let's keep to 4.0 guidelines as we all 
know 4.0 will be far more prevalent than 5.0 for quite some time and 
very likely for years. I would, as a new dev on an entrenched project, 
rather read a short guideline for 4 rather than dealing with another 
that takes into account a completely different code base.  I won't be 
waiting more than a short moment to move to 5 but I can hardly believe 
how many admins are still running 3.8 or older but we need to consider 
that.  If something works, don't mess with it.  If you want to work with 
5.0 you will need to refactor a bit and that is nothing new for anyone 
on this list.  Auto-loading with lib/div for 4.x should follow 4.x 
guidelines.  Lib/div in 5.0 should follow with 5.0 guidelines.  5.0 is 
the spirit of T3 moving forward, not the code, hence the name Phoenix.

Anyhow, +1 for Ingo and Joerg!  Sorry for the winded post I just had to 
get it out.

Aloha

Johnny

ps.  Aerosmith is coming to Maui!  Hopefully I can get a ticket and they 
don't sell out too quickly.  Aloha!

Joerg Schoppet wrote:
> Hi,
> 
> so after a night of thinking about it I have to correct my vote to the
> third one (Ingo).
> 
> Reasons:
> After reading Roberts mail "TYPO3 5.0 and lib/div...", looking at the
> actual code of TYPO3 5.0 and seeing the complains from Ingo I think the
> following:
> 
> Actually, lib/div are TYPO3 4 extensions, which helps ext-developers to
> use a lot of strong oo-pattern within there extensions. Even if TYPO3 5
> will be out (somewhen in the future) the 4-branch will be alive for a
> long time (IMHO). At this moment we have an extrem high count of
> extensions in TER, even if only 50% are "meaningful", it will be a huge
> task until only a small part of extensions will be available for 5.
> Also, as Robert mentioned, and everybody can see in the code: The code
> of 5 will not have so much similarities with the code of 4.
> In 5 there will be a lot of the features, actually provided by lib/div,
> provided by the core.
> 
> So the big question for me is, will lib/div be necessary for 5?
> 
> At the moment, I can not say! But it will be clear, that *EACH*
> extension needs a rewrite. Important, for myself, is, that developers
> learn from lib/div, how to program in an oo way (the concepts). Because
> if the concepts are clear and understandable it will be easy for people
> to move there extensions to 5 (in a conceptual way).
> 
> Naming Guidelines are necessary and because there are naming guidelines
> for 4, I would use for the actual lib/div these naming guidelines.
> 
> 
> Regards
> 
> Joerg
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFGzS8vq5Me6rRDqPURAg8KAJ4516ycTpTSJVM0Wd7XavX3z76QxQCfYY+S
> ANhRC+89u90W4UT8wkp9E7o=
> =i7hr
> -----END PGP SIGNATURE-----