Re: Re: WebReports and Plone

I think this is a major issue. And surprisingly I don't recall much
discussion of it.

My view is that templates are too restrictive if they are implemented as
forms and buttons. If by template we just mean some formatted text with
sections that say things like "Replace this sentence with a few
sentences about how your understanding of infinity changed as you did
the activities." and the child just edits away. In other words, a
template is just a page and there is nothing that needs to be
implemented.

Formatted text makes a good flexible template. If don't want this kind
of flexibility (and I think we do) then maybe we need some template
mechanism.

Now there is a need for a small number of what I'll call computational
templates that do things like support the uploading of ToonTalk code to
the server but those Jesper can build and we probably don't need lots of
variants.

Best,

-ken

----- Original Message ----- 
From: "Yishay Mor" <y.mor-xaKI+XbQf9Vaa/[email protected]>
To: "Ken Kahn" <kenkahn-0OjJFJ8UyiNWk0Htik3J/[email protected]>
Cc: <webreports-uedesign-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>; "Ricardo Saraiva"
<[email protected]>; "Richard Noss" <[email protected]>
Sent: Monday, October 13, 2003 11:17 AM
Subject: Re: [Webreports-uedesign] Re: WebReports and Plone


[clipped]
>
> >In his comments Yishay wrote:
> >
> >"We need to have a mechanixm that reads the wizard / template
structure
> >from a simple text file. Once that's done, you don't need to be a
python
> >programmer to add a button or change a heading."
> >
> >I'm not sure this is high priority. If there are only a few templates
> >then some Plone expert can build them. If there are many and they
keep
> >evolving then what kind of expertise is needed? I'm not so sure that
> >we'll need lots of templates and easy editing of them.
> >
>
> My view is that the templates are at the core of our research.  They
are
> equivelent to Scaldemina's scaffolds.  We want to use them to direct
> users towards particular forms of argumentation.  So, I expect we will
> have quite a few small templates, and that these will evolve a lot
over
> time. Even if the structure stays the same, wording changes.  Remember
> our first packaging scheme had "README" in the first hole. After we
> observed the childrun, we changed it to "Instructions". Semanticaly
the
> same, but much more in tune with the hildren's lagnuage.  I think we
> need to support at least this level of editing with out python. Now
that
> I think of it, I think these templates should be editable via the
> web-interface.
>
>
> - Yishay




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php