- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Polymorph question
by Gary Chambers Sept. 6, 2008

Sept. 6, 2008

There is a preference, something like showEditState (on my N810 so no Squeak just now). Gary. ----- Original message ----- > Gary > is there a way to see when the code has not been accepted? > Right I get blue for the focus but not red when the code is notÂ > accepted. > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 2

Re: [Pharo-project] FileList + Code button?
by Bill Schwab Sept. 6, 2008

Sept. 6, 2008

Stef, This code is coming from Dolphin. I thought about making a modified source filer and then thought of SIF. The most recent code I have found is old, but it should be easy enough to update it, if that is even required. Better ideas are welcome however. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> stephane.ducasse(a)inria.fr 09/06/08 2:59 AM >>> not really. to import code form VW I used the fileout30 format. stef On Sep 6, 2008, at 1:29 AM, Bill Schwab wrote: > Hello all, > > I need to dig into SIF (failing better suggestions??), and will simply > do a "port" starting with the existing code. To look for sore spots, > would I simply point a file list at the .st files and hit "Code"? Is > there a better way? > > Bill > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] Polymorph question
by StÃ©phane Ducasse Sept. 6, 2008

Sept. 6, 2008

Gary is there a way to see when the code has not been accepted? Right I get blue for the focus but not red when the code is not accepted. Stef

2 1

[Pharo-project] FileList + Code button?
by Bill Schwab Sept. 6, 2008

Sept. 6, 2008

Hello all, I need to dig into SIF (failing better suggestions??), and will simply do a "port" starting with the existing code. To look for sore spots, would I simply point a file list at the .st files and hit "Code"? Is there a better way? Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029

2 1

Re: [Pharo-project] Debugging aids
by Bill Schwab Sept. 6, 2008

Sept. 6, 2008

Michael, Ah, the .snafu file type ;) That is an interesting idea. Anybody else for it? It is interesting, as I have written some tools that parse logs for various purposes, and never once thought of doing the obvious. One potential snag is that I found a need to create a process safe stream; I doubt the number of open files would be terrible, but it would be worth a look to see the extent of its use. IIRC, it was for a transcript replacement. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> m.rueger(a)acm.org 9/5/2008 11:02:17 AM >>> Bill Schwab wrote: > Hello all, > > Random thoughts/wishes: > > The UI discussion reminded me of a couple of things. Squeak appears to > overwrite its debug log; minimally, I think there should be an option to > append, and it probably should default to true. Many times, I've had I'd rather have time stamped files. Stack traces are already long enough as they are ;-) Michael _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Re: [Pharo-project] Debugging aids
by Bill Schwab Sept. 6, 2008

Sept. 6, 2008

Stef, Will do. The append option will come first. The crash dumps might take more effort, since I did not even see the feature on Linux. Not sure what to make of that. I guess I was hacking the VM, so maybe it is available only on Windows. If that is the case, we should fix it. I assume you want an option? How about #appendToDebugLog? I will confess to thinking (if only to myself) this should simply be the behavior, but the option route works too. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> stephane.ducasse(a)inria.fr 9/5/2008 11:02:06 AM >>> send us the code :) stef On Sep 5, 2008, at 5:45 PM, Bill Schwab wrote: > Hello all, > > Random thoughts/wishes: > > The UI discussion reminded me of a couple of things. Squeak appears > to > overwrite its debug log; minimally, I think there should be an > option to > append, and it probably should default to true. Many times, I've had > what our British friends would call a knock-on effect overwrite the > trace of the real cause of the problem. The same should apply to the > crash dump. > > The option to show call stacks (which I am not seeing on the Linux VM, > and would like to<g>), should show all non-dead threads, not simply > the > active thread. IIRC, there has been some progress on that front. > > Bill > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] Fwd: going over and integrating Kernel-Extensions
by StÃ©phane Ducasse Sept. 5, 2008

Sept. 5, 2008

> > From: stÃ©phane ducasse <ducasse(a)iam.unibe.ch> > Date: August 22, 2008 9:46:46 AM CEDT > To: An open mailing list to discuss any topics related to an open- > source Smalltalk <Pharo-project(a)lists.gforge.inria.fr> > Subject: going over and integrating Kernel-Extensions > > > Hello pharoers > > it would be nice if we could go over the items (especially the > extensions proposed in > Squeak3.11 Contributions/Kernel-Extensions) on squeaksource and see > what can be integrated into > pharo. > > stef > > >

1 0

Sept. 5, 2008

Hi gary I wanted to remove the class ComponentLikeMorph from the system. So I redefined ScrollPane to be a subclass of the superclass of ComponentLikeMorph MorphicModel subclass: #ScrollPane instanceVariableNames: 'scrollBar scroller retractableScrollBar scrollBarOnLeft getMenuSelector getMenuTitleSelector scrollBarHidden hasFocus hScrollBar' classVariableNames: '' poolDictionaries: '' category: 'Morphic-Windows' it works in pharo 64 but it crashes systematically the vm when polymorph is loaded. Stef

3 7

[Pharo-project] Debugging aids
by Bill Schwab Sept. 5, 2008

Sept. 5, 2008

Hello all, Random thoughts/wishes: The UI discussion reminded me of a couple of things. Squeak appears to overwrite its debug log; minimally, I think there should be an option to append, and it probably should default to true. Many times, I've had what our British friends would call a knock-on effect overwrite the trace of the real cause of the problem. The same should apply to the crash dump. The option to show call stacks (which I am not seeing on the Linux VM, and would like to<g>), should show all non-dead threads, not simply the active thread. IIRC, there has been some progress on that front. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029

3 2

Sept. 5, 2008

Questions ======== - Why the UITheme is responsible to open widgets. Why this is not the UIManager subclass because now a lot of the interface has to be duplicated in UITheme. Answer because the theme is a variation which requires more subtle controls. Now I have the impression that it means that the UIManager is not well done then. - Why in the following method basicNew is used and not new (which would call initialize anyway)? chooseDirectoryIn: aThemedMorph title: title path: path "Answer the result of a file dialog with the given title, choosing directories only." |fd| fd := FileDialogWindow basicNew initialize; title: title; answerDirectory. path ifNotNil: [fd selectPathName: path]. ^(aThemedMorph openModal: fd) answer To support better integration: ======================= We could merge UIManager subclasses MorphicUIManager and PSUIManager PSPluggableListSpec should be merged into PluggableListSpec I tried to understand the difference between standardWindow and pluggableWindow to see if it would make sense to merge them. I started to check all the extensions and yes there are some work but ideally removing the override would be good. Stef

2 1