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

Re: [Pharo-users] Intro to git-only Pharo

by Thierry Goubier

Le 11/05/2017 Ã 20:52, Stephane Ducasse a Ã©crit : > Joachim > > many people are using Pharo to develop ***COMPLEX*** Pharo applications > and it works. They use monticello and metacello and it works. > So you do not have to have Github to make great software in Pharo. > > Now in addition many people are using github to build complex applications > with github. And people have been building complex applications with Monticello, Metacello and Github... Thierry > > Stef > > > On Thu, May 11, 2017 at 9:54 AM, Norbert Hartl <norbert(a)hartl.name > <mailto:norbert@hartl.name>> wrote: > > >> Am 11.05.2017 um 08:54 schrieb jtuchel(a)objektfabrik.de >> <mailto:jtuchel@objektfabrik.de>: >> >> Hi Norbert, >> >> thanks for your explanations. >> So it seems liek I should start by using Pharo6 and load Iceberg >> and just take a look. >> > Yes, iceberg has still some issues but is usable and it will evolve > quickly. If you are the brave type of guy you can start with pharo6 > 64bits ;) > > Norbert > >> Joachim >> >> >> >> Am 10.05.17 um 10:34 schrieb Norbert Hartl: >>> Hi Joachim, >>> >>> I think your timing is quite good. We had some changes in the >>> last years and it is getting better now. >>> Before we had only monticello. Monticello is a zip container that >>> contains a version number in the filename and prior version >>> pointer inside the repository. Regarding dependencies there was >>> nothing that was used widely. Then Metacello appeared and solved >>> the problem by providing dependency management and versioning of >>> dependencies. Dependency management works good, the integrated >>> versioning has issues. Especially when you look at a system like >>> git you can see that versioning is solved there. Filetree is >>> needed because git and other vcs systems are file based so you >>> need to layout your code in files (how quaint!) >>> To make a long story short: The best thing to use is git with >>> Metacello Baselines. Filetree is used to store code. Versioning >>> you do with git tags that can be used in Baselines. Now we have a >>> decent UI (iceberg) that supports the most needed workflow items. >>> We have a UI for the dependency management as well (versionner) >>> but it sadly targets ConfigurationOfs and not BaselineOfs. That >>> needs to be changed. >>> >>> my 2 cents, >>> >>> Norbert >>> >>>> Am 10.05.2017 um 07:56 schrieb Joachim Tuchel >>>> <jtuchel(a)objektfabrik.de <mailto:jtuchel@objektfabrik.de>>: >>>> >>>> Hi guys, >>>> >>>> please forgive me if this mail is a sign of ignorance. I am not >>>> a regular Pharo user and one of the reasons for this is that I >>>> didn't like most of the source management tools around >>>> Monticello. Coming from an envy background, it feels like not >>>> being ready for prime time. Of course you guys have been proving >>>> you can work with these tools quite well, but still I'd be >>>> interested in using Pharo in a pure git-based environment, as it >>>> most closely resembles some of the most-beloved features of envy. >>>> >>>> Over the years there was a lot of work and discussion on >>>> filetree, gitfiletree, iceberg, cypress and maybe quite a few >>>> other projects that sounded promising and interesting. But I >>>> must admit I lost track of what was really done and how far >>>> things went in the last years. >>>> >>>> So are there any pointers to info material that I could look at >>>> to see what the current status of source control in Pharo 5 and >>>> Pharo 6 is and/or will be soon? >>>> >>>> I am mostly interested in these topics: >>>> >>>> * git only - no monticello meta info any more - possible? >>>> * tools like merge/diff, committing from within the image >>>> * dependencies within my own project as well as dependencies >>>> on external code in - possibly multiple - external repositories >>>> * what is the current "most official" source repository for >>>> open source code? >>>> * best practices for managing complex projects and keeping old >>>> versions reproducible at any time >>>> * tutorial for git newbies in a Pharo context? (Like, how do I >>>> start with a new packege - create folder first and do git >>>> init, or start in the image and push into repo later? as I >>>> said: beginners' stuff) >>>> >>>> Thanks for pointers and help >>>> >>>> >>>> Joachim >>>> >>>> >>> >> >> >> -- >> ----------------------------------------------------------------------- >> Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de >> Fliederweg 1 http://www.objektfabrik.de <http://www.objektfabrik.de/> >> D-71640 Ludwigsburg http://joachimtuchel.wordpress.com >> <http://joachimtuchel.wordpress.com/> >> Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 >> > >

May 11, 2017

Re: [Pharo-users] Petri nets and workflow patterns

by Stephane Ducasse

yes :) I contacted the guy to ask for the smalltalk code but he never replied to me may be someone else should try. stef On Thu, May 11, 2017 at 9:59 AM, Serge Stinckwich < serge.stinckwich(a)gmail.com> wrote: > On Wed, May 10, 2017 at 10:09 PM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: > > Norbert > > > > I know petri nets and I was wondering if you were interested in worklow > (as > > in microworkflow). > > because I think that a simple extensible workflow library is missing in > > Pharo > > I guess you talk about this: http://micro-workflow.com/phdthesis/ > > -- > Serge Stinckwich > UCN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > >

May 11, 2017

Re: [Pharo-users] Intro to git-only Pharo

by Stephane Ducasse

Joachim many people are using Pharo to develop ***COMPLEX*** Pharo applications and it works. They use monticello and metacello and it works. So you do not have to have Github to make great software in Pharo. Now in addition many people are using github to build complex applications with github. Stef On Thu, May 11, 2017 at 9:54 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 11.05.2017 um 08:54 schrieb jtuchel(a)objektfabrik.de: > > Hi Norbert, > > thanks for your explanations. > So it seems liek I should start by using Pharo6 and load Iceberg and just > take a look. > > Yes, iceberg has still some issues but is usable and it will evolve > quickly. If you are the brave type of guy you can start with pharo6 64bits > ;) > > Norbert > > Joachim > > > > Am 10.05.17 um 10:34 schrieb Norbert Hartl: > > Hi Joachim, > > I think your timing is quite good. We had some changes in the last years > and it is getting better now. > Before we had only monticello. Monticello is a zip container that contains > a version number in the filename and prior version pointer inside the > repository. Regarding dependencies there was nothing that was used widely. > Then Metacello appeared and solved the problem by providing dependency > management and versioning of dependencies. Dependency management works > good, the integrated versioning has issues. Especially when you look at a > system like git you can see that versioning is solved there. Filetree is > needed because git and other vcs systems are file based so you need to > layout your code in files (how quaint!) > To make a long story short: The best thing to use is git with Metacello > Baselines. Filetree is used to store code. Versioning you do with git tags > that can be used in Baselines. Now we have a decent UI (iceberg) that > supports the most needed workflow items. > We have a UI for the dependency management as well (versionner) but it > sadly targets ConfigurationOfs and not BaselineOfs. That needs to be > changed. > > my 2 cents, > > Norbert > > Am 10.05.2017 um 07:56 schrieb Joachim Tuchel <jtuchel(a)objektfabrik.de>: > > Hi guys, > > please forgive me if this mail is a sign of ignorance. I am not a regular > Pharo user and one of the reasons for this is that I didn't like most of > the source management tools around Monticello. Coming from an envy > background, it feels like not being ready for prime time. Of course you > guys have been proving you can work with these tools quite well, but still > I'd be interested in using Pharo in a pure git-based environment, as it > most closely resembles some of the most-beloved features of envy. > > Over the years there was a lot of work and discussion on filetree, > gitfiletree, iceberg, cypress and maybe quite a few other projects that > sounded promising and interesting. But I must admit I lost track of what > was really done and how far things went in the last years. > > So are there any pointers to info material that I could look at to see > what the current status of source control in Pharo 5 and Pharo 6 is and/or > will be soon? > > I am mostly interested in these topics: > > - git only - no monticello meta info any more - possible? > - tools like merge/diff, committing from within the image > - dependencies within my own project as well as dependencies on > external code in - possibly multiple - external repositories > - what is the current "most official" source repository for open > source code? > - best practices for managing complex projects and keeping old > versions reproducible at any time > - tutorial for git newbies in a Pharo context? (Like, how do I start > with a new packege - create folder first and do git init, or start in the > image and push into repo later? as I said: beginners' stuff) > > Thanks for pointers and help > > > Joachim > > > > > > -- > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de <jtuchel(a)objektfabrik.de> > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > > > >

May 11, 2017

Re: [Pharo-users] Issue with Pillar

by Stephane Ducasse

so ./pillar archetype book will work. On Thu, May 11, 2017 at 8:43 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi alexandre > > This is a problem I identified and I'm trying to fix it. > Now the version works for book, it is the one I used for all the booklets > and new books > I'm writing. > > Stef > > > On Wed, May 10, 2017 at 7:42 PM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > >> Forget about that way which doesn't work. >> >> Use this: https://github.com/cdlm/docker-texlive >> >> Works nicely and removes 90% of the setup frustration (you'll need latest >> docker-ce for this to work). >> >> Phil >> >> On Wed, May 10, 2017 at 5:38 PM, Alexandre Bergel < >> alexandre.bergel(a)me.com> wrote: >> >>> Hi! >>> >>> I am trying to get Pillar working on OS X. I followed the instruction >>> given on https://ci.inria.fr/pharo-contribution/job/EnterprisePhar >>> oBook/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html >>> >>> I did: >>> curl https://raw.githubusercontent.com/pillar-markup/pillar/maste >>> r/download.sh | bash >>> ./pillar archetype welcome >>> make book-result/welcome.html >>> >>> The two first instruction do not seem to cause any trouble. Work as >>> expected. The make instruction produces: >>> -=-=-=-= >>> /tmp/pillar> make book-result/welcome.html >>> mkdir -p ./book-result >>> find . -type d -path ./book-result -prune -o -wholename "*/figures" >>> -exec cp {} --parents -r ./book-result \; >>> cp -r support/ ./book-result >>> ./pillar export --to=html --outputDirectory=./book-result >>> --outputFile=welcome.pillar welcome.pillar >>> MessageNotUnderstood: FileReference>>jsonWriteOn: >>> FileReference(Object)>>doesNotUnderstand: #jsonWriteOn: >>> [ :assoc | >>> needComma >>> ifTrue: [ aStream nextPut: $, ] >>> ifFalse: [ needComma := true ]. >>> assoc key jsonWriteOn: aStream. >>> aStream nextPut: $:. >>> assoc value jsonWriteOn: aStream ] in Dictionary>>jsonWriteOn: in Block: >>> [ :assoc | ... >>> [ :each | each ifNotNil: [ aBlock value: each ] ] in >>> Dictionary>>associationsDo: in Block: [ :each | each ifNotNil: [ aBlock >>> value: each ] ] >>> Array(SequenceableCollection)>>do: >>> Dictionary>>associationsDo: >>> Dictionary>>jsonWriteOn: >>> PRExportPhase>>asJson:withConfiguration: >>> [ :outStream | >>> self >>> writeOutput: (self asJson: output withConfiguration: cocoonConfiguration) >>> toStream: outStream ] in PRExportPhase>>write:using: in Block: [ >>> :outStream | ... >>> [ aBlock value: stream ] in FileReference(AbstractFileReference)>>writeStreamDo: >>> in Block: [ aBlock value: stream ] >>> BlockClosure>>ensure: >>> FileReference(AbstractFileReference)>>writeStreamDo: >>> FileReference(AbstractFileReference)>>pillarWriteDuring: >>> PRExportPhase>>outputStreamDuring: >>> PRExportPhase>>write:using: >>> PRExportPhase>>actionOn: >>> PRExportPhase class(PRPhase class)>>executeOn: >>> [ :input | self executeOn: input ] in PRExportPhase class(PRPhase >>> class)>>buildPipe: in Block: [ :input | self executeOn: input ] >>> LPPhase>>executeOn: >>> [ :subResult :next | next executeOn: subResult ] in >>> LPPipeline>>executeOn: in Block: [ :subResult :next | next executeOn: >>> subResult ] >>> [ :each | nextValue := binaryBlock value: nextValue value: each ] in >>> OrderedCollection(Collection)>>inject:into: in Block: [ :each | >>> nextValue := binaryBlock value: nextValu...etc... >>> OrderedCollection>>do: >>> OrderedCollection(Collection)>>inject:into: >>> LPPipeline>>executeOn: >>> PRPillarConfiguration>>export >>> [ :exporter | (configuration getConfigurationNamed: exporter) export ] >>> in [ configuration defaultExporters >>> do: [ :exporter | (configuration getConfigurationNamed: exporter) export >>> ] ] in PRExportCommandLineHandler>>export in Block: [ :exporter | >>> (configuration getConfigurationNamed...etc... >>> Array(SequenceableCollection)>>do: >>> [ configuration defaultExporters >>> do: [ :exporter | (configuration getConfigurationNamed: exporter) export >>> ] ] in PRExportCommandLineHandler>>export in Block: [ configuration >>> defaultExporters... >>> BlockClosure>>on:do: >>> PRExportCommandLineHandler>>export >>> PRExportCommandLineHandler>>activate >>> make: *** [book-result/welcome.html.json] Error 1 >>> rm book-result/welcome.html.json >>> -=-=-=-= >>> >>> Any idea whatâs wrong? >>> >>> Cheers, >>> Alexandre >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> >

May 11, 2017

Re: [Pharo-users] Issue with Pillar

by Stephane Ducasse

Hi alexandre This is a problem I identified and I'm trying to fix it. Now the version works for book, it is the one I used for all the booklets and new books I'm writing. Stef On Wed, May 10, 2017 at 7:42 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Forget about that way which doesn't work. > > Use this: https://github.com/cdlm/docker-texlive > > Works nicely and removes 90% of the setup frustration (you'll need latest > docker-ce for this to work). > > Phil > > On Wed, May 10, 2017 at 5:38 PM, Alexandre Bergel <alexandre.bergel(a)me.com > > wrote: > >> Hi! >> >> I am trying to get Pillar working on OS X. I followed the instruction >> given on https://ci.inria.fr/pharo-contribution/job/EnterprisePhar >> oBook/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html >> >> I did: >> curl https://raw.githubusercontent.com/pillar-markup/pillar/maste >> r/download.sh | bash >> ./pillar archetype welcome >> make book-result/welcome.html >> >> The two first instruction do not seem to cause any trouble. Work as >> expected. The make instruction produces: >> -=-=-=-= >> /tmp/pillar> make book-result/welcome.html >> mkdir -p ./book-result >> find . -type d -path ./book-result -prune -o -wholename "*/figures" -exec >> cp {} --parents -r ./book-result \; >> cp -r support/ ./book-result >> ./pillar export --to=html --outputDirectory=./book-result >> --outputFile=welcome.pillar welcome.pillar >> MessageNotUnderstood: FileReference>>jsonWriteOn: >> FileReference(Object)>>doesNotUnderstand: #jsonWriteOn: >> [ :assoc | >> needComma >> ifTrue: [ aStream nextPut: $, ] >> ifFalse: [ needComma := true ]. >> assoc key jsonWriteOn: aStream. >> aStream nextPut: $:. >> assoc value jsonWriteOn: aStream ] in Dictionary>>jsonWriteOn: in Block: >> [ :assoc | ... >> [ :each | each ifNotNil: [ aBlock value: each ] ] in >> Dictionary>>associationsDo: in Block: [ :each | each ifNotNil: [ aBlock >> value: each ] ] >> Array(SequenceableCollection)>>do: >> Dictionary>>associationsDo: >> Dictionary>>jsonWriteOn: >> PRExportPhase>>asJson:withConfiguration: >> [ :outStream | >> self >> writeOutput: (self asJson: output withConfiguration: cocoonConfiguration) >> toStream: outStream ] in PRExportPhase>>write:using: in Block: [ >> :outStream | ... >> [ aBlock value: stream ] in FileReference(AbstractFileReference)>>writeStreamDo: >> in Block: [ aBlock value: stream ] >> BlockClosure>>ensure: >> FileReference(AbstractFileReference)>>writeStreamDo: >> FileReference(AbstractFileReference)>>pillarWriteDuring: >> PRExportPhase>>outputStreamDuring: >> PRExportPhase>>write:using: >> PRExportPhase>>actionOn: >> PRExportPhase class(PRPhase class)>>executeOn: >> [ :input | self executeOn: input ] in PRExportPhase class(PRPhase >> class)>>buildPipe: in Block: [ :input | self executeOn: input ] >> LPPhase>>executeOn: >> [ :subResult :next | next executeOn: subResult ] in >> LPPipeline>>executeOn: in Block: [ :subResult :next | next executeOn: >> subResult ] >> [ :each | nextValue := binaryBlock value: nextValue value: each ] in >> OrderedCollection(Collection)>>inject:into: in Block: [ :each | >> nextValue := binaryBlock value: nextValu...etc... >> OrderedCollection>>do: >> OrderedCollection(Collection)>>inject:into: >> LPPipeline>>executeOn: >> PRPillarConfiguration>>export >> [ :exporter | (configuration getConfigurationNamed: exporter) export ] in >> [ configuration defaultExporters >> do: [ :exporter | (configuration getConfigurationNamed: exporter) export >> ] ] in PRExportCommandLineHandler>>export in Block: [ :exporter | >> (configuration getConfigurationNamed...etc... >> Array(SequenceableCollection)>>do: >> [ configuration defaultExporters >> do: [ :exporter | (configuration getConfigurationNamed: exporter) export >> ] ] in PRExportCommandLineHandler>>export in Block: [ configuration >> defaultExporters... >> BlockClosure>>on:do: >> PRExportCommandLineHandler>>export >> PRExportCommandLineHandler>>activate >> make: *** [book-result/welcome.html.json] Error 1 >> rm book-result/welcome.html.json >> -=-=-=-= >> >> Any idea whatâs wrong? >> >> Cheers, >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >

May 11, 2017

Re: [Pharo-users] Not much longer...

by Stephane Ducasse

excellent! On Thu, May 11, 2017 at 3:42 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > On my vacation I saw this progress bar about pharo. So looks close to 6 > for me :) > > > >

May 11, 2017

Re: [Pharo-users] [Moose-dev] [Pharo-dev] [ann] bloc & cairo+morphic

by Stephane Ducasse

Doru can you change the humane assessment blog post? On Thu, May 11, 2017 at 8:07 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Indeed, this is wonderful news that you will rejoin your baby project :). > > Cheers, > Doru > > > > On May 11, 2017, at 6:40 PM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > > > Hi Alain! > > > > Thanks for the mail (even if the historial part has always been pretty > clear to me). > > We miss you! Be back soon! > > > > Cheers, > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > >> On May 11, 2017, at 12:36 PM, Alain Plantec via Pharo-dev < > pharo-dev(a)lists.pharo.org> wrote: > >> > >> > >> From: Alain Plantec <alain.plantec(a)yahoo.com> > >> Subject: Re: [Pharo-users] [ann] bloc & cairo+morphic > >> Date: May 11, 2017 at 12:36:36 PM GMT-3 > >> To: Pharo Development List <pharo-dev(a)lists.pharo.org> > >> Cc: Alain Plantec <alain.plantec(a)yahoo.com>, Moose-related development > <moose-dev(a)list.inf.unibe.ch>, Any question about pharo is welcome < > pharo-users(a)lists.pharo.org> > >> > >> > >> Hello Doru, all, > >> > >> Iâm really happy to see Bloc progresses. > >> Even Iâm not active since more than one year, Bloc is still an > important project for me. > >> > >> but let me complete this short historical presentation a little bit. > >> > >> Bloc is a project that I initiated in 2013 in collaboration with RMOD > following experiments made around the ROME project. > >> The idea was to completely revisit the 2D framework of Pharo to address > Morphic limits. > >> Following an invitation of the Software Composition Group (thanks to > Oscar Nierstrasz and to Doru here), > >> I presented the first version of Bloc at Bern (March, 2015), then Doru > and Aliaksel joined the project. > >> One year ago, during his PhD at Brest, Glenn Cavarle produced a new > version of the Bloc infrastructure that is now the > >> one used together with the layouting system that was implemented by > Aliaksel. > >> > >> Please, do not use the humane assessment web site but the github > project one instead. > >> > >> I will restart working on Bloc/Brick soon in the context of a project > that we recently signed with the Thales company. > >> > >> Thanks, > >> Cheers > >> > >> Alain > >> > >> > >>> On 8 mai 2017, at 23:00, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >>> > >>> Hi, > >>> > >>> We are happy to announce that based on the work of Glenn, Alex > extended Bloc (Sparta) to work directly in the Morphic world using Cairo as > a backend. > >>> > >>> Cairo is less powerful than Moz2D (see the screenshot below for an > example), but the implementation addresses a concern that the community > raised regarding a perceived increased liability due to the dependency to > Moz2D. Essentially this means that Bloc can be treated as another graphical > library that can coexist with Morphic without requiring any external VM > plugin. > >>> > >>> <bloc-two-backends-morphic-host-figures.png> > >>> > >>> I would also like to point out that adding a new backend and host was > possible because of the many iterations (including throwing away whole > implementations) that Alex and Glenn went through. I think they did an > amazing job. > >>> > >>> You can find a bit more details about Bloc here: > >>> http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/ > >>> > >>> Another issue raised regarding Bloc was that of the engineering effort > required to make it a reality. That is why I would also like to announce > that Alex joined feenk.com where he is primarily working on the graphical > stack for Pharo. > >>> > >>> Cheers, > >>> Doru > >>> > >>> > >>> -- > >>> www.tudorgirba.com > >>> www.feenk.com > >>> > >>> "To lead is not to demand things, it is to make them happen." > >>> > >>> > >>> > >>> > >> > >> > >> > >> > > > > _______________________________________________ > > 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 > > "Yesterday is a fact. > Tomorrow is a possibility. > Today is a challenge." > > > > > >

May 11, 2017

Re: [Pharo-users] [Moose-dev] [Pharo-dev] [ann] bloc & cairo+morphic

by Tudor Girba

Hi, Indeed, this is wonderful news that you will rejoin your baby project :). Cheers, Doru > On May 11, 2017, at 6:40 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Hi Alain! > > Thanks for the mail (even if the historial part has always been pretty clear to me). > We miss you! Be back soon! > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On May 11, 2017, at 12:36 PM, Alain Plantec via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: >> >> >> From: Alain Plantec <alain.plantec(a)yahoo.com> >> Subject: Re: [Pharo-users] [ann] bloc & cairo+morphic >> Date: May 11, 2017 at 12:36:36 PM GMT-3 >> To: Pharo Development List <pharo-dev(a)lists.pharo.org> >> Cc: Alain Plantec <alain.plantec(a)yahoo.com>, Moose-related development <moose-dev(a)list.inf.unibe.ch>, Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >> >> >> Hello Doru, all, >> >> Iâm really happy to see Bloc progresses. >> Even Iâm not active since more than one year, Bloc is still an important project for me. >> >> but let me complete this short historical presentation a little bit. >> >> Bloc is a project that I initiated in 2013 in collaboration with RMOD following experiments made around the ROME project. >> The idea was to completely revisit the 2D framework of Pharo to address Morphic limits. >> Following an invitation of the Software Composition Group (thanks to Oscar Nierstrasz and to Doru here), >> I presented the first version of Bloc at Bern (March, 2015), then Doru and Aliaksel joined the project. >> One year ago, during his PhD at Brest, Glenn Cavarle produced a new version of the Bloc infrastructure that is now the >> one used together with the layouting system that was implemented by Aliaksel. >> >> Please, do not use the humane assessment web site but the github project one instead. >> >> I will restart working on Bloc/Brick soon in the context of a project that we recently signed with the Thales company. >> >> Thanks, >> Cheers >> >> Alain >> >> >>> On 8 mai 2017, at 23:00, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> We are happy to announce that based on the work of Glenn, Alex extended Bloc (Sparta) to work directly in the Morphic world using Cairo as a backend. >>> >>> Cairo is less powerful than Moz2D (see the screenshot below for an example), but the implementation addresses a concern that the community raised regarding a perceived increased liability due to the dependency to Moz2D. Essentially this means that Bloc can be treated as another graphical library that can coexist with Morphic without requiring any external VM plugin. >>> >>> <bloc-two-backends-morphic-host-figures.png> >>> >>> I would also like to point out that adding a new backend and host was possible because of the many iterations (including throwing away whole implementations) that Alex and Glenn went through. I think they did an amazing job. >>> >>> You can find a bit more details about Bloc here: >>> http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/ >>> >>> Another issue raised regarding Bloc was that of the engineering effort required to make it a reality. That is why I would also like to announce that Alex joined feenk.com where he is primarily working on the graphical stack for Pharo. >>> >>> Cheers, >>> Doru >>> >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "To lead is not to demand things, it is to make them happen." >>> >>> >>> >>> >> >> >> >> > > _______________________________________________ > 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 "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

May 11, 2017

Re: [Pharo-users] [Pharo-dev] [ann] bloc & cairo+morphic

by Alexandre Bergel

Hi Alain! Thanks for the mail (even if the historial part has always been pretty clear to me). We miss you! Be back soon! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On May 11, 2017, at 12:36 PM, Alain Plantec via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Alain Plantec <alain.plantec(a)yahoo.com> > Subject: Re: [Pharo-users] [ann] bloc & cairo+morphic > Date: May 11, 2017 at 12:36:36 PM GMT-3 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: Alain Plantec <alain.plantec(a)yahoo.com>, Moose-related development <moose-dev(a)list.inf.unibe.ch>, Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > Hello Doru, all, > > Iâm really happy to see Bloc progresses. > Even Iâm not active since more than one year, Bloc is still an important project for me. > > but let me complete this short historical presentation a little bit. > > Bloc is a project that I initiated in 2013 in collaboration with RMOD following experiments made around the ROME project. > The idea was to completely revisit the 2D framework of Pharo to address Morphic limits. > Following an invitation of the Software Composition Group (thanks to Oscar Nierstrasz and to Doru here), > I presented the first version of Bloc at Bern (March, 2015), then Doru and Aliaksel joined the project. > One year ago, during his PhD at Brest, Glenn Cavarle produced a new version of the Bloc infrastructure that is now the > one used together with the layouting system that was implemented by Aliaksel. > > Please, do not use the humane assessment web site but the github project one instead. > > I will restart working on Bloc/Brick soon in the context of a project that we recently signed with the Thales company. > > Thanks, > Cheers > > Alain > > >> On 8 mai 2017, at 23:00, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> We are happy to announce that based on the work of Glenn, Alex extended Bloc (Sparta) to work directly in the Morphic world using Cairo as a backend. >> >> Cairo is less powerful than Moz2D (see the screenshot below for an example), but the implementation addresses a concern that the community raised regarding a perceived increased liability due to the dependency to Moz2D. Essentially this means that Bloc can be treated as another graphical library that can coexist with Morphic without requiring any external VM plugin. >> >> <bloc-two-backends-morphic-host-figures.png> >> >> I would also like to point out that adding a new backend and host was possible because of the many iterations (including throwing away whole implementations) that Alex and Glenn went through. I think they did an amazing job. >> >> You can find a bit more details about Bloc here: >> http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/ >> >> Another issue raised regarding Bloc was that of the engineering effort required to make it a reality. That is why I would also like to announce that Alex joined feenk.com where he is primarily working on the graphical stack for Pharo. >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "To lead is not to demand things, it is to make them happen." >> >> >> >> > > > >

May 11, 2017

Re: [Pharo-users] [ann] bloc & cairo+morphic

by Alain Plantec

Hello Doru, all, Iâm really happy to see Bloc progresses. Even Iâm not active since more than one year, Bloc is still an important project for me. but let me complete this short historical presentation a little bit. Bloc is a project that I initiated in 2013 in collaboration with RMOD following experiments made around the ROME project. The idea was to completely revisit the 2D framework of Pharo to address Morphic limits. Following an invitation of the Software Composition Group (thanks to Oscar Nierstrasz and to Doru here), I presented the first version of Bloc at Bern (March, 2015), then Doru and Aliaksel joined the project. One year ago, during his PhD at Brest, Glenn Cavarle produced a new version of the Bloc infrastructure that is now the one used together with the layouting system that was implemented by Aliaksel. Please, do not use the humane assessment web site but the github project one instead. I will restart working on Bloc/Brick soon in the context of a project that we recently signed with the Thales company. Thanks, Cheers Alain > On 8 mai 2017, at 23:00, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > We are happy to announce that based on the work of Glenn, Alex extended Bloc (Sparta) to work directly in the Morphic world using Cairo as a backend. > > Cairo is less powerful than Moz2D (see the screenshot below for an example), but the implementation addresses a concern that the community raised regarding a perceived increased liability due to the dependency to Moz2D. Essentially this means that Bloc can be treated as another graphical library that can coexist with Morphic without requiring any external VM plugin. > > <bloc-two-backends-morphic-host-figures.png> > > I would also like to point out that adding a new backend and host was possible because of the many iterations (including throwing away whole implementations) that Alex and Glenn went through. I think they did an amazing job. > > You can find a bit more details about Bloc here: > http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/ > > Another issue raised regarding Bloc was that of the engineering effort required to make it a reality. That is why I would also like to announce that Alex joined feenk.com where he is primarily working on the graphical stack for Pharo. > > Cheers, > Doru > > > -- > www.tudorgirba.com > www.feenk.com > > "To lead is not to demand things, it is to make them happen." > > > >

May 11, 2017