Hello Matthew, the inspector is not really ment to include in your own application like you do. So as you said, this could get you into some trouble. As it is not ment like you use it, we can not guarantee to have the API stable.
But even if you get it running with the inspector windows, keep in mind that the object window and the widgets window could not work like they should. As long as the inspector runs in an iframe, it has its own qooxdoo instances. The objects and widgets shown in the windows are loaded from the client application in the iframe. So there is no need for the current version of the inspector to exclude its own objects from the windows like it was done in the 0.7 version of the inspector. The whole code for that has been removed. It didn't work anymore anyway. As for the URL of the API. There was an settings dialog in the 0.7 inspector where you could set the URI of the API you want to show. I opened a bug for reintroducing such a settings window in the current inspector. http://bugzilla.qooxdoo.org/show_bug.cgi?id=2282 Best, Martin Am 22.04.2009 um 14:58 schrieb Matthew Gregory: > We would also like to override things like > inspector.property.PropertyWindow._openApiWindow so it uses the local > api that includes our own classes > > Matthew Gregory wrote: >> Thanks for the reply, >> We already have a toolbar mimicking a ribbon bar in our >> application. We >> have a tab on the ribbon that contains some other useful debug >> commands >> and would like the buttons to open the various inspector windows >> there. >> >> >> Christian Schmidt wrote: >>> Hi Matt, >>> >>> sorry, but I don't really understood what you mean with embed the >>> inspector in our application. >>> >>> Why is the job "generate.py inspector" not applicable for you? >>> >>> Thanks, >>> Chris >>> >>> Matthew Gregory schrieb: >>>> Hi, >>>> Firstly, the inspector is great! >>>> >>>> I am trying to integrate this into our own application. Rather than >>>> doing as the docs (1) suggest I would like to embed the inspector >>>> within >>>> our application for source builds. I've added an entry the >>>> manifest in >>>> our config.json and can reference the class correctly. I've had >>>> some >>>> success so far creating the windows by hand but I have had to add >>>> quite >>>> a few helper functions in my Application.js. Is the inspector faily >>>> stable? I don't mind writing these function, but as it is meant >>>> to be a >>>> seperate application I am concerned that the API might change in >>>> the future. >>>> >>>> Is it worth carrying on with what I have so far, or I am going to >>>> run >>>> into problems? >>>> >>>> >>>> Thanks, >>>> Matt >>>> >>>> >>>> 1.) http://qooxdoo.org/application/inspector >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Stay on top of everything new and different, both inside and >>>> around Java (TM) technology - register by April 22, and save >>>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. >>>> 300 plus technical and hands-on sessions. Register today. >>>> Use priority code J9JMT32. http://p.sf.net/sfu/p >>>> _______________________________________________ >>>> qooxdoo-devel mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >>>> >>> >>> ------------------------------------------------------------------------------ >>> Stay on top of everything new and different, both inside and >>> around Java (TM) technology - register by April 22, and save >>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. >>> 300 plus technical and hands-on sessions. Register today. >>> Use priority code J9JMT32. http://p.sf.net/sfu/p >> >> >> ------------------------------------------------------------------------------ >> Stay on top of everything new and different, both inside and >> around Java (TM) technology - register by April 22, and save >> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. >> 300 plus technical and hands-on sessions. Register today. >> Use priority code J9JMT32. http://p.sf.net/sfu/p > > > ------------------------------------------------------------------------------ > Stay on top of everything new and different, both inside and > around Java (TM) technology - register by April 22, and save > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. > 300 plus technical and hands-on sessions. Register today. > Use priority code J9JMT32. http://p.sf.net/sfu/p > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
