- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Porting Visual Works to Pharo

by Janko MivÅ¡ek

Hi Guillermo, When I sync differences of Aida from VisualWorks to Pharo, I do this way: Preparation: - parcel FileOut30 loaded - Settings->Source Default fileout type: VW3.0 compatible source code (NOT Squeak!) Procedure: - VW: From Store version browser: Fileout differences to file MyPackage-diffs.st - Pharo: in File browser find above file and click button Code - manually sync differences or open new class definitions - manually delete removed methods - fileIn categories or individual changed methods This is syncing differences, but porting a whole package is similar, just fileout a while package instead of differences. Not completely automatic as you see, but with a bit of patience doable in not too long amount of time. Best regards Janko On 18. 03. 2011 03:30, Guillermo Polito wrote: > Maybe this question is out of the scope of this list, but probably > someone can help :). > As described in some threads, I want to use what's described in: > http://scg.unibe.ch/wiki/howtos/portingfromvisualworkstosqueak > > But when I try to load FileOut30 It doesn't load the Squeak > Compatibility classes because it seems I lack the refactoring browser. > I've already tried to load some Refactoring Browser from different > stores, but it screws my image :). > > I'm using the community edition of Visual works in windowze. > > Can someone point me in the right direction? (Let's say I'm not very > used to VisualWorks) > > Thanks! > Guille -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

March 18, 2011

Re: [Pharo-project] [Vm-dev] Running tests for auto-built Cog VMs

by Mariano Martinez Peck

On Fri, Mar 18, 2011 at 2:26 AM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > > > > On Thu, Mar 17, 2011 at 6:21 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> >> On 18 March 2011 01:30, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> > >> > >> > >> > On Thu, Mar 17, 2011 at 10:29 AM, Igor Stasenko <siguctua(a)gmail.com> >> wrote: >> >> >> >> Hello all. >> >> >> >> Our next plan is to extend the Hudson build jobs with tests which are >> >> run after VM has built. >> >> >> >> I'd like to ask, what kind of tests we should run for VMs. >> >> >> >> So, here's my questions: >> >> >> >> - do we need a VM specific tests? Or we just use ordinal tests which >> >> are in image(s) by default? >> > >> > SOme of the standard tests in the Squeak 4.2 suite are specifically for >> VM stuff. The entire suite depends on the VM in some way. It seems >> straight-forward to include tests for specific pieces of functionality, for >> example the mirror primitives, cannotInterpret: and objects-as-methods. >> Adding tests that test new VM functionality is clearly more than a good >> idea; it should be de rigueur. >> > >> >> >> >> - in case if we need to run VM-specific tests, is they are available >> >> somewhere or not? do we need to create separate package/repository for >> >> holding them? >> > >> > Check out a 4.2 image and look at the tests. The organization might not >> be perfect but it's there. >> > >> >> You mean non-VM-specific tests, just those which lying in image(s)? >> >> Yes, that's the first thing which comes into mind. And sure thing for >> start it is ok. >> >> For example, Hudson runs tests for PharoCore1.3 image, each time new >> update there. >> https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3/ >> >> It is easy to tweak this config and run it using freshly built VM(s), >> one per each platform * JIT/Stack/MT configs. >> >> But i wonder if we may need to be more focused and create some package(s) >> to group tests around VM or its individual plugins. >> > > Have you looked, as I suggested, in a Squeak 4.2 image? You'll find > Tests-VM, Tests-Finalization, Tests-ObjectsAsMethods > >> >> So maybe we should integrate them in Pharo too ? > >> >> >> >> >> i'd like to brainstorm that a bit. And then we will do that. >> >> >> >> >> >> -- >> >> Best regards, >> >> Igor Stasenko AKA sig. >> > >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > >

March 18, 2011

Re: [Pharo-project] Pharo in San Martin University

by Richard Durr

Cool :) On Fri, Mar 18, 2011 at 4:18 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > Sorry, I forget to answer this. > > The university link is: http://www.unsam.edu.ar/ > > Btw, the "professor in charge of the course" (I don't know what's the name > in english) is NicolÃ¡s Passerini, and also Javier Fernandez is giving the > lectures with us. > > Cheers, > Esteban > > > El 16/03/2011, a las 1:58p.m., StÃ©phane Ducasse escribiÃ³: > > Great! > do you have a link for the pharo web site? > Stef > > > Hi, > > I want to announce that yesterday I started teaching Pharo at University > San Martin, so this university is now a proud member of the growing list of > universities using this great environment for teaching purposes. One > interesting thing is that we are going to explore some not-so-commonly > taught capabilities, like Traits and the reflection api :) > > > Cheers, > > Esteban > > > > >

March 18, 2011

Re: [Pharo-project] Porting Visual Works to Pharo

by Mariano Martinez Peck

Guille, I cc'ed vw mailing list. Cheers Mariano On Fri, Mar 18, 2011 at 3:30 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Maybe this question is out of the scope of this list, but probably someone > can help :). > As described in some threads, I want to use what's described in: > http://scg.unibe.ch/wiki/howtos/portingfromvisualworkstosqueak > > But when I try to load FileOut30 It doesn't load the Squeak Compatibility > classes because it seems I lack the refactoring browser. I've already tried > to load some Refactoring Browser from different stores, but it screws my > image :). > > I'm using the community edition of Visual works in windowze. > > Can someone point me in the right direction? (Let's say I'm not very used > to VisualWorks) > > Thanks! > Guille >

March 18, 2011

[Pharo-project] [update 1.3] #13094

by StÃ©phane Ducasse

13094 ----- - Issue 3792: PluggableListMorph with a wrapper for display. Thanks Benjamin van Ryseghem. S.

March 18, 2011

Re: [Pharo-project] Issue 3792 in pharo: PluggableListMorph with a wrapper for display

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3792 by stephane...(a)gmail.com: PluggableListMorph with a wrapper for display http://code.google.com/p/pharo/issues/detail?id=3792 in 13094

March 18, 2011

Re: [Pharo-project] [ANN 1.2] prebuilt core 1.2 final

by StÃ©phane Ducasse

lukas Can you tell us where? What method is doing a problem? The point of simpleMorphic is that there is a value in it and if we do not give a chance to people to have a look at it then the money spent by esug is lost (of course esug was not paying for simpleMorphic but this is like that). Stef On Mar 18, 2011, at 7:07 AM, Lukas Renggli wrote: > Ahh, looks like SimpleMorphic has some (probably unintentional) > overrides of core methods. Unloading the package pretty much breaks > everything :-( > > Lukas > > On 18 March 2011 07:02, Lukas Renggli <renggli(a)gmail.com> wrote: >>> Very good! We then can release the 1.2 Full soon, too. >>> I wonder if we should adopt your OB codebase for that? Or do >>> we wait for 1.2.1? >> >> I would wait a bit. I noticed that the debugger is quite broken. I >> only get the pre-debug window, but clicking on any button opens >> another pre-debug window. I don't have time to investigate, is this >> also in core or some side-effect of loading/unloading packages? The >> method #topView seems to be missing. >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch >

March 18, 2011

Re: [Pharo-project] Porting Visual Works to Pharo

by Schwab,Wilhelm K

I have used SIF to move a lot of code from Dolphin to Pharo. Attached is the most recent version I have seen. In some cases, I heavily edited the .sif (text) after export and before import. Be sure to make backups and go for it. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Guillermo Polito [guillermopolito(a)gmail.com] Sent: Thursday, March 17, 2011 10:30 PM To: Pharo Development Subject: [Pharo-project] Porting Visual Works to Pharo Maybe this question is out of the scope of this list, but probably someone can help :). As described in some threads, I want to use what's described in: http://scg.unibe.ch/wiki/howtos/portingfromvisualworkstosqueak But when I try to load FileOut30 It doesn't load the Squeak Compatibility classes because it seems I lack the refactoring browser. I've already tried to load some Refactoring Browser from different stores, but it screws my image :). I'm using the community edition of Visual works in windowze. Can someone point me in the right direction? (Let's say I'm not very used to VisualWorks) Thanks! Guille

March 18, 2011

Re: [Pharo-project] [ANN 1.2] prebuilt core 1.2 final

by StÃ©phane Ducasse

Lukas Marcus is RIGHT. How can we make progress without adding temporarily new libraries and migrating? How can we make progress if people do not use the release candidate phase as it should be? Tell me because we are all ears opened. Stef >> I would not unload packaged. >> >> Everything not tested is broken, and so if you do things like that I am >> sure you will have problems. >> >> And nobody ever unloaded anything from Core. > > You must be joking right? In the mission you say "stable and small > core", but the numbers say something entirely different: PharoCore 1.0 > is 11 MB, PharoCore 1.1 is 14 MB, PharoCore 1.2 is 16 MB. I mentioned > it before in this list, but I already had to unload stuff in PharoCore > 1.1. Honestly, I don't really see the point of a PharoCore image if it > contains more and more not unloadable non-core code. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

March 18, 2011

Re: [Pharo-project] [ANN 1.2] prebuilt core 1.2 final

by StÃ©phane Ducasse

+1 > > I would not unload packaged. >>> >>> Everything not tested is broken, and so if you do things like that I am >>> sure you will have problems. >>> >>> And nobody ever unloaded anything from Core. >> >> You must be joking right? In the mission you say "stable and small >> core", but the numbers say something entirely different: PharoCore 1.0 >> is 11 MB, PharoCore 1.1 is 14 MB, PharoCore 1.2 is 16 MB. I mentioned >> it before in this list, but I already had to unload stuff in PharoCore >> 1.1. Honestly, I don't really see the point of a PharoCore image if it >> contains more and more not unloadable non-core code. >> > Size of the image comes in part from ever growing MC history. The only > other big thing should be the Minimal Morphic code, which is in there > temporarily. > > Else: People are welcome to help. > > We do what we do and then we do a release even if it is imperfect. > Perfection is death, and delaying the release forever "because we could do better" > will not mean that we do better, just that we don't release ever. > > Pharo 1.2 is *not* a goal in itself. It is just a snapshot on the way to a goal. Therefore > it's just a mess that is tested for some month so it does not have any obvious bugs. > Nothing else. > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

March 18, 2011