Hi there,
I've got a small reflexion about the base mechanism of ezcBase that allows
us to add an outside repository of classes [1].
Actually, I manage manually my autoload file and as we discussed before with
James Pic [2], it could be a good point to have an extend to this mechanism
and get a
Hi,
On Wed, Nov 24, 2010 at 10:44 AM, Maxime Thomas maxime.t...@gmail.com wrote:
I've got a small reflexion about the base mechanism of ezcBase that allows
us to add an outside repository of classes [1].
Sounds like a good idea. A common complaint about PEAR packaging from
for example Debian
On 24. nov. 2010, at 09.44, Maxime Thomas wrote:
[…]
I've checked in ez how is done the ezpautoloads script that does the job and
the strategy is the following : list all php files, tokenize it, extract
class names and make the file.
For production environments it makes sense, and we have
On Wed, Nov 24, 2010 at 11:43 AM, Ole Marius Smestad o...@ez.no wrote:
For production environments it makes sense, and we have been toying with the
idea of adopting the scripts to also create a similar list,
which could work with components.
In regular situations you probably need two setups:
Hi Henri,
On 11/23/2010 04:43 PM, Henri Bergius wrote:
Just to introduce myself, I'm Henri Bergius, one of the core
developers of the Midgard framework. Midgard is one of the oldest open
source web frameworks / CMSs for PHP. Midgard is a bit unique that in
addition to the actual web layer
On Wed, Nov 24, 2010 at 12:32 PM, Tobias Schlitt tob...@schlitt.info wrote:
The first doc should wrap up why such a library is needed and which use
cases it should satisfy. The idea here is that we first gather all
potential requirements before discussing a flexible design for the
component.
Hi,
As discussed in my introduction thread[1], I'd like to propose for the
Midgard MVC location library[2] to be contributed to the Zeta
Components stack as a new components. As a first step, here are the
initial requirements for a location library.
Introduction
The purpose of this
Actually, I was thinking about this autoloads script for an app as it's done
with eZP. It could be part of the ezcBase as an independent script.
My point was to challenge the ezpublish strategy and see how to integrate it
into ezcBase.
By the way, I understand the point to normalize that for a
