- Pharo-users - lists.pharo.org

Re: [Pharo-users] Emergency evaluator and GTGenericStackDebugger

by Edward Povazan

Thank you, I didnât know that (I did it with code for the inspector). However disabling/enabling doesnât change anything with regards to the error. And Iâm liking GT a lot, so I will prepare a new image and move my stuff over, good things to finally have a need to learn. -Ed On Dec 7, 2014, at 12:31 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > Hi, > > what image do you use? > If it is pharo4, you can open the settings (World menu>System>Settings) and disable GT playground and inspector (Glamorous Toolkit settings) > > > > > 2014-12-07 6:08 GMT+01:00 Edward Povazan <empovazan(a)gmail.com>: > Hello, > > Iâve been using Pharo for a while as my playground for trying things out, itâs a very soothing place to code and figure out algorithms (except that when I return to my âreal worldâ, the friction with modern tools is amplified). Iâm still a newb when it comes to knowing how things work deeper down. > > Iâm a little stuck. I did something (canât remember) and not realizing that I had a problem, saved my image too. > Now when I try open a Workspace, I get a *** System error handling failed *** with a huge amount of text. > > Iâve uploaded a screen grab here: http://imgur.com/4ZwsF6e > > Is this worth debugging? > > My plan is to install the origin tools, and remove GToolkit. And then reinstall GToolkit. > Would this help? > > And, how? I realize I donât know what tools are in the default Pharo3 image! > Can someone tell me what they are called? > > Thanks! Canât wait to get back to the happy place! > -Ed >

Dec. 8, 2014

Re: [Pharo-users] Emergency evaluator and GTGenericStackDebugger

by Edward Povazan

Yep, I will move my stuff to a new image this week and clean up a bit. I now have a need to learn about serializing my models :) so I import them into a new image. I can post a link when I get it ready. Thanks for your help, Iâve learnt more things. -Ed On Dec 7, 2014, at 4:58 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Could you make the image available? > > Cheers, > Doru > > > > On Sun, Dec 7, 2014 at 1:03 PM, Edward Povazan <empovazan(a)gmail.com> wrote: > Thank you, > > For some reason there were a few. Reverted most. However all my Petit* ones trigger the same error when reloading them. I deleted them. But the error persists, as soon as I try open a Workspace I get the Emergency Evaluator screen. > > -Ed > > On Dec 7, 2014, at 12:21 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> If I understand correctly, you are on Pharo 3. What I suggest is to open the Monticello Browser and look at the changed packages. Then you can load the previous versions of those, and you should get back to normal. >> >> Cheers, >> Doru >> >> >> >> On Sun, Dec 7, 2014 at 6:08 AM, Edward Povazan <empovazan(a)gmail.com> wrote: >> Hello, >> >> Iâve been using Pharo for a while as my playground for trying things out, itâs a very soothing place to code and figure out algorithms (except that when I return to my âreal worldâ, the friction with modern tools is amplified). Iâm still a newb when it comes to knowing how things work deeper down. >> >> Iâm a little stuck. I did something (canât remember) and not realizing that I had a problem, saved my image too. >> Now when I try open a Workspace, I get a *** System error handling failed *** with a huge amount of text. >> >> Iâve uploaded a screen grab here: http://imgur.com/4ZwsF6e >> >> Is this worth debugging? >> >> My plan is to install the origin tools, and remove GToolkit. And then reinstall GToolkit. >> Would this help? >> >> And, how? I realize I donât know what tools are in the default Pharo3 image! >> Can someone tell me what they are called? >> >> Thanks! Canât wait to get back to the happy place! >> -Ed >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Dec. 8, 2014

Re: [Pharo-users] [ann] gtspotter: a moldable interface for spotting objects

by Tudor Girba

Hi, On Mon, Dec 8, 2014 at 12:29 AM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > 2014-12-07 20:19 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > >> Hi, >> >> On Sun, Dec 7, 2014 at 3:52 PM, Thierry Goubier < >> thierry.goubier(a)gmail.com> wrote: >> >>> Cool. >>> >>> Interesting. I recognize some of the patterns I use, but in a slightly >>> different form. >>> >> >> Could you detail? I am asking because I am interesting in search use >> cases to see if they can be expressed in terms of Spotter of if we need to >> extend the interface in some way. GTSpotter is supposed to be moldable >> thus, it is important for it to handle as many use cases as possible. >> > > Well, the hierarchical, drill-down type of recursive searches is something > I do regularly, so I can relate. They are not as general; they revolve as a > cascading sequence of implementors/finder/senders/accesses/package/class > searches, but from inside the browser (but, since a search result is given > in a browser, then you can keep drilling down). > > >> >> >>> The widget look very nice and clean. I'd worry about having a very long >>> top-level list, and I know that some of the search patterns are a bit less >>> efficient than what I use today. >>> >> >> What do you mean by long top-level lists? >> Do you refer to categories for which a query can show many results? In >> this case, our interface always limits the amount per category to 5. After >> reaching 5 items, the rest is being computed in a process with lower >> priority so as not to mess too much with the responsiveness of the UI. If >> you want to see more than 5, you can always dive in the category and then >> you focus only on that category. It seems to work well enough. >> > > Ok. I see how you are targetting that. I was thinking of what would happen > if you have many extensions going into the root items. > I see. We put quite some work in this issue actually. Originally, we showed the list of categories like in Spotlight on Mac, but then we noticed we do not know what categories actually provide a match. So, if you look closely, the widget shows all categories that are at the top and at the bottom of the visible items. As you scroll they scroll in and out of the main list. If there are too many on a row, the labels trim down nicely. We tried with a couple of dozens and it scales reasonably well. I think this widget is quite cool and rather unique (I have not seen this design anywhere else). I will try to describe these design decisions in a future post. >> You should also take into account that most widgets you see are hand-made >> in a lighter Morphic (called Brick) created by Alex Syrel. The goal of this >> one is to be fast and scalable. >> > > Cool. It's an issue for many things, and its great to see someone tackling > speed issues. > > I dropped some type of Morphs for that reason. > > >> >> Does that answer the question? >> > > Yes, it did. > > >> >> I'm impressed by the amount of work going into that. >>> >> >> Thanks. Indeed, the work was quite intensive and we went through 3 major >> variations of the implementations. >> > > What was I told about Smalltalk the very first time I had to use it as a > student? "the language where you can break and redo all your code in a very > short time.". > Indeed. For us, that time was less than 2 months and we started from scratch. Cheers, Doru > > > Thierry > > > > >> >> Cheers, >> Doru >> >> >> >>> >>> Thierry >>> >>> 2014-12-07 14:14 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: >>> >>>> Hi, >>>> >>>> Alex Syrel, Andrei Chis and I are happy to announce a new addition to >>>> the Glamorous Toolkit: >>>> GTSpotter, a novel interface for spotting objects. >>>> >>>> GTSpotter has two goals: >>>> - Provide a uniform yet moldable interface that can work on any object, >>>> and >>>> - Handle searching through arbitrary levels of object nesting. >>>> >>>> We think this will have a significant impact on the development >>>> workflow in Pharo. >>>> >>>> Here is a couple of screenshots: >>>> [image: Inline image 2] [image: Inline image 1] [image: Inline image 3] >>>> >>>> >>>> A trailer is available here: >>>> https://www.youtube.com/watch?v=PhSmjR3NOlU >>>> >>>> A detailed description is available here: >>>> http://www.humane-assessment.com/blog/introducing-gtspotter >>>> >>>> It works already in Pharo 3.0 and can be played with by following the >>>> instructions from: >>>> http://gt.moosetechnology.org >>>> >>>> Please let us know what you think. >>>> >>>> Enjoy, >>>> The Glamorous Team >>>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 7, 2014

Re: [Pharo-users] [ann] gtspotter: a moldable interface for spotting objects

by Thierry Goubier

2014-12-07 20:19 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > On Sun, Dec 7, 2014 at 3:52 PM, Thierry Goubier <thierry.goubier(a)gmail.com > > wrote: > >> Cool. >> >> Interesting. I recognize some of the patterns I use, but in a slightly >> different form. >> > > Could you detail? I am asking because I am interesting in search use cases > to see if they can be expressed in terms of Spotter of if we need to extend > the interface in some way. GTSpotter is supposed to be moldable thus, it is > important for it to handle as many use cases as possible. > Well, the hierarchical, drill-down type of recursive searches is something I do regularly, so I can relate. They are not as general; they revolve as a cascading sequence of implementors/finder/senders/accesses/package/class searches, but from inside the browser (but, since a search result is given in a browser, then you can keep drilling down). > > >> The widget look very nice and clean. I'd worry about having a very long >> top-level list, and I know that some of the search patterns are a bit less >> efficient than what I use today. >> > > What do you mean by long top-level lists? > Do you refer to categories for which a query can show many results? In > this case, our interface always limits the amount per category to 5. After > reaching 5 items, the rest is being computed in a process with lower > priority so as not to mess too much with the responsiveness of the UI. If > you want to see more than 5, you can always dive in the category and then > you focus only on that category. It seems to work well enough. > Ok. I see how you are targetting that. I was thinking of what would happen if you have many extensions going into the root items. > > You should also take into account that most widgets you see are hand-made > in a lighter Morphic (called Brick) created by Alex Syrel. The goal of this > one is to be fast and scalable. > Cool. It's an issue for many things, and its great to see someone tackling speed issues. I dropped some type of Morphs for that reason. > > Does that answer the question? > Yes, it did. > > I'm impressed by the amount of work going into that. >> > > Thanks. Indeed, the work was quite intensive and we went through 3 major > variations of the implementations. > What was I told about Smalltalk the very first time I had to use it as a student? "the language where you can break and redo all your code in a very short time.". Thierry > > Cheers, > Doru > > > >> >> Thierry >> >> 2014-12-07 14:14 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: >> >>> Hi, >>> >>> Alex Syrel, Andrei Chis and I are happy to announce a new addition to >>> the Glamorous Toolkit: >>> GTSpotter, a novel interface for spotting objects. >>> >>> GTSpotter has two goals: >>> - Provide a uniform yet moldable interface that can work on any object, >>> and >>> - Handle searching through arbitrary levels of object nesting. >>> >>> We think this will have a significant impact on the development workflow >>> in Pharo. >>> >>> Here is a couple of screenshots: >>> [image: Inline image 2] [image: Inline image 1] [image: Inline image 3] >>> >>> >>> A trailer is available here: >>> https://www.youtube.com/watch?v=PhSmjR3NOlU >>> >>> A detailed description is available here: >>> http://www.humane-assessment.com/blog/introducing-gtspotter >>> >>> It works already in Pharo 3.0 and can be played with by following the >>> instructions from: >>> http://gt.moosetechnology.org >>> >>> Please let us know what you think. >>> >>> Enjoy, >>> The Glamorous Team >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Dec. 7, 2014

[ANN (Toy)]: EventTweet

by Sean P. DeNigris

When at events like ESUG, I often append a trailer to all my Tweets - something like "[Speaker], [Talk], [ConferenceName | Hashtag]". It can be tedious to copy/paste it in each time, and especially when it must be shortened for a longish Tweet. So I wrote a tiny app that lets you specify your trailer in various degraded (shorter) versions, and as you type, it shows you which are over/under and by how many characters. The code below will get you started and here is a screencast: https://vimeo.com/113763005 Gofer it smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; package: 'EventTweet'; load. ui := EtUI new. "Set up the different versions of the trailer. Order does not matter" ui event trailers: { ' - Gary Zimmer, "Establishing Best Practicesâ for #Farming - Ecological & Otherwise", @AcresUSA 2014'. ' - Gary Zimmer, "Establishing Best Practicesâ for #Farming...", @AcresUSA 2014'. ' - Gary Zimmer, "Establishing Best Practicesâ for #Farming...", @AcresUSA'. ' - Gary Zimmer, @AcresUSA 2014' }. ui openWithSpec. "Now as you type in the editor, the preview will show tweets with each version and how under/over the limit they are. Copy the longest valid tweet to the clipboard - cmd-t" ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Toy-EventTweet-tp4794621.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Dec. 7, 2014

Re: [Pharo-users] [Pharo-dev] [Moose-dev] [ann] gtspotter: a moldable interface for spotting objects

by Tudor Girba

Hi Sven, Exactly! :) To be relevant, we had to show how it solves existing use cases (plus a bit more :)). Next we will focus on objects that are less "code". The hard part of actually getting the interface smooth and performant was kind of done. It's play time now :). As I noted in the post, we already have some 30 extensions for handling these cases. This was actually easy. The menu is an example of how we used this concept to approach a problem that is classically dealt with in a completely different way. There are a couple of things we did not show yet. For example, we already have a simple implementation of how to make a Moose model completely browseable through this interface. But, as with the inspector, the coolest thing is that if someone has a specific need, it is even simpler than with the inspector to hook that need in the system and make it searchable. Your list is definitely exciting, and I am hoping that people will start playing a bit and discover things we otherwise would not consider. It should be easier than with the inspector (because there are less things to specify, hence less variation). And wait to see what happens when we start to combine this interface with others. For example, the interesting thing about being able to search a menu is that you can actually open any menu with a spotter, which essentially has the potential of changing the way we deal with contextual actions (all through keybindings without shortcuts). I am quite sure we are just scratching the surface of what is possible. So, let's play together :). Cheers, Doru On Sun, Dec 7, 2014 at 10:35 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Doru, > > One of the things/aspects that I miss a bit is the 'objects' part. In your > overall description/presentation you talk about 'objects', but right now I > would say it are mainly 'code objects' like classes & methods and friends, > and some IDE artefacts, like menus. > > What about arbitrary (user) objects ? > > Literal constants, like 123, 'some string' ? > Globals like the Transcript ? > Singletons accessible by class side accessors, like announcers ? > An evaluation functionality, just type an expression ? > Examples ? > The clipboard (contents), open windows, processes, ... > > Anyway, I am sure you get the idea ;-) > > Sven > > > On 07 Dec 2014, at 19:07, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > Hi Sven, > > > > Thanks for the kind words. Indeed, having the current selection is one > of the things we should keep in mind. For that we need to go to the next > step and integrate the interface in the overall environment. This will > certainly come. > > > > Cheers, > > Doru > > > > > > > > On Sun, Dec 7, 2014 at 6:57 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > > > > On 07 Dec 2014, at 14:14, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > > > Alex Syrel, Andrei Chis and I are happy to announce a new addition to > the Glamorous Toolkit: > > > GTSpotter, a novel interface for spotting objects. > > > > Excellent work, all around. Congratulations to the team. Thank you for > pushing things like this, for thinking differently. > > > > Yes, I want this in Pharo 4 too, ASAP (especially since the main > shortcut is different from the old one, cmd+Enter vs. shift+Enter). > > > > The presentation is again very well done too: excellent article, super > movie. You are putting the bar very high for the rest of us ;-) > > > > A suggestion/idea: would it be possible to take the current selection > anywhere and feed it into Spotter ? That way there would be very good way > to make it replace all the other shortcuts: you would get implementers, > senders, references almost for free. > > > > Sven > > > > > > > > > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 7, 2014

Re: [Pharo-users] [Pharo-dev] [Moose-dev] [ann] gtspotter: a moldable interface for spotting objects

by Sven Van Caekenberghe

Doru, One of the things/aspects that I miss a bit is the 'objects' part. In your overall description/presentation you talk about 'objects', but right now I would say it are mainly 'code objects' like classes & methods and friends, and some IDE artefacts, like menus. What about arbitrary (user) objects ? Literal constants, like 123, 'some string' ? Globals like the Transcript ? Singletons accessible by class side accessors, like announcers ? An evaluation functionality, just type an expression ? Examples ? The clipboard (contents), open windows, processes, ... Anyway, I am sure you get the idea ;-) Sven > On 07 Dec 2014, at 19:07, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi Sven, > > Thanks for the kind words. Indeed, having the current selection is one of the things we should keep in mind. For that we need to go to the next step and integrate the interface in the overall environment. This will certainly come. > > Cheers, > Doru > > > > On Sun, Dec 7, 2014 at 6:57 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 07 Dec 2014, at 14:14, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > Alex Syrel, Andrei Chis and I are happy to announce a new addition to the Glamorous Toolkit: > > GTSpotter, a novel interface for spotting objects. > > Excellent work, all around. Congratulations to the team. Thank you for pushing things like this, for thinking differently. > > Yes, I want this in Pharo 4 too, ASAP (especially since the main shortcut is different from the old one, cmd+Enter vs. shift+Enter). > > The presentation is again very well done too: excellent article, super movie. You are putting the bar very high for the rest of us ;-) > > A suggestion/idea: would it be possible to take the current selection anywhere and feed it into Spotter ? That way there would be very good way to make it replace all the other shortcuts: you would get implementers, senders, references almost for free. > > Sven > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Dec. 7, 2014

Re: [Pharo-users] Emergency evaluator and GTGenericStackDebugger

by Tudor Girba

You can actually do the same in Pharo 3 as well. Doru On Sun, Dec 7, 2014 at 9:31 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > Hi, > > what image do you use? > If it is pharo4, you can open the settings (World menu>System>Settings) > and disable GT playground and inspector (Glamorous Toolkit settings) > > > > > 2014-12-07 6:08 GMT+01:00 Edward Povazan <empovazan(a)gmail.com>: > >> Hello, >> >> Iâve been using Pharo for a while as my playground for trying things out, >> itâs a very soothing place to code and figure out algorithms (except that >> when I return to my âreal worldâ, the friction with modern tools is >> amplified). Iâm still a newb when it comes to knowing how things work >> deeper down. >> >> Iâm a little stuck. I did something (canât remember) and not realizing >> that I had a problem, saved my image too. >> Now when I try open a Workspace, I get a *** System error handling failed >> *** with a huge amount of text. >> >> Iâve uploaded a screen grab here: http://imgur.com/4ZwsF6e >> >> Is this worth debugging? >> >> My plan is to install the origin tools, and remove GToolkit. And then >> reinstall GToolkit. >> Would this help? >> >> And, how? I realize I donât know what tools are in the default Pharo3 >> image! >> Can someone tell me what they are called? >> >> Thanks! Canât wait to get back to the happy place! >> -Ed >> > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 7, 2014

Re: [Pharo-users] Emergency evaluator and GTGenericStackDebugger

by Nicolai Hess

Hi, what image do you use? If it is pharo4, you can open the settings (World menu>System>Settings) and disable GT playground and inspector (Glamorous Toolkit settings) 2014-12-07 6:08 GMT+01:00 Edward Povazan <empovazan(a)gmail.com>: > Hello, > > Iâve been using Pharo for a while as my playground for trying things out, > itâs a very soothing place to code and figure out algorithms (except that > when I return to my âreal worldâ, the friction with modern tools is > amplified). Iâm still a newb when it comes to knowing how things work > deeper down. > > Iâm a little stuck. I did something (canât remember) and not realizing > that I had a problem, saved my image too. > Now when I try open a Workspace, I get a *** System error handling failed > *** with a huge amount of text. > > Iâve uploaded a screen grab here: http://imgur.com/4ZwsF6e > > Is this worth debugging? > > My plan is to install the origin tools, and remove GToolkit. And then > reinstall GToolkit. > Would this help? > > And, how? I realize I donât know what tools are in the default Pharo3 > image! > Can someone tell me what they are called? > > Thanks! Canât wait to get back to the happy place! > -Ed >

Dec. 7, 2014

Re: [Pharo-users] [Esug-list] [ann] gtspotter: a moldable interface for spotting objects

by Tudor Girba

Hi Thierry, What I meant is that no IDE I know allows you to refine search through arbitrary levels of nesting. For example, looking for senders, filter, implementors, filter, senders, filter ... Is the AltBrowser able to do that? If so, I missed this one. Cheers, Doru On Sun, Dec 7, 2014 at 4:00 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > 2014-12-07 15:56 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > >> Thanks, Stef. >> >> On Sun, Dec 7, 2014 at 2:35 PM, stephane ducasse < >> stephane.ducasse(a)gmail.com> wrote: >> >>> Last time I found myself looking for the sender of x but only inside the >>> implementor of y. >>> and of course I wanted to refactored them. And the default message >>> browser is not parametrized via an environment :_ >>> >> >> Exactly. This problem exists in any IDE I know. >> > > AltBrowser has that type of search builtin. Not the refactoring step, > still. > > RBEnvironment allows that easily, it's just that the tools are not > designed for it. > > Thierry > > >> >> Doru >> >> >>> Stef >>> >>> On 07 Dec 2014, at 05:14, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> Alex Syrel, Andrei Chis and I are happy to announce a new addition to >>> the Glamorous Toolkit: >>> GTSpotter, a novel interface for spotting objects. >>> >>> GTSpotter has two goals: >>> - Provide a uniform yet moldable interface that can work on any object, >>> and >>> - Handle searching through arbitrary levels of object nesting. >>> >>> We think this will have a significant impact on the development workflow >>> in Pharo. >>> >>> Here is a couple of screenshots: >>> <gtspotter-packages-classes.png> >>> <gtspotter-dive-class-method-sender.png> <gtspotter-playground.png> >>> >>> >>> A trailer is available here: >>> https://www.youtube.com/watch?v=PhSmjR3NOlU >>> >>> A detailed description is available here: >>> http://www.humane-assessment.com/blog/introducing-gtspotter >>> >>> It works already in Pharo 3.0 and can be played with by following the >>> instructions from: >>> http://gt.moosetechnology.org >>> >>> Please let us know what you think. >>> >>> Enjoy, >>> The Glamorous Team >>> _______________________________________________ >>> Esug-list mailing list >>> Esug-list(a)lists.esug.org >>> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 7, 2014