September 2014 - Pharo-users

Strange colour reversal on the Spec site

by Andy Burnett

Hello, I am posting here, because I couldn't find a Spec specific list. Two things: 1. The colour scheme for all the code examples on the site seems to have gone very odd. The text is now a light blue/green on a white background. Almost completely illegible. Has someone changed a css file? 2. I noticed in the news section that the license has changed to GPL, because of a disagreement with the direction of Pharo. Could someone explain what the disagreement was, and whether this is something we should be concerned about? Cheers Andy á§

Sept. 10, 2014

Re: [Pharo-users] Tide installation

by Tommaso Dal Sasso

On 10/09/14 16:43, Esteban Lorenzano wrote: > that might be an amber problem. > copying Nico to see if that is the case. Ok, now it worked... I don't know what changed, but seems to be something related to my side. I'll investigate further, forget about it for now. Sorry for bothering you. Thanks, Tommaso > > On 10 Sep 2014, at 16:35, Tommaso Dal Sasso <tommaso.dalsasso(a)gmail.com> wrote: > >> I am having problems with Tide installation. For the last week, after loading the Tide page I get an error in the javascript console that says: >> >> "SyntaxError: missing ; before statement" in Kernel-Methods.js @ line 1780 >> and >> "TypeError: klass is undefined" >> >> As far as I remember, a fresh install last week worked properly, but I cannot understand if it is a Tide or an Amber related problem. >> Does anybody have clue of how to solve that? >> >> Thanks, >> Tommaso >> >> >> On 02/09/14 17:05, Bernat Romagosa wrote: >>> Hi list! >>> >>> I wanted to try out Tide, and I'm following the steps at: https://github.com/tide-framework/tide >>> >>> However, I can't get through the bower install step. Here's the output: >>> >>> >>> bower amber#0efe3ad09 not-cached >>> git://github.com/amber-smalltalk/amber.git#0efe3ad09 >>> <http://github.com/amber-smalltalk/amber.git#0efe3ad09> >>> bower amber#0efe3ad09 resolve >>> git://github.com/amber-smalltalk/amber.git#0efe3ad09 >>> <http://github.com/amber-smalltalk/amber.git#0efe3ad09> >>> bower amber#0efe3ad09 ENORESTARGET Tag/branch 0efe3ad09 does >>> not exist >>> Additional error details: >>> Available tags: 0.10, 0.10.0, 0.11.0, 0.12.0, 0.12.1, 0.12.2, >>> 0.12.3, 0.12.4, 0.12.6, 0.13.0-alpha.1, 0.13.0-alpha.2, 0.9, >>> 0.9.1, legacy, legacy2, legacy3-iife >>> Available branches: 0.13-prereleases, camillo-hacks, chromeos, >>> gh-pages, master, moka, nemo, nw-helios-app, stable, >>> website-deployment >>> >>> >>> >>> I changed 0efe3ad09 for stable in bower.json and it failed with: >>> >>> >>> bower amber#stable not-cached >>> git://github.com/amber-smalltalk/amber.git#stable >>> <http://github.com/amber-smalltalk/amber.git#stable> >>> bower amber#stable resolve >>> git://github.com/amber-smalltalk/amber.git#stable >>> <http://github.com/amber-smalltalk/amber.git#stable> >>> bower amber#stable checkout stable >>> bower amber#stable error Arguments to path.join must >>> be strings >>> Stack trace: >>> TypeError: Arguments to path.join must be strings >>> at path.js:360:15 >>> at Array.filter (native) >>> at Object.exports.join (path.js:358:36) >>> at GitHubResolver.GitResolver._cleanup >>> (/usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:182:26) >>> at >>> /usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:74:25 >>> at Promise.apply >>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1122:26) >>> at Promise.promise.promiseDispatch >>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) >>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:1337:14 >>> at flush >>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:108:17) >>> at process._tickCallback (node.js:415:13) >>> Console trace: >>> Trace >>> at StandardRenderer.error >>> (/usr/local/lib/node_modules/bower/lib/renderers/StandardRenderer.js:74:17) >>> at Logger.updateNotifier.packageName >>> (/usr/local/lib/node_modules/bower/bin/bower:109:18) >>> at Logger.EventEmitter.emit (events.js:95:17) >>> at Logger.emit >>> (/usr/local/lib/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39) >>> at /usr/local/lib/node_modules/bower/lib/commands/install.js:28:16 >>> at _rejected >>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:808:24) >>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:834:30 >>> at Promise.when >>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1079:31) >>> at Promise.promise.promiseDispatch >>> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) >>> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:574:44 >>> System info: >>> Bower version: 1.2.6 >>> Node version: 0.10.25 >>> OS: Linux 3.11.0-19-generic x64 >>> >>> >>> I'm kind of stuck, any tips? >>> >>> Thanks! >>> >>> Bernat. >>> >>> >>> -- >>> Bernat Romagosa. >> >

Sept. 10, 2014

Re: [Pharo-users] Tide installation

by Esteban Lorenzano

that might be an amber problem. copying Nico to see if that is the case. On 10 Sep 2014, at 16:35, Tommaso Dal Sasso <tommaso.dalsasso(a)gmail.com> wrote: > I am having problems with Tide installation. For the last week, after loading the Tide page I get an error in the javascript console that says: > > "SyntaxError: missing ; before statement" in Kernel-Methods.js @ line 1780 > and > "TypeError: klass is undefined" > > As far as I remember, a fresh install last week worked properly, but I cannot understand if it is a Tide or an Amber related problem. > Does anybody have clue of how to solve that? > > Thanks, > Tommaso > > > On 02/09/14 17:05, Bernat Romagosa wrote: >> Hi list! >> >> I wanted to try out Tide, and I'm following the steps at: https://github.com/tide-framework/tide >> >> However, I can't get through the bower install step. Here's the output: >> >> >> bower amber#0efe3ad09 not-cached >> git://github.com/amber-smalltalk/amber.git#0efe3ad09 >> <http://github.com/amber-smalltalk/amber.git#0efe3ad09> >> bower amber#0efe3ad09 resolve >> git://github.com/amber-smalltalk/amber.git#0efe3ad09 >> <http://github.com/amber-smalltalk/amber.git#0efe3ad09> >> bower amber#0efe3ad09 ENORESTARGET Tag/branch 0efe3ad09 does >> not exist >> Additional error details: >> Available tags: 0.10, 0.10.0, 0.11.0, 0.12.0, 0.12.1, 0.12.2, >> 0.12.3, 0.12.4, 0.12.6, 0.13.0-alpha.1, 0.13.0-alpha.2, 0.9, >> 0.9.1, legacy, legacy2, legacy3-iife >> Available branches: 0.13-prereleases, camillo-hacks, chromeos, >> gh-pages, master, moka, nemo, nw-helios-app, stable, >> website-deployment >> >> >> >> I changed 0efe3ad09 for stable in bower.json and it failed with: >> >> >> bower amber#stable not-cached >> git://github.com/amber-smalltalk/amber.git#stable >> <http://github.com/amber-smalltalk/amber.git#stable> >> bower amber#stable resolve >> git://github.com/amber-smalltalk/amber.git#stable >> <http://github.com/amber-smalltalk/amber.git#stable> >> bower amber#stable checkout stable >> bower amber#stable error Arguments to path.join must >> be strings >> Stack trace: >> TypeError: Arguments to path.join must be strings >> at path.js:360:15 >> at Array.filter (native) >> at Object.exports.join (path.js:358:36) >> at GitHubResolver.GitResolver._cleanup >> (/usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:182:26) >> at >> /usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:74:25 >> at Promise.apply >> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1122:26) >> at Promise.promise.promiseDispatch >> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) >> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:1337:14 >> at flush >> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:108:17) >> at process._tickCallback (node.js:415:13) >> Console trace: >> Trace >> at StandardRenderer.error >> (/usr/local/lib/node_modules/bower/lib/renderers/StandardRenderer.js:74:17) >> at Logger.updateNotifier.packageName >> (/usr/local/lib/node_modules/bower/bin/bower:109:18) >> at Logger.EventEmitter.emit (events.js:95:17) >> at Logger.emit >> (/usr/local/lib/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39) >> at /usr/local/lib/node_modules/bower/lib/commands/install.js:28:16 >> at _rejected >> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:808:24) >> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:834:30 >> at Promise.when >> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1079:31) >> at Promise.promise.promiseDispatch >> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) >> at /usr/local/lib/node_modules/bower/node_modules/q/q.js:574:44 >> System info: >> Bower version: 1.2.6 >> Node version: 0.10.25 >> OS: Linux 3.11.0-19-generic x64 >> >> >> I'm kind of stuck, any tips? >> >> Thanks! >> >> Bernat. >> >> >> -- >> Bernat Romagosa. > >

Sept. 10, 2014

Re: [Pharo-users] Tide installation

by Tommaso Dal Sasso

I am having problems with Tide installation. For the last week, after loading the Tide page I get an error in the javascript console that says: "SyntaxError: missing ; before statement" in Kernel-Methods.js @ line 1780 and "TypeError: klass is undefined" As far as I remember, a fresh install last week worked properly, but I cannot understand if it is a Tide or an Amber related problem. Does anybody have clue of how to solve that? Thanks, Tommaso On 02/09/14 17:05, Bernat Romagosa wrote: > Hi list! > > I wanted to try out Tide, and I'm following the steps at: > https://github.com/tide-framework/tide > > However, I can't get through the bower install step. Here's the output: > > > bower amber#0efe3ad09 not-cached > git://github.com/amber-smalltalk/amber.git#0efe3ad09 > <http://github.com/amber-smalltalk/amber.git#0efe3ad09> > bower amber#0efe3ad09 resolve > git://github.com/amber-smalltalk/amber.git#0efe3ad09 > <http://github.com/amber-smalltalk/amber.git#0efe3ad09> > bower amber#0efe3ad09 ENORESTARGET Tag/branch 0efe3ad09 does > not exist > Additional error details: > Available tags: 0.10, 0.10.0, 0.11.0, 0.12.0, 0.12.1, 0.12.2, > 0.12.3, 0.12.4, 0.12.6, 0.13.0-alpha.1, 0.13.0-alpha.2, 0.9, > 0.9.1, legacy, legacy2, legacy3-iife > Available branches: 0.13-prereleases, camillo-hacks, chromeos, > gh-pages, master, moka, nemo, nw-helios-app, stable, > website-deployment > > > > I changed 0efe3ad09 for stable in bower.json and it failed with: > > > bower amber#stable not-cached > git://github.com/amber-smalltalk/amber.git#stable > <http://github.com/amber-smalltalk/amber.git#stable> > bower amber#stable resolve > git://github.com/amber-smalltalk/amber.git#stable > <http://github.com/amber-smalltalk/amber.git#stable> > bower amber#stable checkout stable > bower amber#stable error Arguments to path.join must > be strings > Stack trace: > TypeError: Arguments to path.join must be strings > at path.js:360:15 > at Array.filter (native) > at Object.exports.join (path.js:358:36) > at GitHubResolver.GitResolver._cleanup > (/usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:182:26) > at > /usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:74:25 > at Promise.apply > (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1122:26) > at Promise.promise.promiseDispatch > (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) > at /usr/local/lib/node_modules/bower/node_modules/q/q.js:1337:14 > at flush > (/usr/local/lib/node_modules/bower/node_modules/q/q.js:108:17) > at process._tickCallback (node.js:415:13) > Console trace: > Trace > at StandardRenderer.error > (/usr/local/lib/node_modules/bower/lib/renderers/StandardRenderer.js:74:17) > at Logger.updateNotifier.packageName > (/usr/local/lib/node_modules/bower/bin/bower:109:18) > at Logger.EventEmitter.emit (events.js:95:17) > at Logger.emit > (/usr/local/lib/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39) > at /usr/local/lib/node_modules/bower/lib/commands/install.js:28:16 > at _rejected > (/usr/local/lib/node_modules/bower/node_modules/q/q.js:808:24) > at /usr/local/lib/node_modules/bower/node_modules/q/q.js:834:30 > at Promise.when > (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1079:31) > at Promise.promise.promiseDispatch > (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) > at /usr/local/lib/node_modules/bower/node_modules/q/q.js:574:44 > System info: > Bower version: 1.2.6 > Node version: 0.10.25 > OS: Linux 3.11.0-19-generic x64 > > > I'm kind of stuck, any tips? > > Thanks! > > Bernat. > > > -- > Bernat Romagosa.

Sept. 10, 2014

Re: [Pharo-users] Workshop on Visual Data Narratives using Roassal/Pharo in our local hackerspace in BogotÃ¡ Colombia

by Offray Vladimir Luna CÃ¡rdenas

Thanks Alexandre and Doru, I already have the software as a graph video on our Pharo Zotero bookmark collection: https://www.zotero.org/groups/diseo_y_creacion_phd_msc_universidad_de_calda… My main concern is solving the questions about persistence and updating objects from Glamour browsers, probably because I don't understand transmissions to outside. Once that is solved surely we could document our Visual Data Narratives as structured docs created in a light markup inside Pharo. So any help on the proper threads is welcome. Cheers, Offray On 09/09/2014 11:12 PM, Tudor Girba wrote: > Very nice initiative! > > Doru > > On Tue, Sep 9, 2014 at 9:43 PM, Alexandre Bergel <alexandre.bergel(a)me.com > <mailto:alexandre.bergel@me.com>> wrote: > > This is excellent! > > Just to let you know, if you need to do a demo of Roassal, you have here the > video a an easy to do demo: https://vimeo.com/94724841 > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Sep 9, 2014, at 12:27 PM, Offray Vladimir Luna CÃ¡rdenas > <offray(a)riseup.net <mailto:offray@riseup.net>> wrote: > >> Hi, >> >> This is just a short mail to let you know whats happening here on the >> Pharo/Roassal front. We will be starting our workshops on what we I call >> Visual Data Narratives. Details (in Spanish) here: >> >> http://hackbo.co/hackboweb/eventos/evento/338 >> >> Cheers, >> >> Offray >> >> ps: I will show the Moose outliner, in its alpha stage. Hopefully the >> threads where I ask how to solve the problems will move a little more and >> we will be able to integrate this to the workshops memories building. >> >> > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow" >

Sept. 10, 2014

Re: [Pharo-users] New compiler: variable and recursive bloc of code

by Hilaire

Ok, thanks Le 10/09/2014 10:35, ClÃ©ment Bera a Ã©crit : > > The additional assignment is not needed. > > You get a warning because the warning detection is approximate and > sometimes raises warning whereas it should not, but if you proceed, it > compiles fine. -- Dr. Geo - http://drgeo.eu iStoa - http://istao.drgeo.eu

Sept. 10, 2014

Re: [Pharo-users] Math Ontologie on Pharo 3.0

by Henrik Johansen

IIRC, there are two sources of imported code in Monticello. By default it reads from the DataStream encoded .bin file, which stores source containing wide character as... a binary WideString. Unless the .bin file is somehow corrupted, importing non-ascii .mcz therefore works as long as you have a working DataStream reader. * If that path fails, it will read from the .st file, which, IIRC, had utf8 encoding added quite recently by Nicolas Cellier. So to narrow this down further, one has to ask: For what reason did the DataStream reading fail? - Did the DataStream get written (correctly)? - Did the DataStream fail to read a correctly written file? (f.ex. due to class shape changes in image, without proper backwards compat reading methods added) Why didn't the fallback .st work? - Did the .st file write out as utf8? (could be the case not if written from an older image, but then I'd expect the FileStream to barf, not the compiler) - Did the .st get written as the *correct* utf8? - Did the .st file read in as utf8? Once which combination of those things failed in this case is found, it should be easier to see what a fix could/should be. Cheers, Henry * Which is why non-ascii packages at least used to fail to import in Gemstone, their DataStream reader could not translate WideString instances to the proper internal string representations, and the fallback .st didn't use to be properly encoded. IIRC, the VW reader goes straight for the .st, so same problem there. There's a reason Seaside has ascii-only as a requirement :) On 09 Sep 2014, at 7:07 , Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Check/read my mail again: I don't think it is the compiler (my tests show it is not), then it must be Monticello, in the sense that it treats its input stream (encoding) wrongly. > > On 09 Sep 2014, at 15:25, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > >> >> >> 2014-09-09 14:12 GMT+02:00 Alain Busser <alain.busser(a)gmail.com>: >> Is this a reproducible case? http://ss3.gemstone.com/ss/MathsOntologie/MathsOntologie-AlainBusser.68.mcz >> >> >> Well I tried to merge that in the latest Pharo 4. >> >> With Opal I got the error 'unknown character' >> >> With the old compiler I got unmatched string quote. >> >> If it's French, could it be a ' ? >> >> It looks like a parser bug to me... >> >> >> I hope not :-) >> >> Alain >> >> On Tue, Sep 9, 2014 at 5:43 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> What kind of bug do you have with accent ? Do you have a stack trace ? >> >> More importantly, can you give us a reproducible case ? I will investigate tomorrow if you have a reproducible case to check if this is due to Opal. >> >> It may also be recent changes related to fonts. >> >> 2014-09-08 21:07 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >> I don't think it is related to Opal: I made a test class with an instance variable, accessor and class comment with accents - which I can file out and file in: >> >> >> >> >> >> >> >> I tested in 3.0 and 4.0 >> >> The problem might be with Monticello. >> >> >> On 08 Sep 2014, at 20:05, Hilaire <hilaire(a)drgeo.eu> wrote: >> >>> Oh, by the way, it looks like the accents are on the instance variable names. >>> >>> I edited the subject to not pollute the original discussion thread. >>> >>> Hilaire >>> >>> Le 08/09/2014 20:01, Hilaire a Ã©crit : >>>> Marcus, >>>> >>>> Alain's MathOntologie package provide Classes and Messages with French >>>> accent, to ease the understanding of programming to high school students. >>>> I am suspecting the new compiler or something related does not accepted >>>> accented caracters or something different to ASCII. >>>> >>>> Alain, in your package I noted the sources is not utf-8 but iso-8859-15 >>>> (8 bits), I converted it to utf-8 and tried to get it loaded in Pharo3, >>>> but still accent characters caused problem, see screenshot. >>>> >>>> Enclosed source file utf-8 converted and improper imported source code >>>> with accented variable name. >>>> >>>> Hilaire >>>> >>>> Le 08/09/2014 12:18, Alain Busser a Ã©crit : >>>>> Hi, >>>>> >>>>> I don't know if it is related but I have problems importing french files >>>>> inside Pharo 3: Anytime when there is an accentuated character there is >>>>> an error, and the file is not imported. Even if the character is a quote >>>>> inside double quotes (like in "it don't work") there is an error >>>>> message. Right now I can't import MathsOntologie >>>>> (http://ss3.gemstone.com/ss/MathsOntologie/MathsOntologie-AlainBusser.68.mcz) >>>>> >>>>> into Pharo 3 and I have to go on developing it in Pharo 1.4... >>>>> >>>>> Alain >>>>> >>>> >>>> >>> >>> >>> -- >>> Dr. Geo - http://drgeo.eu >>> iStoa - http://istao.drgeo.eu >>> >>> >> >> >> >> >> > >

Sept. 10, 2014

Re: [Pharo-users] New compiler: variable and recursive bloc of code

by ClÃ©ment Bera

Hello, The additional assignment is not needed. You get a warning because the warning detection is approximate and sometimes raises warning whereas it should not, but if you proceed, it compiles fine. 2014-09-10 8:54 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > Hello, > > I noticed this change described bellow and I just want to have > confirmation about it: > > The new Pharo 2.0 compiler need to have variable assigned with a value > before it used in a recursive bloc of code. Of course it is a bit > inelegant. Or is it something else and does it need to be reported? > > Thanks to let me know > > Hilaire > > For example this Dr. Geo code break in Pharo 2.0: > > | triangle c | > triangle := [:s1 :s2 :s3 :n | > c segment: s1 to: s2; > segment: s2 to: s3; > segment: s3 to: s1. > n > 0 ifTrue: > [triangle > value: s1 > value: (c middleOf: s1 and: s2) hide > value: (c middleOf: s1 and: s3) hide > value: n-1]. > [...] > ]. > > It must be changed to: > > | triangle c | > triangle := []. <= CHANGE HERE > triangle := [:s1 :s2 :s3 :n | > c segment: s1 to: s2; > segment: s2 to: s3; > segment: s3 to: s1. > n > 0 ifTrue: > [triangle > value: s1 > value: (c middleOf: s1 and: s2) hide > value: (c middleOf: s1 and: s3) hide > value: n-1]. > [...] > ]. > > > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istao.drgeo.eu > > >

Sept. 10, 2014

New compiler: variable and recursive bloc of code

by Hilaire

Hello, I noticed this change described bellow and I just want to have confirmation about it: The new Pharo 2.0 compiler need to have variable assigned with a value before it used in a recursive bloc of code. Of course it is a bit inelegant. Or is it something else and does it need to be reported? Thanks to let me know Hilaire For example this Dr. Geo code break in Pharo 2.0: | triangle c | triangle := [:s1 :s2 :s3 :n | c segment: s1 to: s2; segment: s2 to: s3; segment: s3 to: s1. n > 0 ifTrue: [triangle value: s1 value: (c middleOf: s1 and: s2) hide value: (c middleOf: s1 and: s3) hide value: n-1]. [...] ]. It must be changed to: | triangle c | triangle := []. <= CHANGE HERE triangle := [:s1 :s2 :s3 :n | c segment: s1 to: s2; segment: s2 to: s3; segment: s3 to: s1. n > 0 ifTrue: [triangle value: s1 value: (c middleOf: s1 and: s2) hide value: (c middleOf: s1 and: s3) hide value: n-1]. [...] ]. -- Dr. Geo - http://drgeo.eu iStoa - http://istao.drgeo.eu

Sept. 10, 2014

Re: [Pharo-users] Workshop on Visual Data Narratives using Roassal/Pharo in our local hackerspace in BogotÃ¡ Colombia

by Tudor Girba

Very nice initiative! Doru On Tue, Sep 9, 2014 at 9:43 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > This is excellent! > > Just to let you know, if you need to do a demo of Roassal, you have here > the video a an easy to do demo: https://vimeo.com/94724841 > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Sep 9, 2014, at 12:27 PM, Offray Vladimir Luna CÃ¡rdenas < > offray(a)riseup.net> wrote: > > Hi, > > This is just a short mail to let you know whats happening here on the > Pharo/Roassal front. We will be starting our workshops on what we I call > Visual Data Narratives. Details (in Spanish) here: > > http://hackbo.co/hackboweb/eventos/evento/338 > > Cheers, > > Offray > > ps: I will show the Moose outliner, in its alpha stage. Hopefully the > threads where I ask how to solve the problems will move a little more and > we will be able to integrate this to the workshops memories building. > > > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 10, 2014