Re: [fw-general] Establishing naming conventions for Zend Framework 2.0

[Jan Pieper]

+1

already waiting a long time for something like that :)

-- Jan

-- Xavier Vidal Piera <[EMAIL PROTECTED]> wrote
(on Tuesday, 20 May 2008, 11:35 AM +0200):

+1

But please, when will be done, publish a list of changed names in order to do a
carefully search & replace

Any BC changes in 2.0 will (a) need to be well-justified (I think this
one falls in that category), (b) have documentation regarding the nature
of the change, and (c) hopefully also include a script or Zend_Tool
provider for aiding the migration (for instance, finding all instances

of an old class name in your code and renaming).

On Tue, May 20, 2008 at 11:30 AM, Julian Davchev <[EMAIL PROTECTED]> wrote:

    +10 from me.

    I like this + thingy :)

    Ben Scholzen 'DASPRiD' wrote:

        -----BEGIN PGP SIGNED MESSAGE-----
        Hash: SHA1

        +1 from me as well.

        A break of backward compatibility in a major released is acceptable.

        Jurriën Stutterheim schrieb:

            +1 from me too.

            A proposal for this would be great : )

            Op Di, mei 20, 2008 10:05 schreef Mathew Byrne:

                +1


                Backwards compatibility aside coming up with a more consistent
                naming
                scheme would be a massive boon for Zend Framework. We've
                already got rules
                for how names are constructed, now for some guidelines as to
                the semantics
                of ZF component names.

                --
                Mathew Byrne
                http://www.matbyrne.com/



                On May 20, 2008, at 2:00 PM, Matthew Ratzloff wrote:

                    This seems like a perennial issue for me, but I'm bringing
                    it up
                    again because I think it's worthwhile.

                    Since the beginning of this project, there hasn't really
                    been much
                    in the way of direction given on naming standards for
                    classes in Zend
                    Framework. This lack of consistency is what has yielded two
                    nomenclatures for CLI components ("Zend_Console" vs.
                    "Zend_Controller_Response_Cli"), differing terms for
                    similar
                    concepts ("Zend_Json_Decoder" vs. "Zend_Mime_Decode"), both
                    nouns and
                    verbs in equal measure ("Zend_Loader" but not
                    "Zend_Translator";
                    alternately, "Zend_Translate" but not "Zend_Load"), and so
                    on.

                    I first brought this issue up in February 2007 and
                    concluded,
                    "Consistency means predictability, which means being able
                    to recall
                    names without having to check the manual every time. It's
                    why most people
                    can't use PHP's date or string functions without looking at
                    the
                    documentation, for example."

                    There was a lot of agreement from the community (and a
                    couple
                    Zenders) but no movement because the framework was
                    preparing for
                    1.0.  At the time I was told, "There is life after 0.9.0,"
                    and so as
                    we prepare for 2.0, I think it's the perfect time to
                    revisit this.

                    -Matt

        - --
        ...................................
        :  ___   _   ___ ___ ___ _ ___    :
        : |   \ /_\ / __| _ \ _ (_)   \   :
        : | |) / _ \\__ \  _/   / | |) |  :
        : |___/_/:\_\___/_| |_|_\_|___/   :
        :........:........................:
        : Web    : http://www.dasprids.de :
        : E-mail : [EMAIL PROTECTED]       :
        : Jabber : [EMAIL PROTECTED]     :
        : ICQ    : 105677955              :
        :........:........................:
        -----BEGIN PGP SIGNATURE-----
        Version: GnuPG v1.4.6 (GNU/Linux)
        Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

        iD8DBQFIMpGI0HfT5Ws789ARAgiXAKCZ9ZmPhl+2uolK5yuhtgpMy6duawCgpBg0
        NDNwsoTRDMyNpVOQCUrzgyE=
        =vKfs
        -----END PGP SIGNATURE-----

--
Xavier Vidal Piera
Enginyer Tècnic Informàtic de Gestió
Tècnic Especialista Informàtic d'equips
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://web.xaviervidal.net
610.68.41.78