Re: [zeta-dev] Welcome Apache Zeta Components - SVN up and running :)

2010-08-24 Thread James Pic
On Mon, Aug 23, 2010 at 6:21 PM, Gaetano Giunta
giunta.gaet...@gmail.com wrote:
  Tobias Schlitt wrote:

 [...]

 To give you an impression, what we need to do, here a brain dump:

 - - Investigate which open issues need to be transfered
 - - Assign component maintainaners (volunteers?)


I'm (maybe the only one) interrested in UserInput, if you'll assign me
to it then i'll take for mission to help it evolve into a more
complete and cool component for convenient form development.

Regards

-- 
http://jamespic.com/contact
Customer is king - Le client est roi - El cliente es rey.


Re: [zeta-dev] Piwi and ZC (was: Re: [zeta-dev] Re: Class prefix change, was: Re: [zeta-dev] Welcome Apache Zeta Components - SVN up and running :))

2010-08-19 Thread Christian Grobmeier
 sounds interesting. We already started discussing a framework
 component a longer time ago in eZ Components. This component was meant
 to provide integration for the components, like scaffolding scripts.
 Having a complete framework on basis of Zeta would be a step in a
 similar direction.

if you ask me, ZC is very good because you know what it is. Looking at
f. e. Cocoon which has way to much faces i always felt it does to
much. However, if you like the framework - we are willing to let
people in. One of our drawbacks is that we are a small team :-)

On the other hand, PIWI does to much - f. e. we have implemented a
small DI container. Its pretty easy and fine, but basically it would
fit more at ZC than in a webframework. A webframework should only
provide classes which are necessary for webworking. If there is no DI
container in ZC, Piwi could contribute such a component to ZC

 OK would like to hear you opinions on the prefix change.

 We discussed this issue before actually proposing Zeta to the ASF in the
 round which is the PMC today. I can fully understand your arguments in
 favor of a class prefix change. However, we decided against. Of course,
 if the community desires it, we can have a vote again on this issue, but
 I doubt any of the PMCs will vote for a change.

Thats not a problem, justed wanted to know what the status is. I
wanted to avoid to start with efford and then break everything up
because of class prefix change.

 However, I don't see it the last chance to make a change. One day, we
 will be in the need of releasing 2.0 versions of our components and I
 don't see this step too far away (maybe a year?), since PHP 5.3
 establishes more and more. With this step, we can switch directly from a
 class prefix to namespaces, which would actually render this change
 superfluous.

+1

Thanks for the info!
Christian


Re: [zeta-dev] Re: Class prefix change, was: Re: [zeta-dev] Welcome Apache Zeta Components - SVN up and running :)

2010-07-31 Thread Jerome Renard
Hello,

On Sat, Jul 31, 2010 at 6:31 PM, Tobias Schlitt tob...@schlitt.info wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi Andreas,

 On 07/31/2010 05:15 PM, Andreas Schamberger wrote:

  for me it seems wrong if I think 'zeta' and have to type 'ezc'. But
  maybe this is just a problem for me ;)

 I fully understand your concern here and I would still be in favor of
 changing the prefix. However, there should be way of full BC for this
 and until now we did not find any.

 Maybe, we will come to a point where we start building Zeta 2.0 somewhen
 in the future. The we should migrate to using namespaces anyway and the
 issue will be fixed.

  I just wanted to have raised my concern. I'll shut up and let's forget
  about it ;)

 I think it was quite useful having this discussed publicly again. :)


Both options (keeping and updating the ezc prefix) have both pro and cons
and as far as I am concerned
I have no preference. However I think it is important not to confuse ZC
users and as such I would recommend to
provide some kind of FAQ explaining why the prefix is ezc for now, and what
are (of any) plans for the future.
Maybe a full page explaining the history of ZC, from eZ Components to Zeta
Components would help clarify
the context for new users. I can write such a page if you want.

Confused users became generally unhappy user after some period users, and
that we should definitely try to avoid.

What do you think ?

My 0.02 cents,

-- 
Jérôme Renard
http://39web.fr | http://jrenard.info