Now _that's_ clever! That certainly opens up a lot of possibilities...
Of course, I've bitten the bullet and gone for java view subclasses
anyway as they allow a lot of other possibilities, but I do like this
custom webobject solution and I think I could find quite a few uses
for it.
Many thank
Hi there,
On 15/06/2006, at 7:56 AM, David Masters wrote:
On 14 Jun 2006, at 12:54, John Stewart wrote:
If I create a ul wrapper "styleContainer" as below, I'd like to
include the "open" or "closed" styles, as well as a common "clear"
style.
The output would be of the form:
...
On Jun 16, 2006, at 7:27 AM, Mike Schrag wrote:
If I want my title to be "Mike Schrag's Home Page," then I have
some issues. Who generates that string (localization aside for the
moment)? Technically that string is entirely a view construct (the
next designer may want to change it to "Th
On 19 Jun 2006, at 12:43, John Stewart wrote:
On 6/18/06, Guido Neitzer <[EMAIL PROTECTED]> wrote:
Misunderstanding. My fault. I don't do validation in the controller.
I do validation in the model. But I catch the validation errors in an
"EditPage" class and inherit from this class to build m
On Jun 16, 2006, at 8:45 AM, Jean-François Veillette wrote:
Le 06-06-15, à 17:27, Paul Lynch a écrit :
View objects are the dynamic elements used within your
components. Model objects are the EOs, the implementors of
EOEnterpriseObject. Controllers are your subclasses of
WOApplication, W
On Jun 16, 2006, at 5:27 AM, Mike Schrag wrote:
The design of WOComponent seems to be nearly identical to the
design approach Java's Swing JComponent took (who knows, maybe some
of the same people
As pointed out here, the thing to keep in mind is that your model
should NEVER link against t
On 19.06.2006, at 13:43 Uhr, John Stewart wrote:
Misunderstanding. My fault. I don't do validation in the controller.
I do validation in the model. But I catch the validation errors in an
"EditPage" class and inherit from this class to build my concrete
edit pages.
What do you define by valid
On 6/18/06, Guido Neitzer <[EMAIL PROTECTED]> wrote:
Misunderstanding. My fault. I don't do validation in the controller.
I do validation in the model. But I catch the validation errors in an
"EditPage" class and inherit from this class to build my concrete
edit pages.
What do you define by v
On 17.06.2006, at 17:08 Uhr, Paul Lynch wrote:
I don't think that it is fair to make such tight correlation with
Cocoa. Web and desktop have quite different metaphors and
workflows, but still MVC is a good design principle to use.
True.
As many others say, a lot of application logic that
On 16.06.2006, at 17:45 Uhr, Jean-François Veillette wrote:
[D2W]
This is something I should do. This an area that I do not know
enough to use and feel comfy about.
How long is it to get at ease with this? Any good tutorial /
sample code that can ease the learning curve?
I don't know how
On 16 Jun 2006, at 16:45, Jean-François Veillette wrote:
Le 06-06-15, à 17:27, Paul Lynch a écrit :
View objects are the dynamic elements used within your
components. Model objects are the EOs, the implementors of
EOEnterpriseObject. Controllers are your subclasses of
WOApplication, WO
On 16.06.2006, at 17:58 Uhr, Mike Schrag wrote:
An example where I use ERXThreadStorage is that when a user
authenticates, I put the user into thread storage.
I do exactly the same. Anjo gave that hint about two years or so ago.
It's just easier there, because if you don't do it this way you
Rule 5 - Use ERXThreadStorage instead of the session to have not
so much dependencies there.
I do not use this object, I have seen it proposed as a solution for
things I would have done differently. I would like to see a sample
app that make use of it (simple, just enough to prove the
c
I find this discusion very interesting. I'm very glad people
contribute with their own point of view !
First, correcting myself.
- we too often miss an opportunity to create a new class, that will
control the workflow of the many views of the system. we too often
sparkle bit and pieces of o
On 16.06.2006, at 10:24 Uhr, Paul Lynch wrote:
There is only an artificial distinction between "Dynamic Element"
and WOComponent. All dynamic elements are view classes, and they
are also WOComponent subclasses. So yes, WOComponent fills both
roles.
Nope. WODynamicElement and WOComponent
Very interesting discussion.
Although I tend to agree with Paul's analysis on the whole, I would
point out one small error...
On Jun 16, 2006, at 4:24 AM, Paul Lynch wrote:
There is only an artificial distinction between "Dynamic Element"
and WOComponent. All dynamic elements are view cla
ERXWOSwitch/ERXWOCase in Project Wonder :)msOn Jun 16, 2006, at 8:07 AM, John Stewart wrote:These days, in the world of .css, I feel the View needs a bit more complexity. For my purposes, something like a ..., equivalent to a Java "switch" would suffice. __
The design of WOComponent seems to be nearly identical to the design
approach Java's Swing JComponent took (who knows, maybe some of the
same people worked on both -- it's very incestuous in the
valley :) ). Swing docs state that JComponent objects are View-
Controller pairs. That is, they
Quite a diversity of opinions on this one!
To me, the ideal MVC model allows both conceptual design and practical
development of the three separate layers. All one layer should need
to know about another is their common interface.
IMO one of the practical benefits of a good MVC development syst
On 16 Jun 2006, at 03:11, wojingo wrote:
This has been a very interesting discussion, thanks to everyone
involved for the opinions expressed.
Personally, I'm still not entirely convinced about WOComponent
being a controller only and Dynamic Elements being the view objects
as it seems Pau
This has been a very interesting discussion, thanks to everyone involved
for the opinions expressed.
Personally, I'm still not entirely convinced about WOComponent being a
controller only and Dynamic Elements being the view objects as it seems
Paul is saying. I see his point but I'm not stil
This is my take on it, which is supported by various Apple docs on
WebObjects.
WO tries quite hard to strictly follow MVC. You can find plenty of
evidence for this, as well as exceptions, so it is open to
interpretation. In MVC, you have the three 'layers' of an
application, and objects
On Jun 15, 2006, at 5:08 AM, John Stewart wrote:
A slight afterthought...
My idea of MVC is that the only the View deals with appearance,
although may need a certain amount of logic to handle this. The
Controller carries the business logic and shouldn't be concerned
with appearance, tho
I was hoping to handle the View entirely in .html + .wod, so if the
.css changes I just change the references in there. However, the .wod
logic won't cope with that, so I have to extend the View to include a
chunk of Java code. Still MVC as long as I separate it from the
Controller code. How
A slight afterthought...My idea of MVC is that the only the View deals with appearance, although may need a certain amount of logic to handle this. The Controller carries the business logic and shouldn't be concerned with appearance, though has to handle I/O of data to the View.
For example, the C
John S.A technique that I used (I think I understand your question) is to have a eomodel object called "parameters" with fields parameterKey and parameterValue. Then I put whatever various parameters I want to use in there. Then I have a static method in a Util class that is something like String
Thanks guys,I'm working from a third-party css set, and trying to plan ahead for the possibility of that changing, while interface logic stays the same. However, I'll just have to bite the bullet and accept that my Java code has to know what's in there!
JohnOn 6/14/06, David Masters <[EMAIL PROTEC
John,
On 14 Jun 2006, at 12:54, John Stewart wrote:
If I create a ul wrapper "styleContainer" as below, I'd like to
include the "open" or "closed" styles, as well as a common "clear"
style.
The output would be of the form:
...
...
One approach (as I think David LeBer menti
Hi John,
This is a bit of a long winded answer, I apologise for that.
On Wed, 2006-06-14 at 12:54 +0100, John Stewart wrote:
> OK, I've refined down what I'm trying to do.
>
> I'd like to keep this as MVC as possible, so the Java code should not
> deal directly with the alternative styles, thoug
On 14 Jun 2006, at 12:54, John Stewart wrote:
I'd like to keep this as MVC as possible, so the Java code should not
deal directly with the alternative styles, though It will provide the
logic to select the styles.
There's a mismatch here between what you seem to think MVC is, and
what you a
OK, I've refined down what I'm trying to do.I'd like to keep this as MVC as possible, so the Java code should notdeal directly with the alternative styles, though It will provide the
logic to select the styles.The simplest version of this is a straight boolean describing "open"or "closed" styles.
On 2-Jun-06, at 10:49 AM, John Stewart wrote:
Hi!
I'm trying to use dynamic webobject tags in WOBuilder to set up HTML
tag attributes.
e.g.
...
where
String1: WOString {
value = "style2";
}
I can happily add levels of tag nesting here, such as WOConditionals.
It seems to want o
32 matches
Mail list logo
