librelist archives

« back to archive

Photon Apps Naming Proposal

Photon Apps Naming Proposal

From:
Loic d'Anterroches
Date:
2011-06-01 @ 10:35
Hello,

just a short remark. At the moment, I implicitely considered that a
Photon application is within a one level deep folder/namespace.

For example, the namespace \myapp with \myapp\views the views namespace.

What I propose is that one can use any level. For example:

\ceondo\myapp
\ceondo\whatever\fooapp

Of course, it means that the fooapp views are in the file:
ceondo/whatever/fooapp/views.php and the folder ceondo somewhere in
folder available in the PHP include_path.

The goal is - as you can read in the examples - to be able to have your
own kind of "private" namespace for you and your company and to avoid
the creation of "ceondo_myapp" apps which I find ugly.

What do you think about it? I like the idea to be able to "import/use"
any app as long as the app is available in the PHP include path.

loïc

--
Indefero - Project management and code hosting - http://www.indefero.net
Photon - High Performance PHP Framework - http://photon-project.com
Céondo Ltd - Web + Science = Fun - http://www.ceondo.com

Re: [photon.users] Photon Apps Naming Proposal

From:
Nicolas
Date:
2011-06-03 @ 10:51
Hello,

Sorry for the late answer...

Having several levels of depth for namespaces would be useful for bigger
apps, and it doesn't prevent people from using a single-level depth on
smaller ones. So yes, I'm all for it :)

Cheers.
Nicolas




On Wed, Jun 1, 2011 at 12:35 PM, Loic d'Anterroches <loic@ceondo.com> wrote:

> Hello,
>
> just a short remark. At the moment, I implicitely considered that a
> Photon application is within a one level deep folder/namespace.
>
> For example, the namespace \myapp with \myapp\views the views namespace.
>
> What I propose is that one can use any level. For example:
>
> \ceondo\myapp
> \ceondo\whatever\fooapp
>
> Of course, it means that the fooapp views are in the file:
> ceondo/whatever/fooapp/views.php and the folder ceondo somewhere in
> folder available in the PHP include_path.
>
> The goal is - as you can read in the examples - to be able to have your
> own kind of "private" namespace for you and your company and to avoid
> the creation of "ceondo_myapp" apps which I find ugly.
>
> What do you think about it? I like the idea to be able to "import/use"
> any app as long as the app is available in the PHP include path.
>
> loïc
>
> --
> Indefero - Project management and code hosting - http://www.indefero.net
> Photon - High Performance PHP Framework - http://photon-project.com
> Céondo Ltd - Web + Science = Fun - http://www.ceondo.com
>

Re: [photon.users] Photon Apps Naming Proposal

From:
Mehdi Kabab
Date:
2011-06-02 @ 14:04
Hello,

I'm in 100%.

I like the idea of not having to increase the locations of my applications
shared across multiple projects. I simply add the directory to the include
path to enjoy all the applications it contains, for my various projects.

--
Mehdi Kabab

My french book about Gimp: http://gimp4you.eu.org/livre/
Blog: http://pioupioum.fr/
Twitter: http://twitter.com/piouPiouM

Le 1 juin 2011 à 12:35, Loic d'Anterroches a écrit :

> Hello,
> 
> just a short remark. At the moment, I implicitely considered that a
> Photon application is within a one level deep folder/namespace.
> 
> For example, the namespace \myapp with \myapp\views the views namespace.
> 
> What I propose is that one can use any level. For example:
> 
> \ceondo\myapp
> \ceondo\whatever\fooapp
> 
> Of course, it means that the fooapp views are in the file:
> ceondo/whatever/fooapp/views.php and the folder ceondo somewhere in
> folder available in the PHP include_path.
> 
> The goal is - as you can read in the examples - to be able to have your
> own kind of "private" namespace for you and your company and to avoid
> the creation of "ceondo_myapp" apps which I find ugly.
> 
> What do you think about it? I like the idea to be able to "import/use"
> any app as long as the app is available in the PHP include path.
> 
> loïc
> 
> --
> Indefero - Project management and code hosting - http://www.indefero.net
> Photon - High Performance PHP Framework - http://photon-project.com
> Céondo Ltd - Web + Science = Fun - http://www.ceondo.com

Re: [photon.users] Photon Apps Naming Proposal

From:
Loic d'Anterroches
Date:
2011-06-02 @ 14:08
Good.

I kindly ask you not to use the \ceondo namespace :)

On 2011-06-02 16:04, Mehdi KABAB wrote:
> Hello,
> 
> I'm in 100%.
> 
> I like the idea of not having to increase the locations of my 
applications shared across multiple projects. I simply add the directory 
to the include path to enjoy all the applications it contains, for my 
various projects.
> 
> --
> Mehdi Kabab
> 
> My french book about Gimp: http://gimp4you.eu.org/livre/
> Blog: http://pioupioum.fr/
> Twitter: http://twitter.com/piouPiouM
> 
> Le 1 juin 2011 à 12:35, Loic d'Anterroches a écrit :
> 
>> Hello,
>>
>> just a short remark. At the moment, I implicitely considered that a
>> Photon application is within a one level deep folder/namespace.
>>
>> For example, the namespace \myapp with \myapp\views the views namespace.
>>
>> What I propose is that one can use any level. For example:
>>
>> \ceondo\myapp
>> \ceondo\whatever\fooapp
>>
>> Of course, it means that the fooapp views are in the file:
>> ceondo/whatever/fooapp/views.php and the folder ceondo somewhere in
>> folder available in the PHP include_path.
>>
>> The goal is - as you can read in the examples - to be able to have your
>> own kind of "private" namespace for you and your company and to avoid
>> the creation of "ceondo_myapp" apps which I find ugly.
>>
>> What do you think about it? I like the idea to be able to "import/use"
>> any app as long as the app is available in the PHP include path.
>>
>> loïc
>>
>> --
>> Indefero - Project management and code hosting - http://www.indefero.net
>> Photon - High Performance PHP Framework - http://photon-project.com
>> Céondo Ltd - Web + Science = Fun - http://www.ceondo.com
> 

Re: [photon.users] Photon Apps Naming Proposal

From:
Loic d'Anterroches
Date:
2011-06-02 @ 10:39
Hello,

no answers, good idea.

So, you can expect a series of ceondo\something apps. Right now, playing
to see if an app could work as a git http backend.

loïc

On 2011-06-01 12:35, Loic d'Anterroches wrote:
> Hello,
> 
> just a short remark. At the moment, I implicitely considered that a
> Photon application is within a one level deep folder/namespace.
> 
> For example, the namespace \myapp with \myapp\views the views namespace.
> 
> What I propose is that one can use any level. For example:
> 
> \ceondo\myapp
> \ceondo\whatever\fooapp
> 
> Of course, it means that the fooapp views are in the file:
> ceondo/whatever/fooapp/views.php and the folder ceondo somewhere in
> folder available in the PHP include_path.
> 
> The goal is - as you can read in the examples - to be able to have your
> own kind of "private" namespace for you and your company and to avoid
> the creation of "ceondo_myapp" apps which I find ugly.
> 
> What do you think about it? I like the idea to be able to "import/use"
> any app as long as the app is available in the PHP include path.
> 
> loïc
> 
> --
> Indefero - Project management and code hosting - http://www.indefero.net
> Photon - High Performance PHP Framework - http://photon-project.com
> Céondo Ltd - Web + Science = Fun - http://www.ceondo.com

-- 
Dr Loïc d'Anterroches
Founder Céondo Ltd

w: www.ceondo.com       |  e: loic@ceondo.com
t: +44 (0)207 183 0016  |  f: +44 (0)207 183 0124

Céondo Ltd
Dalton House
60 Windsor Avenue
London
SW19 2RR / United Kingdom

Re: [photon.users] Photon Apps Naming Proposal

From:
Mickaël Desfrênes
Date:
2011-06-02 @ 13:03
Why not stick with the standard \vendor\lib\class scheme ?

2011/6/2 Loic d'Anterroches <loic@ceondo.com>

> Hello,
>
> no answers, good idea.
>
> So, you can expect a series of ceondo\something apps. Right now, playing
> to see if an app could work as a git http backend.
>
> loïc
>
> On 2011-06-01 12:35, Loic d'Anterroches wrote:
> > Hello,
> >
> > just a short remark. At the moment, I implicitely considered that a
> > Photon application is within a one level deep folder/namespace.
> >
> > For example, the namespace \myapp with \myapp\views the views namespace.
> >
> > What I propose is that one can use any level. For example:
> >
> > \ceondo\myapp
> > \ceondo\whatever\fooapp
> >
> > Of course, it means that the fooapp views are in the file:
> > ceondo/whatever/fooapp/views.php and the folder ceondo somewhere in
> > folder available in the PHP include_path.
> >
> > The goal is - as you can read in the examples - to be able to have your
> > own kind of "private" namespace for you and your company and to avoid
> > the creation of "ceondo_myapp" apps which I find ugly.
> >
> > What do you think about it? I like the idea to be able to "import/use"
> > any app as long as the app is available in the PHP include path.
> >
> > loïc
> >
> > --
> > Indefero - Project management and code hosting - http://www.indefero.net
> > Photon - High Performance PHP Framework - http://photon-project.com
> > Céondo Ltd - Web + Science = Fun - http://www.ceondo.com
>
> --
> Dr Loïc d'Anterroches
> Founder Céondo Ltd
>
> w: www.ceondo.com       |  e: loic@ceondo.com
> t: +44 (0)207 183 0016  |  f: +44 (0)207 183 0124
>
> Céondo Ltd
> Dalton House
> 60 Windsor Avenue
> London
> SW19 2RR / United Kingdom
>



--

Re: [photon.users] Photon Apps Naming Proposal

From:
Loic d'Anterroches
Date:
2011-06-02 @ 13:52

On 2011-06-02 15:03, Mickaël Desfrênes wrote:
> Why not stick with the standard \vendor\lib\class scheme ?

maybe the best way. In fact, when I do a \ceondo\myapp application, I am
already following this approach.

Any remarks against it?

loïc

> 2011/6/2 Loic d'Anterroches <loic@ceondo.com <mailto:loic@ceondo.com>>
> 
>     Hello,
> 
>     no answers, good idea.
> 
>     So, you can expect a series of ceondo\something apps. Right now, playing
>     to see if an app could work as a git http backend.
> 
>     loïc
> 
>     On 2011-06-01 12:35, Loic d'Anterroches wrote:
>     > Hello,
>     >
>     > just a short remark. At the moment, I implicitely considered that a
>     > Photon application is within a one level deep folder/namespace.
>     >
>     > For example, the namespace \myapp with \myapp\views the views
>     namespace.
>     >
>     > What I propose is that one can use any level. For example:
>     >
>     > \ceondo\myapp
>     > \ceondo\whatever\fooapp
>     >
>     > Of course, it means that the fooapp views are in the file:
>     > ceondo/whatever/fooapp/views.php and the folder ceondo somewhere in
>     > folder available in the PHP include_path.
>     >
>     > The goal is - as you can read in the examples - to be able to have
>     your
>     > own kind of "private" namespace for you and your company and to avoid
>     > the creation of "ceondo_myapp" apps which I find ugly.
>     >
>     > What do you think about it? I like the idea to be able to "import/use"
>     > any app as long as the app is available in the PHP include path.
>     >
>     > loïc
>     >
>     > --
>     > Indefero - Project management and code hosting -
>     http://www.indefero.net
>     > Photon - High Performance PHP Framework - http://photon-project.com
>     > Céondo Ltd - Web + Science = Fun - http://www.ceondo.com
> 
>     --
>     Dr Loïc d'Anterroches
>     Founder Céondo Ltd
> 
>     w: www.ceondo.com <http://www.ceondo.com>       |  e:
>     loic@ceondo.com <mailto:loic@ceondo.com>
>     t: +44 (0)207 183 0016  |  f: +44 (0)207 183 0124
> 
>     Céondo Ltd
>     Dalton House
>     60 Windsor Avenue
>     London
>     SW19 2RR / United Kingdom
> 
> 
> 
> 
> -- 
> 
> 

-- 
Dr Loïc d'Anterroches
Founder Céondo Ltd

w: www.ceondo.com       |  e: loic@ceondo.com
t: +44 (0)207 183 0016  |  f: +44 (0)207 183 0124

Céondo Ltd
Dalton House
60 Windsor Avenue
London
SW19 2RR / United Kingdom