Thanks.

Yup...working on finishing it. Will post here when done.

On Tuesday, April 8, 2014 6:36:04 AM UTC-7, Jan Honza Odvarko wrote:
>
>
>
> On Tuesday, April 8, 2014 3:17:27 PM UTC+2, Sandip Chitale wrote:
>>
>> Hi Jan,
>>
>> Thanks for the response. After a little bit of debugging I figured out 
>> that the 'object' argument is a JavaScript object (possibly a wrapper - due 
>> to a different JavaScript context)
>>
> True
>  
>
>> and that for JSOD purposes I can use it as such. So I am on my way to 
>> finish the implementation. I have also added JSOD Panel as a top level 
>> panel and and am able to switch to it when the context menu is clicked. Now 
>> it is simply a matter of populating the diagram.
>>
> Awesome, let us know when we can check out the extension
>
> Btw. here is a tutorial for developing Firebug extensions
> (just in case you haven't seen that already)
> http://www.softwareishard.com/blog/extending-firebug/
>
> Honza
>
>  
>
>>
>> And yes I will look into building the extension for FB 2.0.
>>
>> Thanks,
>> Sandip 
>>
>> On Tuesday, April 8, 2014 1:08:56 AM UTC-7, Jan Honza Odvarko wrote:
>>>
>>>
>>>
>>> On Tuesday, April 8, 2014 8:06:58 AM UTC+2, Sandip Chitale wrote:
>>>>
>>>> I am trying to integrate my JavaScript Object Diagram (JSOD) with 
>>>> Firebug Watches panel. I have done a similar integration with Chrome 
>>>> devtools. For details see: 
>>>>
>>> Sounds great!
>>>
>>>
>>>
>>>>
>>>> http://sandipchitale.blogspot.com/2014/03/javascript-object-diagram-integration.html
>>>>
>>>> I have started my firebug extension and got to the point of showing a 
>>>> context menu on values in Watches panel. See:
>>>>
>>>>
>>>> <https://lh4.googleusercontent.com/-3Gk2D5Zr6dI/U0OOgLGMdeI/AAAAAAAAE7I/yE_x2cXg9rc/s1600/firebugjsod.png>
>>>>
>>> You should build your extension for Firebug 2
>>> https://blog.getfirebug.com/2014/04/04/firebug-2-0-alpha-2/
>>>
>>> The final 2.0 release will happen in about 2 months (when Firefox 30 is 
>>> out)
>>>
>>> The way how to extend the Watch panel context menu is the same.
>>>
>>> In any case, this Firebug extension example should help
>>> https://github.com/firebug/extension-examples/tree/master/ContextMenu
>>> (if not, let me know and we can create a new example)
>>>
>>>
>>>
>>>> <https://lh4.googleusercontent.com/-3Gk2D5Zr6dI/U0OOgLGMdeI/AAAAAAAAE7I/yE_x2cXg9rc/s1600/firebugjsod.png>
>>>>
>>>> In case of Chrome devtools I basically get hold of the 
>>>> RemoteObject<https://chromium.googlesource.com/chromium/blink/+/master/Source/devtools/front_end/RemoteObject.js>.
>>>>  
>>>> I draw the JSOD based on that. It is my understanding the equivalent of 
>>>> that in Firebug is 
>>>> ObjectReference<https://getfirebug.com/developer/api/firebug1.7/symbols/ObjectReference.html>.
>>>>  
>>>> It should be very 
>>>>
>>> This is version 1.7 and quite obsolete
>>>  
>>>
>>>> easy to port the Chrome integration code once I get hold of the 
>>>> ObjectReference because it is roughly similar to RemoteObject.
>>>>
>>>> Sooo... my question is, how do I get hold of the ObjectReference in my 
>>>> context menu click callback?
>>>>
>>> Take a look at the ContextMenu example, there is the following handler:
>>>
>>> onContextMenu: function(items, object, target, context, panel, popup)
>>>
>>>
>>> The second argument is the clicked object.
>>>
>>> Firebug is not fully remotable at this moment, so the object is direct 
>>> reference.
>>>
>>>
>>> Honza
>>>
>>>  
>>>
>>>> Any tips are appreciated. Once done I will contribute the extension to 
>>>> Firebug community.
>>>>
>>>> Regards,
>>>>
>>>> Sandip
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/firebug.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/firebug/7ff75bc4-5f67-44f9-8c03-4e41b57ad110%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to