But we cannot all start doing different things, right ? There should be some design and structure, that is why I am asking.
On 01 Oct 2014, at 15:59, Esteban Lorenzano <[email protected]> wrote: > cool thing of this new inspector is that is super easy to extend with what > you want > So wouldn’t be complicated to add that functionality :) > > Esteban > > >> On 01 Oct 2014, at 15:51, Ben Coman <[email protected]> wrote: >> >> Sven Van Caekenberghe wrote: >>> I am confused about the GTInspector State tab. What is its definition ? >>> I would say that it shows the raw, fundamental, implementation form of the >>> object, in essence what EyeBasicInspector showed. And that additional tabs >>> offer alternative, more user friendly views. >>> Why then does it not show all variable content and only named variables ? >>> Try inspecting a [Byte]String or [Byte]Array. The State view is useless, it >>> just shows self. Some of these have an items view, but not all. >>> How can I inspect an individual character of a String ? Or an individual >>> byte ? >>> Consider a Float. The State view should show the two (meaningless) slots >>> because that is how Floats are (currently) implemented, and then another >>> tab should show the sign, mantissa, exponent view. >>> In the Eye inspectors we also confused these two aspects in a single view, >>> which is wrong in hindsight, IMHO. It should be crystal clear for a user >>> whether a slot is real or an alternative view of describing the same thing. >>> I could propose changes or a slice, but I think we should agree on the >>> definition of 'State' first. >>> Sven >> >> If its a raw slots view you want, >> maybe that tab should be called 'Slots' ? >> cheers -ben >> > >
