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

Re: [Pharo-users] Interesting Pharo Launcher feedback

by Tim Mackinnon

Just as a small visualisation of below - I hacked the titles just to see (and maybe the project metaphor isnât a bad one?) > On 26 Jun 2018, at 09:13, Tim Mackinnon <tim(a)testit.works> wrote: > > As I mentioned - the user in question was quite complimentary, just confused on first launch. > > Equally we donât want to impact power users, and ultimately we want to encourage everyone to try newer images to help with improvements. > > I honestly think that some slightly improved terminology and a bit of guidance to get your first image (eg picking the correct one) is all it takes. > > Once youâve groked it - you are off. We just want that first experience to be pleasant. > > I personally like to see the list of images and understand how many builds have been made as itâs comforting to see the progress and be encouraged to join in. > > I as going to propose a simple change to the name on the lists like: > > âTemplatesâ -> âImage Templatesâ or maybe even âProject Templatesâ > > âImagesâ -> âDownloaded Imagesâ or maybe âCreated Projectsâ > > (While we are familiar with the term image, maybe itâs an implementation detail - eclipse and IntelliJ create projects, and we arenât so different) > > We could also as Cyril suggests, have a little welcome window with some text and a picture. > > Both really simple to do and probably enough to get people started. After all, our audience is reasonable technical so we shouldnât need to dumb It down too much. > > Iâm also conscious about here is a lot of Pharo 7 work to do as well. > > Tim > > Sent from my iPhone > > On 26 Jun 2018, at 08:09, Christophe Demarey <christophe.demarey(a)inria.fr <mailto:christophe.demarey@inria.fr>> wrote: > >> Hi Tim, >> >>> Le 26 juin 2018 Ã 03:00, Ben Coman <btc(a)openinworld.com <mailto:btc@openinworld.com>> a Ã©crit : >>> >>> On 26 June 2018 at 06:17, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>> Hi everyone - at tonights month UK Smalltalk Meetup, we got some nice compliments on the state of Pharo (the participants - all ex small talkers - although ex in so much as they fondly remembered it and wanted to use it for something relevant now because they enjoyed it in the past). >>> >>> Anyway, one interesting comment stuck out - he had downloaded Pharo (having used Visual Age 15+ years ago) and was a bit overwhelmed with what laugher presented to him. He didnât hate it - but was initially a bit lost as to what it all meant and how to startâ¦ he figured it out, but I thought the feedback was interesting and made me think that maybe we need some form of intro wizard to get people off to a quick start but leave them confident enough that they might come back and try a Pharo 7 or Moose etc. >>> >>> I encouraged him to post something on here, but thoughtI would note it (as it seems quite easy to fix) as an idea while it was fresh in my mind. >>> >>> >>> A welcome tutorial is a good idea. And btw, the sort of idea that only comes from broader use of PharoLauncher. >> >> Thanks for the feedback. >> We also got this feedback from students. We know we have to improve the UI by simplifying it. >> Our idea was to only provide a window with a toolbar and the list of images as the main Pharo Launhcer window. >> On this windows, clicking on the + button will open a Â« wizard Â» like the one for creating repositories in Iceberg. There you could choose to create an image from Â« featured images Â» or ci, etc. >> >> It would lower a lot the cognitive charge of the current window. >> We just need time to implement it. >> >> Cheers, >> Christophe >> >>

June 26, 2018

The cool implication of gtDocumentor gluing examples and how we might augment source naviagation

by Tim Mackinnon

Hi guys - not sure how many people noticed this, but at the end of the tutorial for gtDocumentor, there is a section on Examples as Documentation. What is neat (and easily missed) is how when an example references another - there is a little triangle you can toggle to expose that example inline. (See photo). This isnât a completely new ideas (didnât Newspeak hopscotch do this?) but its very well done in gtDocumentor and this implication could be that if our code editors had this too - then its very handy to unfold code to understand it in one place without having to open new windows. (I still think there are times when you may want to do that - particularly for long chains of methods?) but its certainly an idea that I would be very receptive to having in our code browsers (heck - give me all of gtDocumentor in our source editors). Iâm wondering what others thing of this? Perhpas not for Pharo 7 - but Pharo 8 (pretty please?) Tim p.s. Note to @feenk, as its the last example its incredibly tricky to expand it to actually see it well as you canât scroll further down to then drag the window bigger. I had to add a lot of Crâs to make some space to do this.

June 26, 2018

Re: [Pharo-users] [Moose-dev] [ann] gt documenter

by Tim Mackinnon

Hi - yes, doing the Reset Bloc did fix the problem and I can run both examples (and it doesnât appear to break after running one or the other). HOWEVER - after the reset, when I ran the example with the Mondrian views - right near the beginning where it opens a Pharo browser - the GTDocumentor window turned red with a cross (Note: I had done inspect on the example vs. a playground so I could have a bigger window. I only now noticed that the playground doesnât use a splitter to let you resize its panes?). I had to close my document and try it again - and this time it was fine - but obviously something broke in the sequence of events. Tim > On 26 Jun 2018, at 06:02, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > It looks like something broke in your Bloc. You can reset Bloc from the world menu / Bloc / Reset Bloc. Please let me know if it works. > > Cheers, > Doru > > >> On Jun 26, 2018, at 12:54 AM, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi - so I managed to load up the full monty gtDocumentor into an image (a few false starts as it you try and load the full monty on top of just gtDocumentor e.g in a clean image load >> >> Metacello new >> baseline: 'GToolkit'; >> repository: ' >> github://feenkcom/gtoolkit/src >> '; >> load. >> >> On top of this >> Metacello new >> baseline: 'GToolkitDocumenter'; >> repository: ' >> github://feenkcom/gtoolkit-documenter/src >> '; >> load. >> >> >> It never completes - I gave up after 30 minutes and whining fans on a MacBook Pro. >> >> Anyway - in a completely clean image I loaded just GTookkit and then run >> >> GtDocumenter editorForText: BrToggleExamples comment. >> >> Which seemed to work fine - and showed me some buttons with different dots on them. >> >> So then I went and tried the example I really wanted to see: >> >> IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillarâ. >> >> And it just gives a blank tab in the _Pillar, _Contents and _GT tabs? The contents tab does show me pillar text unrendered. >> >> Interestingly, If I then go back to the previous editorForText example, that did work - it now also also show the same blank tabs. So it seems that something get broken? >> >> This is on OSX with the a 64bit image - labelled 6.1 - 64bit (tech preview) - so the current stable pharo for 64 bit. >> >> Is this a known issue? >> >> Tim >> >> >>> On 20 Jun 2018, at 02:53, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>> Actually I realised it ended up on the be moose forum - hereâs what Doru replied (for any lurkers) >>> >>> >>> >>> Sent from my iPhone >>>> On Jun 18, 2018, at 1:21 PM, Tim Mackinnon <tim(a)testit.works> wrote: >>>> >>>> Guys this is really impressive! >>> >>> Thanks. >>> >>> >>>> 2 things I noticed when going through the example in a new Pharo 6.1 image (with the latest Iceberg) - >>>> >>>> 1) The example "IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar'. â has changed to âIceLibgitRepository â¦â in the newer iceberg - so it might be worth a note in the readme (Iâll submit a PR) >>> Show Quoted Content >>>> 2 things I noticed when going through the example in a new Pharo 6.1 image (with the latest Iceberg) - >>>> >>>> 1) The example "IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar'. â has changed to âIceLibgitRepository â¦â in the newer iceberg - so it might be worth a note in the readme (Iâll submit a PR) >>> >>> Ok. >>> >>> >>>> 2) In a clean 6.1 image I get a walkback (GtPhlowExplicitView>>mondrian DNU) when you try any of the graphical bits , making me think either the dependencies are incorrect on the Baseline (or the instruction for the example also need to mention you need to load something else - presumably Roassal? >>> >>> Indeed, this is due to the fact that loading GToolkitDocumenter does not load GToolkitVisualizer which includes GtMondrian. We are still working on finding the right dependencies balance. >>> >>> Until then, please load the whole GToolkit to get the full support. >>> >>> >>>> 3) You canât scroll the Diff tabs of results, only the Code tabs >>> >>> Good catch! >>> >>> >>> Cheers, >>> Doru >>> >>> Sent from my iPhone >>> >>> On 20 Jun 2018, at 02:47, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>>> Bump (not sure this got through , and keen to know how to load the diagramming bit) >>>> >>>> Guys this is really impressive! >>>> >>>> 2 things I noticed when going through the example in a new Pharo 6.1 image (with the latest Iceberg) - >>>> >>>> 1) The example "IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar'. â has changed to âIceLibgitRepository â¦â in the newer iceberg - so it might be worth a note in the readme (Iâll submit a PR) >>>> >>>> 2) In a clean 6.1 image I get a walkback (GtPhlowExplicitView>>mondrian DNU) when you try any of the graphical bits , making me think either the dependencies are incorrect on the Baseline (or the instruction for the example also need to mention you need to load something else - presumably Roassal? >>>> 3) You canât scroll the Diff tabs of results, only the Code tabs >>>> >>>> Tim >>>> >>>>> On 13 Jun 2018, at 21:57, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>> >>>>> Hi, >>>>> >>>>> We are happy to announce a new leap of GToolkit Documenter, the tool for manipulating live documents directly in the development environment: >>>>> https://github.com/feenkcom/gtoolkit-documenter >>>>> >>>>> Documenter is part of the second generation GToolkit project, it is based on Bloc and works with the latest Pillar. It is mainly developed by Juraj Kubelka. >>>>> >>>>> Attached you can see a preview of how documents look like: >>>>> >>>>> <gt-documenter.png> >>>>> >>>>> At its core it offers a live editor for manipulating Pillar documents. The interaction happens seamlessly directly in the text editor, and it can be combined with different types of previews to serve several classes of use cases: >>>>> â¢ code documentation >>>>> â¢ tutorials >>>>> â¢ interactive data notebook >>>>> >>>>> >>>>> Code documentation >>>>> ---- >>>>> Documenter complements the GToolkit Examples engine to redefine code documentation. When practicing example-driven development, examples get written as part of the typical development. Once examples exist, they can be quickly put together in a document to form documentation. For example, the linked picture shows the comment of a class containing a visual explanation: >>>>> https://twitter.com/feenkcom/status/973899862482866176 >>>>> >>>>> You can see a live example of documentation by inspecting the following snippet: >>>>> GtDocumenter editorForText: BrToggleExamples comment. >>>>> >>>>> >>>>> Tutorials: >>>>> ---- >>>>> Documenter offers a new experience of writing tutorials for Pharo by enabling the creation and embedding of Epicea change sessions directly in the document. For example, take a look at the following animation: >>>>> https://twitter.com/feenkcom/status/999975333972541440 >>>>> >>>>> The document shows a method on top, and a change preview at the bottom showing both the code and the associated diff to the state from the image. Applying the change updates both the change view (no more diff), and method preview. This speeds up significantly the process of going through a tutorial. Furthermore, given that now the document shows the diff to the current image, the reader can safely explore alternative scenario and come back to the tutorial at any time without losing the overview. >>>>> >>>>> The size of the preview can also be adjusted live: >>>>> https://twitter.com/feenkcom/status/1001152789874167808 >>>>> https://twitter.com/feenkcom/status/1001407762285375490 >>>>> >>>>> You can see a live tutorial by inspecting: >>>>> IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillarâ. >>>>> >>>>> >>>>> Interactive data notebook: >>>>> ---- >>>>> A Documenter document can also be used as an interactive notebook. Internally it essentially acts as a playground: >>>>> â¢ it supports defining variables in code snippets, and >>>>> â¢ the execution of code shows an embedded inspector. >>>>> >>>>> For example: >>>>> https://twitter.com/feenkcom/status/996310432225820672 >>>>> https://twitter.com/feenkcom/status/1002851190475026432 >>>>> >>>>> An example, can be seen by inspecting: >>>>> IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit' / 'doc' / 'gtoolkit' / 'gtoolkit.pillar'. >>>>> >>>>> >>>>> As always, please do let us know what you think. >>>>> >>>>> Enjoy, >>>>> The feenk team >>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> www.feenk.com >>>>> >>>>> "If you can't say why something is relevant, >>>>> it probably isn't." >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> Moose-dev(a)list.inf.unibe.ch >>>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>>> >> > > -- > www.tudorgirba.com > www.feenk.com > > "If you interrupt the barber while he is cutting your hair, > you will end up with a messy haircut." > >

June 26, 2018

Re: [Pharo-users] Interesting Pharo Launcher feedback

by Tim Mackinnon

As I mentioned - the user in question was quite complimentary, just confused on first launch. Equally we donât want to impact power users, and ultimately we want to encourage everyone to try newer images to help with improvements. I honestly think that some slightly improved terminology and a bit of guidance to get your first image (eg picking the correct one) is all it takes. Once youâve groked it - you are off. We just want that first experience to be pleasant. I personally like to see the list of images and understand how many builds have been made as itâs comforting to see the progress and be encouraged to join in. I as going to propose a simple change to the name on the lists like: âTemplatesâ -> âImage Templatesâ or maybe even âProject Templatesâ âImagesâ -> âDownloaded Imagesâ or maybe âCreated Projectsâ (While we are familiar with the term image, maybe itâs an implementation detail - eclipse and IntelliJ create projects, and we arenât so different) We could also as Cyril suggests, have a little welcome window with some text and a picture. Both really simple to do and probably enough to get people started. After all, our audience is reasonable technical so we shouldnât need to dumb It down too much. Iâm also conscious about here is a lot of Pharo 7 work to do as well. Tim Sent from my iPhone > On 26 Jun 2018, at 08:09, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > Hi Tim, > >> Le 26 juin 2018 Ã 03:00, Ben Coman <btc(a)openinworld.com> a Ã©crit : >> >> On 26 June 2018 at 06:17, Tim Mackinnon <tim(a)testit.works> wrote: >>> Hi everyone - at tonights month UK Smalltalk Meetup, we got some nice compliments on the state of Pharo (the participants - all ex small talkers - although ex in so much as they fondly remembered it and wanted to use it for something relevant now because they enjoyed it in the past). >>> >>> Anyway, one interesting comment stuck out - he had downloaded Pharo (having used Visual Age 15+ years ago) and was a bit overwhelmed with what laugher presented to him. He didnât hate it - but was initially a bit lost as to what it all meant and how to startâ¦ he figured it out, but I thought the feedback was interesting and made me think that maybe we need some form of intro wizard to get people off to a quick start but leave them confident enough that they might come back and try a Pharo 7 or Moose etc. >>> >>> I encouraged him to post something on here, but thoughtI would note it (as it seems quite easy to fix) as an idea while it was fresh in my mind. >>> >> >> A welcome tutorial is a good idea. And btw, the sort of idea that only comes from broader use of PharoLauncher. > > Thanks for the feedback. > We also got this feedback from students. We know we have to improve the UI by simplifying it. > Our idea was to only provide a window with a toolbar and the list of images as the main Pharo Launhcer window. > On this windows, clicking on the + button will open a Â« wizard Â» like the one for creating repositories in Iceberg. There you could choose to create an image from Â« featured images Â» or ci, etc. > > It would lower a lot the cognitive charge of the current window. > We just need time to implement it. > > Cheers, > Christophe > >

June 26, 2018

Re: [Pharo-users] StCAD is open source

by CÃ©drick BÃ©ler

Excellent ! (BTW, I have problem opening your website). It will be hard to port to pharo ? The main difficulty is to have an equivalent for GF/ST 2D ? Cheers, Cedrick > Le 25 juin 2018 Ã 21:05, Hilaire <hilaire(a)drgeo.eu> a Ã©crit : > > Impressive! > > Hilaire > > >> Le 25/06/2018 Ã 02:05, askoh a Ã©crit : >> I have just open source StCAD (MIT license) which has the code for freeCAD. >> http://askoh.com/stcad >> Although written in VisualWorks Smalltalk, I hope Pharo users will port it >> in part or whole. > > -- > Dr. Geo > http://drgeo.eu > > >

June 26, 2018

Re: [Pharo-users] Interesting Pharo Launcher feedback

by Christophe Demarey

Hi Tim, > Le 26 juin 2018 Ã 03:00, Ben Coman <btc(a)openinworld.com> a Ã©crit : > > On 26 June 2018 at 06:17, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: > Hi everyone - at tonights month UK Smalltalk Meetup, we got some nice compliments on the state of Pharo (the participants - all ex small talkers - although ex in so much as they fondly remembered it and wanted to use it for something relevant now because they enjoyed it in the past). > > Anyway, one interesting comment stuck out - he had downloaded Pharo (having used Visual Age 15+ years ago) and was a bit overwhelmed with what laugher presented to him. He didnât hate it - but was initially a bit lost as to what it all meant and how to startâ¦ he figured it out, but I thought the feedback was interesting and made me think that maybe we need some form of intro wizard to get people off to a quick start but leave them confident enough that they might come back and try a Pharo 7 or Moose etc. > > I encouraged him to post something on here, but thoughtI would note it (as it seems quite easy to fix) as an idea while it was fresh in my mind. > > > A welcome tutorial is a good idea. And btw, the sort of idea that only comes from broader use of PharoLauncher. Thanks for the feedback. We also got this feedback from students. We know we have to improve the UI by simplifying it. Our idea was to only provide a window with a toolbar and the list of images as the main Pharo Launhcer window. On this windows, clicking on the + button will open a Â« wizard Â» like the one for creating repositories in Iceberg. There you could choose to create an image from Â« featured images Â» or ci, etc. It would lower a lot the cognitive charge of the current window. We just need time to implement it. Cheers, Christophe

June 26, 2018

Re: [Pharo-users] Interesting Pharo Launcher feedback

by Cyril Ferlicot

On mar. 26 juin 2018 at 00:18, Tim Mackinnon <tim(a)testit.works> wrote: > Hi everyone - at tonights month UK Smalltalk Meetup, we got some nice > compliments on the state of Pharo (the participants - all ex small talkers > - although ex in so much as they fondly remembered it and wanted to use it > for something relevant now because they enjoyed it in the past). > > Anyway, one interesting comment stuck out - he had downloaded Pharo > (having used Visual Age 15+ years ago) and was a bit overwhelmed with what > laugher presented to him. He didnât hate it - but was initially a bit lost > as to what it all meant and how to startâ¦ he figured it out, but I thought > the feedback was interesting and made me think that maybe we need some form > of intro wizard to get people off to a quick start but leave them confident > enough that they might come back and try a Pharo 7 or Moose etc. > > I encouraged him to post something on here, but thoughtI would note it (as > it seems quite easy to fix) as an idea while it was fresh in my mind. > > Tim > Hi, It is disabled in development I think but with a released version there is a Welcome window. Maybe it should be where we add more tutorials. -- Cyril Ferlicot https://ferlicot.fr

June 26, 2018

Re: [Pharo-users] [Moose-dev] [ann] gt documenter

by Tudor Girba

Hi, It looks like something broke in your Bloc. You can reset Bloc from the world menu / Bloc / Reset Bloc. Please let me know if it works. Cheers, Doru > On Jun 26, 2018, at 12:54 AM, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - so I managed to load up the full monty gtDocumentor into an image (a few false starts as it you try and load the full monty on top of just gtDocumentor e.g in a clean image load > > Metacello new > baseline: 'GToolkit'; > repository: ' > github://feenkcom/gtoolkit/src > '; > load. > > On top of this > Metacello new > baseline: 'GToolkitDocumenter'; > repository: ' > github://feenkcom/gtoolkit-documenter/src > '; > load. > > > It never completes - I gave up after 30 minutes and whining fans on a MacBook Pro. > > Anyway - in a completely clean image I loaded just GTookkit and then run > > GtDocumenter editorForText: BrToggleExamples comment. > > Which seemed to work fine - and showed me some buttons with different dots on them. > > So then I went and tried the example I really wanted to see: > > IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillarâ. > > And it just gives a blank tab in the _Pillar, _Contents and _GT tabs? The contents tab does show me pillar text unrendered. > > Interestingly, If I then go back to the previous editorForText example, that did work - it now also also show the same blank tabs. So it seems that something get broken? > > This is on OSX with the a 64bit image - labelled 6.1 - 64bit (tech preview) - so the current stable pharo for 64 bit. > > Is this a known issue? > > Tim > > >> On 20 Jun 2018, at 02:53, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Actually I realised it ended up on the be moose forum - hereâs what Doru replied (for any lurkers) >> >> >> >> Sent from my iPhone >>> On Jun 18, 2018, at 1:21 PM, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>> Guys this is really impressive! >> >> Thanks. >> >> >>> 2 things I noticed when going through the example in a new Pharo 6.1 image (with the latest Iceberg) - >>> >>> 1) The example "IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar'. â has changed to âIceLibgitRepository â¦â in the newer iceberg - so it might be worth a note in the readme (Iâll submit a PR) >> Show Quoted Content >>> 2 things I noticed when going through the example in a new Pharo 6.1 image (with the latest Iceberg) - >>> >>> 1) The example "IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar'. â has changed to âIceLibgitRepository â¦â in the newer iceberg - so it might be worth a note in the readme (Iâll submit a PR) >> >> Ok. >> >> >>> 2) In a clean 6.1 image I get a walkback (GtPhlowExplicitView>>mondrian DNU) when you try any of the graphical bits , making me think either the dependencies are incorrect on the Baseline (or the instruction for the example also need to mention you need to load something else - presumably Roassal? >> >> Indeed, this is due to the fact that loading GToolkitDocumenter does not load GToolkitVisualizer which includes GtMondrian. We are still working on finding the right dependencies balance. >> >> Until then, please load the whole GToolkit to get the full support. >> >> >>> 3) You canât scroll the Diff tabs of results, only the Code tabs >> >> Good catch! >> >> >> Cheers, >> Doru >> >> Sent from my iPhone >> >> On 20 Jun 2018, at 02:47, Tim Mackinnon <tim(a)testit.works> wrote: >> >>> Bump (not sure this got through , and keen to know how to load the diagramming bit) >>> >>> Guys this is really impressive! >>> >>> 2 things I noticed when going through the example in a new Pharo 6.1 image (with the latest Iceberg) - >>> >>> 1) The example "IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar'. â has changed to âIceLibgitRepository â¦â in the newer iceberg - so it might be worth a note in the readme (Iâll submit a PR) >>> >>> 2) In a clean 6.1 image I get a walkback (GtPhlowExplicitView>>mondrian DNU) when you try any of the graphical bits , making me think either the dependencies are incorrect on the Baseline (or the instruction for the example also need to mention you need to load something else - presumably Roassal? >>> 3) You canât scroll the Diff tabs of results, only the Code tabs >>> >>> Tim >>> >>>> On 13 Jun 2018, at 21:57, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>> Hi, >>>> >>>> We are happy to announce a new leap of GToolkit Documenter, the tool for manipulating live documents directly in the development environment: >>>> https://github.com/feenkcom/gtoolkit-documenter >>>> >>>> Documenter is part of the second generation GToolkit project, it is based on Bloc and works with the latest Pillar. It is mainly developed by Juraj Kubelka. >>>> >>>> Attached you can see a preview of how documents look like: >>>> >>>> <gt-documenter.png> >>>> >>>> At its core it offers a live editor for manipulating Pillar documents. The interaction happens seamlessly directly in the text editor, and it can be combined with different types of previews to serve several classes of use cases: >>>> â¢ code documentation >>>> â¢ tutorials >>>> â¢ interactive data notebook >>>> >>>> >>>> Code documentation >>>> ---- >>>> Documenter complements the GToolkit Examples engine to redefine code documentation. When practicing example-driven development, examples get written as part of the typical development. Once examples exist, they can be quickly put together in a document to form documentation. For example, the linked picture shows the comment of a class containing a visual explanation: >>>> https://twitter.com/feenkcom/status/973899862482866176 >>>> >>>> You can see a live example of documentation by inspecting the following snippet: >>>> GtDocumenter editorForText: BrToggleExamples comment. >>>> >>>> >>>> Tutorials: >>>> ---- >>>> Documenter offers a new experience of writing tutorials for Pharo by enabling the creation and embedding of Epicea change sessions directly in the document. For example, take a look at the following animation: >>>> https://twitter.com/feenkcom/status/999975333972541440 >>>> >>>> The document shows a method on top, and a change preview at the bottom showing both the code and the associated diff to the state from the image. Applying the change updates both the change view (no more diff), and method preview. This speeds up significantly the process of going through a tutorial. Furthermore, given that now the document shows the diff to the current image, the reader can safely explore alternative scenario and come back to the tutorial at any time without losing the overview. >>>> >>>> The size of the preview can also be adjusted live: >>>> https://twitter.com/feenkcom/status/1001152789874167808 >>>> https://twitter.com/feenkcom/status/1001407762285375490 >>>> >>>> You can see a live tutorial by inspecting: >>>> IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillarâ. >>>> >>>> >>>> Interactive data notebook: >>>> ---- >>>> A Documenter document can also be used as an interactive notebook. Internally it essentially acts as a playground: >>>> â¢ it supports defining variables in code snippets, and >>>> â¢ the execution of code shows an embedded inspector. >>>> >>>> For example: >>>> https://twitter.com/feenkcom/status/996310432225820672 >>>> https://twitter.com/feenkcom/status/1002851190475026432 >>>> >>>> An example, can be seen by inspecting: >>>> IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit' / 'doc' / 'gtoolkit' / 'gtoolkit.pillar'. >>>> >>>> >>>> As always, please do let us know what you think. >>>> >>>> Enjoy, >>>> The feenk team >>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> "If you can't say why something is relevant, >>>> it probably isn't." >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)list.inf.unibe.ch >>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>> > -- www.tudorgirba.com www.feenk.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

June 26, 2018

Re: [Pharo-users] [ANN] GNU Dr. Geo release 18.06

by H. Hirzel

On 6/23/18, Hilaire <hilaire(a)drgeo.eu> wrote: > As a matter of accuracy, it is more active essays paradigm[1]. > > Hilaire > > [1] http://www.vpri.org/pdf/tr2009002_active_essays.pdf A good report by now 9 years old worth to be read again. Maybe some discussion could be about this article and the way forward .... (small doable steps) > > Le 23/06/2018 Ã 08:17, Hilaire a Ã©crit : >> They call it Dynabook in the old time... Not yet there 40 years later, >> we are damn slow. > > -- > Dr. Geo > http://drgeo.eu > > > >

June 26, 2018

Re: [Pharo-users] copy & paste

by Otto Behrens

Thanks for the answer. We use the package installation for ubuntu described here: https://pharo.org/gnu-linux-installation-64. The stable version on opensuse is quite old. And apparently not 6.1. So, does this sadly mean that the paragraph on the top of the page "Zip file" is updated, but the rest of the page not? On Sun, Jun 24, 2018 at 11:58 AM, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi Otto, > > I had this issue, but it seems to be gone with P7, at least on the DrGeo > build based on it I can copy and paste from Chromium. > > Hilaire > > > Le 24/06/2018 Ã 11:11, Otto Behrens a Ã©crit : > > > > A very annoying issue I'm having with Pharo 6.0 (running on Ubuntu > > 16.04) is that if I copy text from other applications (eg. chromium > > browser), I cannot paste it into Pharo. I get text copied in Pharo > > from a previous copy. > > > -- > Dr. Geo > http://drgeo.eu > > > >

June 26, 2018