- Pharo-dev - lists.pharo.org

Re: [Pharo-project] inspector gadget

by Matthew Fulmer

On Wed, Dec 03, 2008 at 11:59:10PM -0600, David Pennell wrote: > You can modify iVars in Explorer, but it doesn't update the display. How do you do that? In inspector, you select the ivar in the top-left pane, edit the value in the top-right pane, and press alt-s. I didn't know explorer had anything similar. -- Matthew Fulmer -- http://mtfulmer.wordpress.com/

Dec. 4, 2008

Re: [Pharo-project] inspector gadget

by David Pennell

You can modify iVars in Explorer, but it doesn't update the display. On Wed, Dec 3, 2008 at 11:22 PM, Matthew Fulmer <tapplek(a)gmail.com> wrote: > On Wed, Dec 03, 2008 at 10:26:30PM -0600, David Pennell wrote: > > I agree. > > Just to be clear - I use both because neither does all I need. Explorer > is > > my default choice, but if I need to look at the innards of a String, I > > launch an Inspector. It seems like it would be easy enough to fix these > in > > Explorer and then make that the default inspector. > > > > I'm just returning to Squeak after 8 years and wondering if there are > other > > reasons folks use Inspector instead of Explorer. > > - Inspectors poll objects every 2 seconds or so, and the display > updates when variables change > - You can modify ivars from the inspector, but not from the > explorer > > -- > Matthew Fulmer -- http://mtfulmer.wordpress.com/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 4, 2008

Re: [Pharo-project] inspector gadget

by Matthew Fulmer

On Wed, Dec 03, 2008 at 10:26:30PM -0600, David Pennell wrote: > I agree. > Just to be clear - I use both because neither does all I need. Explorer is > my default choice, but if I need to look at the innards of a String, I > launch an Inspector. It seems like it would be easy enough to fix these in > Explorer and then make that the default inspector. > > I'm just returning to Squeak after 8 years and wondering if there are other > reasons folks use Inspector instead of Explorer. - Inspectors poll objects every 2 seconds or so, and the display updates when variables change - You can modify ivars from the inspector, but not from the explorer -- Matthew Fulmer -- http://mtfulmer.wordpress.com/

Dec. 4, 2008

Re: [Pharo-project] inspector gadget

by David Pennell

I agree. Just to be clear - I use both because neither does all I need. Explorer is my default choice, but if I need to look at the innards of a String, I launch an Inspector. It seems like it would be easy enough to fix these in Explorer and then make that the default inspector. I'm just returning to Squeak after 8 years and wondering if there are other reasons folks use Inspector instead of Explorer. -david On Wed, Dec 3, 2008 at 10:10 PM, David Mitchell <david.mitchell(a)gmail.com>wrote: > I'd vote for the Explorer too, but I'd prefer to keep the name > Inspector and the action Inspect it. > > On Wed, Dec 3, 2008 at 6:32 PM, David Pennell <pennell.david(a)gmail.com> > wrote: > > We currently have both "inspect" and "explore". It would be nice to have > > one tool. I'd vote for "explore" as a base with some enhancements to > pick > > up the useful features from "inspect". > > -david > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 4, 2008

Re: [Pharo-project] inspector gadget

by David Mitchell

I'd vote for the Explorer too, but I'd prefer to keep the name Inspector and the action Inspect it. On Wed, Dec 3, 2008 at 6:32 PM, David Pennell <pennell.david(a)gmail.com> wrote: > We currently have both "inspect" and "explore". It would be nice to have > one tool. I'd vote for "explore" as a base with some enhancements to pick > up the useful features from "inspect". > -david > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

Dec. 4, 2008

[Pharo-project] inspector gadget

by David Pennell

We currently have both "inspect" and "explore". It would be nice to have one tool. I'd vote for "explore" as a base with some enhancements to pick up the useful features from "inspect". -david

Dec. 4, 2008

[Pharo-project] refactor instance variables

by David Pennell

refactor instance variables | accessors used to figure out which instance variables needed to be added and give you a chance to accept or reject the proposed list. After loading the latest updates, it now presents a list of instance variables, letting you pick one and only one to add. The new behavior is very awkward when you've just added several iVars to a class. The old behavior was too "all or nothing". I'd love to see one that presented all of the proposed accessors and let you accept them all or reject selective accessors. -david

Dec. 4, 2008

Re: [Pharo-project] Impressed, overwhelmed, and a little confused

by Keith Hodges

>> StÃ©phane Ducasse wrote: >>> There will be a pharo universe I imagine. >>> >>> Stef >> please no... let the suffering end >> >> Keith Perhaps I should give a little more detail. 1. Searching Universes is a pain 2. Editing Universe entries is a pain 3. Editing Universe entries takes several minutes for update to become available 4. Universes depends upon a server, there is no offline mechanism. 5. Finding what depends upon what is a pain, you have to manually search 6. If something doesn't work as advertised there is nothing you can do about it 7. If something doesn't work as advertised you have to manually search for all of the dependencies to build your own Installer script that you can customise to fix the problem 8. If something doesn't work as advertised you have to contact the administrator for that package and wait for them to fix it. If they are using a different image/universe to you it could be a long wait, because they will have to load up your image version to test it in. 9. Universes is/was non-trivial to discard from the image if you want to use it to build and discard it later. 10. You have to update Universes with every trivial change to your package, there is no way to say, give users the latest if they want it. 11. Je Deteste L'Universes ;-) Keith

Dec. 4, 2008

Re: [Pharo-project] Monticello configuration still broken

by Matthew Fulmer

On Wed, Dec 03, 2008 at 10:24:55PM +0100, St?phane Ducasse wrote: > Because we did not have the time (and nobody took the time to look at > the code > and write a report for us on the extensions and status of MC1.5 and > MC1.6) I'll take care of this. I am going to write up documentation and changes, and some tests for the new features of MC1.5/1.6 when I release mc1.6. I'm gonna make a real release out of 1.6 once I finish SystemEditor, and overhaul the MC/OB integration. I also think I'll try running the entire pharo update stream (minus mc changes) through a 3.9.1 + mc1.6. I think that should be good enough for you. I should have this ready in 2 or 3 months. In the meantime, MC1.0 is working just fine. I've already merged in most of pharo's mc changes into 1.5. -- Matthew Fulmer -- http://mtfulmer.wordpress.com/

Dec. 3, 2008

Re: [Pharo-project] About ecompletion

by David RÃ¶thlisberger

Hi Simon, > > David, do you have some pointers about the recent modification list in > OB? There is the package ColorMap on Squeaksource at http://www.squeaksource.com/Hermion. If it's installed, OB starts to record all recently browsed and modified methods. You can then access the data in CMDataBase. Storage is optimized for the purpose of color maps, but other tools should be able to access the data as well. David

Dec. 3, 2008