- Pharo-dev - lists.pharo.org

Re: [Pharo-project] who is using softSqueak and standard Squeak

by StÃ©phane Ducasse

well UI is really important. We think about the clients of Moose for example. And when I see the video of NullPointer they look sexy Stef > Anyone who is going to touch my beloved standard squeak will be killed!!! > > Just kidding, but I still use it. > However, IMO don't invest time in rewriting the UI for the 10th time! > There is plenty of other things which are more important to get the language up to date. > > (^o^) > camillo > > On 2011-03-28, at 21:56, StÃ©phane Ducasse wrote: > >> May be you should give a try to package them separately. >> Else I will give a try because to me they look a bit outdated. >> >> Stef >> >> On Mar 27, 2011, at 11:15 PM, Stuart Herring wrote: >> >>> I definitely use them - I like being able to locate the windows >>> instantly by colour. And a less practical reason is that the grey >>> default themes always make me feel depressed. Programming shouldn't >>> be grey and boring, it should be fun ;) >>> >>> A new, supported colourised theme would be a wonderful thing - >>> particularly if there were settings to choose the colour scheme. >>> I like the coloured windows so much that I've been tempted to go back >>> to Squeak - right up until the overloaded world menu reminds me why I >>> prefer Pharo. >>> >>> Regards, >>> Stuart >>> >>> On Sat, Mar 26, 2011 at 7:40 PM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>> Hi guys >>>> >>>> just out of curiosity who is using SoftSqueak and Standard Squeak theme? >>>> I know that lukas like colored windows now may be specific new style with this behavior could be done? >>>> >>>> Stef >>>> >>> >> >> > >

March 28, 2011

Re: [Pharo-project] who is using softSqueak and standard Squeak

by Camillo Bruni

Anyone who is going to touch my beloved standard squeak will be killed!!! Just kidding, but I still use it. However, IMO don't invest time in rewriting the UI for the 10th time! There is plenty of other things which are more important to get the language up to date. (^o^) camillo On 2011-03-28, at 21:56, StÃ©phane Ducasse wrote: > May be you should give a try to package them separately. > Else I will give a try because to me they look a bit outdated. > > Stef > > On Mar 27, 2011, at 11:15 PM, Stuart Herring wrote: > >> I definitely use them - I like being able to locate the windows >> instantly by colour. And a less practical reason is that the grey >> default themes always make me feel depressed. Programming shouldn't >> be grey and boring, it should be fun ;) >> >> A new, supported colourised theme would be a wonderful thing - >> particularly if there were settings to choose the colour scheme. >> I like the coloured windows so much that I've been tempted to go back >> to Squeak - right up until the overloaded world menu reminds me why I >> prefer Pharo. >> >> Regards, >> Stuart >> >> On Sat, Mar 26, 2011 at 7:40 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> Hi guys >>> >>> just out of curiosity who is using SoftSqueak and Standard Squeak theme? >>> I know that lukas like colored windows now may be specific new style with this behavior could be done? >>> >>> Stef >>> >> > >

March 28, 2011

Re: [Pharo-project] String asUppercase/asLowercase

by Nicolas Cellier

http://code.google.com/p/pharo/issues/detail?id=2703 Try squeak multilingual experimentations, I'm interested to ear if it would work for you (I'm unfortunately latin and need testing feedback from non latin users). Nicolas 2011/3/28 Denis Kudriashov <dionisiydk(a)gmail.com>: > Hello. > > asUppercase/asLowercase not work for non english strings (russian strings). > > Is it bug? > How it can be implemeted? >

March 28, 2011

Re: [Pharo-project] Opal decompiler: I've been a big good ... I've been a bit bad ...

by Nicolas Cellier

2011/3/28 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> >>> >>> (Unless, of course you simply raise an error during (re)compilation >>> when given ivar removed from class). >> That's the plan yes. Niko is working on that part now. I guess for now we might keep it on Eliot's proposal of just transforming to an undefined field access; but we'll see. >> One of the ideas is of course to collect the methods that get affected by a change and report back to the user; just like with all other types of errors that can occur during class modification. We have a pretty cool model already so it's becoming increasingly easy to install such hooks. I hate self error: 'your class is invalid because of something somewhere', and we'll get that all fixed! > > I would love to have real object that contains compilation error (instead of Transcript show:) so that we can build tool to fix them :) > Various errors can occur at different stages, hence be generated from different classes in current (old) Compiler: - errors at parsing (syntax errors) - errors at name resolving (shadowing, undeclared ...) - errors at code generation (byte code limits ...) Several alternatives APi are possible for handling these errors: - Compiler signal all warning/errors by raising Exceptions, Compiler invocations are wrapped with a handler - Compiler signal all warnings/errors by sending a message to a reified errorHandler inst. var. The errorHandler can be instanciated with different classes for interactive / non interactive The errorHandler knows itself how to interact with user thru TextEditor, menus, or transcript... There is already a mixture of these strategies in current (old) Compiler. Except that compiler talks directly to a requestor and tries to handle interaction by itself if interactive. IMHO, it's better to write all your requirements before thinking of an architecture. Nicolas

March 28, 2011

[Pharo-project] Issue 3899 in pharo: clean up #maybeDuplicateMorph:

by pharo＠googlecode.com

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3899 by marcus.d...(a)gmail.com: clean up #maybeDuplicateMorph: http://code.google.com/p/pharo/issues/detail?id=3899 clean up #maybeDuplicateMorph: Plus some random small cleanups of dead code Attachments: MoreCleans.1.cs 4.2 KB

March 28, 2011

Re: [Pharo-project] Issue 3898 in pharo: Remove some dead code from PasteUpMorph

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #1 on issue 3898 by marcus.d...(a)gmail.com: Remove some dead code from PasteUpMorph http://code.google.com/p/pharo/issues/detail?id=3898 (No comment was entered for this change.)

March 28, 2011

[Pharo-project] Issue 3898 in pharo: Remove some dead code from PasteUpMorph

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3898 by marcus.d...(a)gmail.com: Remove some dead code from PasteUpMorph http://code.google.com/p/pharo/issues/detail?id=3898 PasteUpMorph removeSelector: #automaticPhraseExpansion! PasteUpMorph removeSelector: #backgroundForm! PasteUpMorph removeSelector: #backgroundSketch! PasteUpMorph removeSelector: #checkCurrentHandForObjectToPaste2! PasteUpMorph removeSelector: #deleteBackgroundPainting! PasteUpMorph removeSelector: #displayWorldNonIncrementally! PasteUpMorph removeSelector: #optimumExtentFromAuthor! PasteUpMorph removeSelector: #prepareToPaint:! PasteUpMorph removeSelector: #saveOnFile! Attachments: RandomDeadCode.1.cs 571 bytes

March 28, 2011

[Pharo-project] String asUppercase/asLowercase

by Denis Kudriashov

Hello. asUppercase/asLowercase not work for non english strings (russian strings). Is it bug? How it can be implemeted?

March 28, 2011

Re: [Pharo-project] Issue 3779 in pharo: isUnicodeStringWithCJK returns false on a string containing Kanji

by pharo＠googlecode.com

Updates: Status: FixProposed Labels: Milestone-1.3 Comment #2 on issue 3779 by marcus.d...(a)gmail.com: isUnicodeStringWithCJK returns false on a string containing Kanji http://code.google.com/p/pharo/issues/detail?id=3779 fix attached Attachments: Fix.1.cs 2.6 KB

March 28, 2011

[Pharo-project] [update 1.3] #13115

by Marcus Denker

13115 ----- Issue 3893: PluggableListMorphOfMany better implementation of autoDeselect: Issue 3884: Cleaning st80 Paragraph Issue 3887: Clean Project more Issue 3681: [Failing Test] Tests.Release.ReleaseTest.testObsoleteClasses -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 28, 2011