Re: documenting widgets was: release 0.4.1 bugtriage

Thanks, looking forward to seeing the example.

Tom Trenka wrote:
> Ok.  I would have thought that the original array bug we solved and the 
> templateCssPath thing would have been enough if you were willing to 
> think it through, but whatever.
>
> Right this minute I don't have the time to sit down and write you an 
> example (I'm under 2 deadlines) but when I have a chance, I'll do it.  
> Honestly though, if you just think this through objectively--without 
> trying to apply any external concepts to the problem--you'll see the issue.
>
> trt
>
>
> On 10/29/06, *Bill Keese* <bill@xxxxxxxxxxxxxxx 
> <mailto:bill@xxxxxxxxxxxxxxx>> wrote:
>
>     Tom Trenka wrote:
>
>      > Should I go through the entire widget system and try to document
>     for you
>      > every single type of bug that might be there because we are sharing
>      > properties across objects?
>
>     No, I just want you to write some simple javascript code, showing two
>     defineWidget() calls (a base class and a subclass), each defining a
>     property in the prototype (w/the same name), and then some code that
>     uses the subwidget, and gets a different result than expected.  Don't
>     write any english text, other than "expected result" and "actual
>     result".
>
>     If this technique is broken then you should be able to give a simple
>     self-contained example.
>     _______________________________________________
>     dojo-contributors mailing list
>     dojo-contributors@xxxxxxxxxxxxxxx
>     <mailto:dojo-contributors@xxxxxxxxxxxxxxx>
>     http://dojotoolkit.org/mailman/listinfo/dojo-contributors
>     <http://dojotoolkit.org/mailman/listinfo/dojo-contributors>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> dojo-contributors mailing list
> dojo-contributors@xxxxxxxxxxxxxxx
> http://dojotoolkit.org/mailman/listinfo/dojo-contributors