Podracer / kuda

Automatically exported from code.google.com/p/kuda
GNU General Public License v2.0
0 stars 0 forks source link

New Feature Request: Make Javascript Class names available in Debugger #3

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Set a break point on the first line of hemi.core.init()
2. Launch a sample project.
3. When the break-point hits inspect the variables in firebug, Eclipse, or 
Aptana IDE.
4. You will not see a class name.

-What is the desired output? 

The desired output is to see the name of the class when inspecting the 'this' 
variable. 

-What do you see instead?

I see just 'Object' or '{}' as in attached screen shot.

I think it may be possible to write a separate debug module where class names, 
including the namespace are attached to all JavaScript classed in the 'hemi', 
'hext', 'o3djs' and 'o3d' namespaces. 

If it can be implemented in a separate module, then this module can be excluded 
from a production build. I will start work on this today. 

Original issue reported on code.google.com by raj...@gmail.com on 15 Apr 2011 at 12:36

Attachments:

GoogleCodeExporter commented 8 years ago
This sounds great.

Original comment by jpywt...@gmail.com on 15 Apr 2011 at 4:56

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
This will live in hext.utils, just wanted to note that from email discussion.

Original comment by jpywt...@gmail.com on 19 Apr 2011 at 10:40

GoogleCodeExporter commented 8 years ago

Original comment by raj...@gmail.com on 20 Apr 2011 at 5:28

GoogleCodeExporter commented 8 years ago
Marking verified to denote this issue was part of 1.3.1 release.

Original comment by erik.kit...@gmail.com on 13 May 2011 at 5:34