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

make a simple sample(for korean)
by peter yoo May 13, 2017

May 13, 2017

this requirements. 1. nginx + php-fpm (another web env is ok. important is PHP) 2. Pharo 5 http://workspace.onionmixer.net/mediawiki/index.php?title=Pharo_Json_PHP_Ex… so.. me know now. but need "sample code" then can help to any newbie. always thank you to community. and... Pharo 64bit for linux is good for korean. because input korea charactor is not have problem. all clear now. :D -- http://lookandwalk.com http://looknw.com | http://onionmixer.net peter yoo(Jonghwa Yoo). ROK

3 4

Basic Iceberg First Commit
by Evan Donahue May 12, 2017

May 12, 2017

Hello, I am trying to get Iceberg working. I have a new Pharo 6 image as of about 5 minutes ago, and I am following the tutorial here: https://github.com/pharo-vcs/iceberg I get as far as cloning the repository, but when I enter my github ssh url and hit "Create repository" I get "LGit_GIT_ERROR: no error message set by libgit2." I am wondering three things: 1) What are the dependencies, libgit or otherwise, that I should make sure to have on my system? I have everything mentioned at the top of teh tutorial. 2) Is this tutorial still up to date enough that I should be getting past this step? I know the code is under development. 3) Is there a way to see what actually gets sent to the ffi? Nothing in the call trace looks especially out of place. Thanks, Evan

2 1

Wandering Through Dependency Hell
by Evan Donahue May 12, 2017

May 12, 2017

Hello, I was wondering if there was a resource somewhere that laid out a best practice for how to manage version control in Pharo. I know *how* to use Monticello and Versionner, but something about the way I use them inevitably dooms my efforts to the darkest circles of dependency hell, where strange and gruesome partial versions of old and abandoned branches come back to haunt me like some kind of object oriented night of the living dead. In particular, I usually commit daily to a local repository on my disk, and only occasionally to a remote repository like smalltalkhub. It has come to my attention that this only commits recent changes, with the result that no single repository actually has the current working code that I see in my image. I am in that situation now, where loading the latest version revives some distant and broken code where good, currently working code should be. If anyone knows how to figure out how to force all the current good code in my image into one massive commit, so that other people can check out the current, working version, please do not hesitate to let me know. Thanks, Evan

4 5

SPEC: accept by Tab ?
by Hartmut Krasemann May 12, 2017

May 12, 2017

Hi, maybe someone can give me a hint. I use SPEC for an elaborate GUI with the need to switch autoaccept of inputFields off. So accept of textInputFields is by Return. Since Tabs are used to navigate anyway, It would be great to "accept" on leaving the inputField. I found the possibility to bind a key/keyCombination to an action (as is done in ButtonModel initialize: self bindKeyCombination: Character space toAction: [ self action ] ) However the following code in a TextinputFieldModel textinputField bindKeyCombination: Character tab toAction: textinputField acceptBlock did not work. What should I do? Thanks for a hint -- signatur Hartmut Krasemann KÃ¶nigsberger Str. 41 c D 22869 Schenefeld Tel. 040.8307097 Mobil 0171.6451283 Krasemann(a)acm.org

2 2

Re: [Pharo-users] [Pharo-dev] [ann] bloc & cairo+morphic
by Alexandre Bergel May 12, 2017

May 12, 2017

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." >> >> >> >> > > > >

3 5

<Programming> 2018: Call for Papers
by Sylvia Grewe May 12, 2017

May 12, 2017

------------------------------------------------------------------------------------ <Programming> 2018 : The Art, Science, and Engineering of Programming Mon 9 - Thu 12 April 2018 Nice, France http://2018.programming-conference.org/ In 2017, we started a new conference and journal focused on everything to do with programming, including the experience of programming, called <Programming> for short. The first edition of <Programming> was a great success (see http://twitter.com/programmingconf for testimonies). Paper submissions and publications are handled by the journal. Accepted papers must be presented at the conference. ******************************************************** CALL FOR PAPERS ******************************************************** <Programming> 2018 accept scholarly papers including essays that advance the knowledge of programming. Almost anything about programming is in scope, but in each case there should be a clear relevance to the act and experience of programming. PAPER SUBMISSIONS: August 1 2017 (Research Papers Second Submission Deadline) December 1 2017 (Research Papers Third Submission Deadline) We accept submissions covering several areas of expertise. These areas include, but are not limited to: â¢ General-purpose programming â¢ Distributed systems programming â¢ Parallel and multi-core programming â¢ Graphics and GPU programming â¢ Security programming â¢ User interface programming â¢ Database programming â¢ Visual and live programming â¢ Data mining and machine learning programming â¢ Interpreters, virtual machines and compilers â¢ Modularity and separation of concerns â¢ Model-based development â¢ Metaprogramming and reflection â¢ Testing and debugging â¢ Program verification â¢ Programming education â¢ Programming environments â¢ Social coding ******************************************************** IMPORTANT DATES ******************************************************** Research paper submissions: August 1 2017 (Research Papers Second Submission Deadline) December 1 2017 (Research Papers Third Submission Deadline) Research paper first notification (for second submission deadline): October 1 2017 Research paper final notification (for second submission deadline): November 7 2017 Research paper first notification (for third submission deadline): February 1 2018 Research paper final notification (for third submission deadline): March 7 2018 All important dates can also be found at http://programming-journal.org/timeline/ ******************************************************** ORGANIZATION ******************************************************** General Chair: Manuel Serrano, INRIA France Local Organizing Chair: Tamara Rezk, INRIA France Organizing Committee: Stefan Marr (workshops), Johannes Kepler University Linz Tobias Pape (web technology), HPI - University of Potsdam Sylvia Grewe (publicity), Technische UniversitÃ¤t Darmstadt Germany Program Committee: Guido Salvaneschi (program chair), Technische UniversitÃ¤t Darmstadt, Germany Davide Ancona, University of Genova, Italy Alberto Bacchelli, Delft University of Technology, Netherlands Shigeru Chiba, University of Tokyo, Japan Yvonne Coady, University of Victoria, Canada Susan Eisenbach, Imperial College London, UK Patrick Eugster, TU Darmstadt, Germany and Purdue University, United States Antonio Filieri, Imperial College London, UK Matthew Flatt, University of Utah, United States Lidia Fuentes, Universidad de MÃ¡laga, Spain Richard P. Gabriel, Dream Songs, Inc. & IBM Research, California Jeremy Gibbons, University of Oxford, UK Yossi Gil, Isreal Institute of Technology Elisa Gonzalez Boix, Vrije Universiteit Brussel, Belgium Phlipp Haller, KTH Royal Institute of Technology, Sweden Matthew Hammer, University of Colorado, Boulder, United States Felienne Hermans, Delft University of Technology, Netherlands Robert Hirschfeld, Hasso Plattner Institute (HPI), Germany Roberto Ierusalimschy, Pontifical Catholic University of Rio de Janeiro, Brazil Jun Kato, National Institute of Advanced Industrial Science and Technology, Japan JÃ¶rg Kienzle, McGill University, Canada Neelakantan R. Krishnaswami, University of Cambridge, UK Ralf LÃ¤mmel, University of Koblenz-Landau, Germany Hidehiko Masuhara, Tokyo Institute of Technology, Japan Mira Mezini, Technische UniversitÃ¤t Darmstadt, Germany Emerson Murphy-Hill, North Carolina State University, United States Mario SÃ¼dholt, IMT Atlantique, Inria, France Sam Tobin-Hochstadt, Indiana University, United States Tijs van der Storm, CWI & University of Groningen, Netherlands Eelco Visser, Delft University of Technology, Netherlands ******************************************************** <Programming> 2018 is kindly supported by: INRIA France AOSA ********************************************************

1 0

Intro to git-only Pharo
by Joachim Tuchel May 12, 2017

May 12, 2017

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

8 12

Petri nets and workflow patterns
by Norbert Hartl May 11, 2017

May 11, 2017

Are there any resources regarding petri nets or control flowâ¦/workflow patterns in pharo or smalltalk? thanks, Norbert

5 12

Issue with Pillar
by Alexandre Bergel May 11, 2017

May 11, 2017

Hi! I am trying to get Pillar working on OS X. I followed the instruction given on https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… I did: curl https://raw.githubusercontent.com/pillar-markup/pillar/master/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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 4

Not much longer...
by Norbert Hartl May 11, 2017

May 11, 2017

On my vacation I saw this progress bar about pharo. So looks close to 6 for me :)

2 1