headers
VINCENT-ROYOL Philippe | 2 Apr 2010 14:01
Picon
Favicon

addClassRepository problem.

Hi dear community,

 

                I cant find where my fault is.. I would like to load eZCompents classes and some external classes files.

Directories look like this :

 

./classes/myclass.php

./classes/autoload/my_autoload.php

./lib/eZComponents/

./lib/autoload.php

./index.php

 

On ./lib/autoload.php i wrote :

 

require_once "./lib/eZComponents/Base/src/base.php";

 

ezcBase::addClassRepository( './classes' );

/** Autoload classes **/

function __autoload( $className ) {

        ezcBase::autoload( $className );

}

 

On ./classes/autoload/my_autoload.php :

 

return array (

                'myclass' => '../classes/myclass.php',

        );

 

And on index.php i call ./lib/autoload.php. It works with eZComponents classes, but cant find my own classes .. Someone could help me please ?

 

Thanks

Philippe

<div><div class="WordSection1">
<p class="MsoNormal">Hi dear community,<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I cant find where my fault is.. I would like to load eZCompents classes and some external classes files.<p></p></p>
<p class="MsoNormal">Directories look like this&nbsp;:<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><span>./</span><span>classes/myclass.php<p></p></span></p>
<p class="MsoNormal"><span>./classes/autoload/my_autoload.php<p></p></span></p>
<p class="MsoNormal"><span>./lib/eZComponents/≤p></p></span></p>
<p class="MsoNormal"><span>./lib/autoload.php<p></p></span></p>
<p class="MsoNormal"><span>./index.php<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>On ./lib/autoload.php i wrote&nbsp;:<p></p></span></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><span>require_once "./lib/eZComponents/Base/src/base.php";<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>ezcBase::addClassRepository( './classes' );<p></p></span></p>
<p class="MsoNormal"><span>/** Autoload classes **/<p></p></span></p>
<p class="MsoNormal"><span>function __autoload( $className ) { <p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ezcBase::autoload( $className );<p></p></span></p>
<p class="MsoNormal"><span>}<p></p></span></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">On ./classes/autoload/my_autoload.php&nbsp;:<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><span>return array (<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 'myclass' =&gt; '../classes/myclass.php',<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; );<p></p></span></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">And on index.php i call ./lib/autoload.php. It works with eZComponents classes, but cant find my own classes .. Someone could help me please&nbsp;?<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Thanks<p></p></p>
<p class="MsoNormal">Philippe<p></p></p>
</div></div>
Permalink | Reply | 2 comments |
headers
Maxime Thomas - Wascou | 2 Apr 2010 16:50
Favicon

Re: addClassRepository problem.

Hi,

It's seems that this fonction excepts the name of the autoload file to autoload.php and not my_autoload.php.

Max


2010/4/2 VINCENT-ROYOL Philippe <p.vincent-royol-QVQq/ah98mc@public.gmane.org>

Hi dear community,

 

                I cant find where my fault is.. I would like to load eZCompents classes and some external classes files.

Directories look like this :

 

./classes/myclass.php

./classes/autoload/my_autoload.php

./lib/eZComponents/

./lib/autoload.php

./index.php

 

On ./lib/autoload.php i wrote :

 

require_once "./lib/eZComponents/Base/src/base.php";

 

ezcBase::addClassRepository( './classes' );

/** Autoload classes **/

function __autoload( $className ) {

        ezcBase::autoload( $className );

}

 

On ./classes/autoload/my_autoload.php :

 

return array (

                'myclass' => '../classes/myclass.php',

        );

 

And on index.php i call ./lib/autoload.php. It works with eZComponents classes, but cant find my own classes .. Someone could help me please ?

 

Thanks

Philippe


--
Components mailing list
Components-p125XxirBjMXWF+eFR7m5Q@public.gmane.org
http://lists.ez.no/mailman/listinfo/components


<div>
<p>Hi,<br><br>It's seems that this fonction excepts the name of the autoload file to autoload.php and not my_autoload.php.<br><br>Max<br><br><br></p>
<div class="gmail_quote">2010/4/2 VINCENT-ROYOL Philippe <span dir="ltr">&lt;<a href="mailto:p.vincent-royol@...">p.vincent-royol@...</a>&gt;</span><br><blockquote class="gmail_quote">
<div link="blue" vlink="purple" lang="FR"><div>
<p class="MsoNormal">Hi dear community,</p>
<p class="MsoNormal">
&nbsp;</p>
<p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I cant find where my fault is.. I would like to load eZCompents classes and some external classes files.</p>
<p class="MsoNormal">Directories look like this&nbsp;:</p>
<p class="MsoNormal">
&nbsp;</p>
<p class="MsoNormal"><span>./</span><span>classes/myclass.php</span></p>
<p class="MsoNormal"><span>./classes/autoload/my_autoload.php</span></p>
<p class="MsoNormal"><span>./lib/eZComponents/≤/span></p>
<p class="MsoNormal"><span>./lib/autoload.php</span></p>
<p class="MsoNormal">
<span>./index.php</span></p>
<p class="MsoNormal"><span>&nbsp;</span></p>
<p class="MsoNormal"><span>On ./lib/autoload.php i wrote&nbsp;:</span></p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">
<span>require_once "./lib/eZComponents/Base/src/base.php";</span></p>
<p class="MsoNormal"><span>&nbsp;</span></p>
<p class="MsoNormal">
<span>ezcBase::addClassRepository( './classes' );</span></p>
<p class="MsoNormal"><span>/** Autoload classes **/</span></p>
<p class="MsoNormal"><span>function __autoload( $className ) { </span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ezcBase::autoload( $className );</span></p>
<p class="MsoNormal"><span>}</span></p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">On ./classes/autoload/my_autoload.php&nbsp;:</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">
<span>return array (</span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 'myclass' =&gt; '../classes/myclass.php',</span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; );</span></p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">And on index.php i call ./lib/autoload.php. It works with eZComponents classes, but cant find my own classes .. Someone could help me please&nbsp;?</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal">Thanks</p>
<p class="MsoNormal">Philippe</p>
</div></div>
<br>--<br>
Components mailing list<br><a href="mailto:Components@...">Components@...</a><br><a href="http://lists.ez.no/mailman/listinfo/components" target="_blank">http://lists.ez.no/mailman/listinfo/components</a><br><br>
</blockquote>
</div>
<br>
</div>
Permalink | Reply | 1 comment |
headers
VINCENT-ROYOL Philippe | 2 Apr 2010 16:54
Picon
Favicon

Re: addClassRepository problem.

xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">

Was just an error . thanks to Eirik :

 

Quote :

Shouldn't the autoload file be called ./classes/autoload/autoload.php instead of ./classes/autoload/my_autoload.php?

Philippe

 

De : maxime.thom-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [mailto:maxime.thom-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org] De la part de Maxime Thomas - Wascou
Envoyé : vendredi 2 avril 2010 16:51
À : VINCENT-ROYOL Philippe
Cc : components-p125XxirBjMXWF+eFR7m5Q@public.gmane.org
Objet : Re: [Components] addClassRepository problem.

 

Hi,

It's seems that this fonction excepts the name of the autoload file to autoload.php and not my_autoload.php.

Max

2010/4/2 VINCENT-ROYOL Philippe <p.vincent-royol-QVQq/ah98mc@public.gmane.org>

Hi dear community,

 

                I cant find where my fault is.. I would like to load eZCompents classes and some external classes files.

Directories look like this :

 

./classes/myclass.php

./classes/autoload/my_autoload.php

./lib/eZComponents/

./lib/autoload.php

./index.php

 

On ./lib/autoload.php i wrote :

 

require_once "./lib/eZComponents/Base/src/base.php";

 

ezcBase::addClassRepository( './classes' );

/** Autoload classes **/

function __autoload( $className ) {

        ezcBase::autoload( $className );

}

 

On ./classes/autoload/my_autoload.php :

 

return array (

                'myclass' => '../classes/myclass.php',

        );

 

And on index.php i call ./lib/autoload.php. It works with eZComponents classes, but cant find my own classes .. Someone could help me please ?

 

Thanks

Philippe


--
Components mailing list
Components-p125XxirBjMXWF+eFR7m5Q@public.gmane.org
http://lists.ez.no/mailman/listinfo/components

 

<div>
<p> xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"&gt;</p>
<div class="WordSection1">
<p class="MsoNormal"><span>Was just an error&nbsp;. thanks to Eirik&nbsp;:<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>Quote&nbsp;:<p></p></span></p>
<p class="MsoNormal">Shouldn't the autoload file be called <span>./classes/autoload/autoload.php</span> instead of <span>./classes/autoload/my_autoload.php?<br><br></span><span><p></p></span></p>
<p class="MsoNormal"><span>Philippe<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>De&nbsp;:</span><span> maxime.thom@... [mailto:maxime.thom@...] De la part de Maxime Thomas - Wascou<br>Envoy&eacute;&nbsp;: vendredi 2 avril 2010 16:51<br>&Agrave;&nbsp;: VINCENT-ROYOL Philippe<br>Cc&nbsp;: components@...<br>Objet&nbsp;: Re: [Components] addClassRepository problem.<p></p></span></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Hi,<br><br>It's seems that this fonction excepts the name of the autoload file to autoload.php and not my_autoload.php.<br><br>Max<br><br><p></p></p>
<div>
<p class="MsoNormal">2010/4/2 VINCENT-ROYOL Philippe &lt;<a href="mailto:p.vincent-royol@...">p.vincent-royol@...</a>&gt;<p></p></p>
<div><div>
<p class="MsoNormal">Hi dear community,<p></p></p>
<p class="MsoNormal">&nbsp;<p></p></p>
<p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I cant find where my fault is.. I would like to load eZCompents classes and some external classes files.<p></p></p>
<p class="MsoNormal">Directories look like this&nbsp;:<p></p></p>
<p class="MsoNormal">&nbsp;<p></p></p>
<p class="MsoNormal"><span>./classes/myclass.php</span><p></p></p>
<p class="MsoNormal"><span>./classes/autoload/my_autoload.php</span><p></p></p>
<p class="MsoNormal"><span>./lib/eZComponents/≤/span><p></p></p>
<p class="MsoNormal"><span>./lib/autoload.php</span><p></p></p>
<p class="MsoNormal"><span>./index.php</span><p></p></p>
<p class="MsoNormal">&nbsp;<p></p></p>
<p class="MsoNormal">On ./lib/autoload.php i wrote&nbsp;:<p></p></p>
<p class="MsoNormal">&nbsp;<p></p></p>
<p class="MsoNormal"><span>require_once "./lib/eZComponents/Base/src/base.php";</span><p></p></p>
<p class="MsoNormal"><span>&nbsp;</span><p></p></p>
<p class="MsoNormal"><span>ezcBase::addClassRepository( './classes' );</span><p></p></p>
<p class="MsoNormal"><span>/** Autoload classes **/</span><p></p></p>
<p class="MsoNormal"><span>function __autoload( $className ) { </span><p></p></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ezcBase::autoload( $className );</span><p></p></p>
<p class="MsoNormal"><span>}</span><p></p></p>
<p class="MsoNormal">&nbsp;<p></p></p>
<p class="MsoNormal">On ./classes/autoload/my_autoload.php&nbsp;:<p></p></p>
<p class="MsoNormal">&nbsp;<p></p></p>
<p class="MsoNormal"><span>return array (</span><p></p></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 'myclass' =&gt; '../classes/myclass.php',</span><p></p></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; );</span><p></p></p>
<p class="MsoNormal">&nbsp;<p></p></p>
<p class="MsoNormal">And on index.php i call ./lib/autoload.php. It works with eZComponents classes, but cant find my own classes .. Someone could help me please&nbsp;?<p></p></p>
<p class="MsoNormal">&nbsp;<p></p></p>
<p class="MsoNormal">Thanks<p></p></p>
<p class="MsoNormal">Philippe<p></p></p>
</div></div>
<p class="MsoNormal"><br>--<br>Components mailing list<br><a href="mailto:Components@...">Components@...</a><br><a href="http://lists.ez.no/mailman/listinfo/components" target="_blank">http://lists.ez.no/mailman/listinfo/components</a><p></p></p>
</div>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
</div>
Permalink | Reply | 0 comments |
headers
Piotrek Karas | 4 Apr 2010 02:46
Picon
Favicon

eZC CodeSniffer coding standard

Hello,

Is there a CodeSniffer coding standard for eZ Components? If so, is it 
publicly available? Gaetano mentioned it here:
http://share.ez.no/forums/developer/php-codesniffer-vs-ez-publish
but the conversation didn't move on...

Thanks,
Piotrek
Permalink | Reply | 1 comment |
headers
Raul Mateos | 9 Apr 2010 09:27
Picon
Gravatar

Adding custom text to graphs

Hello!

I'm trying to add a custom text in some graphs. There is any way to do
that with the current version? If so, how to set where to put the
text.

Thanks in advance,

Raul
Permalink | Reply | 0 comments |
headers
Piotrek Karas | 11 Apr 2010 08:14
Picon
Favicon

Implementation guidelines: properties, internal properties etc.

Hello,

I've got a few questions that may be a bit lame - hope it's OK.

I'm writing a couple of PHP "components" internally for our purposes. 
First I thought they would be just independent groups of classes, 
nothing to it, but then I thought maybe following the eZComponents way 
would be a good thing (especially for I will use or extend few of them). 
So I dove into the implementation guidelines 
(http://www.ezcomponents.org/contributing/coding_standards), most of 
which is very clear and helpful.

However, what I don't quite grasp is the distinction between internal 
properties following traditional getXxx()/setXxx() pattern, and "just" 
properties, for which the magic methods __get()/__set/__isset() are used 
and which operate on $properties property.

Could someone explain (or point to some deeper source):

1) What is/was the rationale behind this separation? I think I 
understand technical consequences, but I fail to see the reasons... The 
guidelines say: "The implementation of the properties happens in the 
__set() and __get() magic methods to allow value bounds checking and 
access control.". Wouldn't that be possible with traditional getters and 
setters? I would be grateful for some example illustration here.

2) What method of deciding which would become an internal property and 
which would become $properties[$name] would you recommend? Any golden 
rule here?

3) Is there any way of making IDE to see/hint which $properties are 
available or is it completely out of reach with this architecture?

4) Also, is this how inheritance is achieved with the $properties?

<?php
class classWithFirstProperty
{
     protected $properties = array();

     public function __set( $name, $value )
     {
         switch ( $name )
         {
             case 'firstProperty':
                 $this->properties[$name] = (string) $value;
                 break;

             default:
                 throw new ezcBasePropertyNotFoundException( $name );
                 break;
         }
     }

     public function __get( $name )
     {
         switch ( $name )
         {
             case 'firstProperty':
                 $this->properties[$name] = (string) $value;
                 break;

             default:
                 throw new ezcBasePropertyNotFoundException( $name );
                 break;
         }
     }
}

class classWithSecondProperty extends classWithFirstProperty
{
     protected $properties = array();

     public function __set( $name, $value )
     {
         switch ( $name )
         {
             case 'secondProperty':
                 $this->properties[$name] = (string) $value;
                 break;

             default:
                 parent::__set( $name, $value );
                 break;
         }
     }

     public function __get( $name )
     {
         switch ( $name )
         {
             case 'secondProperty':
                 $this->properties[$name] = (string) $value;
                 break;

             default:
                 parent::__get( $name );
                 break;
         }
     }
}

$twoPropertyObject = new classWithSecondProperty();
$twoPropertyObject->firstProperty = 123;
$twoPropertyObject->secondProperty = 456;
?>

Would that be correct?

5) Would you recommend to stick with eZC way? Why? Why not?

I would be grateful for any help or suggestions regarding these topics.

Cheers,
Piotrek
Permalink | Reply | 2 comments |
headers
Piotrek Karas | 11 Apr 2010 08:34
Picon
Favicon

Re: 2010 roadmap

James Pic wrote:
> On Mon, Feb 8, 2010 at 11:19 AM, Piotrek Karas 
> <p.karas.lists@...
<mailto:p.karas.lists@...>> wrote:
> 
> 
>>     I wonder what that means in terms of eZ Components as a product - will
>>     that seize to exist on its own (or in other words: outside of being part
>>     of future eZ Publish)? What do you think?
> 
> 
> eZ Components is used in other projects than eZ Publish like Arbit 
> tracker, Jetfuel framework or WCV to name some open source ones.
> 
> That said, can you define/elaborate *technically* the concept "seizing 
> to exist on its own (outside of being part of future eZ Publish)"?
> 
> Regards
> 

Hello James, hello all,

Maybe I didn't express myself clearly. More what I meant was whether
will eZ Components be still developed as a project kind of independent*
from eZ Publish, with its own dedicated team, roadmap, new components
added gradually? Or will they be more likely to be lead by future 
versions of eZ Publish, and not much further?

The major technical difference would be whether new components keep 
showing up and evolve and are maintained, even if eZ Publish won't 
require them, or will the development of new stuff be limited to what eZ 
Systems need for their products.

Unless I am missing something, both ways seem possible and reasonable to 
me. Please let me know what do you think about it, even if I am just 
mumbling ;)

This thing might have been discussed or explained during latest 
conference and meetings, unfortunately I missed those...

BTW. Any update on the 2010 roadmap?

* - I wrote kind of independent because as far as I know eZC were to 
become the building blocks for eZ Publish and other solutions. However, 
they seem a very stable and independent project/product today.

Cheers,
Piotrek
Permalink | Reply | 1 comment |
headers
Kristof Coomans | 11 Apr 2010 09:15
Picon
Favicon
Gravatar

Re: Implementation guidelines: properties, internal properties etc.

Hi Piotrek

On Sun, Apr 11, 2010 at 8:14 AM, Piotrek Karas
<p.karas.lists@...> wrote:
> Hello,
>
> I've got a few questions that may be a bit lame - hope it's OK.
>
> I'm writing a couple of PHP "components" internally for our purposes.
> First I thought they would be just independent groups of classes,
> nothing to it, but then I thought maybe following the eZComponents way
> would be a good thing (especially for I will use or extend few of them).
> So I dove into the implementation guidelines
> (http://www.ezcomponents.org/contributing/coding_standards), most of
> which is very clear and helpful.
>
> However, what I don't quite grasp is the distinction between internal
> properties following traditional getXxx()/setXxx() pattern, and "just"
> properties, for which the magic methods __get()/__set/__isset() are used
> and which operate on $properties property.
>
> Could someone explain (or point to some deeper source):
>
> 1) What is/was the rationale behind this separation? I think I
> understand technical consequences, but I fail to see the reasons... The
> guidelines say: "The implementation of the properties happens in the
> __set() and __get() magic methods to allow value bounds checking and
> access control.". Wouldn't that be possible with traditional getters and
> setters? I would be grateful for some example illustration here.
>
> 2) What method of deciding which would become an internal property and
> which would become $properties[$name] would you recommend? Any golden
> rule here?
>
> 3) Is there any way of making IDE to see/hint which $properties are
> available or is it completely out of reach with this architecture?
>
> 4) Also, is this how inheritance is achieved with the $properties?
>
> <?php
> class classWithFirstProperty
> {
>     protected $properties = array();
>
>     public function __set( $name, $value )
>     {
>         switch ( $name )
>         {
>             case 'firstProperty':
>                 $this->properties[$name] = (string) $value;
>                 break;
>
>             default:
>                 throw new ezcBasePropertyNotFoundException( $name );
>                 break;
>         }
>     }
>
>     public function __get( $name )
>     {
>         switch ( $name )
>         {
>             case 'firstProperty':
>                 $this->properties[$name] = (string) $value;
>                 break;
>
>             default:
>                 throw new ezcBasePropertyNotFoundException( $name );
>                 break;
>         }
>     }
> }
>
> class classWithSecondProperty extends classWithFirstProperty
> {
>     protected $properties = array();
>
>     public function __set( $name, $value )
>     {
>         switch ( $name )
>         {
>             case 'secondProperty':
>                 $this->properties[$name] = (string) $value;
>                 break;
>
>             default:
>                 parent::__set( $name, $value );
>                 break;
>         }
>     }
>
>     public function __get( $name )
>     {
>         switch ( $name )
>         {
>             case 'secondProperty':
>                 $this->properties[$name] = (string) $value;
>                 break;
>
>             default:
>                 parent::__get( $name );
>                 break;
>         }
>     }
> }
>
> $twoPropertyObject = new classWithSecondProperty();
> $twoPropertyObject->firstProperty = 123;
> $twoPropertyObject->secondProperty = 456;
> ?>
>
> Would that be correct?
>
> 5) Would you recommend to stick with eZC way? Why? Why not?
>
>
> I would be grateful for any help or suggestions regarding these topics.
>
> Cheers,
> Piotrek
> --
> Components mailing list
> Components@...
> http://lists.ez.no/mailman/listinfo/components
>
>

Hi Piotrek

To answer 3), there is a  <at> property tag which is supported by most
IDE's, See http://manual.phpdoc.org/HTMLSmartyConverter/PHP/phpDocumentor/tutorial_tags.property.pkg.html

The other questions I leave to those more familiar with the eZ
Components guidelines ;)

Best regards

Kristof
--

-- 
Components mailing list
Components@...
http://lists.ez.no/mailman/listinfo/components
Permalink | Reply | 0 comments |
headers
Piotrek Karas | 11 Apr 2010 09:22
Picon
Favicon

Re: Implementation guidelines: properties, internal properties etc.

Kristof Coomans wrote:
> Hi Piotrek
> 
> To answer 3), there is a  <at> property tag which is supported by most
> IDE's, See http://manual.phpdoc.org/HTMLSmartyConverter/PHP/phpDocumentor/tutorial_tags.property.pkg.html
> 
> The other questions I leave to those more familiar with the eZ
> Components guidelines ;)
> 
> Best regards
> 
> Kristof
> 

Hello Kristof,

Thanks a lot - works like a charm!

Cheers,
Piotrek
Permalink | Reply | 0 comments |
headers
James Pic | 14 Apr 2010 11:18
Picon
Gravatar

Re: 2010 roadmap

On Sun, Apr 11, 2010 at 8:34 AM, Piotrek Karas
<p.karas.lists@...> wrote:
>
> * - I wrote kind of independent because as far as I know eZC were to
> become the building blocks for eZ Publish and other solutions. However,
> they seem a very stable and independent project/product today.
>

It is stable, with i guess a total active user base of ~20-25 persons.

Many eZ Component users reinvent the same things: auth/profile
applications, schema migration tools, production commands, form
configuration stuff .... IMHO it would be much easier to pass the 100
active users if new users would not have to reinvent what previous
users made. This would allow eZC to grow at the same rhythm as its
active user base.

Regards

James

--

-- 
http://jamespic.com/contact
Customer is king - Le client est roi - El cliente es rei.
Permalink | Reply | 0 comments |

Gmane