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

[Pharo-project] [update 1.2] #12255

by Marcus Denker

12255 ----- Issue 3324: Closing find dialog does not reinstate top window Issue 3318: DropList positioning to fit display Issue 3292: SourceReference>>parseTimestampFrom: chokes on tk 2/18/97 Issue 3293: UITheme examples broken Issue 3181: PharoCorePackageDependenciesTests failure and error -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Nov. 25, 2010

Re: [Pharo-project] Issue 3318 in pharo: DropList positioning to fit display

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3318 by marcus.denker: DropList positioning to fit display http://code.google.com/p/pharo/issues/detail?id=3318 12255

Nov. 25, 2010

Re: [Pharo-project] Issue 3292 in pharo: SourceReference>>parseTimestampFrom: chokes on 'tk 2/18/97'

by pharo＠googlecode.com

Updates: Status: Closed Comment #3 on issue 3292 by marcus.denker: SourceReference>>parseTimestampFrom: chokes on 'tk 2/18/97' http://code.google.com/p/pharo/issues/detail?id=3292 12255

Nov. 25, 2010

Re: [Pharo-project] Net::Telnet equivalent

by Chris Cunningham

Here is the code. -Chris

Nov. 25, 2010

Re: [Pharo-project] Issue 3325 in pharo: SourcedMethodReference bug due to parseTimestampFrom:

by pharo＠googlecode.com

Updates: Status: Closed Comment #3 on issue 3325 by marcus.denker: SourcedMethodReference bug due to parseTimestampFrom: http://code.google.com/p/pharo/issues/detail?id=3325 (No comment was entered for this change.)

Nov. 25, 2010

Re: [Pharo-project] RBScanner>>#initializeClassificationTable

by Levente Uzonyi

On Thu, 25 Nov 2010, Henrik Johansen wrote: > My bad, in the 4.1 image there's > Preferences >> allowUnderscoreAssignment > ^ self > valueOfFlag: #allowUnderscoreAssignment > ifAbsent: [false] > (Added by Parser class>>#initialize), I didn't check if it was actually in use anymore. > > Compatibility seems the be the reason anyways though, as you said the Scanner pragma preference has a different name. I doubt there was any effort to write compatible code, there are countless packages that were originally written in Squeak, but now they are incompatble with it. In Squeak the pragma preference in Scanner was renamed recently to allowUnderscoreAsAssignment to resolve the incompatibility. > > > On Nov 25, 2010, at 11:42 56AM, Levente Uzonyi wrote: > >> On Thu, 25 Nov 2010, Henrik Johansen wrote: >> >>> P.S. At the very least it could be changed to Scanner isLiteralSymbol: #_ >> >> I guess not. There was a bug in Squeak (and probably Pharo too), because the compiler replaced #_ to #':=' during compilation. See http://bugs.squeak.org/view.php?id=7571 . > > :( > Can't reproduce it in Pharo 1.0 onwards, with allowUnderscore on/off, though. That's fair, because you can't use underscores in selectors in Pharo. Levente > > Cheers, > Henry

Nov. 25, 2010

Re: [Pharo-project] Issue 3325 in pharo: SourcedMethodReference bug due to parseTimestampFrom:

by pharo＠googlecode.com

Comment #2 on issue 3325 by Benjamin.VanRyseghem.Pharo: SourcedMethodReference bug due to parseTimestampFrom: http://code.google.com/p/pharo/issues/detail?id=3325 Ok, fix proposed in the entry 3292 :)

Nov. 25, 2010

Re: [Pharo-project] Printing an array on file without quotes

by StÃ©phane Ducasse

Oscar There are only a few really really newbies questions. Then we like newbies and their questions because we learned all a lot from them. So this is not because we may talk about stuff that looks complex that - they are (often this is just that we do not have enough time to understand) - we know everything - we do not like to reply to simple questions - we do not like to learn from answer to simple questions. So keep asking questions and having fun with us. I hate those mailing-lists where people are asked to do their homework. :) Stef

Nov. 25, 2010

Re: [Pharo-project] Issue 3291 in pharo: Missing text field with completion

by StÃ©phane Ducasse

lukas could you publish CompletionRequest somewhere in a place like a bug entry so that we integrate it :) Stef > Le 25/11/2010 12:03, Lukas Renggli a Ã©crit : >>> So, its a basic widget which, afaik is missing and that could be used with >>> ob-tools. >> I don't follow what you and Francisco are saying. >> >> IMHO there is a much better widget already in OB. > sorry but why much better? > OBCompletionRequest is a dialog. > What I propose is to enrich PluggableTextFieldMorph > with the possibility to use a completion list. > So we have two differents things here. > And indeed, OBCompletionRequest should be named CompletionRequest > and integrated in the core. > Showing it in the browser find class was not a good idea... > Cheers > Alain > >> I suggest to make >> that a standard widget so that other tools outside of OB can take >> advantage too. >> >> It is simple subclass of DialogWindow morph from Polymorph and can be >> fully configured and opened for example like this: >> >> OBCompletionRequest new >> prompt: 'Find Class'; >> searchBlock: [ :string | self findClassIn: target environment >> pattern: string ]; >> labelBlock: [ :class | class name ]; >> iconBlock: [ :class | class browserIcon ]; >> signal >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> >> > >

Nov. 25, 2010

Re: [Pharo-project] Issue 3292 in pharo: SourceReference>>parseTimestampFrom: chokes on 'tk 2/18/97'

by pharo＠googlecode.com

Comment #2 on issue 3292 by Benjamin.VanRyseghem.Pharo: SourceReference>>parseTimestampFrom: chokes on 'tk 2/18/97' http://code.google.com/p/pharo/issues/detail?id=3292 It should fix the problem ^^ Attachments: VeronicasBugFix.1.cs 1.2 KB

Nov. 25, 2010