May 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] NetNameResolver in Pharo 1.1
by Chris Muller May 14, 2010

May 14, 2010

You have an out-of-date version of "Ma Armored Code" package. Â It sounds like you are not using instructions on the Magma installation page..? Â http://wiki.squeak.org/squeak/2657 The Installer script provided there is correct, I'm not sure what happened.. You could also use Monticello Configurations, but they appear to not be working in Pharo 1.1 right now. Â I don't know whether Miguel updated his Metacello config for Magma; I have not yet had time to get into Metacello or I would have done it. So how did you install this? On Fri, May 14, 2010 at 9:43 AM, Michael Roberts <mike(a)mjr104.co.uk> wrote: > Hi just trying to run the tests via the standard magma test > expression. So it is looking to see if Display exists. That's the > point on my mac I recognize that it annoyingly changes my screen > resolution :-) > > anyway it is missing your ma extension to query the namespace. > > Cheers > mike > > On Friday, May 14, 2010, Chris Muller <asqueaker(a)gmail.com> wrote: >>> installer) it seems. I am missing an implementation of a method >>> maAt:ifPresent:ifAbsent: on Smalltalk. >> >> Hi Mike, this is left-over from when Smalltalk became a >> SmalltalkImage. Â But I am confused because I thought I had those all >> cleaned up. Â Indeed, I did not find any senders of that to Smalltalk. >> >> Were you just trying to load it or run the test suite? Â If you would >> post the stack I would be able to see what you were trying to do and >> would be happy to fix it. >> >> Â - Chris >> >>> >>> anyone with a spare moment might like to figure that out. The >>> underscores need fixing in dependent packages (write barrier tests) >>> as well >>> >>> so we should maybe do something simpler to test the network. >>> >>> thanks, >>> Mike >>> >>> _______________________________________________ >>> 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] IWST 2010 CfP - Deadline Extension
by Michael Haupt May 14, 2010

May 14, 2010

* apologies for multiple copies * The submission deadline for the International Workshop on Smalltalk Technologies (IWST) 2010 has been extended to June 18. Please find the details below. Call for Papers International Workshop on Smalltalk Technologies (IWST) 2010 co-located with European Smalltalk User Group Conference (ESUG) Barcelona, Spain, September 11-17, 2010 ** Description The goal of the IWST workshop series is to create and foster a forum around advances or experience in Smalltalk. We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk-related topics. There are two possible kinds of submissions, which must be in ACM SIGPLAN style: * Research papers (up to 10 pages). Submissions in this category will be rigorously reviewed, and accepted papers will be published in the ACM Digital Library (ACM SIGPLAN has approved, the final ACM approval is pending). * Demonstration papers (up to 4 pages). Submissions in this category will not be published in the ACM Digital Library, but will be available for download from the workshop web page. ** Submission and Reviewing Process The EasyChair submission web site is at http://www.easychair.org/conferences/?conf=iwst10. Authors will be given the opportunity to comment on reviewers' work by providing feedback on the reviews. For this purpose, a questionnaire will be sent to authors. Their answers will be evaluated anonymously, and feedback will be handed on to reviewers. ** Important Dates Submission: June 18, 2010 (Samoa time) Feedback: July 16, 2010 ESUG Early Registration Deadline: July 9, 2010 Authors will be able to register for the early rate if their registration depends on IWST notification. Workshop: September 12, 2010, Barcelona, Spain ** Programme Committee Co-Chairs: Michael Haupt, Hasso-Plattner-Institut, University of Potsdam, Germany Robert Hirschfeld, Hasso-Plattner-Institut, University of Potsdam, Germany PC Members: Gabriela Arevalo, Universidad Nacional de La Plata, Argentina Johannes Brauer, NORDAKADEMIE, Germany Johan Brichau, UniversitÃ© catholique de Louvain, Belgium Marcus Denker, INRIA Lille - Nord Europe, France Theo D'Hondt, Vrije Universiteit Brussel, Belgium James Foster, GemStone Systems, Inc., USA Andy Kellens, Vrije Universiteit Brussel, Belgium Andreas Raab, Teleplace Inc., USA Lukas Renggli, Software Composition Group (SCG), University of Bern, Switzerland Randal L. Schwartz, Stonehenge Consulting Services, Inc. Dave Ungar, IBM Research

1 0

[Pharo-project] Categories and Packages
by Geert Claes May 14, 2010

May 14, 2010

Categories are used to group related Classes together in an Image. The notion of Repositories and Packages were probably introduced to manage saving versions of code outside the Image and sharing this code easier. I am only trying to understand the reason why Classes are grouped in Categories as well as Packages especially since by convention the Package name is the same as the Class name? -- View this message in context: http://forum.world.st/Categories-and-Packages-tp2216632p2216632.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

3 4

[Pharo-project] Text selection color too dark in Pharo 1.1
by Adrian Lienhard May 14, 2010

May 14, 2010

In Pharo 1.0 the background color of selected text looks as follows: In Pharo 1.1: The text is harder to read with the new color. Was this changed on purpose? Adrian

3 3

[Pharo-project] Pharo tips
by Torsten Bergmann May 14, 2010

May 14, 2010

I would also add ... textMorph lock. ... to the PharoTipsMorph>>initialize method so it is not editable anymore. Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

1 0

[Pharo-project] Pharo tips
by Torsten Bergmann May 14, 2010

May 14, 2010

>I open it in pharo I see that I have SystemWindowButton class >missing. What steps should I follow to port that from Squeak? Replace SystemWindowButton with IconicButton and it works in Pharo too (with old icons).But you can exchange the graphics with own methods returning a Form instance. Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 1

[Pharo-project] FFI cleanups (no underscore assignment)
by Torsten Bergmann May 14, 2010

May 14, 2010

Hi, FFI still had underscore assignments in the Unix package which I fixed now in "FFI-Unix-tbn.3.mcz". The Metacello configuration is also updated. If you work with Metacello you can use: In Squeak: ---------------------------------------------------- Installer ss project: 'MetacelloRepository'; install: 'ConfigurationOfFFI'. (Smalltalk at: #ConfigurationOfFFI) load ---------------------------------------------------- In Pharo: ---------------------------------------------------- Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfFFI'; load. (Smalltalk at: #ConfigurationOfFFI) load ---------------------------------------------------- Have fun Torsten -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

1 0

[Pharo-project] [NativeBoost] New update available
by Igor Stasenko May 14, 2010

May 14, 2010

Hello all, i just published a heavily updated version of NativeBoost project. See http://code.google.com/p/nativeboost/wiki/Installation Also, a newer prebuilt win32 vm is available for download. Here the list of changes: VM side. - plugin no longer requires platform specific support code. All platform specific stuff is now [can be] implemented at language side. - added a small extension to Interpreter (#swapActiveContext:restoreMethod:) for callbacks support Language side. - NBUtils renamed to NativeBoost class and now will serve as a core API class, which is a starting place of most basic NativeBoost functionality - added a lazy and seamless image restart handling. None of NativeBoost code contributing to image startup phase. It starting up lazily and automatically, upon first access to its functionality. - added an external native function generator, to support generating a code and placing it into non-movable external memory region - various tests, bells & whistles. And last , but not least - added initial callback support There are two kinds of callbacks supported: native and language-side. With native callbacks , there is nothing fancy: generate native code and copy it to external memory. Then pass its address to any function which takes callback as argument. Period. A language-side callbacks required much more implementation effort to function properly, but easy to use by developers. You just need to subclass the NBFFICallback class, and override two methods at class side in your subclass: fnSpec & callType a #fnSpec should answer a callback function specification , like: #(int ( int a, int b)) and callType should answer either #cdecl or #stdcall, which tells what calling convention your function should use. To create a callback , just do: callback := MyCallback on: [:arg1 :arg2 | ... do something here .. ]. and then simply pass it to any FFI callout method which takes it as argument: self foo: x bar: y callback: callback where #foo:bar:callback: defined as FFI callout as followin: foo: aFoo bar: cylinder callback: fn <primitive: #primitiveNativeCall module: #NativeBoostPlugin> ^ NBFFICallout cdecl: #(void qsort (int aFoo, ulong cylinder, MyCallback fn)) module: 'myModule' note the name of class 'MyCallback' , supplied as argument type. This stuff is not tested throughoutly, so take care. I am used only a single function for testing callbacks - a qsort(), provided by C run-time library. The difference between natively-implemented callbacks and language-side ones is paramount (but that was expected, isnt? :) NBFFICallbackTests new benchQSort #(2689 184 21322) 2689 - array sort using purely smalltalk 184 - array sort with native callback 21322 - array sort with callback to a language side. Any comments and questions are wellcome. -- Best regards, Igor Stasenko AKA sig.

1 0

[Pharo-project] Pharo by example book: copying/pasting code snippets
by Andrei Stebakov May 13, 2010

May 13, 2010

When I copy and paste code snippets from the book, the compiler complains about the minus signs (which is different character from what Pharo expects): For example the line from the book: (j > 1) ifTrue: [ (cells at: i at: j - 1) toggleState]. I have to change to (with "short" minus sign) (j > 1) ifTrue: [ (cells at: i at: j - 1) toggleState]. Otherwise the method doesn't get accepted. I wonder if this is a PDF issue and if it could be corrected? Thank you, Andrew

5 4

Re: [Pharo-project] (igor) Help for 1.1: condenseChanges does not work anymore
by Igor Stasenko May 13, 2010

May 13, 2010

On 9 May 2010 21:39, Alain Plantec <alain.plantec(a)free.fr> wrote: > Le 09/05/2010 18:48, Igor Stasenko a Ã©crit : >> >> On 9 May 2010 13:29, Alain Plantec<alain.plantec(a)free.fr> Â wrote: >> >>> >> This was a result of lack of attention, not my real intent. :) >> > > ok, so we have the same version >> >> But unfortunately, this solution seems to be broken to. It works one time, >>> >>> but while trying to >>> condenseChanges again several time, my squeak process is killed without >>> flushing any log. >>> >> >> You mean running #condenseChanges multiple times in a row, or >> interrupting it and then start over again? >> You should know, that it is important to not interrupt it in the >> middle, because when you doing that, >> part of your methods having old source pointers, while rest part >> having new ones, >> and there is no way to tell, which one is correct. >> > > I take a fresh image. > SmalltalkImage current condenseChanges. > then > I update some methods individually and save my image, > then > SmalltalkImage current condenseChanges. > and it crash > Ok, i took the 11343 - fixed the #condenseChanges - ran Smalltalk condenseChanges - changed the single method - saved image - ran Smalltalk condenseChanges again no crash reported. > Alain > -- Best regards, Igor Stasenko AKA sig.

5 10