May 2014 - Pharo-dev - lists.pharo.org

Coral is green

by Stephan Eggermont

PetitParser 1.6 instead of 1.5. Tests only work when no Nautilus browser is open. Some notification problem when creating classes. OSProcess ci has lots of failing tests, so we don't know if it actually worksâ¦ Diego & Stephan Verstuurd vanaf mijn iPhone

May 21, 2014

Re: [Pharo-dev] Pharo in Rasbian ?

by Alexandre Bergel

> So, before proposing it, we need to make it more stable, and cleaner. Sure! I am just suspecting there is a great opportunity for a larger adoption of our tools Alexandre > > Cheers, > Jannik > > > 2014-05-20 17:43 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Ah okay, this is an answer that I understand :-) > > We are not really good at promoting what we are doing. > For the the case of Rasbian, it seems not that difficult to have Phratch and Pharo installed per default, if there is Scratch and Squeak. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On May 20, 2014, at 11:06 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > > FFI for the raspberry pie was finished for the Pharo vm 3 weeks ago. > > > > So I guess the Phratch team has not found the time yet to do that, but it should be possible. > > > > > > > > -- > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > http://www.phratch.com > http://car.mines-douai.fr/ > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 21, 2014

Re: [Pharo-dev] Roassal2 starting point

by Alexandre Bergel

Hi Uko, Roassal2 has not been officially announced and released. The reason is simple: Roassal2 targets an audience larger than the Pharo/VW/Amber communities. We would love to see Journalists, Data scientists, Artists, Educators and software engineers enjoying our tools. However, we have to be ready to expose Roassal2 to the World. There are many missing pieces: the font problem has to be solved, we need for a proper documentation, need more sexy examples, nicer integration on the webâ¦ Roassal2 is largely compatible with Roassal1. However, you probably want to do some significant rewriting to benefit from all the cool animations, color fading, fancy interactions, and much more. We do not have much documentation so far. It will soon come. A book is currently being written (by the way, I am looking to see the effort of Pillar). A large Chilean crew will be present at esug to demonstrate Roassal2 with fireworks and trumpets. Cheers, Alexandre On May 21, 2014, at 5:31 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi everyone. Is Roassal2 released? I guess is was already integrated into Moose, and from time to time I see amazing pictures and video on Twitter/Facebook. But is there any new guide? Or changes list from Roassal1? > > Cheers. > Uko -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 21, 2014

Re: [Pharo-dev] a Pharo talk from a ruby conference

by Ben Coman

May 21, 2014

Re: [Pharo-dev] Making screenshots programmatically for book

by Ben Coman

Ben Coman wrote: > Stephan Eggermont wrote: >> This code allows me to generate some screenshots. >> The exporter deletes the old picture, if it exists. >> >> |directory exporter window bounds | >> directory := FileSystem workingDirectory / 'pictures' . >> directory ensureCreateDirectory. >> exporter := DOScreenshotExporter new. >> exporter directory: directory. >> exporter writeWorldAs: 'world.png'. >> window := DOPartiesList new openWithSpec window. >> exporter writeMorph: window value as: 'PartiesList.png'. >> bounds := window fullBounds. >> exporter writeMorph: window value rectangle: (bounds insetBy: 20@20) >> as: 'PartOfPartiesList.png'. >> window close. >> > Now what is the best way to associate such code with a Pillar source > file. > 1. Put screenshot generation script inline? > 2. Put screenshot generation script in a separate file with same > basename as the produced bitmap file? > 2a. Have a command line handler to manually invoke snapshot generation? > 2b. Have a Pillar notation that references the script rather than > the produced file, and generate snapshot each time? (maybe good for > CI, but slows user down) > > cheers -ben > > Thinking further on this, it could be useful when Pillar processes a source file to mark code to be executed in the image running Pillar. For instance when the reader is asked to do something, sometimes a snapshot taken manually might be done out of order and something not-yet-done (in the sequence of the tutorial) slips into the snapshot. For example, if the reader is asked to add a class, Pillar source might hypothetically look like this... [[[ Object subclass: #BlankCell instanceVariableNames: '' classVariableNames: '' category: 'LaserGame-Model' ]]] executeInImage +First class created>generateFrom://figures/firstClass.st>file://figures/firstClass.png|width=50|label=firstClass+ This would ensure the snapshots a synchronised with the narrative. That is how it might work for code blocks that are shown in the narrative, but you might also want to be able to execute support code in the background. Probably you would want to save the image to a new file to avoid accidentally corrupting the Pillar program. This is not something I'd want to play with right now, but just interested in feedback while its fresh in my mind. cheers -ben

May 21, 2014

Re: [Pharo-dev] Pharo in Rasbian ?

by ClÃ©ment Bera

2014-05-20 17:06 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > 2014-05-20 16:23 GMT+02:00 Juan <smalltalker.marcelo(a)gmail.com>: > > Jannik >> >> >> the phratch proyect provides access to GPIO port? >> ffi to achieve such access is available? >> any ideas? >> > > FFI for the raspberry pie was finished for the Pharo vm 3 weeks ago. > Sorry as JB pointed me out, the FFI for the Raspberry Pie is working, but is not integrated into the Pharo VM yet. > > So I guess the Phratch team has not found the time yet to do that, but it > should be possible. > > >> thanks in advance >> best >> >> jmdc >> >> >> On Tue, May 20, 2014 at 10:36 AM, jannik laval <jannik.laval(a)gmail.com>wrote: >> >>> Hi, >>> >>> Probably he does not know phratch for Rasberry-Pi: >>> https://ci.inria.fr/pharo-contribution/view/Phratch/job/Phratch-OneClick-RP… >>> >>> Cheers :) >>> >>> >>> 2014-05-20 15:32 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: >>> >>> Hi! >>>> >>>> A friend of mine recently bought a Raspberry pi and installed Rasbian, >>>> a Debian-like OS for Raspberry. Squeak and Scratch are installed per >>>> default. There is room to fill here... >>>> >>>> >>>> Cheers, >>>> Alexandre >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> >>> ~~Jannik Laval~~ >>> Ãcole des Mines de Douai >>> Enseignant-chercheur >>> http://www.jannik-laval.eu >>> http://www.phratch.com >>> http://car.mines-douai.fr/ >>> >> >> >

May 21, 2014

NativeBoost and WKHTML

by Torsten Bergmann

Sven wrote: >Just out of curiosity, why not use Artefact, https://sites.google.com/site/artefactpdf ? > >I haven't looked at the different approaches, but I have this natural tendency against native >libraries, >if we can do it directly in Pharo. That is why I am asking: why this road and not the other >? Short Answer: So you know the usual "Pharo does not yet rule the world" and the usual "designers do not yet code in Smalltalk" discussion ;) Long Answer: You half-way answered yourself "if we can do it directly in Pharo ..." which could be answered with "not yet out of the box". It's not that I dislike the Artefact "Smalltalk only" approach. In fact I have contributed also to this project (cleaned and refactored it) and use it for simple stuff. Still there are some small issues remaining (no support to embedd fonts, etc). Also there is no "visual template editor" - so currently you have to "code your layout". So very often using HTML and CSS for an easy and good looking print is much better and easier to do than manually code each box, line, text manually. Also there are tons of visual HTML Editors, HTML is easy to generate and CSS allows you to style. If you work with Seaside then you also already have the HTML. So far there is no HTML/CSS to Artfeact project and it would not be easy to reimplement such a beast (if done for all possible cases). WKHTML uses the QT Webkit rendering engine and we do not have to reinvent the wheel. I fully understand that the native library is not as portable as a ST only solution but we already provide and use Cairo, Freetype and others with the default Pharo release. WKHTML is LGPL so if I understand correctly there is no conflict in using and redistributing. Bye T.

May 21, 2014

Re: [Pharo-dev] Making screenshots programmatically for book

by Ben Coman

Stephan Eggermont wrote: > This code allows me to generate some screenshots. > The exporter deletes the old picture, if it exists. > > |directory exporter window bounds | > directory := FileSystem workingDirectory / 'pictures' . > directory ensureCreateDirectory. > exporter := DOScreenshotExporter new. > exporter directory: directory. > exporter writeWorldAs: 'world.png'. > window := DOPartiesList new openWithSpec window. > exporter writeMorph: window value as: 'PartiesList.png'. > bounds := window fullBounds. > exporter writeMorph: window value rectangle: (bounds insetBy: 20@20) as: 'PartOfPartiesList.png'. > window close. > Now what is the best way to associate such code with a Pillar source file. 1. Put screenshot generation script inline? 2. Put screenshot generation script in a separate file with same basename as the produced bitmap file? 2a. Have a command line handler to manually invoke snapshot generation? 2b. Have a Pillar notation that references the script rather than the produced file, and generate snapshot each time? (maybe good for CI, but slows user down) cheers -ben

May 21, 2014

Re: [Pharo-dev] Call for co-coders

by stepharo

I started to write to files with roadmaps so that other people can work with me :). https://github.com/pharo-project/pharo-workingRoadmaps Nicola Heiss should prepare one or two on cleaning Nautilus, Theme, and or KeyMappings Stef

May 21, 2014

Re: [Pharo-dev] [Seaside-dev] Magritte versions

by Esteban Lorenzano

I made it because 3.1.3 does not loads in Pharo 3 and I needed it. It changes some RectangleMorph dependencies and I do not remember what more. I said it in the list when I did it (like 3 months ago, I do not remember). Please, if you are going to remove it, give me a valid configuration that I can use instead. Esteban On 21 May 2014, at 06:50, Diego Lont <diego.lont(a)delware.nl> wrote: > Hi all, > > We would like to have more communication about the Magritte configuration. We will start by describing the current state, as far as we know it. > > The current released version of Magritte is 3.1.3. This versions contains the latest changes and is a release version, so should not be changed. Please use #release3.1 in referring to this version, to allow for minor updates and bug fixes to be automatically integrated. > The #release3.0 is also maintained, as this refers to #release3.0 of Seaside. And as long as #release3.1 of Seaside is not released on Gemstone, I will maintain this version. > > There is also versions 3.2. We do not know why this version is created. It uses a duplicate baseline (only the Grease version differs), and no big changes for Magritte are planned (to my knowledge). So we propose to remove this version. If you want this version to be kept, please reply this mail with a reason. Version 3.2 is outdated, but it implies to be more recent than 3.1.3. > > For the time being I will only remove the 3.2-baseline, as it is duplicate. If I do not receive a mail saying 3.2 should be kept, I will remove this version beginning of June. > > For development I will create a version 3.1.4. I will also point #development to this version. > > Discussion on Magritte List. > > Cheers, > Stephan and Diego > > _______________________________________________ > seaside-dev mailing list > seaside-dev(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

May 21, 2014