> Yeah, I see the code... but your question didn't make any sense. The
> code you posted would work fine. I think you'll have to phrase your
> question differently -- e.g. by posting code that *actually* doesn't
> do what you expect.
I will post a another sample code to illustrate my problem.
>
> The only suggestion I really have for the code (at a glance) is that
> you should be consistent about using fully qualified MochiKit names.
> In a bunch of places you're using the short ones (appendChildNodes),
> and other places you're using the long ones
> (MochiKit.Signal.disconnect). It's kinda misleading.
Yeah, I will update this. This really confusing for other ppl.
> Also the code would be more readable if you didn't mix tabs and
> spaces. Firefox's default tab stop isn't the same as what you wrote it
> with. Using spaces everywhere is generally best. Most text editors can
> be configured to expand tabs ("soft tabs").
Was not knowing such issue, I will update script to use Spaces instead
of tabs.
Thanks Bob for your suggestion, I will try to post a sample with
exactly problem I am facing with OOP type approach in JS.
Many thanks for your above suggestions, this will really help me to
write some quality JS.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/mochikit?hl=en
-~----------~----~----~----~------~----~------~--~---
