June 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] merging images?

by Schwab,Wilhelm K

Esteban, A partial reply: for images, it is "easy" - not sure about icons. I often write code to annotate images; #getCanvas is the starting point. From there, you can draw pretty much whatever you want on an ordinary Form instance. The form can be loaded from a file or created to size and splattered with subsets of images loaded from disk, etc. I have long been under the impression that icons are somehow different, having size (not a big deal), transparency (more trouble?) and ultimately storage and file format requirements (not sure). It would indeed be nice to be able to easily manipulate icons in the image. It appears that some among us know how to do it :) Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Esteban Lorenzano [estebanlm(a)gmail.com] Sent: Friday, June 10, 2011 8:41 AM To: Pharo Development Subject: [Pharo-project] merging images? Hi, I wonder if there is a way to merge two Form objects into a new one? I'm trying to add "status" to some icons, something like "filter active" an icon with a mark, "filter inactive", another mark. Of course, I can create two different icons, but I thought "it would be nice to have this as a general functionality" :) Cheers, Esteban

June 12, 2011

Re: [Pharo-project] OCompletion is broken in 1.3

by Schwab,Wilhelm K

It works now, but can't be disabled by settings. Please see Issue 4390 with attached fix: http://code.google.com/p/pharo/issues/detail?id=4390 The fix adds a condition on ECPreferences class>>enabled to disallow completion when appropriate. The relevant line is the following: completionAllowed := ECPreferences enabled and:[ ECController allowModel: stringHolder ]. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck [marianopeck(a)gmail.com] Sent: Friday, June 10, 2011 8:30 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] OCompletion is broken in 1.3 THanks ben for all your help. It is fixed now. On Fri, Jun 10, 2011 at 12:22 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com<mailto:benjamin.vanryseghem.pharo@gmail.com>> wrote: In fact, I have posted two things: - a little improvement in OCompletion (not related to the bug) - then I take a look at OCompletionPharoCompatibility, but I have done a mistake because the package is OcompletionPharoCompatibility (with a minus "c") So finally, the only thing I have done to fix the bug is to change the ConfigurationOfOCompletion which now call a post load method to reset the default toolset and take in account the registry method. I hope I haven't done too many stupid things :) Ben On Jun 10, 2011, at 12:05 PM, Mariano Martinez Peck wrote: so...I saw you commit in OCompletion and then rollback the pharo-ish part. So..can that be put instead to OCompletionPharoCompatibilty and we are done? then we update ConfigurationOfOCompletion and we fix it :) On Fri, Jun 10, 2011 at 11:59 AM, Mariano Martinez Peck <marianopeck(a)gmail.com<mailto:marianopeck@gmail.com>> wrote: On Thu, Jun 9, 2011 at 12:45 PM, Benjamin Van Ryseghem <benjamin.vanryseghem.pharo(a)gmail.com<mailto:benjamin.vanryseghem.pharo@gmail.com>> wrote: It's fixed, I am looking where to post the fix :) Thanks!!!!!!!!!!!!! Put it somewhere please :) OCompletionPharoCompatibilty is not enough? you have commit rights there.... Ben 2011/6/9 Benjamin Van Ryseghem <benjamin.vanryseghem.pharo(a)gmail.com<mailto:benjamin.vanryseghem.pharo@gmail.com>> It comes from Toolset change. OCompletion should be registered as a Completion tool (but I do not remember the magic formula ^^) Ben 2011/6/9 Marcus Denker <marcus.denker(a)inria.fr<mailto:marcus.denker@inria.fr>> On Jun 9, 2011, at 12:21 PM, Benjamin Van Ryseghem wrote: > It happened between 13217 and 13234 ... > > Maybe the Paragraph changes ? > The Dev vs. Core is killing us. We need *one* image. We should really try to do that with 1.4, it will make everything simpler and easier to manage. Marcus -- Marcus Denker -- http://www.marcusdenker.de<http://www.marcusdenker.de/> INRIA Lille -- Nord Europe. Team RMoD. -- Mariano http://marianopeck.wordpress.com<http://marianopeck.wordpress.com/> -- Mariano http://marianopeck.wordpress.com<http://marianopeck.wordpress.com/> -- Mariano http://marianopeck.wordpress.com

June 12, 2011

[Pharo-project] [update 1.3] #13261

by Marcus Denker

13261 ----- Issue 4389: TestRunner was reverted to reference CrLfFileStream. Undo http://code.google.com/p/pharo/issues/detail?id=4389 Issue 4373: Failing test: CommandLineTest testDispatch http://code.google.com/p/pharo/issues/detail?id=4373 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 12, 2011

[Pharo-project] Glorp lost versions

by Guillermo Polito

Hi! Maybe someone can help me here :( 2 minutes ago, I've executed for the 23d time the following script Gofer it squeaksource: 'DBXTalk'; package: 'Glorp'; package: 'GlorpTests'; push And Squeaksource keeps losing versions :(. This makes me feel very unsafe. Maybe it's just a problem with those specific packages, I don't know :/. Thanks, Guille

June 12, 2011

[Pharo-project] Glorp port support for Postgres native driver Was: [ANN] New Glorp Port

by Guillermo Polito

Hi! I've done some little changes in order to have the native postgresql driver working in pharo 1.3 with glorp :). To download it, evaluate: (ConfigurationOfGlorpDBX project version: #stable) load: 'GlorpPostgresV2NativeWithTests' There are 998 tests (Glorp, Postgresql, Cryptography), and most of them are green. Most of the fails are from cryptography :/... I tested it in 1.3 only by now. Guille On Tue, Jun 7, 2011 at 12:09 AM, Yanni Chiu <yanni(a)rogers.com> wrote: > On 06/06/11 10:57 PM, Guillermo Polito wrote: > >> I'm glad to announce a first stable version of the new Glorp Port, from >> VW 7.7.1. >> > > Great news. > Any docs on what are the differences from the previous version? > What issues might there be in migration? > Does the Native PostgreSQL client still work with this new port? > _______________________________________________ > SqueakDBX mailing list > SqueakDBX(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx >

June 11, 2011

Re: [Pharo-project] [SqueakDBX] Re: [ANN] New Glorp Port

by Guillermo Polito

Hi Alan!! On Wed, Jun 8, 2011 at 4:46 PM, Alan Knight <knight(a)acm.org> wrote: > Thanks. > > I got Michael to import this into the public Store. That's an interesting > exercise, because in current versions, Store uses Glorp, so loading a > different version of Glorp and trying to publish it is interesting. > So you imported our changes in a branch of your repo? I was going to make a list of what we had to do to import it into pharo to send it to you :). Actually I learnt a lot (and I still do) while doing the port, but my learning process is a bit chaothic, and making a list in the first try was not easy for me, hehe. > Even in a different namespace the class extensions of base classes collide. > But it got imported. I'd like to be able to compare this to the current > Glorp versions and bring back portability fixes into the main branch. One > issue is that this comes as one package, GlorpDBX, so the package structure > of the original is lost. That can probably be worked around, but it's a bit > of work. > Actually yes, since in pharo we don't have namespaces, we had to recategorize a lot of classes to put it a little of order, hehe. > > Also, when you say "from VW 7.7.1" can I assume that means you started from > the version of Glorp distributed with VW 7.7.1, which would be '7.7.1 - 19'? > Yeap :) Thanks! Guille > > ------------------------------ > > Guillermo Polito <guillermopolito(a)gmail.com> > June 6, 2011 10:57 PM > > > I'm glad to announce a first stable version of the new Glorp Port, from VW > 7.7.1. > > The port has been integrated with the DBXTalk Driver (before known as > SqueakDBX), and tested on the following platforms: > > MySql: 872 tests run, 18 errors, 6 failures > PostgreSQL: 872 tests, 18 errors, 6 failures > Oracle: 872 tests, 21 errors, 5 failures. > > Most of the errors are caused by stuff the DBXTalk Driver does not support > yet, like LOBS. Also, there are some bugs yet I have to attack and learn > how to get rid of, hehe. > > One think to be careful of yet is the licencing (or how it should be > written). Glorp licence today is LGPL, but in the way to be MIT :). > > So, if you want to download and try it, evaluate in a workspace, in Pharo > 1.2 and 1.3, > > Gofer it > squeaksource: 'DBXTalk'; > package: 'ConfigurationOfGlorpDBX'; > load. > > (ConfigurationOfGlorpDBX project version: #stable) load > > And start playing! > > I think I'll become the new port mantainer, so feedback, bug reports and > everything else is appreciated. > > BTW, documentation and some new tools are on the way too. > > > Guille :) > > > _______________________________________________ > SqueakDBX mailing list > SqueakDBX(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/squeakdbx > >

June 11, 2011

Re: [Pharo-project] [Pharo-users] Pharo on Fedora 15_64

by Mariano Martinez Peck

On Sat, Jun 11, 2011 at 10:13 PM, <bblochl(a)arcor.de> wrote: > I actually installed Fedora 15 with GNOME 3 on a AMD-64 a couple of days > back and tried to run Pharo, latest stable version and ran into some > problem: > > [bb@localhost Pharo-1.2.1-CogOneClick.app]$ ./Pharo.sh > ./Pharo.sh: > /home/bb/Pharo/Pharo-1.2.1-CogOneClick.app/Contents/Linux/squeakvm: > /lib/ld-linux.so.2: bad ELF interpreter: Datei oder Verzeichnis nicht > gefunden > ./Pharo.sh: Zeile 16: > /home/bb/Pharo/Pharo-1.2.1-CogOneClick.app/Contents/Linux/squeakvm: Erfolg > [bb@localhost Pharo-1.2.1-CogOneClick.app]$ ldd `which ls` > alias: > ldd: ./alias: Datei oder Verzeichnis nicht gefunden > ls='ls: > ldd: ./ls='ls: Datei oder Verzeichnis nicht gefunden > --color=auto': > ldd: ./--color=auto': Datei oder Verzeichnis nicht gefunden > /bin/ls: > linux-vdso.so.1 => (0x00007fffc7bc8000) > libselinux.so.1 => /lib64/libselinux.so.1 (0x0000003761400000) > librt.so.1 => /lib64/librt.so.1 (0x00007f5c7914b000) > libcap.so.2 => /lib64/libcap.so.2 (0x0000003764400000) > libacl.so.1 => /lib64/libacl.so.1 (0x000000376e800000) > libc.so.6 => /lib64/libc.so.6 (0x00007f5c78db1000) > libdl.so.2 => /lib64/libdl.so.2 (0x00007f5c78bac000) > /lib64/ld-linux-x86-64.so.2 (0x00007f5c79367000) > libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f5c78991000) > libattr.so.1 => /lib64/libattr.so.1 (0x000000376a800000) > [bb@localhost Pharo-1.2.1-CogOneClick.app]$ readelf -l a.out > bash: readelf: command not found... > [bb@localhost Pharo-1.2.1-CogOneClick.app]$ > > What to do now?? > > Regards > > B. Blochl > > -- Mariano http://marianopeck.wordpress.com

June 11, 2011

Re: [Pharo-project] PharoKernel 13258

by StÃ©phane Ducasse

On Jun 11, 2011, at 1:30 PM, Pavel Krivanek wrote: > No, that is not the main problem. The image has some redrawing > problems and hangs easily but it is important that we have working > image with all PharoCore images loaded (build.sh -loadCore) but > without initialization (build.sh -initCore) so the Morphic > initialization can be tested and improved easily and fastly. Ok let us know how we can help. STef > > -- Pavel > > On Fri, Jun 10, 2011 at 9:51 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> because of the missing initialize? >> I'm integrating them now. >> >> Stef >> On Jun 10, 2011, at 9:26 PM, Pavel Krivanek wrote: >> >>> Hi, >>> >>> I generated new PharoKernel images: >>> https://gforge.inria.fr/frs/download.php/28639/PharoKernel-1.3-13258.zip >>> >>> Gofer is working again and whole PharoCore is loadable too (although >>> the resultant image is almost unusable). >>> >>> Cheers, >>> -- Pavel >>> >> >> >> >

June 11, 2011

Re: [Pharo-project] PharoKernel 13258

by Pavel Krivanek

No, that is not the main problem. The image has some redrawing problems and hangs easily but it is important that we have working image with all PharoCore images loaded (build.sh -loadCore) but without initialization (build.sh -initCore) so the Morphic initialization can be tested and improved easily and fastly. -- Pavel On Fri, Jun 10, 2011 at 9:51 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > because of the missing initialize? > I'm integrating them now. > > Stef > On Jun 10, 2011, at 9:26 PM, Pavel Krivanek wrote: > >> Hi, >> >> I generated new PharoKernel images: >> https://gforge.inria.fr/frs/download.php/28639/PharoKernel-1.3-13258.zip >> >> Gofer is working again and whole PharoCore is loadable too (although >> the resultant image is almost unusable). >> >> Cheers, >> -- Pavel >> > > >

June 11, 2011

[Pharo-project] [update 1.3] #13260

by Marcus Denker

13260 ----- Issue 4377: Deprecate UrlArgumentList http://code.google.com/p/pharo/issues/detail?id=4377 Issue 4388: unload ToolBuilder on #cleanUpForProduction http://code.google.com/p/pharo/issues/detail?id=4388 Issue 4385: Fix for activate/passivate for (currently) non-visible tabs. http://code.google.com/p/pharo/issues/detail?id=4385 Issue 4386: Fix for tab group page contents jumping around slightly. http://code.google.com/p/pharo/issues/detail?id=4386 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 11, 2011