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

Re: [Pharo-users] [ann] moldable editor - with expandable elements

by Thierry Goubier

2017-08-26 14:46 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > > 2017-08-26 14:31 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > >> Denis - that's a very cool idea if I've understood you - expand in the >> source code of the current method, literally inline? So you could scroll up >> and down to view the context as you expand it out? >> > > Yes, exactly. > Then that would look a bit like the NewSpeak code browser, if you would like to try the concept. There are disadvantages to that paradigm. One of those is that the system browser in Pharo is ill-suited to long methods. Thierry > > >> One of the complaints around refactoring is that you lose context of >> surrounding code - intelligent in place expansion would be the best of both >> worlds... >> >> Tim >> >> Sent from my iPhone >> >> On 26 Aug 2017, at 11:40, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> >> This is really cool. It opens so many possibilities. >> >> I imaging method editor where message sends can be expanded to >> implementors just in place. >> >> 2017-08-26 1:03 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: >> >>> 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). >>> >>> <pillar-mondrian-expanded-preview.png> >>> >>> 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. 26, 2017

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

by Ben Coman

Hi Ted, You might consider building a debug VM. There is a random chance it provides useful insight. At its simplest all you need to do is... $ git clone https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ cd opensmalltalk-vm/build.macos32x86/pharo.cog.spur $ ./mvm -A taken from... https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/build.macos32x86… First confirm the problem still exists in each of three generated VMs started normally, then later try using lldb to trace what methods are executed. (though I'm not familiar with lldb - you'll need to google some tutorials) cheers -ben On Fri, Aug 25, 2017 at 9:55 PM, TedVanGaalen <tedvga(a)gmail.com> wrote: > Hi Ben, > Did the following > - restoring Pharo.app/Contents/MacOS/Plugins/libFT2Plugin.dylib (by > renaming its extension back to .dylib) > - started Pharo > -setting use Free type ON > -setting Update fonts at start ON > > it then immediately starts loading fonts, (which I thought might be a > good idea > because perhaps fonts were not completely loaded in the image, > but that didnât make any difference) > > -saved and quit > -fired up Pharo again. > > didnât help. Same problems occur > > then: (as you have asked) > > - started Pharo again > -setting use Free type OFF > -setting Update fonts at start OFF > -saved and quit > -fired up Pharo again. > > didnât help either > > I have no idea what the cause might be, > but if you have other suggestions to test > I be glad to help. (if not a thousand attempts :o) > > in the mean time I use 5 until a next release comes out 7 ? that works ok. > > kind regards > TedvG > > > > > On 25. Aug 2017, at 06:07, Ben Coman [via Smalltalk] <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4964080&i=0>> wrote: > > What happens if you untick "Use FreeType" in System > Settings? > > cheers -ben > > > On Thu, Aug 24, 2017 at 10:06 PM, TedVanGaalen <<a href="x-msg://1/user/ > SendEmail.jtp?type=node&node=4963983&i=0" target="_top" > rel="nofollow" link="external" class="">[hidden email]> wrote: > >> yes, after full screen -> normal window -> minimise -> reshow it did. >> (not in any particular order, tried al those before as well) >> >> TedvG >> >> >> On 24. Aug 2017, at 15:46, EstebanLM [via Smalltalk] <[hidden email] >> <http://user/SendEmail.jtp?type=node&node=4963891&i=0>> wrote: >> >> and image still freezing? >> >> Esteban >> >> On 24 Aug 2017, at 15:28, TedVanGaalen <<a href="<a >> href="x-msg://3/user/" class="">x-msg://3/user/SendEm >> ail.jtp?type=node&node=4963878&i=0" target="_top" rel="nofollow" >> link="external" class="">[hidden email]> wrote: >> >> Hi Esteban, >> unfortunately that doesnât make any difference. >> What I did: >> extension temporarily renamed to â¦..wasAdylib >> Started Pharo app by clikcing on it (gets the downloaded maiden image) >> then: >> âFT2Error:Freetype2 primitive failed [error -1][canât get error string]â >> >> >> > > > ------------------------------ > 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-tp4957969p4963983.html > To unsubscribe from Pharo 6.0 and 6.1 64 bit freeze on MacMini, click here > . > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > > > > ------------------------------ > View this message in context: Re: Pharo 6.0 and 6.1 64 bit freeze on > MacMini > <http://forum.world.st/Pharo-6-0-and-6-1-64-bit-freeze-on-MacMini-tp4957969p…> > Sent from the Pharo Smalltalk Users mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com. >

Aug. 26, 2017

Re: [Pharo-users] [ann] moldable editor - with expandable elements

by Denis Kudriashov

2017-08-26 14:31 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: > Denis - that's a very cool idea if I've understood you - expand in the > source code of the current method, literally inline? So you could scroll up > and down to view the context as you expand it out? > Yes, exactly. > One of the complaints around refactoring is that you lose context of > surrounding code - intelligent in place expansion would be the best of both > worlds... > > Tim > > Sent from my iPhone > > On 26 Aug 2017, at 11:40, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > This is really cool. It opens so many possibilities. > > I imaging method editor where message sends can be expanded to > implementors just in place. > > 2017-08-26 1:03 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > >> 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). >> >> <pillar-mondrian-expanded-preview.png> >> >> 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. 26, 2017

Re: [Pharo-users] [ann] moldable editor - with expandable elements

by Tim Mackinnon

Denis - that's a very cool idea if I've understood you - expand in the source code of the current method, literally inline? So you could scroll up and down to view the context as you expand it out? One of the complaints around refactoring is that you lose context of surrounding code - intelligent in place expansion would be the best of both worlds... Tim Sent from my iPhone > On 26 Aug 2017, at 11:40, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > This is really cool. It opens so many possibilities. > > I imaging method editor where message sends can be expanded to implementors just in place. > > 2017-08-26 1:03 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: >> 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). >> >> <pillar-mondrian-expanded-preview.png> >> >> 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. 26, 2017

Re: [Pharo-users] Object>>#name deprecated in Pharo 6 -- what do I need to do?

by Ben Coman

Just checking my presumption... is PPCMNode>>#gtTreeViewIn: you own application method? So where it sends #name, instead send #printString (or #asString). Alternatively, #name is being sent to some domain object that doesn't implement #name, so it falls back to the super one from Object. So implement YourDomainObject>>#name: so the one from Object is not executed. cheers -ben On Sat, Aug 26, 2017 at 4:38 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > OK, so #name should not be used at all [1] > > The error message I get is > > PPCommonMarkSpecTest class>>DoIt (blockVisitor is Undeclared) > The method Object>>#name called from PPCMNode>>#gtTreeViewIn: has been > deprecated. > Implement your own domain representation of an object, or use > #asString or #printString instead. > > > I wonder how I can fix this without going to much into details. > > --Hannes > > > ------------------------------------------------------------ > ------------------------------------------------------------ > [1] Pharo 6.1 source code: > > Object>>name > "Answer a name for the receiver. This is used generically in the > title of certain inspectors, such as the referred-to inspector, and > specificially by various subsystems. By default, we let the object > just print itself out.. " > > self > deprecated: 'Implement your own domain representation of > an object, > or use #asString or #printString instead.' > on: '27 May 2016' > in: #Pharo6. > ^ self printString > > On 8/25/17, Ben Coman <btc(a)openinworld.com> wrote: > > I don't have an Image to check, but I believe Object>>name > > just does "^self printString", > > so by default, in your application send #printString instead of #name. > > > > cheers -ben > > > > P.S. Perhaps this would be a good candidate for automated rewrite? > > > > > > On Thu, Aug 24, 2017 at 8:49 PM, H. Hirzel <hannes.hirzel(a)gmail.com> > wrote: > > > >> Hello > >> > >> In the last days there was a discussion that > >> > >> Object>>#name > >> > >> > >> should no longer be used. I did not follow the discussion in detail. > >> What was decided how #name should be replaced? > >> > >> What do I need to do if I get a deprecation warning [1]? > >> > >> > >> Thanks for the answer in advance > >> > >> Hannes > >> > >> > >> > >> > >> [1] > >> The method Object>>#name called from PPCMNode>>#gtTreeViewIn: has been > >> deprecated. > >> Implement your own domain representation of an object, or use > >> #asString or #printString instead. > >> > >> Select Proceed to continue, or close this window to cancel the > operation. > >> > >> > > > >

Aug. 26, 2017

Re: [Pharo-users] [ANN] Pharo wiki , is here

by Dimitris Chloupis

Thank you for pointing me to the right direction. Because your images come from the presentation that is already linked in the wiki I do not think its necessary to further link those pages too. If you have something to add further to the documentation of Pillar I could make a separate page for Pillar so that I don't cram the projects pages. The Pillar tutorial is also linked in the how to section https://github.com/pharo-project/pharo/blob/master/wiki/contents/howto.md I really appreciate helping me with the wiki Hizrel , keep the info coming :) On Sat, Aug 26, 2017 at 2:00 PM H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Just realized that this diagram > > > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > gives a good overview as well. Only the transformers are missing which > are rather important as well. > > On 8/26/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > > Thanks for creating an overview paragraph about Pillar in the file > > > > > https://github.com/pharo-project/pharo/blob/master/wiki/contents/projects.md > > > > The three slides which given an overview of Pillar are screen shots > > taken from this document > > > > http://esug.org/data/ESUG2015/4%20thursday/1600-1630%20Pilar/Pillar.pdf > > > > I do not know if the source of this 'Pillar.pdf' presentation is > > available somewhere. > > > > Maybe for the moment you just refer to the slide numbers > > > > > > Parsing slide 29 > > Transformation slide 30 > > Export slide 31 > > > > To keep this in mind is useful for the current Pillar discussions on this > > list. > > > > > > On 8/26/17, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > >> i linked everything else to the wiki but not these pdfs, are they hosted > >> somewhere ? where you found them ? > >> > >> On Sat, Aug 26, 2017 at 12:23 PM H. Hirzel <hannes.hirzel(a)gmail.com> > >> wrote: > >> > >>> On 8/26/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > >>> > And > >>> > > >>> > Main repository: > >>> > http://smalltalkhub.com/mc/Pier/Pillar/main/ > >>> > >>> And the three slides which give a high-level overview of the Pillar > >>> system > >>> > >>> HH. > >>> > >> > > > >

Aug. 26, 2017

Re: [Pharo-users] [ANN] Pharo wiki , is here

by H. Hirzel

Just realized that this diagram https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… gives a good overview as well. Only the transformers are missing which are rather important as well. On 8/26/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Thanks for creating an overview paragraph about Pillar in the file > > https://github.com/pharo-project/pharo/blob/master/wiki/contents/projects.md > > The three slides which given an overview of Pillar are screen shots > taken from this document > > http://esug.org/data/ESUG2015/4%20thursday/1600-1630%20Pilar/Pillar.pdf > > I do not know if the source of this 'Pillar.pdf' presentation is > available somewhere. > > Maybe for the moment you just refer to the slide numbers > > > Parsing slide 29 > Transformation slide 30 > Export slide 31 > > To keep this in mind is useful for the current Pillar discussions on this > list. > > > On 8/26/17, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: >> i linked everything else to the wiki but not these pdfs, are they hosted >> somewhere ? where you found them ? >> >> On Sat, Aug 26, 2017 at 12:23 PM H. Hirzel <hannes.hirzel(a)gmail.com> >> wrote: >> >>> On 8/26/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> > And >>> > >>> > Main repository: >>> > http://smalltalkhub.com/mc/Pier/Pillar/main/ >>> >>> And the three slides which give a high-level overview of the Pillar >>> system >>> >>> HH. >>> >> >

Aug. 26, 2017

Re: [Pharo-users] [Pillar] How do I open the Pillar editor in Pharo 6?

by Tudor Girba

In an image having Pillar, inspect a Pillar file. Something like this: âpath/to/file.pillar' asFileReference Cheers, Doru > On Aug 26, 2017, at 9:56 AM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > > Hello Doru > > On 8/26/17, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Hi, >> >> Just for information: Pillar already ships with a live editor with syntax >> highlighting that I built a couple of years ago. > > Thank you for this information, Doru. > > Earlier this week I was looking for a "Pillar tool" in Pharo 6 and was > told, that there is none. > I did not find a link in the help system nor a menu entry in the world menu. > > How do I get at this live editor? > >> 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 >> > > > Regards > Hannes -- www.tudorgirba.com www.feenk.com "Quality cannot be an afterthought."

Aug. 26, 2017

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

by H. Hirzel

The proper reference to the repository MCHttpRepository location: 'http://smalltalkhub.com/mc/Pier/Pillar/main' user: '' password: '' On 8/26/17, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Cyril, > > Thank you for the info where I can find the proof of concept done by > Kasper Ãsterbye > to render Pillar code in Morphic. > > I want to read the code and learn from it how to come up with an > enhanced version of what Stephane D. was refering to > > http://smalltakhub.com/#!/~Pier/Pillar/packages/Pillar-Renderer/ > > Name: Pillar-Renderer-StephaneDucasse.7 > Author: StephaneDucasse > Time: 7 May 2017, 7:00:52.414735 pm > UUID: a64b56cd-530b-0d00-a0f1-dba809b4cbdf > > --Hannes > > On 8/26/17, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: >> Le 26/08/2017 Ã 10:31, H. Hirzel a Ã©crit : >>> >>> Hello Cyril >>> >>> Thank you for these two references with some info to the >>> >>> Pillar-TextRenderer >>> >>> Kasper Ãsterbye did. Do you have an idea where I could find the code. >>> >>> I found nothing so far in >>> >>> http://smalltalkhub.com/mc/Pier/Pillar/main/ >>> >>> Regards >>> Hannes >>> >> >> Hi, >> >> They are on the Pillar repository. >> >> There is this package: >> http://smalltalkhub.com/#!/~Pier/Pillar/packages/Pillar-TextRenderer >> And this one: >> http://smalltalkhub.com/#!/~Pier/Pillar/packages/Pillar-NautilusProofOfConc… >> >> Note that it will not work on recent Pharo since it was a Proof of >> concept done with PluggableTextMorph. Now the comment pane moved from >> PluggableTextMorph to Rubric. >> >> -- >> Cyril Ferlicot >> https://ferlicot.fr >> >> http://www.synectique.eu >> 2 rue Jacques PrÃ©vert 01, >> 59650 Villeneuve d'ascq France >> >> >

Aug. 26, 2017

Re: [Pharo-users] [ann] moldable editor - with expandable elements

by Tudor Girba

Hi, This is achieved through the integration in Morphic we announced a couple of months ago. Now, Sparta offers: - two backends: Moz2D and Cairo - two host systems: SDL2 and Morphic By default, Bloc ships with Sparta working on Cairo and Morphic, and with this you can use any Bloc element inside a morph. Glamour also comes with a BlocPresentation that makes use of this ability, and this is what you see in the picture. So, it is possible to use this inside Morphic, and our effort will be focused exclusively around this editor. Cheers, Doru > On Aug 26, 2017, at 11:44 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > I wondering how you compose bloc component inside morphic inspector? (which is shown in your pictures) > Did you already have GT inspector in Bloc? > Is it posible to use this editor in morphic? Can we replace rubric? > > 2017-08-26 1:03 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > 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. > > <pillar-mondrian-examples.png> > > 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). > > <pillar-mondrian-expanded-preview.png> > > 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." > > -- www.tudorgirba.com www.feenk.com "Every successful trip needs a suitable vehicle."

Aug. 26, 2017