« Return to Thread: Request for feedback: moving Zend.php to Zend/Zend.php
Re: Request for feedback: moving Zend.php to Zend/Zend.php
by Ralph Schindler
::
Rate this Message:
Bill Karwin wrote:
> Please take a look at http://framework.zend.com/issues/browse/ZF-958
>
> We propose to move Zend.php to <zf-home>/library/Zend/Zend.php. The
> class name would continue to be 'Zend', and we're not suggesting
> changing any methods within the class. Therefore no usage of this class
> would change.
>
> The only change in your application would be that you need to change
> this:
>
> require_once 'Zend.php';
>
> To this:
>
> require_once 'Zend/Zend.php';
Massive -1 on this unless we decided to tackle some issues that have
been raised in the past:
1) Zend class is very schizophrenic when it comes to its duty.
a) it does loading of things which are possibly better suited
for a Zend_Loader
b) it does registry tasks that could better be implemented as
static get/set/has/remove methods of Zend_Registry.
c) it does dumping which would better exist inside Zend_Debug
d) it has an exception method that has no business there anymore
2) deployment: svn:externals IMO, is not the desired method of
distribution. SVN, simply put, is a repository tool for the development
of code, not the distribution of code/complete solution.
Furthermore, I am not so much a fan of an exception to the rule class
without a very strong reason. If we do wish to remove Zend.php (which I
am totally OK with since it by itself offers very little on its own..
even as 'glue'), perhaps it would be better suited as Zend/Framework.php
To me 'Framework' implies 'glue', and this would remove it from the main
directory.
If we offer this class/file as the glue to the framework, or, first file
someone is told to use in a bootstrap, I would hate to have that first
class a would-be ZendFramework user viewing be an 'exception to the
rule'... That off the bat, seems like bad form, and puts out the
perception that this framework favors lax practices over rigid
structure. Rigid structure being a good thing for people to know what
to expect and where to expect it in this 'library'.
Thoughts?
> If there are no strong objections, I'll make this change.
Consider this my strong objection.. unless someone can enlighten me a
bit... I've been known to come around :)
> Regards,
> Bill Karwin
> Please take a look at http://framework.zend.com/issues/browse/ZF-958
>
> We propose to move Zend.php to <zf-home>/library/Zend/Zend.php. The
> class name would continue to be 'Zend', and we're not suggesting
> changing any methods within the class. Therefore no usage of this class
> would change.
>
> The only change in your application would be that you need to change
> this:
>
> require_once 'Zend.php';
>
> To this:
>
> require_once 'Zend/Zend.php';
Massive -1 on this unless we decided to tackle some issues that have
been raised in the past:
1) Zend class is very schizophrenic when it comes to its duty.
a) it does loading of things which are possibly better suited
for a Zend_Loader
b) it does registry tasks that could better be implemented as
static get/set/has/remove methods of Zend_Registry.
c) it does dumping which would better exist inside Zend_Debug
d) it has an exception method that has no business there anymore
2) deployment: svn:externals IMO, is not the desired method of
distribution. SVN, simply put, is a repository tool for the development
of code, not the distribution of code/complete solution.
Furthermore, I am not so much a fan of an exception to the rule class
without a very strong reason. If we do wish to remove Zend.php (which I
am totally OK with since it by itself offers very little on its own..
even as 'glue'), perhaps it would be better suited as Zend/Framework.php
To me 'Framework' implies 'glue', and this would remove it from the main
directory.
If we offer this class/file as the glue to the framework, or, first file
someone is told to use in a bootstrap, I would hate to have that first
class a would-be ZendFramework user viewing be an 'exception to the
rule'... That off the bat, seems like bad form, and puts out the
perception that this framework favors lax practices over rigid
structure. Rigid structure being a good thing for people to know what
to expect and where to expect it in this 'library'.
Thoughts?
> If there are no strong objections, I'll make this change.
Consider this my strong objection.. unless someone can enlighten me a
bit... I've been known to come around :)
> Regards,
> Bill Karwin
« Return to Thread: Request for feedback: moving Zend.php to Zend/Zend.php
| Free embeddable forum powered by Nabble | Forum Help |
