On Sat, 1 Mar 2008, James Pic wrote:
Delegate most high-level calls to the user?
---
[snip]
We should choose one of those three possible implementations.
I prefer the second one because i think that it makes classes to be less
dependant : more
Derick Rethans wrote:
On Sat, 23 Feb 2008, James Pic wrote:
Thomas Nunninger wrote:
Am Freitag, 22. Februar 2008 schrieben Sie:
Thomas Nunninger wrote:
- I'm still not sure if we need controller multiplicity at all. I
guess, it's a problem of my limited phantasie/experience
Hello everybody,
I fixed consistency between design and requirements docs, and merged our latest
conclusions.
http://svn.ez.no/svn/ezcomponents/experimental/MvcTools/design/requirements.txt
http://svn.ez.no/svn/ezcomponents/experimental/MvcTools/design/design.txt
Also, please give your opinion
Derick Rethans wrote:
On Sat, 23 Feb 2008, James Pic wrote:
Gaetano Giunta wrote:
- in the end, MVC !== WEB. This is the biggest pain point with all these
routing/chaining problems. Mvc was dreamed in a different era, and fits
badly to modern-day web apps (unless maybe you do
On Sat, 23 Feb 2008, James Pic wrote:
Thomas Nunninger wrote:
Am Freitag, 22. Februar 2008 schrieben Sie:
Thomas Nunninger wrote:
- I'm still not sure if we need controller multiplicity at all. I
guess, it's a problem of my limited phantasie/experience as I can't
imagine a
On Sat, 23 Feb 2008, Thomas Nunninger wrote:
Am Samstag, 23. Februar 2008 schrieb James Pic:
Thomas Nunninger wrote:
Don't know how other systems solve that. In eZ Publish those
zones are just some templates that are included in
page_layout.tpl. Things like tree menu or a box
Hi,
Am Montag, 25. Februar 2008 schrieb Derick Rethans:
On Sat, 23 Feb 2008, Thomas Nunninger wrote:
Am Samstag, 23. Februar 2008 schrieb James Pic:
Thomas Nunninger wrote:
Don't know how other systems solve that. In eZ Publish those
zones are just some templates that are included
Hi Kevin,
Thanks for your feedback !
Kevin Waterson wrote:
On Thu, 2008-02-21 at 10:56 +0100, Thomas Nunninger wrote:
- I'm still not sure if we need controller multiplicity at all. I guess,
it's a problem of my limited phantasie/experience as I can't imagine a
situation where I need
Hi,
We have worked on the design doc on IRC yesterday and it's ready for
discussion. It does not meet all requirements but we should agree on
what has been done before talking about the basic error controller
and such. It's online on
Hi Thomas,
Thanks for your revelant work !
Thomas Nunninger wrote:
- I'm still not sure if we need controller multiplicity at all. I guess,
it's a problem of my limited phantasie/experience as I can't imagine a
situation where I need it. But if we have only one controller, we only
have one
On Thu, 2008-02-21 at 10:56 +0100, Thomas Nunninger wrote:
- I'm still not sure if we need controller multiplicity at all. I guess,
it's a problem of my limited phantasie/experience as I can't imagine a
situation where I need it. But if we have only one controller, we only
have one output
On Mon, 11 Feb 2008, Alexandru Stanoi wrote:
Another thing: I thought Interface should not be part of class names
(see ezcMvcRouterInterface and ezcMvcRequestParserInterface).
That is correct.
regards,
Derick
--
Components mailing list
Components@lists.ez.no
Hello everybody,
It's good that the link posted by Thomas N. is down because the document's
quality was very low (a first try).
You'll notice that this document really concentrates on system-conception
(high-level and general); because I beleive that I'm bound to fail at real
object-conception
Hi,
is_null, as we didn't manage to chat directly in IRC on weekend, I post
my questions related to your design draft
(http://rafb.net/p/VLt8Wm42.html) here on the list...
The questions are about your example code:
// ezcMvcUrlUserInputTieinRequestParser implements
//
14 matches
Mail list logo
