On 19. aug. 2010, at 13.40, Christian Grobmeier wrote:
> Hello,
>
> a friend of mine and I wrote a framework together. I have the strong
> feeling that PIWI should be based on ZC in near future since it offers
> solutions for much problems we have. Additionally ZC can help PIWI to
> concentrate
On Mon, Aug 23, 2010 at 6:21 PM, Gaetano Giunta
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 on
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?)
db and dbschema, if there are none other yet
bye
Gaetano
Hello everyone,
On Thu, 2010-08-19 at 13:40 +0200, Christian Grobmeier wrote:
[...]
> However I would like to know if there has been a decision meanwhile on
> the prefix issue (see below). I would like to avoid to include ZC
> before this change has been done, if it is going to happen.
>
> My pre
> 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.
Christian,
On 08/19/2010 01:40 PM, Christian Grobmeier wrote:
> a friend of mine and I wrote a framework together. I have the strong
> feeling that PIWI should be based on ZC in near future since it offers
> solutions for much problems we have. Additionally ZC can help PIWI to
> concentrate on it
Hello,
a friend of mine and I wrote a framework together. I have the strong
feeling that PIWI should be based on ZC in near future since it offers
solutions for much problems we have. Additionally ZC can help PIWI to
concentrate on its maingoal. Maybe there is a chance to pull out a few
classes, l
Tobias,
On Mon, Aug 2, 2010 at 10:30 AM, Tobias Schlitt wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jerome,
> [...]
>
> > 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 im
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 08/01/2010 07:24 PM, Derick Rethans wrote:
> On Sat, 31 Jul 2010, Tobias Schlitt wrote:
>> I think that such a process is a good idea. Providing full requirements
>> and design documentation up front is not always possible and indeed
>> repres
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jerome,
On 07/31/2010 06:53 PM, Jerome Renard wrote:
> On Sat, Jul 31, 2010 at 6:31 PM, Tobias Schlitt wrote:
>> 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'.
On Sat, 31 Jul 2010, Tobias Schlitt wrote:
> I think that such a process is a good idea. Providing full requirements
> and design documentation up front is not always possible and indeed
> represents a quite high barrier for new contributions.
However, providing the idea and what you're trying to
Hello,
On Sat, Jul 31, 2010 at 6:31 PM, Tobias Schlitt 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
-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
chang
Hi,
for me it seems wrong if I think 'zeta' and have to type 'ezc'. But
maybe this is just a problem for me ;)
I just wanted to have raised my concern. I'll shut up and let's forget
about it ;)
Regards,
Andreas
Am 31.07.2010 16:46, schrieb Tobias Schlitt:
-BEGIN PGP SIGNED MESSAGE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 07/31/2010 04:44 PM, Piotrek Karas wrote:
> W dniu 2010-07-31 15:02, Andreas Schamberger pisze:
>> creating a successful new brand zeta components in my opinion also
>> requires to change the prefix even if causes some migration pain.
> Maybe
W dniu 2010-07-31 15:02, Andreas Schamberger pisze:
Hi,
creating a successful new brand zeta components in my opinion also
requires to change the prefix even if causes some migration pain.
Maybe giving the old prefix a new meaning could be an easier and safer
approach? For example: Enterpris
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 07/31/2010 03:02 PM, Andreas Schamberger wrote:
> creating a successful new brand zeta components in my opinion also
> requires to change the prefix even if causes some migration pain.
I don't see where the class prefix does much harm here. W
You can also call static function by :
call_user_func( "ezcClassName::myFunc" );
2010/7/31 Andreas Schamberger
> Hi,
>
> creating a successful new brand zeta components in my opinion also requires
> to change the prefix even if causes some migration pain.
>
> Am 31.07.2010 13:36, schrieb Tobia
It could also be a good opportunity to get some working code (not
necessarily responding to zc standards) from people or companies who want to
share.
The component it self can be an aggregate of all those peaces of code.
Max
2010/7/31 Tobias Schlitt
> -BEGIN PGP SIGNED MESSAGE-
> Hash:
Hi,
creating a successful new brand zeta components in my opinion also
requires to change the prefix even if causes some migration pain.
Am 31.07.2010 13:36, schrieb Tobias Schlitt:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 07/31/2010 12:57 PM, Andreas Schamberger wrote:
1) I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 07/31/2010 12:57 PM, Andreas Schamberger wrote:
> 2) Incubation: Maybe it would be a good idea to have some kind of
> incubation process for new components that must not fully comply with all
> (quality) requirements yet. This would maybe lowe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 07/31/2010 12:57 PM, Andreas Schamberger wrote:
> 1) I'm not so happy with keeping the ezc prefix. As far as I recall it
> wasn't really considered to change the class prefix to zeta. Ok the
> reasoning is valid but wouldn't this big step of m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Andreas,
thanks for your input.
On 07/31/2010 12:57 PM, Andreas Schamberger 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 maintain
Hi,
great news :)
> 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?)
> - - Discusss future release process
> - - Start fixing bugs
> - - Make a first official release :)
On Sat, 2010-07-24 at 13:00 +0200, Tobias Schlitt wrote:
> - - Investigate which open issues need to be transfered
I would volunteer to maintain Document & Graph - since I am the main
developer of them anyways…
Kind regards,
Kore
--
Kore Nordmann(GPG 0xDD
Hi Tobias,
On Sat, Jul 24, 2010 at 1:00 PM, Tobias Schlitt wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ladies and gentlemen,
>
> I'm proud to announce that our new SVN space is up and running under
>
>https://svn.apache.org/repos/asf/incubator/zetacomponents/
>
> Now tha
On Sat, Jul 24, 2010 at 1:00 PM, Tobias Schlitt wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ladies and gentlemen,
>
> I'm proud to announce that our new SVN space is up and running under
>
>
Great job! Congrats ;)
- - Investigate which open issues need to be transfered
> - - Ass
Hello,
great news and thanks for the hard work on this Tobias!
Christian
On Sat, Jul 24, 2010 at 1:00 PM, Tobias Schlitt wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ladies and gentlemen,
>
> I'm proud to announce that our new SVN space is up and running under
>
> https:/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ladies and gentlemen,
I'm proud to announce that our new SVN space is up and running under
https://svn.apache.org/repos/asf/incubator/zetacomponents/
Now that the code is finally dropped, we may (and even must) call
ourselves "Apache Zeta Co
29 matches
Mail list logo
