August 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Where (as in Git project) should Calypso browser source code commands live?

by Denis Kudriashov

it is separate repo https://github.com/pharo-ide/SystemCommands 2018-08-19 23:12 GMT+01:00 Tim Mackinnon <tim(a)testit.works>: > Thanks for chipping in Denis - I guess whatâs weird about this set of > commands is that they are a bit editor specific as they all move your > cursor or text selection to specific places (the other commands are much > more generic). > > Still, I think it makes sense to put them in a sub-package like > SystemCommands-SourceNaviagationCommands. > > But I guess my real question is, what project owns these commands? When I > make changes, neither the Pharo nor Calypso projects show anything to > commit ? > > Tim > > Sent from my iPhone > > > > Sent from my iPhone > On 19 Aug 2018, at 14:41, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi Tim. > > The idea was to have reusable commands to work with system objects > (method, classes and packages). It is clear that those commands should not > depends on browser and should be accessible from other tools. This is the > reason why they are packaged separately (SystemCommands > <https://github.com/pharo-ide/SystemCommands>). > > According to your question I would add your commands to > SystemCommands-SourceCodeCommands package because they are bound to > source code, not just to text editor. > > 2018-08-19 16:12 GMT+01:00 Tim Mackinnon <tim(a)testit.works>: > >> Hi - Iâve had a few changes lined up to try and help P7 be a little more >> IntelliJ like. But Iâm not sure what package my small extensions should >> live in? >> >> I used SycRenameTempCommand as an example - but it lives in a package >> called "SystemCommands-SourceCodeCommandsâ - however I canât see where >> that package is git versioned as when I browse the Pharo working copy, it >> doesnât appear. Is this some low level piece that hasnât been moved into >> git yet? >> >> My commands are - ExtendSelection (a keypress to intelligently widen the >> selection of selected code to aid refactoring or moving code around), and >> JumpToNextKeyword - a keystroke to intelligently jump you to where you can >> enter a code completed keyboard or block variable etc. >> >> This got me thinking - about where these should live - are they in the >> Calypso project - and would l do a PR there - or are they in Pharo and I >> create a PR there? >> >> Suggestions? >> >> Tim >> > >

Aug. 19, 2018

Re: [Pharo-users] Where (as in Git project) should Calypso browser source code commands live?

by Tim Mackinnon

Thanks for chipping in Denis - I guess whatâs weird about this set of commands is that they are a bit editor specific as they all move your cursor or text selection to specific places (the other commands are much more generic). Still, I think it makes sense to put them in a sub-package like SystemCommands-SourceNaviagationCommands. But I guess my real question is, what project owns these commands? When I make changes, neither the Pharo nor Calypso projects show anything to commit ? Tim Sent from my iPhone Sent from my iPhone > On 19 Aug 2018, at 14:41, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi Tim. > > The idea was to have reusable commands to work with system objects (method, classes and packages). It is clear that those commands should not depends on browser and should be accessible from other tools. This is the reason why they are packaged separately (SystemCommands). > > According to your question I would add your commands to SystemCommands-SourceCodeCommands package because they are bound to source code, not just to text editor. > > 2018-08-19 16:12 GMT+01:00 Tim Mackinnon <tim(a)testit.works>: >> Hi - Iâve had a few changes lined up to try and help P7 be a little more IntelliJ like. But Iâm not sure what package my small extensions should live in? >> >> I used SycRenameTempCommand as an example - but it lives in a package called "SystemCommands-SourceCodeCommandsâ - however I canât see where that package is git versioned as when I browse the Pharo working copy, it doesnât appear. Is this some low level piece that hasnât been moved into git yet? >> >> My commands are - ExtendSelection (a keypress to intelligently widen the selection of selected code to aid refactoring or moving code around), and JumpToNextKeyword - a keystroke to intelligently jump you to where you can enter a code completed keyboard or block variable etc. >> >> This got me thinking - about where these should live - are they in the Calypso project - and would l do a PR there - or are they in Pharo and I create a PR there? >> >> Suggestions? >> >> Tim >

Aug. 19, 2018

Re: [Pharo-users] How best to cope with 2 editor/browser frameworks - Calypso and RubSmalltalkEditor

by Tim Mackinnon

Thanks Denis - I guess for now I can put the methods in RubSmalltalkEditor so that the playground can operate and then my Calypso plugins can also reference that code too (if class methods). Is the idea that playground will become part of Calypso too? If so, I can add the methods I need as an extension (although I guess this wonât work as the keyboard mapping for playground in one method and not extensible like Calypso which uses pragmas). Iâll do something as a pr and we can figure it out. Itâs worth saying, that for my Calypso plugins Iâve had to abuse your mechanism a bit as the simple #execute mechanism doesnât give me access to the text morph to control the cursor. I was able to do it though via the prompting mechanism (I just donât show any ui prompt). Tim Sent from my iPhone > On 19 Aug 2018, at 14:28, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi. > > I dont't know answer to your question. But for the note: > Calypso was needed to override existing way to spawn implementors/senders and so on. So I added subclass of RubSmalltalkEditor - ClyTextEditor which overrides required methods. > So if you will put new methods into the RubSmalltalkEditor then Calypso will be able to use them. > > 2018-08-19 16:55 GMT+01:00 Tim Mackinnon <tim(a)testit.works>: >> Hi Iâm trying to work out the best way to cope with the fact that we are in a hybrid place where the Playground is using an RubSmalltalkEditor but Calypso has its own mechanisms for editing code. >> >> I have commands that should/can work in both the playground as well as code method editor (in Calypso). >> >> Previously my code lived in RubSmalltalkEditor and Nautilus was using that too - but now Iâm not sure where to put some reusable methods that use RBParser and the AST to find the best place to position your cursor. >> >> I can make a class method on RubSmalltalkEditor and Calypso commands could reference that (but that feels wrong somehow). I could make some extension methods on RBParser and both places reference that - but then who should own the extension method (as I think RubSmalltalkEditor is lower level and Calypso is then loaded on top). >> >> Anyone have some good suggestions? >> >> Tim >

Aug. 19, 2018

Re: [Pharo-users] Where (as in Git project) should Calypso browser source code commands live?

by Denis Kudriashov

Hi Tim. The idea was to have reusable commands to work with system objects (method, classes and packages). It is clear that those commands should not depends on browser and should be accessible from other tools. This is the reason why they are packaged separately (SystemCommands <https://github.com/pharo-ide/SystemCommands>). According to your question I would add your commands to SystemCommands-SourceCodeCommands package because they are bound to source code, not just to text editor. 2018-08-19 16:12 GMT+01:00 Tim Mackinnon <tim(a)testit.works>: > Hi - Iâve had a few changes lined up to try and help P7 be a little more > IntelliJ like. But Iâm not sure what package my small extensions should > live in? > > I used SycRenameTempCommand as an example - but it lives in a package > called "SystemCommands-SourceCodeCommandsâ - however I canât see where > that package is git versioned as when I browse the Pharo working copy, it > doesnât appear. Is this some low level piece that hasnât been moved into > git yet? > > My commands are - ExtendSelection (a keypress to intelligently widen the > selection of selected code to aid refactoring or moving code around), and > JumpToNextKeyword - a keystroke to intelligently jump you to where you can > enter a code completed keyboard or block variable etc. > > This got me thinking - about where these should live - are they in the > Calypso project - and would l do a PR there - or are they in Pharo and I > create a PR there? > > Suggestions? > > Tim >

Aug. 19, 2018

Re: [Pharo-users] How best to cope with 2 editor/browser frameworks - Calypso and RubSmalltalkEditor

by Denis Kudriashov

Hi. I dont't know answer to your question. But for the note: Calypso was needed to override existing way to spawn implementors/senders and so on. So I added subclass of RubSmalltalkEditor - ClyTextEditor which overrides required methods. So if you will put new methods into the RubSmalltalkEditor then Calypso will be able to use them. 2018-08-19 16:55 GMT+01:00 Tim Mackinnon <tim(a)testit.works>: > Hi Iâm trying to work out the best way to cope with the fact that we are > in a hybrid place where the Playground is using an RubSmalltalkEditor but > Calypso has its own mechanisms for editing code. > > I have commands that should/can work in both the playground as well as > code method editor (in Calypso). > > Previously my code lived in RubSmalltalkEditor and Nautilus was using that > too - but now Iâm not sure where to put some reusable methods that use > RBParser and the AST to find the best place to position your cursor. > > I can make a class method on RubSmalltalkEditor and Calypso commands could > reference that (but that feels wrong somehow). I could make some extension > methods on RBParser and both places reference that - but then who should > own the extension method (as I think RubSmalltalkEditor is lower level and > Calypso is then loaded on top). > > Anyone have some good suggestions? > > Tim >

Aug. 19, 2018

How best to cope with 2 editor/browser frameworks - Calypso and RubSmalltalkEditor

by Tim Mackinnon

Hi Iâm trying to work out the best way to cope with the fact that we are in a hybrid place where the Playground is using an RubSmalltalkEditor but Calypso has its own mechanisms for editing code. I have commands that should/can work in both the playground as well as code method editor (in Calypso). Previously my code lived in RubSmalltalkEditor and Nautilus was using that too - but now Iâm not sure where to put some reusable methods that use RBParser and the AST to find the best place to position your cursor. I can make a class method on RubSmalltalkEditor and Calypso commands could reference that (but that feels wrong somehow). I could make some extension methods on RBParser and both places reference that - but then who should own the extension method (as I think RubSmalltalkEditor is lower level and Calypso is then loaded on top). Anyone have some good suggestions? Tim

Aug. 19, 2018

Re: [Pharo-users] Gemstone as a service?

by James Foster

> On Aug 19, 2018, at 1:28 AM, Marten Feldtmann <itlists(a)schrievkrom.de> wrote: > > This would be of general interest ... I suppose > > Marten Iâm certainly hoping so! From the schedule: A Browser-based IDE for Cloud-hosted GemStone When Wed, September 12, 12:30pm â 12:45pm Description James Foster Polito While Smalltalk has been an innovator in many ways, hosted development tools has not been a notable area of leadership. Smalltalkâs ecosystem tends to have a more challenging install process (particularly for GemStone) and this may limit its ability to attract attention. Tools like Cloud9 and Jupyter make it very easy to experiment with C++ or Python using just a web browser. In this presentation we look at an approach to using GemStone in the cloud with only a web browser. James Foster P.S. Iâm not sure how âPolitioâ got added to my name in the ESUG schedule, but https://www.urbandictionary.com/define.php?term=Polito <https://www.urbandictionary.com/define.php?term=Polito>, gives the following definition: "A sweet, innocent guy at heart. Not afraid to express himself. Full of prosperity <https://www.urbandictionary.com/define.php?term=prosperity> and talent, loving every moment he gets from pleasing a crowd. A carefree character that has a clear feminine side. Stands out from the crowd and always has something to share and someone to share it with. Moves on quickly through life and is admired by many, but hurts people with comments that may seem very simple to him. Naive at times, Linguistic <https://www.urbandictionary.com/define.php?term=Linguistic>, cheerful, honest, smiley, juvenile <https://www.urbandictionary.com/define.php?term=juvenile>, good-looking, confident, funny, talented.... this list could go on forever ;) " > Am 19.08.2018 um 05:15 schrieb James Foster: >> Will you be coming to ESUG? Perhaps we could discuss this in more detail >> after my talk on Wednesday at 12:30 >> (https://esug.github.io/2018-Conference/conf2018.html) >> >> James Foster >> >>> On Aug 18, 2018, at 9:11 AM, Andy Burnett >>> <andy.burnett(a)knowinnovation.com >>> <mailto:andy.burnett@knowinnovation.com>> wrote: >>> >>> Hello, >>> I was wondering if anyone offers GaaS? I would love to be able to just >>> focus on writing code, and leave the system management to others. >>> Gemstone does seem to offer a very complete package. >>> >>> Also, does anyone know what's happening with Pharocloud? The site is >>> still running, but it seems to be very quiet. >>> >>> Cheers >>> Andy >> > > > -- > Marten Feldtmann >

Aug. 19, 2018

Where (as in Git project) should Calypso browser source code commands live?

by Tim Mackinnon

Hi - Iâve had a few changes lined up to try and help P7 be a little more IntelliJ like. But Iâm not sure what package my small extensions should live in? I used SycRenameTempCommand as an example - but it lives in a package called "SystemCommands-SourceCodeCommandsâ - however I canât see where that package is git versioned as when I browse the Pharo working copy, it doesnât appear. Is this some low level piece that hasnât been moved into git yet? My commands are - ExtendSelection (a keypress to intelligently widen the selection of selected code to aid refactoring or moving code around), and JumpToNextKeyword - a keystroke to intelligently jump you to where you can enter a code completed keyboard or block variable etc. This got me thinking - about where these should live - are they in the Calypso project - and would l do a PR there - or are they in Pharo and I create a PR there? Suggestions? Tim

Aug. 19, 2018

Re: [Pharo-users] Error in fresh image

by Ben Coman

On Sat, 18 Aug 2018 at 20:21, Jeff Gray <jeff(a)rogerthedog.com> wrote: > > I am trying to recover my project from a broken image, so thought I could get > a fresh image and then import from the old changes file. > > I just downloaded and unzipped the Pharo Standalone for Windows. > I unzipped it and copied the image and changes to my existing Pharo 6.1 > folder. > The first thing I see is this error: > > <http://forum.world.st/file/t160774/pharo.png> > > Should I try too get an older image file or will somebody look at fixing in > a new version? I'm not sure. There is a setting "Use Free type..." that you can try turning off-then-on to reset fonts. Could you provide the exact link you downloaded to ensure others can test the same artifact? cheers -ben

Aug. 19, 2018

Re: [Pharo-users] RubShoutStylerDecorator doesnotunderstand: #move:for:controller:

by Jeff Gray

I've fixed it. Looks like a lot of the code, but not all, had been auto-formatted. I didn't consciously do it, but I may have fallen asleep while coding and mashed some keys. I'm getting up early (4am) so coming home on the train at 6:00pm is pretty sketchy :-) I pulled the code into a new image from the changes file, which fortunately did not include the formatting, so could copy back the original code into my broken image. Once complete everything works again. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 19, 2018