January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Error when i try save a image [WAS] Fwd: [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by nullPointer

Thanks, that patch works for me :) Regards Mariano Martinez Peck wrote: > > The problem is that when you save the image, in the shutDown list, there > is > freetype and it tries to finish all the handlers. The problem in this case > is that one of those handlers that seems to be trying to finish has > something in nil or some bad parameter which of course, gives a primitive > mail. That's all my idea, maybe I am wrong as it is the first time I look > in > this code. > > As a work arround, you can install the StrikeFOnts instead of TrueTypes. > It > is not > the real solution, but works. Just take the dev image with trutype and > evaluate: > > FreeTypeCache clearCurrent. > StrikeFont installDejaVu. > > > Cheers > > On Mon, Jan 11, 2010 at 5:30 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> I could reproduce the problem. epicfan which OS are you using ? VM >> version >> ? >> >> >> On Mon, Jan 11, 2010 at 5:18 PM, Mariano Martinez Peck < >> marianopeck(a)gmail.com> wrote: >> >>> yes, actually that's was the mail about. >>> >>> >>> >>> On Mon, Jan 11, 2010 at 5:11 PM, StÃ©phane Ducasse < >>> stephane.ducasse(a)inria.fr> wrote: >>> >>>> Do Yyou still have the problem with the latest rc version? >>>> >>>> Stef >>>> On Jan 11, 2010, at 5:02 PM, Mariano Martinez Peck wrote: >>>> >>>> > Sorry epicfan I have no idea at all. I cc Pharo mailing list that >>>> maybe >>>> someone can help you. >>>> > >>>> > I was going to cc nullPointer, but I discover it is you!!! hahahahah >>>> > >>>> > >>>> > ---------- Forwarded message ---------- >>>> > From: <epicfan(a)gmail.com> >>>> > Date: Mon, Jan 11, 2010 at 4:46 PM >>>> > Subject: Re: [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1 >>>> > To: marianopeck(a)gmail.com >>>> > >>>> > >>>> > The next error: >>>> > >>>> > >>>> http://code.google.com/p/pharo/issues/detail?id=1283&can=7&q=bug%20when%20t… >>>> > >>>> > In the last version of developer image that error was fix it. But in >>>> that 10505 image returns :| >>>> > >>>> > Regards. >>>> > >>>> > >>>> > >>>> > >>>> > PD. Could I do something in my code for delete that problem? >>>> > >>>> > Regards again. >>>> > >>>> > _______________________________________________ >>>> > Pharo-project mailing list >>>> > Pharo-project(a)lists.gforge.inria.fr >>>> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- View this message in context: http://n2.nabble.com/Error-when-i-try-save-a-image-WAS-Fwd-BetaTesting-ANN-… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 12, 2010

Re: [Pharo-project] Pharo core and Seaside 3.0

by Schwab,Wilhelm K

With stipulation of the fact that helper methods can be taken too far, what is wrong with something like Gofer loadSeaside28? Answer: nothing if it hides the details of using the configuration. The problem with the FFI, Seaside, etc. load methods is not that they exist, it is that they use obsolete techniques and/or are broken. One question in my mind is how to replace ScriptLoader class>>loadLatestPackage:fromRepository:. Will Gofer new add:packageName; repository:aRepository; load take care of that? Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Tuesday, January 12, 2010 1:36 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Pharo core and Seaside 3.0 On Jan 12, 2010, at 7:25 PM, Lukas Renggli wrote: >> And also the class side install methods of Gofer please. >> >> Lets clean the way for Gofer as downloader/installer, Metacello as >> package management tools. > > These are examples to demonstrate how gofer works. They are not > supposed to be called for loading stuff. > > I am just using them all the time to keep my images up to date :-) :) well this was the same for scriptLoader :) I will pay attention to scriptLoader Stef > > Lukas > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 12, 2010

Re: [Pharo-project] Pharo core and Seaside 3.0

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/detail?id=1791 :) On Jan 12, 2010, at 7:34 PM, Miguel Enrique CobÃ¡ Martinez wrote: > El mar, 12-01-2010 a las 19:25 +0100, Lukas Renggli escribiÃ³: >>> And also the class side install methods of Gofer please. >>> >>> Lets clean the way for Gofer as downloader/installer, Metacello as >>> package management tools. >> >> These are examples to demonstrate how gofer works. They are not >> supposed to be called for loading stuff. >> >> I am just using them all the time to keep my images up to date :-) > > But for some users they are causing confusion, given the current soup of > install tools. > If you don't mind, I really delete them or at least put a big advise in > the comment to not use them because any momento will be outdated and > maybe linking to the metacello instructions. You can always keep use > them if you know they are correct for you. > > What do you think? > >> >> Lukas >> >> > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 12, 2010

Re: [Pharo-project] clone vs shallowCopy

by Stan Shepherd

StÃ©phane Ducasse wrote: > > http://code.google.com/p/pharo/issues/list?thanks=1789 > > I do not understand why we need deepCopy and why deepCopy does not > implement the veryDeepCopy semantics? > > On Jan 12, 2010, at 1:41 PM, Levente Uzonyi wrote: > >>> - #copy is the normal copy operation. It should be used by default and >>> never overridden. It calls #postCopy that can be overridden to have >>> class specific copy semantics. >>> >>> - #shallowCopy does a shallow copy. It should never be overridden and >>> only be used if you want to get these very specific semantics. >>> >>> - #deepCopy does a deep copy. It should never be overridden and only >>> be used if you want to get these very specific semantics. >> >> It doesn't handle cycles, #veryDeepCopy does. >> > > > see discussion for http://code.google.com/p/pharo/issues/detail?id=521. The behaviors are different. So #deepCopy perhaps should go, but it is not safe to assume that #deepCopy can just be replaced with #veryDeepCopy Stan -- View this message in context: http://n2.nabble.com/clone-vs-shallowCopy-tp4290815p4293752.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 12, 2010

Re: [Pharo-project] clone vs shallowCopy

by Igor Stasenko

I think that #clone comes from Self or other prototype-based things. I prefer to use it instead of #shallowCopy, because as to me its more concise and more precise term for such operation - creating a 'bit-identical' copy of object. 2010/1/12 Lukas Renggli <renggli(a)gmail.com>: >> where do you see that it is morphic related for me clone is only implemented >> on character, Boolean, Object, SMalltInt symbol, UndefinedObject > > I am wrong. Forget what I said about #clone. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Jan. 12, 2010

Re: [Pharo-project] [update 1.1] #11153

by Henrik Johansen

I think you missed the "StrikeFont installDejaVu", which is necessary to reinstall BitMap DejaVu with correct derived fonts. At least for me, setting code font to italic, then opening a system browser on a method still looks bad Cheers, Henry On Jan 12, 2010, at 5:34 03PM, Marcus Denker wrote: > 11153 > ----- > > Issue 268: TODO: CurvierMorph should be merged with PolygonMorph > Issue 1141: Monticello directory selection window is non-resizable and very small > Issue 1770: Kernel-Tests-ClassBuilder category is not remove after ClassBuilderFormatTests tests are run > Issue 1774: Monticello repository edit works but doesnt update UI > Issue 1780: StrikeFont issues with derived fonts > Issue 1782: Save Dialog too small > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 12, 2010

Re: [Pharo-project] [Feature Request] Better integration with OSX Window Management

by Stefan Marr

Hi: On 12 Jan 2010, at 19:09, John Toohey wrote: > In cases like this, I have used http://www.heliumfoot.com/mercurymover/ to recover windows that are positioned off the current screen. Use the task selector to get the focus on the app, and then the arrow keys to move it back to your laptop. Thanks for the tip, was looking for something like that. Anyway. I just tried the new Mac VM 5.3b1 of John M. McIntosh and that one works nicely. So, I guess, it is a VM issue. Best Stefan > > > On Mon, Jan 11, 2010 at 07:34, Stefan Marr <pharo(a)stefan-marr.de> wrote: > Hello: > > I just had a very annoying experience with the lake of sufficient window management tools on Mac OS X. (Annoying enough to write this mail...) > > > The following happened: > > At home I have a external screen attached to my mac book, it is configured to be a secondary screen positioned above the main (internal) screen. > > The Pharo window was moved to that screen. > > In the office, I have another configuration, and there was no way to get hold of the Pharo window anymore. > > It remembered its positioning and was just of screen. Expose allows me to see it, and shows even a beautiful animation moving it out of reach after clicking on it. > > Obviously the menu SqueakVM > Quit is not really helpful, since the question whether to save or not is displayed unreachable off screen, too. > > > > I am not sure whether the standard OS X window menu functionality with "minimize" and "zoom" would help here, but might be a start. On the other hand, I would guess, that the OSX windowing systems sends some events which could be handled like all other windows do. > > > The only workaround for the moment, is to have a external screen and fiddle with the screen configuration and positioning until I can get hold of the window... Not exactly convenient. > > > Best regards > Stefan > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 3956 > Fax: +32 2 629 3525 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > -JT > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525

Jan. 12, 2010

Re: [Pharo-project] NewCompiler load on PharoCore

by Miguel Enrique CobÃ¡ Martinez

El mar, 12-01-2010 a las 19:36 +0100, Lukas Renggli escribiÃ³: > > Has NewCompiler teste on PharoCore? > > Jorge is working on it. It does not work on Pharo yet. Ok, thanks, for the moment will omit the WriteBarrier on NewCompiler in the Metacello configuration for Magma. Thanks > > Lukas > -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Jan. 12, 2010

Re: [Pharo-project] NewCompiler load on PharoCore

by Lukas Renggli

> Has NewCompiler teste on PharoCore? Jorge is working on it. It does not work on Pharo yet. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 12, 2010

Re: [Pharo-project] Pharo core and Seaside 3.0

by StÃ©phane Ducasse

On Jan 12, 2010, at 7:25 PM, Lukas Renggli wrote: >> And also the class side install methods of Gofer please. >> >> Lets clean the way for Gofer as downloader/installer, Metacello as >> package management tools. > > These are examples to demonstrate how gofer works. They are not > supposed to be called for loading stuff. > > I am just using them all the time to keep my images up to date :-) :) well this was the same for scriptLoader :) I will pay attention to scriptLoader Stef > > Lukas > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 12, 2010