[Pharo-dev] Are #explorerContents and #hasContentsInExplorer obsolete ?

Tudor Girba tudor at tudorgirba.com
Mon Dec 30 07:45:13 EST 2013


I know. This is why I am arguing that we should make the optional tools not
optional. It would be a more profitable approach :).

Cheers,
Doru


On Mon, Dec 30, 2013 at 11:02 AM, Marcus Denker <marcus.denker at inria.fr>wrote:

>
> On 28 Dec 2013, at 13:36, Tudor Girba <tudor at tudorgirba.com> wrote:
>
> > Thanks for raising this :).
> >
> > I now added a simple implementation in the GTInspector to have Pointers
> available for all objects. Perhaps it is overdoing it to have it by default
> on all objects, but it was cheap to implement in a crude way. I still do
> not eliminate all inspector related objects that point to the current
> object, but it's a start (see attached the pointers to Smalltalk).
> >
>
> If the inspector that is in Pharo gets a solution for pointers, then we
> can directly clean up a lot of old code.
> With this being done for tools that are just loadable optionally —> we
> still have to keep the old code of the Explorer around.
>
>         Marcus
>



-- 
www.tudorgirba.com

"Every thing has its own flow"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131230/7882bcd3/attachment-0002.html>


More information about the Pharo-dev mailing list