If you attempt to inspect a Titanium namespace or Titanium proxy, you get some pretty lackluster results due to the nature of Titanium proxies:
≫ triple
[launching app]
> typeof Titanium.XML
'object'
> Ti.XML.apiName
'Ti.XML'
> Ti.XML
undefined
So we know it's an object and that it has an apiName, but beyond that, normal inspection just doesn't work.
It would be awesome when returning the inspection value if we did the following:
- checked to see if it is a Titanium proxy (weak check for
apiName will work for now)
- If it's not, then just return the value as usual
- If it is a proxy, use the
apiName and the api.jsca file (which we're already loading for tab completion) to create a proxy of the proxy (yikes) which has all the appropriate properties and values attached to it, via manual assignments based on the api.jsca data.
- Now that we have a real JS object and not a Titanium proxy, we can pass it through the normal inspection return value function and we should get a full listing of all properties and values.
- Voila, full inspection of Titanium proxies
If you attempt to inspect a Titanium namespace or Titanium proxy, you get some pretty lackluster results due to the nature of Titanium proxies:
So we know it's an object and that it has an
apiName, but beyond that, normal inspection just doesn't work.It would be awesome when returning the inspection value if we did the following:
apiNamewill work for now)apiNameand theapi.jscafile (which we're already loading for tab completion) to create a proxy of the proxy (yikes) which has all the appropriate properties and values attached to it, via manual assignments based on the api.jsca data.