- Pharo-dev - lists.pharo.org

Re: [Pharo-project] When is a freeze a bug or me fiddling too much

by Henrik Sperre Johansen

On 16.12.2011 10:31, Schwab,Wilhelm K wrote: > Kasper, > > With all due respect to nearly everyone else here, and in other groups, (IMNSHO on this point), do not start with a morph. Draw on a bitmap/Form, and then display the result. It does wonders for allowing/forcing you to think about resolutions, resulting in code that has a chance of being reused on non-display devices (Windows has an advantage on that front - as much as I hate to admit they got something right<g>). > myExtent := 200@100. myForm := Form extent: myExtent depth: 32. formCanvas := myForm getCanvas. myMorph origin: 0@0 extent: myExtent. myMorph drawOn: formCanvas. myForm asMorph displayInWorld. Cheers, Henry

Dec. 16, 2011

Re: [Pharo-project] Startup Preferences

by Ben Coman

Dec. 16, 2011

Re: [Pharo-project] setting Windows Application Title Bar

by Ben Coman

Dec. 16, 2011

Re: [Pharo-project] NB Bug?

by Sean P. DeNigris

Stefan Marr-3 wrote > > LuaJIT2's FFI... specifically the 'cut&past part' > Wow, that's awesome! Why would it ever be any harder than that? -- View this message in context: http://forum.world.st/NB-Bug-tp4192637p4204556.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 16, 2011

Re: [Pharo-project] When is a freeze a bug or me fiddling too much

by Sean P. DeNigris

KasperOsterbye wrote > > My question is - are there any guidelines on when I should just live with > it, or if it is a bug? > I always use haltOnce inside Morphic (and maybe use a fresh throw-away image) -- View this message in context: http://forum.world.st/When-is-a-freeze-a-bug-or-me-fiddling-too-much-tp4203… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 16, 2011

Re: [Pharo-project] IdentitySet but using #hash rather than #identityHash ?

by Henrik Sperre Johansen

On 16.12.2011 03:26, Levente Uzonyi wrote: > > How about my numbers? :) > > "Preallocate objects, so we won't count gc time." > n := 1000000. > objects := Array new: n streamContents: [ :stream | > n timesRepeat: [ stream nextPut: Object new ] ]. > > set := IdentitySet new: n. > Smalltalk garbageCollect. > [1 to: n do: [ :i | set add: (objects at: i) ] ] timeToRun. "4949" > > set := LargeIdentitySet new. > Smalltalk garbageCollect. > [1 to: n do: [ :i | set add: (objects at: i) ] ] timeToRun. "331" > > set := (PluggableSet new: n) > hashBlock: [ :object | object identityHash * 4096 + object class > identityHash * 64 ]; "Change this to #basicIdentityHash in Pharo" > equalBlock: [ :a :b | a == b ]; > yourself. > Smalltalk garbageCollect. > [1 to: n do: [ :i | set add: (objects at: i) ] ] timeToRun. "5511" > > > I also have a LargeIdentityDictionary, which is relatively fast, but > not as fast as LargeIdentitySet, because (for some unknown reason) we > don't have a primitive that could support it. If we had a primitive > like primitive 132 which would return the index of the element if > found or 0 if not, then we could have a really fast > LargeIdentityDictionary. > > > Levente Hehe yes, if writing a version fully exploiting the limited range, that's probably the approach I would go for as well. (IAssuming it's the version at http://leves.web.elte.hu/squeak/LargeIdentitySet.st) Mariano commented in the version at http://www.squeaksource.com/FuelExperiments that it's slow for them, which I guess is due to not adopting #identityHash calls to #basicIdentityHash calls for Pharo: ((0 to: 4095) collect: [:each | each << 22 \\ 4096 ]) asSet size -> 1 So it basically uses 1 bucket instead of 4096... Whoops. :) Uploaded a new version to the MC repository which is adapted for Pharo, on the same machine my numbers were taken from, it does the same test as I used above in 871 ms. (181 with preallocation). Cheers, Henry

Dec. 16, 2011

Re: [Pharo-project] NB Bug?

by Norbert Hartl

Am 16.12.2011 um 11:47 schrieb Igor Stasenko: > On 16 December 2011 11:02, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: >> >> On 16 Dec 2011, at 10:49, Igor Stasenko wrote: >>>> >>> oh please. that's even less obvious usage :) >>> there's a lot of different stuff in C syntax which you can play with. >>> But it doesn't means that you need to routinely support >>> everything in FFI callout specs. >>> >>> as i said, the function signature syntax are close to C syntax, but >>> not strictly C. >> >> Igor, what is your goal with that? >> Have something working, or have something usable? >> >> If your goal is to have something usable, then your direct competitor is LuaJIT2's FFI >> http://luajit.org/ext_ffi.html >> and you should show similar ambitions. (Note specifically the 'cut&past part') >> Otherwise, it will always remain just a nice try, an experiment that never got finished/productized. >> >> My understanding is that your boss got other plans for Pharo... >> > well, there are things which i would like to have, like integrating > with Cog (so a call to generated native code > will be performed directly , instead via primitive), non-blocking and callbacks. > This is much more important to have than subtleties, how to define a > function which takes no arguments by using '()' or '(void)'.. > Kind of 'triangle has three corners' vs 'triangle has three edges' discussion. > Igor, importance lies in the eye of the beholder. You are doing great stuff and you don't want to waste your time with things you consider unnecessary. But you need to decide what is the goal of NativeBoost. If you like to keep the pace and realize cool demos then you shouldn't listen to other people. If you think you like to make it an accepted piece of software that has a lot of users then you need listen to them. People posting in this thread are your potential users. They tell you things the fail over. If this happens more often you'll loose them because they don't want to waste their time with non-working stuff (the term non-working also lies in the eye of the beholder). Basically it is that easy. If you don't care about the (probably stupid) wishes of your users it stays your private pet project. Norbert

Dec. 16, 2011

[Pharo-project] [update 1.4] #14261

by Marcus Denker

14261 ----- Issue 4745: Debugger opens when trying to get unimplemented calls http://code.google.com/p/pharo/issues/detail?id=4745 Issue 4870: numargs? http://code.google.com/p/pharo/issues/detail?id=4870 Issue 5111: Make TestRunner search input ignore case http://code.google.com/p/pharo/issues/detail?id=5111 Issue 5087: remove unsent methods from ServerDirectory http://code.google.com/p/pharo/issues/detail?id=5087 -- Marcus Denker -- http://marcusdenker.de

Dec. 16, 2011

Re: [Pharo-project] NB Bug?

by Igor Stasenko

On 16 December 2011 11:02, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: > > On 16 Dec 2011, at 10:49, Igor Stasenko wrote: >>> >> oh please. that's even less obvious usage :) >> there's a lot of different stuff in C syntax which you can play with. >> But it doesn't means that you need to routinely support >> everything in FFI callout specs. >> >> as i said, the function signature syntax are close to C syntax, but >> not strictly C. > > Igor, what is your goal with that? > Have something working, or have something usable? > > If your goal is to have something usable, then your direct competitor is LuaJIT2's FFI > http://luajit.org/ext_ffi.html > and you should show similar ambitions. (Note specifically the 'cut&past part') > Otherwise, it will always remain just a nice try, an experiment that never got finished/productized. > > My understanding is that your boss got other plans for Pharo... > well, there are things which i would like to have, like integrating with Cog (so a call to generated native code will be performed directly , instead via primitive), non-blocking and callbacks. This is much more important to have than subtleties, how to define a function which takes no arguments by using '()' or '(void)'.. Kind of 'triangle has three corners' vs 'triangle has three edges' discussion. -- Best regards, Igor Stasenko.

Dec. 16, 2011

[Pharo-project] [update 1.4] #14260

by Marcus Denker

14260 ----- Issue 5084: Remove textStyle FileOut http://code.google.com/p/pharo/issues/detail?id=5084 Issue 5108: InflateStream bug with empty strings http://code.google.com/p/pharo/issues/detail?id=5108 Issue 4920: Copying a trait fails http://code.google.com/p/pharo/issues/detail?id=4920 Issue 5081: Remve Morph saving to file/loading http://code.google.com/p/pharo/issues/detail?id=5081 -- Marcus Denker -- http://marcusdenker.de

Dec. 16, 2011