September 2017 - Pharo-users

[DesktopManager] Ctlr - D (do-it) is blocked after installation of desktop manager

by H. Hirzel

Hello After I have installed the DesktopManager in Pharo 6.1 (labelled as 6.0) I cannot use the ctrl D shortcut to issue a 'do it' command. It interferes with the ctrl-D short cut system of the desktop manager. The do-it shortcut do execute a Smalltalk expression is more important for the than the direct access to the desktop manager. How can I resolve this? Menu 'Tools -> System -> Keymap browser' gives a list of key mapping assignments, but does not allow to edit them. Regards Hannes

Sept. 4, 2017

Re: [Pharo-users] [ann] moldable editor - transcript with adornments

by H. Hirzel

Great idea to introduce transcript next to get a builder object which in turn then implements the extended API! And the extended API allows to embed expandable elements. On 9/4/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > A new area is finally opening.... Great work. > > > On Mon, Sep 4, 2017 at 1:54 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> We are happy to announce that the moldable editor helped us create a >> richer transcript: GT Transcript. >> >> The transcript is traditionally a stream of plain text. As we now have an >> elaborate editor, we can take advantage of it to help us display richer >> representations. >> >> The API is backward compatible with the existing transcript. To enable >> the >> new features, we introduced a builder. For example: >> transcript nextPutAll: âsomethingâ >> becomes >> transcript next putAll: âsomethingâ >> and after #next we can add multiple attributes that we want to affect the >> following insertion of a text. >> >> Below you can find an example detailing most of the API. The most notable >> additions is the support for expandable adornments. For example, >> #showException: provides an in-place expansion of the stack of the >> exception context. >> >> >> To get an idea of how this tool can be useful, take a look at the >> following video showing the visual logging of a Bloc animation: >> https://youtu.be/9VATYNaLwJY >> >> >> The code can be found in the new incarnation of GToolkit: >> Iceberg enableMetacelloIntegration: true. >> Metacello new >> baseline: 'GToolkit'; >> repository: 'github://feenkcom/gtoolkit/src'; >> load. >> >> Cheers, >> The feenk team >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> âSoftware has no shape. Actually, it has no one shape. It has many." >> >> >

Sept. 4, 2017

Re: [Pharo-users] [ann] moldable editor - transcript with adornments

by Stephane Ducasse

A new area is finally opening.... Great work. On Mon, Sep 4, 2017 at 1:54 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > We are happy to announce that the moldable editor helped us create a > richer transcript: GT Transcript. > > The transcript is traditionally a stream of plain text. As we now have an > elaborate editor, we can take advantage of it to help us display richer > representations. > > The API is backward compatible with the existing transcript. To enable the > new features, we introduced a builder. For example: > transcript nextPutAll: âsomethingâ > becomes > transcript next putAll: âsomethingâ > and after #next we can add multiple attributes that we want to affect the > following insertion of a text. > > Below you can find an example detailing most of the API. The most notable > additions is the support for expandable adornments. For example, > #showException: provides an in-place expansion of the stack of the > exception context. > > > To get an idea of how this tool can be useful, take a look at the > following video showing the visual logging of a Bloc animation: > https://youtu.be/9VATYNaLwJY > > > The code can be found in the new incarnation of GToolkit: > Iceberg enableMetacelloIntegration: true. > Metacello new > baseline: 'GToolkit'; > repository: 'github://feenkcom/gtoolkit/src'; > load. > > Cheers, > The feenk team > > -- > www.tudorgirba.com > www.feenk.com > > âSoftware has no shape. Actually, it has no one shape. It has many." > >

Sept. 4, 2017

Re: [Pharo-users] You can help me

by Ben Coman

Do you mean applications, or infrastructure? For applications, you might to consider getting on the phone to interview developers from Pharo Success Stories... http://pharo.org/success cheers -ben On Fri, Sep 1, 2017 at 6:16 AM, horrido <horrido.hobbies(a)gmail.com> wrote: > I'm writing an article about Pharo. I would like to list the Top 10 "really > big" things that have been developed in the past several years, /or are > being developed right now/. Please word it in a way that laypeople (like > CTOs and non-Smalltalkers) can understand. Thanks. > > (I know "really big" is rather subjective. I leave it to your discretion.) > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Sept. 4, 2017

[ann] moldable editor - transcript with adornments

by Tudor Girba

Hi, We are happy to announce that the moldable editor helped us create a richer transcript: GT Transcript. The transcript is traditionally a stream of plain text. As we now have an elaborate editor, we can take advantage of it to help us display richer representations. The API is backward compatible with the existing transcript. To enable the new features, we introduced a builder. For example: transcript nextPutAll: âsomethingâ becomes transcript next putAll: âsomethingâ and after #next we can add multiple attributes that we want to affect the following insertion of a text. Below you can find an example detailing most of the API. The most notable additions is the support for expandable adornments. For example, #showException: provides an in-place expansion of the stack of the exception context. To get an idea of how this tool can be useful, take a look at the following video showing the visual logging of a Bloc animation: https://youtu.be/9VATYNaLwJY The code can be found in the new incarnation of GToolkit: Iceberg enableMetacelloIntegration: true. Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load. Cheers, The feenk team -- www.tudorgirba.com www.feenk.com âSoftware has no shape. Actually, it has no one shape. It has many."

Sept. 3, 2017

Re: [Pharo-users] Usability issues with Calypso

by Tim Mackinnon

Ah - you are right that rename is in there (Iâd never noticed it was in the suggestions menu - which I find a confusingly named sub-menu ) - but I am missing the more appropriately named âSource Code Refactoringâ menu, which it also appears along with extract method etc. This menu is not in Calypso right? Tim > On 3 Sep 2017, at 17:24, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi Tim. > > No. It is available by cmd+r and from suggestions menu like in Nautilus. But maybe I do not know other place which you use for this > > 2017-09-03 17:03 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: > Hi Denis - I just noticed that the source refactoring menu is missing in Calypso as well? (So you canât rename a temp for example). > > Tim > >> On 2 Sep 2017, at 10:30, Denis Kudriashov <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>> wrote: >> >> Hi >> >> 2017-09-01 14:26 GMT+02:00 kmo <voxkmp(a)gmail.com <mailto:voxkmp@gmail.com>>: >> I have been keen to use Calypso (I love the way it shows inherited methods) >> as my browser but I am finding some usability issues. It may be just me but >> some things I find off-putting. >> >> Any feedback is very important. >> >> >> I don't really like the way that adding a new class is done by a new tab >> that appears now and then in the editing area. To my mind the Nautilus way >> of launching a dialog to create a class seems more natural - and opens the >> way in future for a class creation wizard - something that can't be done in >> a code window. If we have to do it in a code tab then it would be better if >> the tab remained there all the time - I don't like the way it appears and >> disappears. It takes a while to learn what to click to do this. >> >> In fact current behaviour is not replacement of old context menu command. It is just rethinking of classic single source code pane of old browsers. >> So we will add missing command to context menu. But I think the command should open the current "New class" tab instead of old dialog request. >> Also old browser behaviour is still working. You can create new class from the class editor tab. Just type new class name in the definition of selected class. >> >> >> Also, all class creation presumes a subclass of Object in Calypso. i miss >> the ability in Nautilus to select a class and immediately create a subclass >> of it. Am I missing something here? Is there a way? >> >> You are right. It is missing command like previous one. We will add it. >> >> >> On the topic of my ignorance - what is a /project /in Calypso? How do you >> create one? >> >> Now it is more like a stub. >> There is integration with new package management Cargo (Christophe is working on it). But it is probably not ready yet. >> I think we should also implement Metacello backend. >> Anyway project mode will become default view in future. >> >> >> And what does realize do? >> >> It creates stub implementation of abstract methods (found in superclasses). >> I think in Calypso this command is not needed anymore because there is "should be implemented" method group which shows all these abstract methods. >> >> >> Also I think that the pop up menus could be subdivided into categories >> rather than present all the options in an unbroken list. And the order of >> options seems odd. To my mind/ senders /and /implementers /are two menu >> options that should always go together - not be separated by/ rename/ and >> /move to class side/ et cetera. >> >> Yes, I will add it. >> >> You can report issues directly at github project https://github.com/dionisiydk/Calypso/issues. <https://github.com/dionisiydk/Calypso/issues.> >> Thank's for you feedback. >> >> >> >> Just my two cents. >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> >> >> > >

Sept. 3, 2017

Re: [Pharo-users] Bitbucket CI

by Peter UhnÃ¡k

I am familiar neither with BuildCI nor pharo-build, nor was I aware that they would be popular/used/ready-to-use as SmalltalkCI On Sun, Sep 3, 2017 at 5:03 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Peter UhnÃ¡k wrote > > SmalltalkCI... you should be able to run it on any linux box > > Thanks. I got it working locally fairly easily. During my investigation, I > noticed that SmalltalkCI seems to be based on BuildCI, which is in turn > built on pharo-builder. I can't help but wonder why so many frameworks - > are > these for distinct use cases, or more like different flavors? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Sept. 3, 2017

Re: [Pharo-users] Usability issues with Calypso

by Denis Kudriashov

Hi Tim. No. It is available by cmd+r and from suggestions menu like in Nautilus. But maybe I do not know other place which you use for this 2017-09-03 17:03 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > Hi Denis - I just noticed that the source refactoring menu is missing in > Calypso as well? (So you canât rename a temp for example). > > Tim > > On 2 Sep 2017, at 10:30, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi > > 2017-09-01 14:26 GMT+02:00 kmo <voxkmp(a)gmail.com>: > >> I have been keen to use Calypso (I love the way it shows inherited >> methods) >> as my browser but I am finding some usability issues. It may be just me >> but >> some things I find off-putting. >> > > Any feedback is very important. > > >> >> I don't really like the way that adding a new class is done by a new tab >> that appears now and then in the editing area. To my mind the Nautilus way >> of launching a dialog to create a class seems more natural - and opens the >> way in future for a class creation wizard - something that can't be done >> in >> a code window. If we have to do it in a code tab then it would be better >> if >> the tab remained there all the time - I don't like the way it appears and >> disappears. It takes a while to learn what to click to do this. >> > > In fact current behaviour is not replacement of old context menu command. > It is just rethinking of classic single source code pane of old browsers. > So we will add missing command to context menu. But I think the command > should open the current "New class" tab instead of old dialog request. > Also old browser behaviour is still working. You can create new class from > the class editor tab. Just type new class name in the definition of > selected class. > > >> >> Also, all class creation presumes a subclass of Object in Calypso. i miss >> the ability in Nautilus to select a class and immediately create a >> subclass >> of it. Am I missing something here? Is there a way? >> > > You are right. It is missing command like previous one. We will add it. > > >> >> On the topic of my ignorance - what is a /project /in Calypso? How do you >> create one? >> > > Now it is more like a stub. > There is integration with new package management Cargo (Christophe is > working on it). But it is probably not ready yet. > I think we should also implement Metacello backend. > Anyway project mode will become default view in future. > > >> And what does realize do? >> > > It creates stub implementation of abstract methods (found in superclasses). > I think in Calypso this command is not needed anymore because there is > "should be implemented" method group which shows all these abstract methods. > > >> >> Also I think that the pop up menus could be subdivided into categories >> rather than present all the options in an unbroken list. And the order of >> options seems odd. To my mind/ senders /and /implementers /are two menu >> options that should always go together - not be separated by/ rename/ and >> /move to class side/ et cetera. >> > > Yes, I will add it. > > You can report issues directly at github project https://github.com/ > dionisiydk/Calypso/issues. > Thank's for you feedback. > > > >> >> Just my two cents. >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> > >

Sept. 3, 2017

Re: [Pharo-users] Usability issues with Calypso

by Tim Mackinnon

Hi Denis - I just noticed that the source refactoring menu is missing in Calypso as well? (So you canât rename a temp for example). Tim > On 2 Sep 2017, at 10:30, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi > > 2017-09-01 14:26 GMT+02:00 kmo <voxkmp(a)gmail.com <mailto:voxkmp@gmail.com>>: > I have been keen to use Calypso (I love the way it shows inherited methods) > as my browser but I am finding some usability issues. It may be just me but > some things I find off-putting. > > Any feedback is very important. > > > I don't really like the way that adding a new class is done by a new tab > that appears now and then in the editing area. To my mind the Nautilus way > of launching a dialog to create a class seems more natural - and opens the > way in future for a class creation wizard - something that can't be done in > a code window. If we have to do it in a code tab then it would be better if > the tab remained there all the time - I don't like the way it appears and > disappears. It takes a while to learn what to click to do this. > > In fact current behaviour is not replacement of old context menu command. It is just rethinking of classic single source code pane of old browsers. > So we will add missing command to context menu. But I think the command should open the current "New class" tab instead of old dialog request. > Also old browser behaviour is still working. You can create new class from the class editor tab. Just type new class name in the definition of selected class. > > > Also, all class creation presumes a subclass of Object in Calypso. i miss > the ability in Nautilus to select a class and immediately create a subclass > of it. Am I missing something here? Is there a way? > > You are right. It is missing command like previous one. We will add it. > > > On the topic of my ignorance - what is a /project /in Calypso? How do you > create one? > > Now it is more like a stub. > There is integration with new package management Cargo (Christophe is working on it). But it is probably not ready yet. > I think we should also implement Metacello backend. > Anyway project mode will become default view in future. > > > And what does realize do? > > It creates stub implementation of abstract methods (found in superclasses). > I think in Calypso this command is not needed anymore because there is "should be implemented" method group which shows all these abstract methods. > > > Also I think that the pop up menus could be subdivided into categories > rather than present all the options in an unbroken list. And the order of > options seems odd. To my mind/ senders /and /implementers /are two menu > options that should always go together - not be separated by/ rename/ and > /move to class side/ et cetera. > > Yes, I will add it. > > You can report issues directly at github project https://github.com/dionisiydk/Calypso/issues. <https://github.com/dionisiydk/Calypso/issues.> > Thank's for you feedback. > > > > Just my two cents. > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> > >

Sept. 3, 2017

Re: [Pharo-users] Bitbucket CI

by Sean P. DeNigris

Peter UhnÃ¡k wrote > SmalltalkCI... you should be able to run it on any linux box Thanks. I got it working locally fairly easily. During my investigation, I noticed that SmalltalkCI seems to be based on BuildCI, which is in turn built on pharo-builder. I can't help but wonder why so many frameworks - are these for distinct use cases, or more like different flavors? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 3, 2017