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

Re: [Pharo-users] Microservices using Pharo

by Sven Van Caekenberghe

> On 26 Jun 2018, at 15:24, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> Am 26.06.2018 um 14:52 schrieb Andrei Stebakov <lispercat(a)gmail.com>: >> >> Does anyone use Pharo for Miro services? I heard about Seaside and Teapot, just was wondering if Pharo can handle multiple simultaneous requests and if it can, where it reaches the limit. > > I use it extensively. I use Zinc-REST package to offer services. The answer how much it can handle in parallel is hard to answer. For this you need to tell what you are about to do. But a rule of thumb is not to exceed 5 parallel tasks that are working at the same time. But a lot of tasks have wait times while accessing another HTTP service, a database, a filesystem etc. For this you can easily go up to 10 I guess. > > But these numbers are more of a gut feeling then something scientific > > Norbert A single ZnServer instance on a single image can handle thousands of requests per seconds (local network, very small payload, low concurrency). On a modern multi core / multi processor machine with lots of memory you can 10s if not 100s of Pharo image under a load balancer, provided you either do not share state or use high performance state sharing technology - this is the whole point of REST. Of course, larger payloads, more complex operations, real world networking, etc will slow you down. And it is very easy to make some architectural or implementation error somewhere that makes everything slow. As they say, YMMV. Sven

June 26, 2018

Re: [Pharo-users] Interesting Pharo Launcher feedback

by H. Hirzel

On 6/26/18, 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. +1 Maybe just a note on the download website which 'new project' (image) beginners should go for.... --Hannes > > 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] Microservices using Pharo

by Norbert Hartl

> Am 26.06.2018 um 14:52 schrieb Andrei Stebakov <lispercat(a)gmail.com>: > > Does anyone use Pharo for Miro services? I heard about Seaside and Teapot, just was wondering if Pharo can handle multiple simultaneous requests and if it can, where it reaches the limit. I use it extensively. I use Zinc-REST package to offer services. The answer how much it can handle in parallel is hard to answer. For this you need to tell what you are about to do. But a rule of thumb is not to exceed 5 parallel tasks that are working at the same time. But a lot of tasks have wait times while accessing another HTTP service, a database, a filesystem etc. For this you can easily go up to 10 I guess. But these numbers are more of a gut feeling then something scientific Norbert

June 26, 2018

Re: [Pharo-users] The cool implication of gtDocumentor gluing examples and how we might augment source naviagation

by Tim Mackinnon

Hi Doru - Iâll comment inline below: > On 26 Jun 2018, at 13:05, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > >> On Jun 26, 2018, at 1:16 PM, Tim Mackinnon <tim(a)testit.works> wrote: >> >> 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. > > Thanks for going through the tutorial. Quick questions: > - how did it feel to go through it? > - did applying changes work fine for you? > - was there any confusion about what happened and where you were in the tutorial? > - anything missing that might have helped? Going through the tutorial felt reasonably intuitive (I have sort of seen people use Jupyter from afar, so I guess I had an idea of what it was trying to do) I did notice that when I click on the Apply buttons, the change to âAppliedâ was a bit subtle - particular if you scroll back to see if you missed a step. So not sure if colouring the applied buttons or having some kind of Tick might make it a bit more obvious (but it wasnât that bad) Applying the changes seemed to work fine - sometimes examples took a bit of time, (but there is the progress indicator top left - although I was looking at the button that I clicked, so maybe some subtle feedback there might help as well) I didnât really get confused - however I will confess I only superficially followed along and didnât question any of what it was telling me (e.g. what methods actually got created etc.). But conceptually it felt compelling and I believed it. I did find it a little bit sluggish to scroll (on a MacBook Pro 13â 2015 16gb ram) - so sometimes I over scrolled - I also kind of missed having a proper scrollbar in the window to help me understand how far down I was. I already mentioned the diff pane scrolling issue. Also, only being able to resize output boxes down was sometimes a bit frustrating (but workable) I wasnât clear on whether I was supposed to be able to edit the markup myself while reading - e.g. putting * around some text didnât make it bold (I kind of thought it might - but maybe thatâs not supported?) When I click on the + or - magnifying glasses, I also canât scroll anymore (so its not like a zoom level - but again maybe this is just how its supposed to work? - clicking circle/square icon put it back to 100% and it worked fine). Before I loaded the full gToolkit, I did get some messages about things being undefined - but the example still worked and I understood I needed to load something else (and hence asked you here). Something that did cross my mind (and this was something I questioned about Jupyter) - if you want to reuse intermediate results - as in assign a script result to a variable and then reference later down in your text (like when doing a mathâs problem) - it wasnât clear if that is possible and obvious. Something like X := ${example:GtExamplesTutorial>>#createFileInMemory}$ And then you talk about X and then demonstrate something like (making use of X): ${example:GtExamplesTutorial>>#selectUppcaseLinesFrom: X}$ Iâm guessing you can hide it all in the image with global variables - but I was thinking about how we auto define variables in the playground, and then incorporating those in the narrative. Anyway I was very impressed (as was the group at UK Smalltalk) - there is lots of legs in this. Tim P.s. It was cool that the inspectors work and jump into the gtInspector stuff. I wasnât clear on what all the different tabs are - maybe of which are similar (_Pillar vs _GT) - but I assume this is just the WIP nature of it. I did also get a few talkbacks clicking on items in the inspector -but again WIP or just missing dependencies? > >> 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). > > This actually a new take on the nature of an editor. Hopscotch did not allow expanding things inside the text editor. The editor was always a leaf, and it is so in all editors I have seen so far. In our case, the triangle is added live by the syntax highlighter. Right now, we only use it for navigating examples both because we needed to explore how we can make deeply nested examples simple to reason about, and because we wanted to validate the Bloc architecture. > > Of course, this ability is usable in many different ways. For example, the embedding in Pillar of various artifacts is done using the same mechanisms. And I think you will start seeing all sorts of applications in the UI area that you will simply not see in other places. > > >> 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. > > Thanks. Indeed, the resizer solution you see now is just a first attempt without much polishing. > > > Cheers, > Doru > > >> <PastedGraphic-1.png> >> >> >> > > -- > www.tudorgirba.com > www.feenk.com > > "Problem solving efficiency grows with the abstractness level of problem understanding." > > > > >

June 26, 2018

Microservices using Pharo

by Andrei Stebakov

Does anyone use Pharo for Miro services? I heard about Seaside and Teapot, just was wondering if Pharo can handle multiple simultaneous requests and if it can, where it reaches the limit.

June 26, 2018

Re: [Pharo-users] Pharo 7, Iceberg, Proxy and Windows

by Vitor Medina Cruz

Thanks Guille, will do that on further occasions, I just got excited to make it work for me :) I had see the page you sent already, but git works fine in any other program here (eg. command line, Intellij and Sourcetree) so I don't think the problem here is related to what was described by the stackoverflow page (and, well, I don't have admin rights in this machine, so I am unable to apply the proposed patch :( ). Anyways, I will try to use Iceberg only for commit/fetch and make the pull/push from command line. Regards, Vitor On Mon, Jun 25, 2018 at 6:23 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Hi Vitor, > > I've created an issue with your problem. > > https://github.com/pharo-vcs/iceberg/issues/885 > > I encourage you to do so too, because following the mailing list is > sometimes hard :) > > About your second issue, you should know that libgit ( > libgit2.github.com/libgit2) will mostly bypass git and reimplement most > of its features. > So, most of the times it will read git's settings, and some other times > not. > And also there is the possibility that Iceberg overrides those settings > too. > > For example, your fix > > *self prim_fetch_opts prim_proxy_opts prim_type: LGitProxyTypeEnum > git_proxy_auto* > > does enable automatic proxy verification and forbids people to set their > own proxy. > Not saying that this is bad but the contrary: I think it is a really good > default value :). > > Similar to that there are the ssh verifications on Iceberg. So far > - we do not check the certificate stores from the machine (we could > through FFI, the sub-project is listed in here https://github.com/pharo- > vcs/iceberg/wiki/How-to-help-us,-What-you-could-contribute) > - I don't think so far there is a hook to "disable ssh verification". > This could be dangerous... > > I've googled the error a bit, and found this. Maybe you can try it and see > wether the solution belongs to iceberg, or that we should enhance the > documentation? > > https://stackoverflow.com/questions/48985995/gitkraken- > and-github-failed-to-get-server-certificate-the-handle-is-in-the-wr > > Tx, > Guille > > On Thu, Jun 21, 2018 at 5:49 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> > wrote: > >> I am sorry, the correct message is "LGit_GIT_ERROR: failed to get server >> certificate: The handle is in the wrong state for the requested operation". >> >> >> I tried to add corporate certificates to the git curl-ca-bundle.crt, I >> tried to git config --global http.sslVerify false also, no success... :( >> >> On Thu, Jun 21, 2018 at 9:31 AM, Vitor Medina Cruz <vitormcruz(a)gmail.com> >> wrote: >> >>> Ok, I forgot to mention I have changed LGitRepository>>clone:url:local_path:options:, >>> but for some odd reason it's arguments names were switched to arg 1, arg2, >>> arg3 etc, so the out error was because was renamed to one of those generic >>> arg names. I figure that out looking at the versions of the methods, and it >>> apers that when I first access it this change is made. >>> >>> Anyways, I fixed that and I still get "IceGenericError: failed to get >>> server certificate: The identifier is not in the correct state for the >>> resquested operation" >>> >>> On Wed, Jun 20, 2018 at 4:49 PM, Vitor Medina Cruz <vitormcruz(a)gmail.com >>> > wrote: >>> >>>> Hello, >>>> >>>> Iceberg fail to function behind a proxy on Pharo 7 32bits Windows. When >>>> I try to clone I get a: >>>> >>>> IceGenericError: failed to get server certificate: The identifier is >>>> not in the correct state for the resquested operation >>>> >>>> I had a similar problem some time ago with Pharo 6, in which I made a >>>> local hot fix after questioning here. The fix was to the LGitCloneOptions >>>> and LGitFetchOptions both at the initializeWithDefaults, currently this >>>> method on LGitCloneOptions is like this: >>>> >>>> >>>> initializeWithDefaults >>>> self withReturnHandlerDo: [ >>>> self >>>> clone_init_options: self >>>> version: LGitOptionsVersionsEnum >>>> git_clone_options_version_1 ]. >>>> >>>> >>>> >>>> * self prim_fetch_opts prim_proxy_opts prim_type: LGitProxyTypeEnum >>>> git_proxy_auto* >>>> The bold is the fix, but it should come first in the method: >>>> >>>> initializeWithDefaults >>>> >>>> >>>> * self prim_fetch_opts prim_proxy_opts prim_type: LGitProxyTypeEnum >>>> git_proxy_auto* self withReturnHandlerDo: [ >>>> self >>>> clone_init_options: self >>>> version: LGitOptionsVersionsEnum >>>> git_clone_options_version_1 ]. >>>> >>>> >>>> That way worked on Pharo 6, but now I got a: >>>> >>>> "FFIVariableNameNotFound: Could not find accessor for variable named >>>> 'out'" >>>> >>>> Any clues? >>>> >>>> Regards, >>>> Vitor >>>> >>> >>> >> > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 >

June 26, 2018

Re: [Pharo-users] The cool implication of gtDocumentor gluing examples and how we might augment source naviagation

by Sean P. DeNigris

Tim Mackinnon wrote > its very handy to unfold code to understand it in one place There is also a Code Bubble-like demo from Feenk. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 26, 2018

Re: [Pharo-users] The cool implication of gtDocumentor gluing examples and how we might augment source naviagation

by Tudor Girba

Hi, > On Jun 26, 2018, at 1:16 PM, Tim Mackinnon <tim(a)testit.works> wrote: > > 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. Thanks for going through the tutorial. Quick questions: - how did it feel to go through it? - did applying changes work fine for you? - was there any confusion about what happened and where you were in the tutorial? - anything missing that might have helped? > 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). This actually a new take on the nature of an editor. Hopscotch did not allow expanding things inside the text editor. The editor was always a leaf, and it is so in all editors I have seen so far. In our case, the triangle is added live by the syntax highlighter. Right now, we only use it for navigating examples both because we needed to explore how we can make deeply nested examples simple to reason about, and because we wanted to validate the Bloc architecture. Of course, this ability is usable in many different ways. For example, the embedding in Pillar of various artifacts is done using the same mechanisms. And I think you will start seeing all sorts of applications in the UI area that you will simply not see in other places. > 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. Thanks. Indeed, the resizer solution you see now is just a first attempt without much polishing. Cheers, Doru > <PastedGraphic-1.png> > > > -- www.tudorgirba.com www.feenk.com "Problem solving efficiency grows with the abstractness level of problem understanding."

June 26, 2018

Re: [Pharo-users] Interesting Pharo Launcher feedback

by Sean P. DeNigris

Tim Mackinnon wrote > maybe the project metaphor isnât a bad one? Let's sync with Denis because Calypso already has a stub for "Projects" and we don't want to overload this term adding to the confusion! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 26, 2018

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

by Tudor Girba

Hi, Thanks for trying it out. I never encountered the issue you mentioned. However, the red cross appears due to a Morphic-related problem, not a Bloc one. Cheers, Doru > On Jun 26, 2018, at 11:44 AM, Tim Mackinnon <tim(a)testit.works> wrote: > > 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." >> >> > > -- www.tudorgirba.com www.feenk.com "Sometimes the best solution is not the best solution."

June 26, 2018