Re: Terminology: Visit vs. Global vs. ???

--Apple-Mail-2-439957463
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=ISO-8859-1;
	format=flowed

Maybe you should just include that defn of Visit in the docs (or is it=20=

there already?).  I think 'Visit' is a good way of describing what it=20
is - as long as Tapestry has its own session type object, Visit works=20
for me...

Re: Gesture:
ServiceRequestEncoding?  LinkEncoding (matches well with the components=20=

that do the rendering)?

R

On Saturday, December 28, 2002, at 01:32  AM, Howard M. Lewis Ship=20
wrote:

> So, I'm revisiting the documenation and I start wondering ... maybe we=20=

> should clean up some of the terminology?
> =A0
> Where did "Visit" come from?=A0 It actually predates Tapestry; I was =
on=20
> a project and we were killing trees with useless diagrams.=A0 I was =
busy=20
> teaching the other developers about servlets and EJBs and we were on a=20=

> tight schedule.=A0 Anyway, I was pushing the idea that we should =
collect=20
> information that would be used by many different parts of the=20
> application into a central object, so that we wouldn't constantly have=20=

> to getAttribute() and downcast.=A0 I prefer keeping things strongly=20
> typed.
> =A0
> That started a=A0discussion about what that central object would be=20
> called.=A0 Somehow, we came up with Visit (i.e., it stores the=20
> information about the user's visit).=A0 The intent with the name was =
to=20
> make it obvious that it was short-term information, discarded when the=20=

> user's visit to the application ended.
> =A0
> Despite all that, I think calling it something else, say "Globals" (or=20=

> what?=A0 Suggestions welcome)=A0 may simplify adoption.
> =A0
> Also, I don't know why I came up with "Gesture".=A0 Gesture in UI =
terms=20
> is an all-encompassing term for any kind of input the user can do:=20
> keypress, mouse clicks and drags, etc.=A0 But that's not really how=20
> Gesture is used in Tapestry, since Gesture should=A0 be used when=20
> recognizing input (something the engine services do).
> =A0
> How about "EncodingOfURLAndRequestParameters"?=A0=20
> EncodedServiceRequest?=A0 EncodedRequest?=A0 RequestEncoding?=A0
> =A0
> =A0
> ----
> Howard Lewis Ship
> [email protected]
> http://tapestry.sf.net

--Apple-Mail-2-439957463
Content-Transfer-Encoding: quoted-printable
Content-Type: text/enriched;
	charset=ISO-8859-1

Maybe you should just include that defn of Visit in the docs (or is it
there already?).  I think 'Visit' is a good way of describing what it
is - as long as Tapestry has its own session type object, Visit works
for me...


Re: Gesture: =20

ServiceRequestEncoding?  LinkEncoding (matches well with the
components that do the rendering)?


R


On Saturday, December 28, 2002, at 01:32  AM, Howard M. Lewis Ship
wrote:


<excerpt><fontfamily><param>Arial</param><smaller>So, I'm revisiting
the documenation and I start wondering ... maybe we should clean up
some of the terminology?</smaller></fontfamily>

=A0

<fontfamily><param>Arial</param><smaller>Where did "Visit" come from?=A0
It actually predates Tapestry; I was on a project and we were killing
trees with useless diagrams.=A0 I was busy teaching the other developers
about servlets and EJBs and we were on a tight schedule.=A0 Anyway, I
was pushing the idea that we should collect information that would be
used by many different parts of the application into a central object,
so that we wouldn't constantly have to getAttribute() and downcast.=A0 I
prefer keeping things strongly typed.</smaller></fontfamily>

=A0

<fontfamily><param>Arial</param><smaller>That started a=A0discussion
about what that central object would be called.=A0 Somehow, we came up
with Visit (i.e., it stores the information about the user's visit).=A0
The intent with the name was to make it obvious that it was short-term
information, discarded when the user's visit to the application =
ended.</smaller></fontfamily>

=A0

<fontfamily><param>Arial</param><smaller>Despite all that, I think
calling it something else, say "Globals" (or what?=A0 Suggestions
welcome)=A0 may simplify adoption.</smaller></fontfamily>

=A0

<fontfamily><param>Arial</param><smaller>Also, I don't know why I came
up with "Gesture".=A0 Gesture in UI terms is an all-encompassing term
for any kind of input the user can do: keypress, mouse clicks and
drags, etc.=A0 But that's not really how Gesture is used in Tapestry,
since Gesture should=A0 be used when recognizing input (something the
engine services do).</smaller></fontfamily>

=A0

<fontfamily><param>Arial</param><smaller>How about
"EncodingOfURLAndRequestParameters"?=A0 EncodedServiceRequest?=A0
EncodedRequest?=A0 RequestEncoding?=A0</smaller></fontfamily>

=A0

=A0

<fontfamily><param>Arial</param><smaller>----

Howard Lewis Ship

<underline><color><param>1999,1999,FFFF</param>[email protected]

http://tapestry.sf.net

</color></underline></smaller></fontfamily></excerpt>=

--Apple-Mail-2-439957463--



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf