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

[Pharo-project] [update 1.4] #14257

by StÃ©phane Ducasse

14257 ----- - Issue 5095: Monticello snapshotting does lots of unnecessary screen updates. Thanks Lukas and Stef :) http://code.google.com/p/pharo/issues/detail?id=5095 - Issue 5083: remove unused methods from SmartRefStream. Thanks Marcus Denker. http://code.google.com/p/pharo/issues/detail?id=5083

Dec. 14, 2011

Re: [Pharo-project] Better Gofer error messages

by StÃ©phane Ducasse

open a bug entry and we will fix that :) You could even provide the code and it will be faster > >>> Please please, let someone improve Gofer error messages, which are now >>> totally non-understandable. Check in advance if some package is there >>> and say "No package with that name", or even better, "no package with >>> expected name: Blabla6.xxx" or something. > >> can you point which messages are a problem > > Say you evaluate this script: > > Gofer new > squeaksource: 'Fuel'; > package: 'ConfigurationOFuel'; > load. > (Smalltalk at: #ConfigurationOfFuel) load. > > Did you notice a typo in script? Hardly. Now see what exception look like: > > Error: Unable to resolve ConfigurationOFuel > > GoferPackageReference(Object)>>error: > GoferPackageReference(GoferReference)>>resolveWith: > [:each | each resolveWith: self] in Gofer>>resolved > Array(SequenceableCollection)>>collect: > Gofer>>resolved > ... > > My thinking: What is it unable to resolve, what is to be resolved > anyway? But if error will be something like: > > "Unable to find or resolve package ConfigurationOFuel, check > the name. See Gofer class comment for more" > > It will certainly lead me to check for the typo first and only if > failed, go to class comment and find a wiki page. > >>> What it is now is unusable, sorry. To prepare a right script is a big >>> pain. Specially because there are nowhere rules how packages are >>> resolved by a name. It will help if in exception at least a link to the >>> some wiki with rules would be shown. > >> why don't you use metacello? >> there 45 pages documentation on it > > Gofer is needed for Metacello too and yes, Metacello has similar > problems with not very helpful error messages. > > See how Fuel guys improve error reporting in recent Fuel, after having > the same cryptic messages before. > > Best regards > Janko > > > -- > Janko MivÅ¡ek > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si >

Dec. 14, 2011

Re: [Pharo-project] GUI Testing Library

by Sean P. DeNigris

Tudor Girba-2 wrote > > I think the best would be to add it externally from a configuration. So, I > created one: > Thanks! Of course if it's external no one will use it to test the image itself :( p.s. I added middle click and tests for all click types -- View this message in context: http://forum.world.st/GUI-Testing-Library-tp4097866p4196899.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 14, 2011

Re: [Pharo-project] 1.3, PBE and lab setups

by StÃ©phane Ducasse

Hi dave > I am trying to get our local admins to set up labs so students can use the latest Pharo. > > Currently we have 1.2 and PBE .image files and by removing the field in the INI file that specified the image, if you clicked on Pharo, you'd get a dialogue asking which image you wanted. All of these are on read-only mounts, so if you want to save to the image, you need to copy the image to your home directory and then you could navigate to that image file on startup. Dropping an image on the executable works fine, though. > > Additionally, the PBE book doesn't play well with 1.3 (things that the book says die when you try them). Apparently you can't open the PBE image from the 1.3 binary without it crashing, either. > > So I have 3 questions: > > 1) is 1.3 the system to use, or will 1.4 be stable soon? use 1.3 :) > 2) is the PBE book getting updated to work with a vanilla 1.3/1.4 image? No if nobody does it. We are focusing on PBE2 > 3) what is the timeline on these, as our semester starts Jan 10. :) I would love to see the exercises that you will ask them. > > Thanks ../Dave >

Dec. 14, 2011

Re: [Pharo-project] Better Gofer error messages

by Janko MivÅ¡ek

S, StÃ©phane Ducasse piÅ¡e: > On Dec 14, 2011, at 5:35 PM, Janko MivÅ¡ek wrote: >> Please please, let someone improve Gofer error messages, which are now >> totally non-understandable. Check in advance if some package is there >> and say "No package with that name", or even better, "no package with >> expected name: Blabla6.xxx" or something. > can you point which messages are a problem Say you evaluate this script: Gofer new squeaksource: 'Fuel'; package: 'ConfigurationOFuel'; load. (Smalltalk at: #ConfigurationOfFuel) load. Did you notice a typo in script? Hardly. Now see what exception look like: Error: Unable to resolve ConfigurationOFuel GoferPackageReference(Object)>>error: GoferPackageReference(GoferReference)>>resolveWith: [:each | each resolveWith: self] in Gofer>>resolved Array(SequenceableCollection)>>collect: Gofer>>resolved ... My thinking: What is it unable to resolve, what is to be resolved anyway? But if error will be something like: "Unable to find or resolve package ConfigurationOFuel, check the name. See Gofer class comment for more" It will certainly lead me to check for the typo first and only if failed, go to class comment and find a wiki page. >> What it is now is unusable, sorry. To prepare a right script is a big >> pain. Specially because there are nowhere rules how packages are >> resolved by a name. It will help if in exception at least a link to the >> some wiki with rules would be shown. > why don't you use metacello? > there 45 pages documentation on it Gofer is needed for Metacello too and yes, Metacello has similar problems with not very helpful error messages. See how Fuel guys improve error reporting in recent Fuel, after having the same cryptic messages before. Best regards Janko -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

Dec. 14, 2011

Re: [Pharo-project] Better Gofer error messages

by Janko MivÅ¡ek

S, Lukas Renggli piÅ¡e: >> What it is now is unusable, sorry. To prepare a right script is a big >> pain. Specially because there are nowhere rules how packages are >> resolved by a name. It will help if in exception at least a link to the >> some wiki with rules would be shown. > > I assume you didn't even bother to check the class comment of Gofer, > because if you did you would have found a verbatim copy of the wiki > article. Sure I didn't and hardly anyone will come to this idea when seeing this cryptic error. Of course if error message would lead me to class comment, things would be different. This error is frequent, so error message should be more descriptive, this is my point. Best regards Janko -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

Dec. 14, 2011

Re: [Pharo-project] How turn on Halo's?

by Sean P. DeNigris

Sean P. DeNigris wrote > > Does anyone know where the functionality lived? > Found it! Add the so-commented two lines below to restore two-way halo cycling. Am I the only one who misses this or should I add a setting? Morph>>handlerForBlueButtonDown: anEvent "Return the (prospective) handler for a mouse down event. The handler is temporarily installed and can be used for morphs further down the hierarchy to negotiate whether the inner or the outer morph should finally handle the event. Note: Halos handle blue button events themselves so we will only be asked if there is currently no halo on top of us." self wantsHaloFromClick ifFalse:[^nil]. "Add next two lines to restore two-way halo cycling" anEvent handler ifNil:[^self]. (anEvent handler isKindOf: PasteUpMorph) ifTrue:[^self]. (anEvent shiftPressed) ifFalse:[^nil] "let outer guy have it" ifTrue:[^self] "let me have it" -- View this message in context: http://forum.world.st/How-turn-on-Halo-s-tp2227309p4196786.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 14, 2011

Re: [Pharo-project] Startup Preferences

by Benjamin

On Dec 14, 2011, at 6:23 PM, Sean P. DeNigris wrote: > > Benjamin Van Ryseghem-2 wrote >> >> So it's really boring (and time consuming) to have to set my preferences >> to have a nice environment to work with all the time. >> > > I understand that and have the same problem, but solved it in the image with > code and Metacello. Mariano has a blog post about it at > http://marianopeck.wordpress.com/2011/11/19/loading-projects-and-building-y…. > In fact, the Metacello approach solves the next problem the script will run > into, which is that each version of Pharo is a different incompatible > platform, so there will have to be a different script for each 1.3, 1.4, > 102.16; or create tags, or a script language, or... But sometimes, we want different script for different version. Use case: integration. When Stef is integrating, paths for scripts are different, and so are repos. The Metacello approach is network dependent. When I download a new image from Jenkins, I do it through a script which save the latest version. So if Jenkins is down (or my internet connection), I can have a fresh image. Another thing is, I won't have to Gofer blabla, I am to lazy (and my memory is too bad for that ^^) ;) Moreover, I had no clue this solution was existing ;) I want it to work out of the box, without thinking (and I am damn good at that ^^) ;) Ben > > I am hesitant to add mechanisms outside the image because one of Smalltalk's > compelling strengths is its consistency (we don't even have mathematical > operator precedence, for ch*st sake :)) and this is one more thing to > learn/understand/remember esp. for newbies. Also, maybe this is how Java's > XML virus started ;-) > > -- > View this message in context: http://forum.world.st/Startup-Preferences-tp4129591p4196010.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Dec. 14, 2011

[Pharo-project] 1.3, PBE and lab setups

by Dave Mason

I am trying to get our local admins to set up labs so students can use the latest Pharo. Currently we have 1.2 and PBE .image files and by removing the field in the INI file that specified the image, if you clicked on Pharo, you'd get a dialogue asking which image you wanted. All of these are on read-only mounts, so if you want to save to the image, you need to copy the image to your home directory and then you could navigate to that image file on startup. Dropping an image on the executable works fine, though. Additionally, the PBE book doesn't play well with 1.3 (things that the book says die when you try them). Apparently you can't open the PBE image from the 1.3 binary without it crashing, either. So I have 3 questions: 1) is 1.3 the system to use, or will 1.4 be stable soon? 2) is the PBE book getting updated to work with a vanilla 1.3/1.4 image? 3) what is the timeline on these, as our semester starts Jan 10. Thanks ../Dave

Dec. 14, 2011

[Pharo-project] FFI is broken in Cog [WAS] Re: Pharo 1.3 vs 1.2.1 some results for ConfigurationOfODBC - success

by Mariano Martinez Peck

On Wed, Dec 14, 2011 at 5:10 PM, Ben Coman <btc(a)openinworld.com> wrote: > ** > > That works great. Thanks Mariano. Since I got the file direct from you I > have uploaded it to [2] in case it is of use to others. > > I see the file you provide is "Pharo-1.3-13307-OneClickWin.zip" has many > more dlls than the file of the same name from INRIA>Files [1]. Is this a > fix that can be added by a user to the released Pharo-1.3-13315, or > otherwise be flagged to go into a possible Pharo-1.3.1 ? > > I was exploring the load sequence and it was interesting to discover that > in a fresh image, after... > > Gofer new > > squeaksource: 'ODBC'; > > package: 'ConfigurationOfODBC'; load. > > (Smalltalk at: #ConfigurationOfODBC) load. > > ..."listLoadedModules" did not show odbc32. This only appeared after > executing... > > connection := ODBCConnection dsn: 'TestMDB' user: '' password: ''. > > That is cool seeing the dynamic nature of plugin loading. Now while you > will already be aware of the difference between your supplied file [2] and > the one from [1], for my own learning attempt it would seem from > "SmalltalkImage current listLoadedModules" that the difference is... > SqueakFFIPrims VMMaker-oscog.54 (e) working > versus > SqueakFFIPrims VMMaker-oscog-IgorStasenko.123 (e) not working. > ... and unfortunately there is no version information on odbc32. > Yes, the zip I provided you is a CogVM one click I did myself for windows because the default is not working. It was always a mess for me. I didn't even remember what I did to make it work. I think I took the SqueakFFI dll from an older Cog VM or from the one build by Jenkins or something like that. Until I make it work. But out of the box, the FFI is not working. Maybe it has been fixed. You can try the very last VM of Eliot (since there is no Jenkins for Windows yet) http://www.mirandabanda.org/files/Cog/VM/VM.r2522/cogwin.zip is it working? > > A side comment for whoever maintains ConfigurationOfODBC... I wonder if > this could be made to fail earlier - at the "(Smalltalk at: > #ConfigurationOfODBC) load" rather than waiting for the first attempt at a > connection. I think logically proving access to the external library > should be part of the package load. This would help isolate such issues for > users new to the package. I notice that after a SaveAndExit and restart, > the odbc plugin is no longer shown in "listLoadedModules" until dynamically > reloaded on next use of "ODBCconnection". This would remain the standard > behaviour after proving access to the library for the first time during the > package load. > +1 > > [1] https://gforge.inria.fr/frs/?group_id=1299&release_id=6364 > [2] > http://files.openinworld.com/Pharo-1.3-13307-OneClickWin-ODBC-thx-Mariano.z… > > cheers, Ben > > Mariano Martinez Peck wrote: > > > > On Tue, Dec 13, 2011 at 11:50 AM, Ben Coman <btc(a)openinworld.com> wrote: > >> Thanks, but nothing is attached. >> > > Sorry, here it is. > > >> Also, I'm not sure how to "make sure odbc libraries are findable by >> Windows." >> > > odbc.dll and friends should be in a place where Windows search dlls. I > think you won't have a problem since Windows usually puts such library in > its correct place. > > >> Nothing is changed in the environment between running 1.2.1 and 1.3. >> >> btw, I've been reading your blog on building the VM, and you indicated >> you would welcome feedback on english grammar. Here in one and a typo... >> http://marianopeck.wordpress.com/2011/04/ >> 1. "as you can image" >> "as you can imagine" >> 2. "wolrd" >> "world" >> >> > Thanks, I have just integrated them. > > >> cheers, Ben >> >> >> >> Mariano Martinez Peck wrote: >> >> Hi. Just as a test, would you like to test the attached VM? change xxx >> with zip. >> Just make sure odbc libraries are findable by Windows. >> >> Cheers >> >> On Sun, Dec 11, 2011 at 6:45 AM, Ben Coman <btc(a)openinworld.com> wrote: >> >>> Fadi Mansour wrote: >>> >>>> Hi, >>>> >>>> I'm having the same issue while trying to use ODBC with Pharo's OnClick >>>> image 1.3. >>>> >>>> Did you find anything about the issue here? >>>> >>>> Regards, >>>> >>>> Fadi >>>> >>>> >>>> >>>> >>>> >>>> >>> I've been offline while attending to a machine rebuild shutdown on a >>> mine site. I've only just got back today to start having a look at it >>> again. >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > > > -- Mariano http://marianopeck.wordpress.com

Dec. 14, 2011