August 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] Getting started with Seaside 2.9 + pharo
by Torsten Bergmann Aug. 19, 2009

Aug. 19, 2009

Pat Maddox wrote on Pharo-project list >So far getting set up has been quite frustrating and now I'm looking >for some help...I want to start developing Seaside 2.9 on Pharo. How >do I do that? I crosspost this to squeak-dev and seaside too since this question comes up from time to time: If you want to load and use all the latest seaside stuff (Pharo and seaside29) then you should download the newest beta image (non-web) from the pharo download site, see [1]. If you are on win32 you can alternatively use the installer exe to get the full package (including latest VM, fonts, ...), see [2]. If you want you can update the image (according to Damien [3] it is now not only possible to update the core image but also the pharo main image with all the dev-tools, thats the one on the pharo download site) However, in a recent Pharo you can evaluate ScriptLoader loadSeaside29 This internally loads the "LoadOrderTest" (check the class ScriptLoader how its done) from the seaside squeaksource repo ([4]). The load order test is typically updated by the gemstone/seaside developers with the latest seaside 29 packages in the correct order - so it loads the latest seaside 2.9 stuff. Acccording to planetmisc feed it was updated on 17th August (see [5]). so you should get all new packages from Seaside29. Click "OK" when asked to load, NO to run the tests and after loading select "Tools -> More -> Seaside Control Panel" from the world menu. See also [6] This should bring up the new control panel and you can use the context menu to add an adapter on a specific port and run it. If you want you can open Monticello browser on the seaside 29 repo and load newer packages. Have fun Torsten [1] http://pharo-project.org/pharo-download [2] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-August/012100.html [3] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-August/012048.html [3] http://www.squeaksource.com/Seaside29.html [4] http://planetmisc.squeak.org/ [5] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-August/011942.html -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate fÃ¼r nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02

1 0

[Pharo-project] ORM for Pharo
by Esteban A. Maringolo Aug. 19, 2009

Aug. 19, 2009

My prototype is getting less proto, and I found out it doesn't have complex relations, and the system is going to perform faster if I have tables for most of it. What are the choices I have for doing ORM in Pharo? Â¿Does GLORP work? Â¿Any other options? I don't have a strong preference for the RDBMS engine, it can be anything (free), being it MySQL, PostgreSQL or Sql Server Express. Best regards, Esteban A. Maringolo

9 22

[Pharo-project] Second LIfe plugin API
by Lawson English Aug. 19, 2009

Aug. 19, 2009

As part of my on-going work on finding synergy, someone, somewhere, might want to look at this: http://wiki.secondlife.com/wiki/Media_Rendering_Plugin_Framework_Technical_… and consider what might be done with Squeak/Phara/Croquet/Cobalt/Seaside in a Second Life context. Lawson

1 1

Re: [Pharo-project] [croquet-dev] Re: [squeak-dev] Second LIfe plugin API
by Lawson English Aug. 19, 2009

Aug. 19, 2009

https://svn.secondlife.com/svn/linden/branches/2009/plugin-api/indra/media_… Is the source for the plugin samples. That's as much info as I can get past what little is on the wiki... http://wiki.secondlife.com/wiki/Media_Rendering_Plugin_Framework Lawson

1 0

[Pharo-project] Fwd: OverlyComplex
by StÃ©phane Ducasse Aug. 18, 2009

Aug. 18, 2009

Begin forwarded message: > From: "Ken.Dickey" <Ken.Dickey(a)whidbey.com> > Date: August 18, 2009 8:36:53 PM CEDT > To: pharo-project-owner(a)lists.gforge.inria.fr > Subject: OverlyComplex > > Greetings, > > I have done a brief write up of Complex issues that most concern me > and opened > ISSUE 1072: OverlyComplex. > > http://code.google.com/p/pharo/issues/detail?id=1072 > > > Note that there are to be three proposals: > removeComplex [Issue OverlyComplex] > basicComplex > extendedComplex > > SLICE-remove-Complex, the first of the three changesets, has been > added to > PharoInbox as per > http://code.google.com/p/pharo/wiki/HowToContribute > > I logged on to Pharo's Google Wiki but fail to see how to add a > topic/page. > Can some kind soul help me out? > > Again, I am new to your processes, so any help/suggestions/info are > welcomed. > > Thanks much, > -KenD >

4 5

[Pharo-project] Fwd: REPOST: Complex Solution Outline
by StÃ©phane Ducasse Aug. 18, 2009

Aug. 18, 2009

Begin forwarded message: > From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> > Date: August 18, 2009 2:09:15 AM CEDT > To: "Ken.Dickey" <Ken.Dickey(a)whidbey.com> > Cc: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: RE: REPOST: Complex Solution Outline > > Ken, > > Please put this on the wiki; we try to keep the process > transparent. As should be no surprise by now, I question the value > of $< for complex numbers - I just don't see the point of defining > one that works so infrequently as this, and I see reasons not to > offer one at all. People knowing their way around floating point > math and applications of complex variables will know what to do for > any given comparison based on physical motivations. > > Removing things and making packages seems (Stef?) to be a general > approach to cleaning, so I doubt there will be resistance to that > idea. > > I think the extended complex solution is risky. That is not to say > you should not write it and use it, but it should be separate and > clearly marked with caveats; I can speak only for myself (and > probably for Sig), but I would *not* want it in my image. Much of > what you have expressed as concerns about the current implementation > involves yet another dimension, which is treating the few "nice" > numbers that exist without roundoff error; it would be an exact and/ > or symbolic package. I think it would yield very little benefit > from a LOT of work, but you seem to care about it, so it should > probably be described. Even if it never gets built, giving it a > name would help sort out the various feature demands. > > Finally, there is a lot that should be added to this. There should > be a GSL or similar FFI or plugin and wrappers to bring the > elementary and special functions into Pharo. That is actually > bigger than just complex numbers, so it probably deserves its own > wiki page and plan. > > Bill > > > > -----Original Message----- > From: Ken.Dickey [mailto:Ken.Dickey@whidbey.com] > Sent: Monday, August 17, 2009 6:14 PM > To: Schwab,Wilhelm K > Subject: REPOST: Complex Solution Outline > > Bill, > > Feedback appreciated. > > Thanks, > -KenD > VVV==============unComplex.txt================VVV > INTRODUCTION > > The current Complex class is not carrying its weight in the Pharo- > Core image. > It appears to be little used and has some serious integration > problems with the numeric classes. > > This proposal has three parts, removeComplex, basicComplex, and > extendedComplex. > > The removeComplex package removes the Complex class and associated > code from the current (beta1) image. > > The basicComplex package adds Complex back with some additional > changes to fix some of the integration problems, but leaves out some > mathematical properties to assure backward compatability. > > The extendedComplex package makes the Complex number implemantation > more complete mathematicaly at the expense of backward code > compatability and may break some software. Caveat programmer. > > Note that there is no attempt to change oddities of Smalltalk syntax. > E.g. > (3 + 1/2i) --> (0 - 2i) NOT (3 + (1/2)i) > > > > PROBLEMS > > In mathematics, type Complex is a superset of type Real, but in > Pharo the class Complex is unrelated to subclasses of Number. This > causes some common expectations to be disappointed. In particular, > the following patterns break > down: > > [1] If (A=a) and (B=b) and (A<B) then (a<b) [2] A squared sqrt = A > [3] A isNumber => (A class) isKindOf: Number > > [1] | A a B b } > A := 0. > a := A + 0i. > B := 1. > b := B asComplex. > A = a. "true" > B = b. "true" > A < B. "true" > a < b. "ERROR" > > [2] 1i squared. "-1 + 0i" > 1i squared sqrt. "ERROR" > 1i squared real sqrt. "ERROR" > > [3] (1.2 + (1/2)i) isNumber. "true" > (1.2 + (1/2)i) class isKindOf: Number. "false" > > In particular, isNumber is used in a number of low-level methods > which would not deal well with complex numbers. > > E.g. FloatArray>> > *= anObject > ^anObject isNumber > ifTrue:[self primMulScalar: anObject asFloat] > ifFalse:[self primMulArray: anObject] > > > SOLUTIONS > > > [A] removeComplex > > Removing the Complex code gives more traditional Smalltalk > expectations. In particular this conservative approach yields the > best code backward compatability because Complex is a relatively > recent addition to Squeak and was not present in many older > Smalltalk implementations. In particular, problems [1][2][3] cannot > arise. > > > [B] basicComplex > > [1] Can be fixed by adding a "formal" method to Complex with > selector #< which only compares real numbers (those whose imaginary > component is zero). > > [2] Will remain unaddressed for backward compatability. > > [3] I propose to remove the isNumber method from Complex and add > isNumberOrComplex to both Number, Object, and Complex. [Better > solutions anyone? Better name (isNumeric)?] This avoids changing a > lot of baseline code. > > > [C] extendedComplex > > [2] The sqrt and ln methods will extended to return complex results > for negative numbers. > > Other changes may be cased by adding guard code for users of methods > which did not formerly return complex results. > > > > -KenD [Ken dot Dickey at Whidbey dot Com] > ^^^==============unComplex.txt===============^^^

2 1

[Pharo-project] [ANN] 10415->10418
by StÃ©phane Ducasse Aug. 18, 2009

Aug. 18, 2009

Issue 1067: ByteArray doesNotUnderstand: hex Issue 1045: TTFontReader class-installTTFasTextStylesizes calls FormSetFont>>pixelSize: Issue 1073: addMethod: aMethodReference Issue 936: Traits package not browseable in Monticello one step more towards 1.0 Stef PS: I think that in 1.1 we will have to think how to open a bit more the integration process. The problem is how to make sure that we get a good quality.

1 0

[Pharo-project] patched MIMEDocument>>contentType:content:
by Sebastian Sastre Aug. 18, 2009

Aug. 18, 2009

Hi there, in order to be able to load SIXX 0.95 from universal installer I've needed to unelegantly patch it (a pharo 413) to: contentType: aString content: content "create a MIMEObject with the given content-type and content" "MIMEObject contentType: 'text/plain' content: 'This is a test'" | ans idx | ans := self new. ans privateContent: content. "parse the content-type" (aString isNil or: [ idx := aString asString indexOf: $/. idx = 0]) ifTrue: [ ans type: (MIMEType main: 'application' sub: 'octet-stream')] ifFalse: [ ans type: (MIMEType main: (aString asString copyFrom: 1 to: idx-1) sub: (aString asString copyFrom: idx+1 to: aString asString size))]. ^ans sebastian

2 1

[Pharo-project] Slime and '#fixCallbackTemps possibly missing'
by Stan Shepherd Aug. 18, 2009

Aug. 18, 2009

Hi, one of the Slime error checks throws the warning '#fixCallbackTemps possibly missing'. Am I right in thinking I can ignore this in the Seaside one click image? Thanks ...Stan -- View this message in context: http://n2.nabble.com/Slime-and-%27-fixCallbackTemps-possibly-missing%27-tp3… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 3

[Pharo-project] Preference browser does not load from disk
by csrabak＠bol.com.br Aug. 18, 2009

Aug. 18, 2009

2 2