- Pharo-dev - lists.pharo.org

[Pharo-project] [update] #10167
by Marcus Denker Nov. 25, 2008

Nov. 25, 2008

- clean more Preferences (Marcus Denker) - Scriptloader Seaside loading methods (Torsten Bergmann) - Postscript: (Preferences preferenceAt: #allowEtoyUserCustomEvents) changeInformee: nil changeSelector: nil. Preferences removePreference: #batchPenTrails. Preferences removePreference: #allowEtoyUserCustomEvents. Preferences removePreference: #automaticViewerPlacement. Preferences removePreference: #capitalizedReferences. Preferences removePreference: #fenceEnabled. Preferences removePreference: #keepTickingWhilePainting. Preferences removePreference: #tileTranslucentDrag. Preferences removePreference: #translationWithBabel. Preferences removePreference: #useButtonProprtiesToFire. Preferences removePreference: #alphabeticalProjectMenu. Preferences removePreference: #showAdvancedNavigatorButtons. Preferences removePreference: #ignoreStyleIfOnlyBold. Preferences removePreference: #propertySheetFromHalo. -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

1 0

[Pharo-project] SUnit: history support and OB icons
by Simon Denier Nov. 25, 2008

Nov. 25, 2008

Hi all Just to notify a new enhancement to review in the PharoInbox. SLICE-Issue338-SUnitHistoryAndIcons-simon_denier.2 Short doc: Add: - support history for test runs as well as progression filter to show test in progression, regression - support icons in OB to show the current state of a test: passed, failed, progressed, regressed... History support: - whenever some test cases run from the TestRunner, their results are stored in a class side variable TestResult class>>History - contextual menu for history in TestRunner>>error pane: 1) History: access submenu to TestRunner instance history: can save and show progress between results ran in the same TestRunner; lost when this particular instance of TestRunner is closed 2) Store results as progress reference: create/update a lastStoredRun method on the class side of each TestCase which have just been run, containing the results 3) Show progress: make a diff between the last run and the lastStoredRun, showing progress or regress in tests (new passed, new failures, new errors) The idea is that whenever you are satisfied with the current results of some of your tests, you can save this state as a reference point with the 'Store results...' action. This reference point can be compared with subsequent test results to show your progression or regression. Test results are stored in a class side variable some are kept local to your image. Reference results are stored in a special method for each TestCase, so that they are saved with their package and can be used as a common reference for package developers. So a good practice is to store the latest test results as reference before committing your changes. Icons support: OB Package browser now has icons for test methods in TestCase subclasses: - green circle: test has passed in the last run - red circle: test has failed - half green/half red circle: state unknown, test has no history or test has changed since last run - (no icon): test has raised an error - upside green arrow: test has progressed since last reference run - downside blue triangle: test has regressed since last reference run A test is in progression if it goes from error or failure to passed state. A test is in regression if it goes from passed to error or failure state. The last two icons have other meanings with methods not related to test, so we should change them whenever someone has better icons. Authors: Alexandre Bergel, Simon Denier, David RÃ¶thlisberger -- Simon

5 32

[Pharo-project] Pharo-dev logo :)
by Igor Stasenko Nov. 25, 2008

Nov. 25, 2008

Hope it not hurts anyone's feelings.. Just for fun :) -- Best regards, Igor Stasenko AKA sig.

4 7

Re: [squeak-dev] Re: [Pharo-project] Alien FFI
by John M McIntosh Nov. 24, 2008

Nov. 24, 2008

On 24-Nov-08, at 6:37 AM, David Pennell wrote: > John, > > Its probably worthwhile to find a place to post Eliot's > documentation files for Alien. > > -david Documentation files and a start on a wiki page is at: http://wiki.squeak.org/squeak/6100 -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

1 0

[Pharo-project] Event rewrite
by Michael Rueger Nov. 24, 2008

Nov. 24, 2008

Hi all, after wrapping the current implementation which I test and packaged in the experimental polymorph image I tried to install it in the newest Pharo image and it doesn't work (freezes). Anyone a suggestion what might have changed in the area of event handling or process management? I started going through the different classes but maybe somebody has a hint where to look? As reward there will be no more EventSensor and EventTicklerProcess :-) Thanks Michael

6 34

Re: [squeak-dev] Re: [Pharo-project] Alien FFI
by John M McIntosh Nov. 24, 2008

Nov. 24, 2008

Ok, well asAlien seems to be used as conversion methods to ensure a passed object is an alien. What would you like to do instead? I'll integrate the primitive Error code changes this week and do any clean up. If you would like to suggest which variable bindings can be deleted I'll correct that. On 24-Nov-08, at 9:49 AM, Vassili Bykov wrote: > On Mon, Nov 24, 2008 at 12:13 AM, John M McIntosh > <johnmci(a)smalltalkconsulting.com> wrote: >> I would suggest someone with an eye towards "Compiler, CompileMethod, >> ParseNode" carefully look at the changes in "Alien-Core" to ensure >> I've not >> trashed some important part of the Pharo Compiler or Traits. I >> can't say if >> the changes are destructive or passive? > > Many of those have to do with primitive errorCode support, and it > would be nice to categorize them separately. I didn't look closely, > but those that have to do with variable bindings are likely to be > irrelevant. > > And sorry, but adding #asAlien to True, False and UndefinedObject is > just wrong. Nor should have it been in String from the start. > > Cheers, > > --Vassili > -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

1 0

Re: [Pharo-project] HostWindows rewrite
by Bill Schwab Nov. 24, 2008

Nov. 24, 2008

I agree: it would be useful to control host windows in some way, whether as described below, or via Wx, etc. The native windows/controls have their uses, though they are not (IMHO) the panacea that many believe them to be. So, it would be very nice to be able to mix native and emulated GUI elements. 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 >>> antony.blakey(a)gmail.com 11/9/2008 4:35 PM >>> On 09/11/2008, at 10:17 PM, Igor Stasenko wrote: > What you'll never see in new plugin: > - native widgets support or any kind of dealing with native widgets/ > controls. Notwithstanding this, IMO a really good feature would be the ability to create and manage native views within windows, where e.g. a Morph could be 'backed' by a native view. This feature alone is enough to later allow native controls (such as WebKit) to mix with 'light' controls with correct z-ordering/clipping/event handling etc. Of course one could retrofit such a feature, but using native views from the start would encourage any Morphic mods (or other widget set) to use native views and hence be ready for better integration. Antony Blakey -------------------------- CTO, Linkuistics Pty Ltd Ph: 0438 840 787 Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. -- Douglas Adams _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

Nov. 24, 2008

Hi all I loaded OB shout ecompletion and we were apply coding with damien. And the image froze (deeply) when we redefined a class. So the thread changes may be a problem. Stef

4 8

[Pharo-project] ob list?
by Esteban Lorenzano Nov. 24, 2008

Nov. 24, 2008

Hi, Does anybody knows if there is a OB specific discussion list? I'm having some issues with latest OBPackageBrowser implementation (OBTreeColumn) and I want to discuss/understand the implementation... Thanks, Esteban

2 1

[Pharo-project] How to set the color of a gradient button ?
by Hilaire Fernandes Nov. 24, 2008

Nov. 24, 2008

On button created with polymorph, like btn := self newButtonFor: self action: #openFinish label: 'J''ai fini !' help: 'Presse ce bouton lorsque tu as fini l''exercice'. ^ btn onColor: Color green muchLighter offColor: Color gray Changing the color does not work as expected. There are a couple of metod to change the color but none are working. Hilaire -- http://blog.ofset.org/hilaire

2 1