If this is the case, then we can deal with it like we have the
component families: e.g. reorderer, inline edit and we would have
renderer with kids: client-side and server-side.
+1 on renderer.
J
~~~~~~~~~~~~~~~~~~~~~~
Jess Mitchell
Boston, MA, USA
Project Manager / Fluid Project
[email protected]
/ w / 617.326.7753 / c / 919.599.5378
jabber: [email protected]
http://www.fluidproject.org
~~~~~~~~~~~~~~~~~~~~~~
On Mar 9, 2009, at 11:15 AM, Justin wrote:
I like the name Renderer
However, are we going to have a server based and client side based
renderer (maybe during Fluid Engage)? If that is the case, I prefer
Client-side Renderer.
- Justin
On 9-Mar-09, at 10:51 AM, Anastasia Cheetham wrote:
I'm working on the technical documentation on the wiki, and I'm
finding that our renderer is being referred to using a variety names:
Renderer
Fluid Renderer
Fluid/RSF Renderer
Client-side Renderer
I'd like to propose that we settle on a single name, and update our
documentation to use that name consistently.
In keeping with the names that we've used for other components
(Reorderer, Uploader, Pager...), I propose that we simple refer to
it as
Renderer
Thoughts?
--
Anastasia Cheetham [email protected]
Software Designer, Fluid Project http://fluidproject.org
Adaptive Technology Resource Centre / University of Toronto
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
