Re: protected methods

Sounds reasonable to me, though I would hope this is a group effort and not solely on just a couple peoples heads. (just because coming up with good terms is almost as hard as defining the api itself ;) )

I've started a wiki page for it, feel free to rename/move it etc...It's just a placeholder to get things started:

http://dojo.jot.com/WikiHome/WeeklyIrcMeetings/Irc061018/Agenda061018/TheDojoWay/Language%20Terms

On 10/27/06, Bill Keese <bill@xxxxxxxxxxxxxxx> wrote:

Jesse Kuhnert wrote:
> P.S. Sorry for hijacking your thread, but I'm not sure you'll ever truly
> be rid of it as long as we keep throwing the wrong terminology around.
> If we're going to present ourselves as _javascript_ experts we should at
> least have enough respect for the language to use the correct terms..

So, I'm open to using any terms.  My suggestion (to Jesse, Tom, etc.) is
that instead of having so many emails about the topic, just make a
proposal of the words you think are good, and then we can vote on it.

Just be sure to list all the concepts in your proposal (ie, if we say
"constructor" instead of "class", then what do we say instead of
"superclass", "subclass", "extend", "override", "protected", "public",
and "private"?  Really, anything is OK with me, but I need words similar
to the words above in order to be able to write about the widgets.)
_______________________________________________
dojo-contributors mailing list
dojo-contributors@xxxxxxxxxxxxxxx
http://dojotoolkit.org/mailman/listinfo/dojo-contributors

-- 
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer

Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
_______________________________________________
dojo-contributors mailing list
dojo-contributors@xxxxxxxxxxxxxxx
http://dojotoolkit.org/mailman/listinfo/dojo-contributors