Le 01/08/2010 14:27, Tarjei a écrit :
Hi, as with my other answer, I've been on vacation so apologies for a
late reply.
On 12 Jul, 10:47, Fabien Potencier<fabien.potenc...@symfony-
project.com> wrote:
On 7/11/10 1:17 PM, Tarjei wrote:
Hi, here are my initial questions and comments regarding Symfony2.
Wow, that's a lot of feedback! Thank you very much. My answers below..
1. Deployment.
Are you planning a .phar deployment solution where the src directory
gets bundled up as a .phar file and distributed to the server? Have
you though through the different deploments scenarios for bundles?
Possibly. Packaging and distribution is something we will take care of
late in the Symfony2 timeline as this orthogonal to everything else.
One thing that I now see as an issue is that the console command
should be able to install pear packages into the application somehow
so that they live in a local installation and not as something that
comes with your operating system. This is because you want to be able
to install and maintain different combinations of PEAR/phar packages
for different applications.
3. Names
The console command should start with a letter that no other directory
in the same directory starts with. I.e. not console and config as that
would reduce the number of redundant hits to tab.
Any idea?
I've tried to come up with something better. One solution could be to
use a large C (i.e. Console) or maybe S2 or just symfony/Symfony. If
you keep the command local, there is no reason why it shouldn't be
named the same as the old symfony command - maybe shorten it to symf2
or something to make them appear differently to google.
Another issue is that console has so many other meanings (if I saw the
command w/o context I would have thought it opened a terminal or
something) that it is a bit confusing.
Also, I find the separation of templates into Resources/views a bit
strange. Templates are a very important part of every webapplication
and should be easier to find- I.e. they should have a toplevel
directory in a bundle.
The reasonning behind this decision is to put all non-classes into one
directory (the Resources/ directory). It contains templates, config
files, assets, ...
Hmm I can understand that - still. Hmm, I guess this is a bikeshed
issue so I'll shut up :)
<(snip)>
Regarding Symfony2 vs symfony, one thing I've been thinking about is
that instead of having a migration system from 1.4 to 2, maybe it
would be easier to create a plugin that lets you use bundles and S2
applications within existing symfony applications. This will make it
possible for developers to write most of their applications to be
ready for 2.0 while still using 1.4.
Maybe should you prefer writing a bundle for using symfony 1.4 plugins
and controllers inside Symfony2, to, after the release of Symfony2,
allow developpers to slowly move from 1.4 to 2.0. But I believe it's not
so easy as saying it, so I believe it's not a priority. And a plugin in
1.4 to use Symfony2's bundles is much more difficult, maybe as difficult
as coding S2. So I believe the other way is better :)
Thanks to both you and the others replying to my questions and
comments. I'm looking forward to the next codedrop :)
Kind regards,
Tarjei Huse
Thank you for having read,
Ekinox
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
