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

Back to the mailing-list

by Pharo4Stef

Hi guys I decided to stop my retreat and be back to the mailing-list. Iâm preparing some actions that I want to discuss with you. Stef

Feb. 22, 2014

Re: [Pharo-dev] test failures in downloaded image 30733

by btc＠openinworld.com

Feb. 22, 2014

Re: [Pharo-dev] Morphic UI designer

by Stephan Eggermont

At the moment I'm moving, so I have very little time to do something about it. Current state is described in a thread from end of last year: http://forum.world.st/have-a-question-for-morphic-Designer-in-pharo-td47313… Stephan

Feb. 21, 2014

Re: [Pharo-dev] SWIG for Native Boost FFI

by GÃ¶ran Krampe

Hey! On 02/21/2014 06:50 PM, Ronie Salgado wrote: > Hi there!, > > It is great to hear that it is being useful. Currently I am taking some > vacations, so I will probably be without Internet access for some days. [SNIP] > I took that kind of approach because it gives more flexibility, but it > provides probably a reduced performance in comparison with placing the > callouts directly in the wrapped classes. Some people that saw this when > developing this did not like this approach. Yeah, I can see what you mean - and I think that's just fine. One bit tricky problem: there are classes generated starting with lower case. That doesn't fly :) Also, LF instead of CRs after signatures makes NB barf when parsing. That was easily solved with a global tr '\n' '\r' of course, the class naming is a bit harder - need to go to the source. I can see if I can find that one :) regards, GÃ¶ran PS. Tried wrapping Nanomsg.org today, got so far as to start running test code - but then it fails creating a socket - not sure why, might not be your fault at all actually :) When it works I will blog about it.

Feb. 21, 2014

Re: [Pharo-dev] SWIG for Native Boost FFI

by Alexandre Bergel

Really impressive Ronie!! Alexandre > Le 21-02-2014 Ã 12:50, Ronie Salgado <roniesalg(a)gmail.com> a Ã©crit : > > Hi there!, > > It is great to hear that it is being useful. Currently I am taking some vacations, so I will probably be without Internet access for some days. > Currently the most missing parts are documentation, which I am going to write when having some time. > > Here are some early details, before I start properly documenting them: > Â·This is heavily based in the C# bindings. There are additional typemaps such as nbtype, nbin and nbout. They are similar to the cstype, csin and csout typemaps presents the C# generator. > Â·They are two Smalltalk class and some common superclasses generated. One Smalltalk class contains all the NB-FFI callout methods, another contains wrappers for all the global C/C++ stuff. > Â·For each C++ a Smalltalk class is generated. > Â·The common superclass provides a destroy method for destroying an object. > Â·The extra overhead in new are to register properly with the GC. > Â·The C pointer is wrapped in a reference object that contains things for properly interact with the GC and destroying C++ object avoiding crashing the VM. > > Swig usually makes some kind of opaque type for some pointers. If they are intended to be an Array, maybe some extra typemaps has to be added. More information about typemaps is on the SWIG manual. > > I took that kind of approach because it gives more flexibility, but it provides probably a reduced performance in comparison with placing the callouts directly in the wrapped classes. Some people that saw this when developing this did not like this approach. > > I will document all of this more properly later, but I have to go now because I am in a hurry. > > Best regards, > Ronie Salgado > > > 2014-02-21 7:16 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>: >> Excellent!!!! >> >> That's really a missing block coming to life! >> >> I'll try it this weekend on my Linux system. >> >> Phil >> >> >> >>> On Fri, Feb 21, 2014 at 10:24 AM, GÃ¶ran Krampe <goran(a)krampe.se> wrote: >>> Hi all! >>> >>>> On 01/22/2014 09:25 PM, Ronie Salgado wrote: >>>> I started working on extending SWIG to generate bindings for NativeBoost >>>> FFI, using as a reference the C# binding generator. I am committing my >>>> work on this into https://github.com/ronsaldo/swig/ . >>> >>> Just wanted to report that this stuff WORKS :) >>> >>> * I cloned down Ronie's SWIG. Did the autogen.sh, ./configure, make, make install dance. >>> * I went into Examples/ruby/value and: >>> * Changed module name to "Example" (instead of "example") >>> * Ran: swig -pharo example.i (produces C code and Example.st) >>> * Compile: gcc -m32 -c -fpic -fPIC example_wrap.c example.c >>> * Link: gcc -m32 -shared example.o example_wrap.o -o Example.so >>> * Then I filed in Example.st into Pharo 2.0, and put Example.so in the directory where I started the pharo VM. >>> >>> And well, after fixing some buglets (if you want to recreate this, email me or ask here) it works! I added a little test class for fun. >>> >>> Fantastic stuff! Sure, not complete by any means, but hey, it worked and not a single VM crash while playing with it. Ronie - good work! >>> >>> If you are on a Linux, I attached these two files. File into Pharo 2.0, open TestRunner and run ExampleTest. >>> >>> regards, GÃ¶ran >

Feb. 21, 2014

Re: [Pharo-dev] SWIG for Native Boost FFI

by Ronie Salgado

Hi there!, It is great to hear that it is being useful. Currently I am taking some vacations, so I will probably be without Internet access for some days. Currently the most missing parts are documentation, which I am going to write when having some time. Here are some early details, before I start properly documenting them: Â·This is heavily based in the C# bindings. There are additional typemaps such as nbtype, nbin and nbout. They are similar to the cstype, csin and csout typemaps presents the C# generator. Â·They are two Smalltalk class and some common superclasses generated. One Smalltalk class contains all the NB-FFI callout methods, another contains wrappers for all the global C/C++ stuff. Â·For each C++ a Smalltalk class is generated. Â·The common superclass provides a destroy method for destroying an object. Â·The extra overhead in new are to register properly with the GC. Â·The C pointer is wrapped in a reference object that contains things for properly interact with the GC and destroying C++ object avoiding crashing the VM. Swig usually makes some kind of opaque type for some pointers. If they are intended to be an Array, maybe some extra typemaps has to be added. More information about typemaps is on the SWIG manual. I took that kind of approach because it gives more flexibility, but it provides probably a reduced performance in comparison with placing the callouts directly in the wrapped classes. Some people that saw this when developing this did not like this approach. I will document all of this more properly later, but I have to go now because I am in a hurry. Best regards, Ronie Salgado 2014-02-21 7:16 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>: > Excellent!!!! > > That's really a missing block coming to life! > > I'll try it this weekend on my Linux system. > > Phil > > > > On Fri, Feb 21, 2014 at 10:24 AM, GÃ¶ran Krampe <goran(a)krampe.se> wrote: > >> Hi all! >> >> On 01/22/2014 09:25 PM, Ronie Salgado wrote: >> >>> I started working on extending SWIG to generate bindings for NativeBoost >>> FFI, using as a reference the C# binding generator. I am committing my >>> work on this into https://github.com/ronsaldo/swig/ . >>> >> >> Just wanted to report that this stuff WORKS :) >> >> * I cloned down Ronie's SWIG. Did the autogen.sh, ./configure, make, make >> install dance. >> * I went into Examples/ruby/value and: >> * Changed module name to "Example" (instead of "example") >> * Ran: swig -pharo example.i (produces C code and Example.st) >> * Compile: gcc -m32 -c -fpic -fPIC example_wrap.c example.c >> * Link: gcc -m32 -shared example.o example_wrap.o -o Example.so >> * Then I filed in Example.st into Pharo 2.0, and put Example.so in the >> directory where I started the pharo VM. >> >> And well, after fixing some buglets (if you want to recreate this, email >> me or ask here) it works! I added a little test class for fun. >> >> Fantastic stuff! Sure, not complete by any means, but hey, it worked and >> not a single VM crash while playing with it. Ronie - good work! >> >> If you are on a Linux, I attached these two files. File into Pharo 2.0, >> open TestRunner and run ExampleTest. >> >> regards, GÃ¶ran >> > >

Feb. 21, 2014

Re: [Pharo-dev] Multiple-selection drag-and-drop

by Martin Dias

On Fri, Feb 21, 2014 at 2:14 PM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > This works: > > m := TreeModel new. > m roots: #(1 2 3 4 5). > m dragEnabled: true. > m dropEnabled: true. > > m transferBlock: [ :p :s | > TransferMorph > withPassenger: s model > selectedItems from: s ]. > > m multiSelection: true. > > m openWithSpec. > > I guess the same applies for the other model, aka, redefining the > TransferMorph. > I am currently working on a TransferModel to hide the morphic part of it, > but it will not be in Pharo 3.0. Great, it worked. Thanks

Feb. 21, 2014

Re: [Pharo-dev] Pharo 3| Nautilus question

by Noury Bouraqadi

Done. Created both issues. Noury On 20 fÃ©vr. 2014, at 15:11, Esteban Lorenzano wrote: > > On 20 Feb 2014, at 15:02, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > >> Hi, >> >> When I add a package, I was expecting to see it appear in monticello. I guess it's a pending feature. Isn't it? Will we get it in 3.0? >> I'm aksing this because I found this comment: 'A NautilusMonticello is a class used to handle monticello integration into Nautilus by creating the menu entriesâ > > Honestly, I think thatâs a bug nowâ¦ since 1RPackage = 1MCPackage now, people is expecting to have them autocreatedâ¦ probably we should add an issue to add it in 3 (even if is a missing feature, is so annoying that has the level of âbugâ, IMO) > >> >> BTW, I have encountered a problem when dealing with protocols in Nautilus. >> Suppose I want to add a protocol 'animation' to a new class. >> When I type in 'animation', the window filters out all suggestions but keeps 'zoom animation'. >> >> If I only hit the OK button, the newly created protocol is 'zoom animation'. >> But, I didn't select the suggestion. So, I was expecting to have the 'animation' as protocol name. >> Did I miss something? > > add a bug to the tracker, please :) > > cheers, > Esteban > >> >> I tested on a 30771 and in older versions too. >> >> Thanks >> Noury >> -- >> http://twitter.com/#!/NouryBouraqadi >> http://car.mines-douai.fr/noury >> >> > > Noury -- http://twitter.com/#!/NouryBouraqadi http://car.mines-douai.fr/noury

Feb. 21, 2014

Re: [Pharo-dev] postgresV2

by Juan

hi It's a Postgres case problem. postgres translate any sentence to lowercase. For use uppercase you need use the " character. for example 'select * from TESTABLE' postgres execute 'select * from testable' and TESTABLE doesn't exists error. If you want uppercase you need reformulate sentence like this 'select * from "TESTABLE" ;' :( best regards jmdc On Fri, Feb 21, 2014 at 11:28 AM, Carlo <snoobabk(a)gmail.com> wrote: > In psql you could try: > \c testdb > > Then create the table. > \conninfo will tell you which db you are connected to. > > Carlo > > On 21 Feb 2014, at 4:25 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Yupee! That worked fine. Thanks. I can move on now. > > Any idea how to connect to a non-default DB? > > Doru > > > On Fri, Feb 21, 2014 at 3:22 PM, Carlo <snoobabk(a)gmail.com> wrote: > >> Hi >> >> I just tried following your steps and had the exact same issues. >> What I now tried is connecting to default DB which seems to be your USER >> name which worked for me. >> So in your scenario connect to girba as DB instead of testdb and you >> should succeed. >> >> Cheers >> Carlo >> >> On 21 Feb 2014, at 4:16 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> >> >> >> On Fri, Feb 21, 2014 at 7:33 AM, Sven Van Caekenberghe <sven(a)stfx.eu> >> wrote: >> >>> Weird, you seem to have a DB connection. >>> >> >> Exactly. So, that is good :) >> >> >>> Try something that does not need a table, like >>> >>> select current_time; >>> >> >> Thanks for the suggestion. Funny enough, this worked fine. >> >> >> Did you create 'testdb' and was 'testable' actually created there ? >>> >>> Can you connect to the DB on the command line ? >>> >>> $ psql testdb >>> >>> >> The DB seems to be created: >> >> girba=# \l >> List of databases >> Name | Owner | Encoding | Collate | Ctype | Access >> privileges >> >> -----------+-------+----------+-------------+-------------+------------------- >> girba | girba | UTF8 | en_US.UTF-8 | en_US.UTF-8 | >> postgres | girba | UTF8 | en_US.UTF-8 | en_US.UTF-8 | >> template0 | girba | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/girba >> + >> | | | | | >> girba=CTc/girba >> template1 | girba | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/girba >> + >> | | | | | >> girba=CTc/girba >> testdb | girba | UTF8 | en_US.UTF-8 | en_US.UTF-8 | >> (5 rows) >> >> And the table seems to be created, too. I have: >> >> girba=# \dt >> List of relations >> Schema | Name | Type | Owner >> --------+-----------+-------+------- >> public | testtable | table | girba >> (1 row) >> >> >> Anything else I could test? >> >> Doru >> >> >> On 21 Feb 2014, at 06:55, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> > Hi, >>> > >>> > I am trying to get the Postgres support to work on Mac, but I have >>> difficulties and I would need a bit of help. >>> > >>> > Here is what I do: >>> > >>> > 1. Install Postgres from http://postgresapp.com >>> > >>> > 2. Open the psql console and create a test table: >>> > CREATE TABLE TESTTABLE >>> ( >>> > ID int, >>> >>> TEXT varchar(255) >>> > ); >>> > >>> > 3. In Pharo, load PostgresV2: >>> > Gofer new >>> > smalltalkhubUser: 'PharoExtras' project: 'PostgresV2'; >>> > configuration; >>> > load. >>> > (#ConfigurationOfPostgresV2 asClass project version: '2.0-baseline') >>> load >>> > >>> > 4. In a Workspace: >>> > | conn | >>> > conn := PGConnection new. >>> > conn connectionArgs: >>> > (PGConnectionArgs >>> > hostname: 'localhost' >>> > portno: 5432 >>> > databaseName: 'testdb' >>> > userName: 'girba' >>> > password: ''). >>> > conn startup. >>> > >>> > This works fine and the PGResult is good (if I use a wrong user, it >>> tells me that the user does not exist). >>> > >>> > 5. However: >>> > >>> > conn execute: 'SELECT * FROM TESTTABLE;' >>> > >>> > ==> PGErrorResponse(value='ERROR: relation "testtable" does not exist >>> at character 15 >>> > ') >>> > >>> > What am I missing? >>> > >>> > Doru >>> > >>> > -- >>> > www.tudorgirba.com >>> > >>> > "Every thing has its own flow" >>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > >

Feb. 21, 2014

Re: [Pharo-dev] WhatsUp from: 2014-02-17 until: 2014-02-28

by Tudor Girba

Nice. Let us know how it goes. Doru On Fri, Feb 21, 2014 at 3:29 PM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > On Fri, Feb 21, 2014 at 2:38 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Interesting :). Could you say more about this? Is it available for > testing > > somewhere? > > not yet available but we should be able to release it open source. We > just wrote a Python program that generates MSE files. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 21, 2014