<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Thanks for the comments. I plan to do the changes in 3 parts:<div><br><div>First - I'll shortly all the docs to use lz.tagname or lz.ClassName as you describe,</div><div>and get the navbars in good shape. There are no lfc changes here, so risk</div><div>is low.</div><div><br></div><div>Second - I'll publish names for the Service classes. Currently they are declared</div><div>as e.g. LzTimerService and the doc renaming treats this as lz.TimerService (as you want).</div><div>But these class names have not yet been published in the code.</div><div><br></div><div>Third - the internal naming that tucker wants:</div><div> $lzc$class_TimerService instead of LzTimerService. This does not</div><div>affect doc appearance as doc will already show this as lz.TimerService.</div><div>However it will affect doc implementation (as we do simple Lz => lz. substituting).</div><div>The external effect is just to remove LzTimerService to address global namespace solution, yes?</div><div>I think this issue comes up with all class names (LzNode? LzCanvas?) so do we get</div><div>a real benefit of fixing one without the other? I'd like to open a separate JIRA to track this</div><div>discussion.</div><div><br></div><div><div><div>On Jul 26, 2008, at 12:34 PM, David Temkin wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>This looks good to me, with one addition/clarification:<br><br>The name for all LFC classes that define tags should be lower-case, to match the tag name. That is, use "lz.view" instead of "lz.View" (or the deprecated "LzView").<br><br>That way all tags, whether defined in the LFC or user-defined in LZX, will have runtime objects that match their class names, within the "lz" namespace.<br><br>LFC classes that do *not* define tags should retain their current CamelCase names, within "lz".<br><br>To summarize, all objects that were formerly global, both classes and singleton services, should be under "lz", and should be referred to that way in the docs. All classes that define tags, whether user-defined, defined in custom components, or defined in the LFC should have class names that match the tag name, within the "lz" namespace.<br><br>Tucker, please confirm.<br><br>- D.<br><br><br>On Jul 24, 2008, at 4:17 PM, P T Withington wrote:<br><br><blockquote type="cite">David needs to be in the loop on this. This is my understanding:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">For any class that implements a tag 'foo' there will be an entry `lz.foo` that returns that class. E.g., <view> is implemented by `LzView` but that is deprecated, use `lz.view` instead. This is simply a matter of fixing the documentation, because these entries already exist in `lz`.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">For any service class that defines a singleton service 'Service', we would _like_ there to be an entry `lz.Service`. E.g., the timer service is currently defined by `LzTimerService` and instantiated as the singleton `LzTimer`. What we would like is `lz.Timer` to be how you access the singleton, and `lz.TimerService` to be how you access the class. This requires updating the LFC _and_ adjusting the documentation. Since you can't say:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> class lz.TimerService {...<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">this means you will have to say:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> class $lzc$class_TimerService {...<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">lz.TimerService = $lzc$class_TimerService;<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">For any other classes that are public in the LFC, we would like them to be also now accessed from `lz`. The only one I can think of is LzEventable, which happens to show up in the doc. This would need to be handled as above.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">If all of this sounds like a kludge, it is; just a smidge less than the previous kludge. What we really want to do is to have a couple of namespaces, `lz` and `lzinternal` and put the LFC in `lzinternal` except for public API's which would be in `lz`. The big issue there is retrofitting that into JS1 where the namespace(s) will presumably be represented by Object's and the compiler will have to magically translate `lz:foo` to `lz.foo`.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On 2008-07-24, at 13:07EDT, Donald Anderson wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">Probably because I forgot them!<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">On Jul 24, 2008, at 10:38 AM, P T Withington wrote:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">For some reason, Mail is not showing me your attachments?<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">On 2008-07-24, at 09:39EDT, Donald Anderson wrote:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Tucker -<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">I'd like to pick up the ball again on the lz.classname stuff.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">I left it in a state that was probably incorrect, but didn't really<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">have a clear picture of the final goal - and I'll need your help<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">to advance it.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">To make this easy, I'm attaching webloc<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">files for a couple of 'typical' pages, maybe you can tell me quickly<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">what's clearly wrong and how to change it to get something at least<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">closer to the goal. We can do by phone/IM if that's better.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Much of the hard stuff (figuring out how to mod the doc pages) is done,<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">and once we have some general rules for the naming,<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">it should be pretty easy to fix. If there's no hard rule for naming,<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">or there might be exceptions, we could add a javadoc tag to<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">the sources.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Thanks.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">- Don<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">--<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Don Anderson<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Java/C/C++, Berkeley DB, systems consultant<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">voice: 617-547-7881<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">email: <a href="mailto:dda@ddanderson.com">dda@ddanderson.com</a><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">www: <a href="http://www.ddanderson.com">http://www.ddanderson.com</a><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">--<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Don Anderson<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Java/C/C++, Berkeley DB, systems consultant<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">voice: 617-547-7881<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">email: <a href="mailto:dda@ddanderson.com">dda@ddanderson.com</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">www: <a href="http://www.ddanderson.com">http://www.ddanderson.com</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><br></div></blockquote></div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br class="Apple-interchange-newline">--</div><div><br>Don Anderson<br>Java/C/C++, Berkeley DB, systems consultant<br><br>voice: 617-547-7881<br>email: <a href="mailto:dda@ddanderson.com">dda@ddanderson.com</a><br>www: <a href="http://www.ddanderson.com/">http://www.ddanderson.com</a><br></div></div></span></span><br class="Apple-interchange-newline"></div></span></div></span><br class="Apple-interchange-newline"> </div><br></div></div></body></html>