Re: Terminology: Visit vs. Global vs. ???
"Geoff Longman" <glongman-JVFTG6EM2JjNybAxKxMg8VaTQe2KTcn/@public.gmane.org> Fri, 27 Dec 2002 16:35:26 -0500
| Newsgroups | gmane.comp.java.tapestry.contrib |
|---|---|
| Message-ID | <042101c2adef$deb22100$1700a8c0@MOONBEAM> |
This is a multi-part message in MIME format.
------=_NextPart_000_041E_01C2ADC5.F5B445B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I like Visit and Gesture as they are, thank you very much! :-)
Geoff
----- Original Message -----=20
From: Richard Lewis-Shell=20
To: tapestry-contrib-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org=20
Sent: Friday, December 27, 2002 4:23 PM
Subject: Re: [Tapestry-contrib] Terminology: Visit vs. Global vs. ???
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:
So, I'm revisiting the documenation and I start wondering ... maybe =
we should clean up some of the terminology?
=20
Where did "Visit" come from? It actually predates Tapestry; I was =
on a project and we were killing trees with useless diagrams. I was =
busy teaching the other developers about servlets and EJBs and we were =
on a tight schedule. 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. I prefer keeping things strongly typed.
=20
That started a discussion about what that central object would be =
called. Somehow, we came up with Visit (i.e., it stores the information =
about the user's visit). 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.
=20
Despite all that, I think calling it something else, say "Globals" =
(or what? Suggestions welcome) may simplify adoption.
=20
Also, I don't know why I came up with "Gesture". Gesture in UI =
terms is an all-encompassing term for any kind of input the user can do: =
keypress, mouse clicks and drags, etc. But that's not really how =
Gesture is used in Tapestry, since Gesture should be used when =
recognizing input (something the engine services do).
=20
How about "EncodingOfURLAndRequestParameters"? =
EncodedServiceRequest? EncodedRequest? RequestEncoding?=20
=20
=20
----
Howard Lewis Ship
[email protected]
http://tapestry.sf.net
------=_NextPart_000_041E_01C2ADC5.F5B445B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I like Visit and Gesture as they are, =
thank you=20
very much! :-)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Geoff</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A [email protected] =
href=3D"mailto:[email protected]">Richard=20
Lewis-Shell</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
title=3Dtapestry-contrib-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org=20
=
href=3D"mailto:tapestry-contrib-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org">tapestry-contrib@l=
ists.sourceforge.net</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Friday, December 27, 2002 =
4:23=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [Tapestry-contrib] =
Terminology: Visit vs. Global vs. ???</DIV>
<DIV><BR></DIV>Maybe you should just include that defn of Visit in the =
docs=20
(or is it 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 =
for=20
me...<BR><BR>Re: Gesture: <BR>ServiceRequestEncoding? LinkEncoding =
(matches=20
well with the components that do the rendering)?<BR><BR>R<BR><BR>On =
Saturday,=20
December 28, 2002, at 01:32 AM, Howard M. Lewis Ship wrote:<BR><BR>
<BLOCKQUOTE><?fontfamily><?param Arial><?smaller>So, I'm revisiting =
the=20
documenation and I start wondering ... maybe we should clean up some =
of the=20
=
terminology?<?/smaller><?/fontfamily><BR> <BR><?fontfamily><?param =
Arial><?smaller>Where=20
did "Visit" come from? It actually predates Tapestry; I was on =
a=20
project and we were killing trees with useless diagrams. I was =
busy=20
teaching the other developers about servlets and EJBs and we were on =
a tight=20
schedule. Anyway, I was pushing the idea that we should =
collect=20
information that would be used by many different parts of the =
application=20
into a central object, so that we wouldn't constantly have to =
getAttribute()=20
and downcast. I prefer keeping things strongly =
typed.<?/smaller><?/fontfamily><BR> <BR><?fontfamily><?param =
Arial><?smaller>That=20
started a discussion about what that central object would be=20
called. Somehow, we came up with Visit (i.e., it stores the=20
information about the user's visit). 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=20
ended.<?/smaller><?/fontfamily><BR> <BR><?fontfamily><?param =
Arial><?smaller>Despite=20
all that, I think calling it something else, say "Globals" (or =
what? =20
Suggestions welcome) may simplify=20
adoption.<?/smaller><?/fontfamily><BR> <BR><?fontfamily><?param =
Arial><?smaller>Also,=20
I don't know why I came up with "Gesture". Gesture in UI terms =
is an=20
all-encompassing term for any kind of input the user can do: =
keypress, mouse=20
clicks and drags, etc. But that's not really how Gesture is =
used in=20
Tapestry, since Gesture should be used when recognizing input=20
(something the engine services =
do).<?/smaller><?/fontfamily><BR> <BR><?fontfamily><?param =
Arial><?smaller>How=20
about "EncodingOfURLAndRequestParameters"? =20
EncodedServiceRequest? EncodedRequest? =
RequestEncoding? <?/smaller><?/fontfamily><BR> <BR> <BR><?=
fontfamily><?param Arial><?smaller>----<BR>Howard=20
Lewis=20
Ship<BR><U><?color><?param =
1999,1999,FFFF>[email protected]<BR>http://tapestry.sf.net<BR><?/color></U=
><?/smaller><?/fontfamily></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_041E_01C2ADC5.F5B445B0--
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf