Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: 
 <1E0CC447E59C974CA5C7160D2A2854EC097D0E@SJMEMXMB04.stjude.sjcrh.local>
From: "Hunsberger, Peter" <Peter.Hunsberger@stjude.org>
To: <dev@cocoon.apache.org>
Date: Mon, 1 Sep 2003 12:32:21 -0500
Subject: RE: Writing for users (was: Re: [RT] Improving Sitemap and
 Flowscript)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-SEF-723560E2-3392-41F8-A983-A3F5486E94A: 1
content-class: urn:content-classes:message
Thread-Topic: Writing for users (was: Re: [RT] Improving Sitemap and
 Flowscript)
Thread-Index: AcNwpxbEPLGuNOy/QryBLTFcN1BgzwABbHow
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Gianugo Rabellino <gianugo@apache.org> writes:

> Hunsberger, Peter wrote:
> >=20
> > Now-a-days I think anyone that has done even a bit of Web=20
> programming=20
> > has been exposed to some form of Object Model.  Microsoft refers to=20
> > them in their DHTML documentation, then you've got all the various=20
> > DOMs hanging around.
>=20
> Microsoft isn't actually my official reference. :-) I have the=20
> perception that environment is more generic than object model, but=20
> probably both me and you are too biased. We should ask managers. :-)

Fair enough...

> > You've pretty well gotta have some comfort with OO
> > terms if you're touching Cocoon...
>=20
> I have to strongly disagree here. Please point me to an example of OO=20
> skills needed to manage a sitemap (*not* develop Cocoon=20
> components): if=20
> there are, we are doing something wrong and the just failed=20
> to build the=20
> pyramid envisioned a long time ago. You need to know XML,=20
> granted, but I=20
> see no real need of OO background.

Ok, let me rephrase that: you've pretty well gotta have some comfort
with OO terms if you're touching the Web these days...

> > Even managers need some basic understanding of OO if they=20
> are going to=20
> > manage their staff effectively.  Given that they shouldn't=20
> really care=20
> > one of their staff is adapting an environment or an object mode I'd=20
> > vote for object model.  Environment actually sounds harder=20
> to explain=20
> > to the managers I know.
>=20
> Remember that in this case manager !=3D CTO. A sitemap manager is just 
> someone managing the URI space and building pipelines. And to me it's=20
> quite the opposite: most (sitemap) managers I know would understand=20
> environment much better, since it's not context specific.

What's an environment?  Seriously: if I tell my manager I've to modify
an object model he's going to more or less understand.  If I tell him
I've got to modify an environment he'll think I'm talking about Windows
level variables and wonder a) why it takes any time at all, and b) why
doesn't Cocoon have a better way of being configured, like that big XML
file we occasionally talk about. Then he'll be really mystified if I
have to explain to him that some coding is required. OTOH, this is a
mostly Windows shop, so your mileage may vary...

=20