- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Dealing with incompatibility (was: Re: MIMEdatabase fix?)

by StÃ©phane Ducasse

On Feb 24, 2009, at 9:21 PM, Michael Rueger wrote: > StÃ©phane Ducasse wrote: >> On Feb 24, 2009, at 7:35 PM, Michael Rueger wrote: >> >>> slightly shorter it is the fork in the road: >>> >>> are you committing to Pharo or Squeak? >> >> I did not get that? >> commited :)? to pharo? > > Well, yes :-) > Basically meaning we need to maintain packages explicitly for Pharo. Yes! >> For MIME I would like to hear if seasider have an alternative to KOM: >> is swazoo an ok alternative? > > The problem with MIME and Kom is that Kom changes quite a few things, > which basically require to revert most of the MIME changes. > The recursion with the mimeType method is one of them. Arggh ok now I understand. Stef > > > Michael > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 24, 2009

Re: [Pharo-project] Fixing Polymorph overrides

by Igor Stasenko

2009/2/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hi gary > > We discussed yesterday and we would like to know how we could reduce > the overrides > made by polymorph because we will get in trouble in the long run. > What is your view on that? > Can i put my 5 cents in it? - collect all such overrides into a separate package, named Morphic :) > Stef > > > _______________________________________________ > 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.

Feb. 24, 2009

Re: [Pharo-project] Some issues with Pharo-dev build #10243

by Igor Stasenko

one more thing: pressing 'restart' does not restarts evaluation from choosen context, and also throws me an error, when i previously created a new method by 'create method' button. (*sarcasm*) I think this build should be renamed to pharo-dev-dev , to indicate that this image is suitable for developing a development tools, like Debugger (*sarcasm end*) Nevertheless, you doing a great job guys! :) -- Best regards, Igor Stasenko AKA sig.

Feb. 24, 2009

[Pharo-project] Some issues with Pharo-dev build #10243

by Igor Stasenko

This is mostly feedback on using Debugger - on DNU, if i press 'create a method' debugger opens, and shows extra (debugger related) context frames up to the method context which is just created. (while writing this, i found that it shows these extra contexts even if i simply press 'debug') : -------------- Process>>suspend OTToolset class>>debug:context:label:contents:fullView: OTToolset class>>debugError: [] in DEVToolSet class>>debugError: {[:obtools | obtools debugError: anError]} [] in DEVToolSet class>>ifOBTools:else: {[:obtools | aBlock value: obtools]} OTToolset class(Object)>>ifNil:ifNotNilDo: DEVToolSet class>>ifOBTools:else: DEVToolSet class>>debugError: ToolSet class>>debugError: UnhandledError>>defaultAction UndefinedObject>>handleSignal: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: UnhandledError(Exception)>>signal UnhandledError class>>signalForException: Error>>defaultAction UndefinedObject>>handleSignal: Error(Exception)>>pass [] in PasteUpMorph>>becomeActiveDuring: {[:ex | ActiveWorld := priorWorld. ActiveEvent := priorEvent. ActiveHand :...]} BlockContext>>valueWithPossibleArgs: [] in MethodContext(ContextPart)>>handleSignal: {[(self tempAt: 2) valueWithPossibleArgs: {exception}]} BlockContext>>ensure: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: Error(Exception)>>signal Error(Exception)>>signal: ...... only here starts the context i'm interested in ..... ------------ - mistakenly clicked on 'proceed' while not saved the method caused a losing unsaved work - i'll be happy, to have 'create a method' button, when code throws #subclassResponsibility error :) -- Best regards, Igor Stasenko AKA sig.

Feb. 24, 2009

Re: [Pharo-project] Towards Pharo 1.0

by Schwab,Wilhelm K

Michael, Alien vs. FFI - it's all the same to me - I think??? Whatever you guys want to do, as long as we can connect to the outside world. The less we get tripped up by underscores in doing it, the better. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Michael Rueger Sent: Tuesday, February 24, 2009 3:24 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Towards Pharo 1.0 Schwab,Wilhelm K wrote: > FFI has (it seems to me) long been viewed as an evil in the Squeak > community. I have no idea whether that is justified, but I have to > say that the analogous features in Dolphin have been essential. The motiviation behind not including FFI in the "standard" image was security. FFI allows you to circumvent the Squeak sandbox. Which is only really interesting for Squeak applications that download untrusted code from somewhere (e.g. etoys projects). > > Unless there is a very good reason to exclude it, I would ask for FFI > in 1.0. For myself, the next big hurdle is underscores, largely > because so many of the external entities to which I would be mapping > contain them. I would support that, if it wasn't for Alien, which should be replacing FFI any time now :-) Michael _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 24, 2009

Re: [Pharo-project] Towards Pharo 1.0

by Michael Rueger

Schwab,Wilhelm K wrote: > FFI has (it seems to me) long been viewed as an evil in the Squeak > community. I have no idea whether that is justified, but I have to > say that the analogous features in Dolphin have been essential. The motiviation behind not including FFI in the "standard" image was security. FFI allows you to circumvent the Squeak sandbox. Which is only really interesting for Squeak applications that download untrusted code from somewhere (e.g. etoys projects). > > Unless there is a very good reason to exclude it, I would ask for FFI > in 1.0. For myself, the next big hurdle is underscores, largely > because so many of the external entities to which I would be mapping > contain them. I would support that, if it wasn't for Alien, which should be replacing FFI any time now :-) Michael

Feb. 24, 2009

[Pharo-project] Fixing Polymorph overrides

by StÃ©phane Ducasse

Hi gary We discussed yesterday and we would like to know how we could reduce the overrides made by polymorph because we will get in trouble in the long run. What is your view on that? Stef

Feb. 24, 2009

Re: [Pharo-project] Dealing with incompatibility (was: Re: MIMEdatabase fix?)

by Michael Rueger

StÃ©phane Ducasse wrote: > On Feb 24, 2009, at 7:35 PM, Michael Rueger wrote: > >> slightly shorter it is the fork in the road: >> >> are you committing to Pharo or Squeak? > > I did not get that? > commited :)? to pharo? Well, yes :-) Basically meaning we need to maintain packages explicitly for Pharo. > For MIME I would like to hear if seasider have an alternative to KOM: > is swazoo an ok alternative? The problem with MIME and Kom is that Kom changes quite a few things, which basically require to revert most of the MIME changes. The recursion with the mimeType method is one of them. Michael

Feb. 24, 2009

Re: [Pharo-project] Dealing with incompatibility (was: Re: MIMEdatabase fix?)

by StÃ©phane Ducasse

On Feb 24, 2009, at 7:35 PM, Michael Rueger wrote: > > slightly shorter it is the fork in the road: > > are you committing to Pharo or Squeak? I did not get that? commited :)? to pharo? > > > So lessen or rather delay the pain for larger projects like Seaside we > could agree on postponing changes like MIME (patching it up for now) > and > Unicode/ParagraphEditor until after 1.0. I cannot reply for Unicode (even if this would be good to have that). For MIME I would like to hear if seasider have an alternative to KOM: is swazoo an ok alternative? I have the impression that we should crunch the 1.0 issues and go beta and open a new stream for 1.1 Stef > > > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 24, 2009

Re: [Pharo-project] Towards Pharo 1.0

by Schwab,Wilhelm K

FFI has (it seems to me) long been viewed as an evil in the Squeak community. I have no idea whether that is justified, but I have to say that the analogous features in Dolphin have been essential. Unless there is a very good reason to exclude it, I would ask for FFI in 1.0. For myself, the next big hurdle is underscores, largely because so many of the external entities to which I would be mapping contain them. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of John M McIntosh Sent: Tuesday, February 24, 2009 12:53 PM To: StÃ©phane Ducasse Cc: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Towards Pharo 1.0 Well the current macintosh VM has the support code in it. I can't speak for the windows or unix version. Oomeone *has* to review the alien compiler changes and confirm they are ok, Yesterday I realized there were three class vars missing from ParseNode and 1 method from MethodNode. That I have fixed. The Pharo team has to decided if they want to make Alien (or some FFI) product part of the base system, versus the current thought of only loading FFI if you understand you need it. For Sophie loading FFI in to the base app then let us build components subclassed by operating system to provide functionality faster than doing primitives, and of course modifiable by any smalltalker. On 24-Feb-09, at 5:36 AM, StÃ©phane Ducasse wrote: > Hi john > > what is the work to be done to get alien in pharo? > > Stef -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ======================================================================== _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 24, 2009