Why do you say that? You get two different solutions. GTInspector is around since almost four years and it was brewed in the more research-oriented Moose environment. At the moment, the Pharo solution adopted just the multiple presentations part. I agree that it is not at all as powerful as GTInspector (both implementation and conceptual wise), but it's already better than it exists in other environments.
In the meantime, GTInspector will grow more to show what else is possible, and hopefully, the community will finally look at it and see that it offers a completely new way of developing :). Doru On Fri, Mar 7, 2014 at 8:39 PM, Yuriy Tymchuk <[email protected]> wrote: > Yes, I know. And this is sad :( > > > On 07 Mar 2014, at 18:45, Tudor Girba <[email protected]> wrote: > > We cannot do that because they are based on two radically different > technologies. > > Doru > > > On Fri, Mar 7, 2014 at 4:43 PM, Yuriy Tymchuk <[email protected]>wrote: > >> Hi everyone. >> >> This day I've attended Moose dojo and I'm pretty impressed with the >> possibilities of GTInspector. The one thing that I've noticed is that both >> GTInspactor and EyeInspector support custom inspections for objects. I'm >> wandering if we can come up with a common protocol to give an object >> specific infector view, and not develop a separate thing for each inspector. >> >> Uko >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"
