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

[ann] moldable editor - with expandable elements

by Tudor Girba

Hi, We are really pleased to announce another major advancement in the development of the moldable editor, and most of it was enabled because of one new feature: expandable elements. We think this will impact significantly our day to day interactions. To exemplify what we mean, we will make use of two more alpha projects that we did not announce yet: GT Documenter (a set of documentation tools based on Pillar and GT Examples) and GT Mondrian (the graph visualization engine), both of which are being implemented in Bloc. Please take a look at the following pictures showing the documentation Pillar file that ships together with GT Mondrian. What stands out are the two embedded pictures. These are actually not pictures, but visualizations rendered live during the viewing of the document out of a referenced GT Example. Now, GT Examples are likely also new for most people. We introduced them a couple of years ago based on the original idea of Markus Gaelli. These are a kind of tests that return an object and that can be built out of other examples. The nice thing is that they are always executable and testable. So, of course, if you see the resulting object, you can also see the code that created it, and if you see the code, you can even execute it live, right in place (notice the preview of the second snippet). Perhaps the most controversial part of GT Examples is that they offer a mechanism to define static dependencies via pragmas. Please, letâs leave this debate to another occasion, but please also notice that tools can use that static information to unfold the code of the referenced method (notice the nested code editors). A side note: if you look closer at the list with three items at the top of the Tutorial section, you will notice numbering next to #. That is actually syntax highlighting and so is the mechanism that embeds the expandable elements. Itâs really cool. Taking step back, when we introduced the editor a few weeks ago, we called it moldable because we said we can make it take different shapes easily. GT Documenter with everything you see in the above screenshots has currently ~500 lines of code, and all this while still having an editor that is highly scalable. We think that Bloc and Brick will change dramatically face of Pharo and now we can start to get a glimpse of what is possible. For example, the use case presented above is more than a technical tool, and we think this will change both the way we write documentation and the way we consume it. All these will be presented at ESUG both during presentations and at the Innovation Awards competition. In the meantime, those that want to play with it can execute the following in both Pharo 6.1 and Pharo 7.0: Iceberg enableMetacelloIntegration: true. Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load. And then inspect: './pharo-local/iceberg/feenkcom/gtoolkit/doc/mondrian/index.pillar' asFileReference Cheers, The feenk team -- www.tudorgirba.com www.feenk.com "Innovation comes in the least expected form. That is, if it is expected, it already happened."

Aug. 25, 2017

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini

by john pfersich

That's what I'm thinking. I'm going to do some research tonight. I'll report back what I find out. Sent from my iPhone > On Aug 25, 2017, at 07:03, TedVanGaalen <tedvga(a)gmail.com> wrote: > > Hi John, > â¦ thanks. another wild, wild guess: > it could then perhaps be, (if Pharo uses Open GL) that my graphics > card has Open GL incompatibility? or that Pharo 6.1 uses Open GL > calls not implemented on an Intel HD Graphics 4000 chip as in my mac mini? > > kind regards > TedvG > > > >> On 25. Aug 2017, at 06:56, John Pfersich [via Smalltalk] <[hidden email]> wrote: >> >> I don't know if it matters, but on my Retina 5K, 27 inch, Late 2015 iMac, AMD Radeon R9 M395 wirh 2048 MB running MacOS 10.12.6 I don't have a problem resizing or maximizing Pharo 6.1. >> >>> On Mon, Jul 31, 2017 at 6:28 AM, Ted F.A.van Gaalen <<a href="x-msg://3/user/SendEmail.jtp?type=node&node=4963988&i=0" target="_top" rel="nofollow" link="external" class="">[hidden email]> wrote: >>> >>> >>> >>> Hi, I reverted to 5.0 because Pharo 6.0 and 6.1 64 bit hangs on >>> my Mac Mini with UDH 4K screen (may that has to do with?) >>> with its maiden image (at first start after download >>> when: I resize or go to full screen. Maybe VM problem? >>> my mac Mini metrics: >>> Hardware Overview: >>> >>> Model Name: Mac mini >>> Model Identifier: Macmini6,2 >>> Processor Name: Intel Core i7 >>> Processor Speed: 2,6 GHz >>> Number of Processors: 1 >>> Total Number of Cores: 4 >>> L2 Cache (per Core): 256 KB >>> L3 Cache: 6 MB >>> Memory: 4 GB >>> Boot ROM Version: MM61.0106.B1F >>> SMC Version (system): 2.8f0 >>> >>> maybe this problem was already reported, but could find it. >>> >>> >>> Kind Regards >>> TedvG >>> >>> >>> >> >> >> >> If you reply to this email, your message will be added to the discussion below: >> http://forum.world.st/Pharo-6-0-and-6-1-64-bit-freeze-on-MacMini-tp4957969p… >> To unsubscribe from Pharo 6.0 and 6.1 64 bit freeze on MacMini, click here. >> NAML > > > View this message in context: Re: Pharo 6.0 and 6.1 64 bit freeze on MacMini > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 25, 2017

Re: [Pharo-users] Morphic renderer for Pillar?

by Tudor Girba

Hi, Just for information: Pillar already ships with a live editor with syntax highlighting that I built a couple of years ago. And there are two inspector presentations available: - If you inspect a class, you will get a Pillar comment presentation with syntax highlighting - If you inspect a .pillar file, you will get a Pillar editor with syntax highlighting Cheers, Doru > On Aug 26, 2017, at 12:15 AM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Le 25/08/2017 Ã 11:04, H. Hirzel a Ã©crit : >> Hello Stephane >> >> On 8/24/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> [...] >>> >>> This is good that there is Section 7 this in the doc. [1] We started to >>> build a simple Morphic renderer for Pillar. >>> We should continue. If someone wants to have fun. This would be nice >>> to have see it coming to live. >> >> I am interested in this. Where is the code? >> >> BTW if other people want to do a Pillar renderer for Bloc I have no >> problem with that..... >> :-; >> [...] >> >> Regards >> --Hannes >> >> >> [1] https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >> > > Hi, > > Back in 2015 there was Kasper Ãsterbye who did a Pillar-TextRenderer > > There is a screen slide 21: > http://esug.org/data/ESUG2015/4%20thursday/1600-1630%20Pilar/Pillar.pdf > > Here is the thread: > http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-td… > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France > -- www.tudorgirba.com www.feenk.com "Not knowing how to do something is not an argument for how it cannot be done."

Aug. 25, 2017

Re: [Pharo-users] Morphic renderer for Pillar?

by Cyril Ferlicot D.

Le 25/08/2017 Ã 11:04, H. Hirzel a Ã©crit : > Hello Stephane > > On 8/24/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > [...] >> >> This is good that there is Section 7 this in the doc. [1] We started to >> build a simple Morphic renderer for Pillar. >> We should continue. If someone wants to have fun. This would be nice >> to have see it coming to live. > > I am interested in this. Where is the code? > > BTW if other people want to do a Pillar renderer for Bloc I have no > problem with that..... > :-; > [...] > > Regards > --Hannes > > > [1] https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > Hi, Back in 2015 there was Kasper Ãsterbye who did a Pillar-TextRenderer There is a screen slide 21: http://esug.org/data/ESUG2015/4%20thursday/1600-1630%20Pilar/Pillar.pdf Here is the thread: http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-td… -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Aug. 25, 2017

Re: [Pharo-users] Morphic renderer for Pillar?

by Peter UhnÃ¡k

> > > Please note the embedded picture. > Only now I've realized that it is an embedded view and not just an opened moose panel, looking forward to this! Peter

Aug. 25, 2017

Re: [Pharo-users] Morphic renderer for Pillar?

by H. Hirzel

On 8/25/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > The package contains two approaches to render a Pillar document object > to Morphic. > > 1. PRVisitor subclass: #PRMorphWriter > 2. PRDocumentWriter subclass: #PRMorphWriter2 > After removing PRMorphWriter we have what the screen shot shows. PRMorphWriter2 using PRMorphCanvas does the job. PRMorphInterface is a demo class and PRRenderingExamples contains some demo Pillar source code. Stephane, you wrote "Ideally we should add the pillar element to the associated morphic to manage back link from the renderer to the pillar tree. But this is to be done." I do not understand what you mean with this. It sound like there should there be a link from the morph used in rendering to the Pillar document object model node? The way how it is implemented at the moment is different. An instance of the class Text is created. parseButton action: [ document := PRPillarParser new parse: textInput text. morphWriter start: document. textResult text: morphWriter text ]. Then it seems that just a TextMorph is displayed writer text asMorph openInWindow. And what is the reason for this? --Hannes

Aug. 25, 2017

Re: [Pharo-users] Morphic renderer for Pillar?

by H. Hirzel

The package contains two approaches to render a Pillar document object to Morphic. 1. PRVisitor subclass: #PRMorphWriter 2. PRDocumentWriter subclass: #PRMorphWriter2 The class comment for PRDocumentWriter says I'm the superclass of all classes supposed to output a pier document to a text file. I have a canvas to which the subclasses can write to using dedicated brushes. I have a configuration which specifies some details about how to write text (e.g., end of line convention). Class PRRenderer has examples for both approaches PRRenderer example "1" PRRenderer example3 "2 -- using PRMorphWriter2" "(example2 is not working)" I assume to use PRDocumentWriter subclass: #PRMorphWriter2 is the way forward and PRMorphWriter can be removed. --Hannes On 8/25/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Feel free to enhance it. > It was fun to hack the visitor and to flesh the renderer on the fly. > > On Fri, Aug 25, 2017 at 3:48 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> Stephane, >> >> Thank you. >> The rendering seems to be very useful as is. >> >> The screen shot shows what you get if you execute >> >> PRMorphInterface new openWithSpec. >> >> >> I will read the code in detail. >> >> --Hannes > >

Aug. 25, 2017

Re: [Pharo-users] [Pharo-dev] [Ann][Pillar] Travis -> Bintray for PDFs

by Serge Stinckwich

This is great Stef ! I'm waiting for the documentation to update all my projects with the new process. On Fri, Aug 25, 2017 at 4:42 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi > > with Damien Pollet, we went over all the booklets and some of the > Pharo books currently written in Pillar and made sure that each time > you commit > > - a travis job is run > - latex is produced as well as pdf > - the pdf is stored on bintray > - the release versions are stored on the github repo (I should verify) > > So now you can just do a PR and you get a super nice PDF. > > Have a look at Glorp or Voyage for example > > - https://github.com/SquareBracketAssociates/Booklet-Glorp > - https://github.com/SquareBracketAssociates/Booklet-Voyage > > You can access the bintray files from the squarebracketassociates > lovely binTray account :) > > https://bintray.com/squarebracketassociates/wip/download_file?file_path= > voyage-wip.pdf > > > I'm writing a doc of the process so that other people can do it for > their private projects. > > > Stef > > -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Aug. 25, 2017

Re: [Pharo-users] Minimizing an Application

by Stephane Ducasse

It is always easier to start than to finish something. :) For the small core we are getting there as Guillermo work showed it to us. 70 is bootstrap from source. Do you believe it? It is real and tangible. People can do it on their own machine. And this is just the start. Now we have our roadmap it is available and we will work on that roadmap. We know where we go and why we go there :). Stef On Fri, Aug 25, 2017 at 1:44 PM, Tim Mackinnon <tim(a)testit.works> wrote: > Mariano's PhD was on this - as mentioned it to me a few weeks ago. This was > one of the reasons for building fuel - to enable this sort of thing on top - > and he proved it worked. > > Dimitrus - the idea is to I have a small core that loads quick and then less > used elements can be paged in when needed (but maybe that's what you're > saying too). > > I disagree that Pharo desperately needs image assembly tools. It's quite > specialised - and we have some core tools to work with, and minimal images > to start from. > > While I'd love more - finishing off what we already have in play (e.g. Got, > bloc, Calypso ...) would seem more urgent. > > Tim > > Sent from my iPhone > > On 25 Aug 2017, at 08:47, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > I still dont know what opening has to do with transmitting, even when you do > it remotely , a socket / websocket connection should be all you need. For me > transmitting the entire image would be necessary only in the case you want > to install it remotely and that remote location has no immediate access to > the installation. > > On Fri, Aug 25, 2017 at 7:14 AM Ben Coman <btc(a)openinworld.com> wrote: >> >> I understand that to mean effectively that you are "opening" the image >> across the net - so eventually you need to whole image transmitted, but you >> don't have to wait for the whole thing before you start running it. >> cheers -ben >> >> >> On Fri, Aug 25, 2017 at 2:00 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> >> wrote: >>> >>> Indeed that can be a barrier but why you would want to transmit an >>> entire image instead of portion of it using something like fuel files or >>> other binary formats ? It would dramatically reduce the size of data you >>> transmit. >>> >>> On Thu, Aug 24, 2017 at 8:10 PM Craig Latta <craig(a)blackpagedigital.com> >>> wrote: >>>> >>>> >>>> > ...10mbs which is the size pharo image can be reduced to is nothing >>>> > for todays TBs hard drives and GBs flash drives and online storage. >>>> > Unless you do an embedded app and 10 mbs are huge for your limited >>>> > storage. >>>> >>>> Or you want to minimize initial startup time, including the time it >>>> takes to transmit the entire system over the net. >>>> >>>> >>>> -C >>>> >>>> -- >>>> Craig Latta >>>> Black Page Digital >>>> Amsterdam :: San Francisco >>>> craig(a)blackpagedigital.com >>>> voice through 2017-09-12: >>>> + 1 510 833 5799 (SMS ok) >>>> +31 20 893 2796 (no SMS) >>>> >>>> >> >

Aug. 25, 2017

Re: [Pharo-users] [DesktopManager][Question] How do I jump to a particular desktop?

by H. Hirzel

Hello Torsten Thank you for the links to the DeskTopManager documentation. I know can use playgrounds with expressions like (Desktop manager desktops detect: [ :dt | dt name = 'Pillar Morphic Renderer']) useAsDesktop. and (Desktop manager desktops detect: [ :dt | dt name = 'PetitParser']) useAsDesktop. to quickly move to different desktops. In my intallation I added a utility method so that I can do Desktop manager switchToDesktopNamed: 'TeaLight' Kind regards Hannes [1] DeskTopManager>>switchToDesktopNamed: switchToDesktopNamed: aString (Desktop manager desktops detect: [ :dt | dt name = aString]) useAsDesktop. On 8/25/17, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi Hannes, > > Code is on http://smalltalkhub.com/#!/~TorstenBergmann/DesktopManager > which points to this article: > https://medium.com/@astares/multiple-desktops-for-pharo-5cbc46f3179f > which should explain the details and that you can access the desktops > using: > > Desktop manager desktops > > You can also click "CTRL+D" folowed again by another "CTRL+D" > (DesktopManager -> Desktops") to have a custom spotter > just for showing/switching the desktops. > > There is also > > CTRL + D followed by CTRL + AââââDesktop Addâ > CTRL + D followed by CTRL + NââââDesktop Nextâ > CTRL + D followed by CTRL + PââââDesktop Previousâ > > The only downside is that the global shortcut handler catches the "CTRL+D" > for DesktopManager but also > eats the same key event from the Playground which means the "do it" (which > is also CTRL+D" is not > working in a Playground anymore when DesktopManager is installed. > > Have not yet found a suitable solution for this. Contributions/fixes/ideas > to solve this are very > welcome. > > Thx > T. > >> Gesendet: Freitag, 25. August 2017 um 14:56 Uhr >> Von: "H. Hirzel" <hannes.hirzel(a)gmail.com> >> An: astares(a)gmx.de >> Cc: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> >> Betreff: Re: [DesktopManager][Question] How do I jump to a particular >> desktop? >> >> P.S. I just realized that the 'Spotter' opens a desktop if I search for >> it. >> >> So with some specific naming I can quickly switch desktops this way as >> well. >> >> On 8/25/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> > Hello >> > >> > I have loaded your DesktopManager package into Pharo 6/6.1. It is >> > useful as always! >> > >> > A remark: >> > >> > If I open a new desktop the desktop is white and not black (New Pharo >> > 'dark' theme). I have to choose the theme manually through the >> > 'Settings' dialog, searching for 'theme' and then reconfirming that I >> > want the 'dark' theme. >> > >> > >> > A question: >> > >> > I Squeak I can jump to a particular 'desktop' (actually 'Project' >> > there ) with some code [1] in a workspace (playground) like >> > >> > (Project named: 'Pillar') enter >> > >> > Is there a similar construction with the DesktopManager? >> > >> > To jump to another desktop with a code snipped is useful as the number >> > of Desktops increases. Currently I have 14 and it may increase up to >> > 50. >> > >> > This also helps to create buttons to jump to a particular desktop. >> > >> > Thank you for the answer in advance >> > >> > Hannes Hirzel >> > >> > >> > [1] http://wiki.squeak.org/squeak/1013 >> > >> >

Aug. 25, 2017