June 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] roadmap for 1.4

by Yanni Chiu

On 19/06/11 1:27 AM, Pavel Krivanek wrote: > Hi, > > I think that the best idea is to have one image for the system > developers and end-users (for example, I almost never used full Pharo so > it lost one tester). On the other hand we should continue with the > modularization to allow to generate headless kernel image, gopher image, > basic morphic image etc. on the request with bootstrapping. To have > smallest possible image is not the main goal of the effort around > PharoKernel. The main goal is to have beauty modular system where all > dependencies all described well and packages can be easily loaded and > unloaded. The buildserver can generate all the set of images for special > purposes so it will be more natural then now when we have two main images. +1 Me too - I never use full Pharo. I build the image I want from Core. If there were a suitable special purpose image built as outlined above, then that image would be my new starting point. If not, then I guess I would have to start from whatever Core+Dev image results from the process, and then unload stuff (or, if it isn't too big, use it as is).

June 19, 2011

[Pharo-project] ESUG 2011 Innovation Technology Awards reminder

by Jordi Delgado

Hi, Just a reminder: ESUG 2011 Innovation Technology Awards (http://esug.org/Conferences/2011/InnovationTechnologyAwards) We are proud to announce the 8th Innovation Technology Awards. Have you written innovative Smalltalk? The developers of any Smalltalk-based software can enter by submitting a 3-5min video of their software. Entrants demo their systems in a session at the end of Monday August 22nd 2011, after which the conference attendees vote. (A vote consists in providing a sorted list of 3 preferred pieces of software.) The top 3 teams with the most innovative software will receive, respectively, 500 Euros, 300 Euros and 200 Euros. The results are announced in the Awards ceremony that is held during the social event. Applicants should provide the following information on the conference registration server. Once you have registered your personal info, an "Awards" menu allows submitting your software. You can provide this information when you first register, or login again later and update your details. Info to provide: Name of the software Licence information (free, or shareware, or a commercial) Name of the Smalltalk dialect used Names, Affiliation and Country of developers URL for a video (3-5 min) showing a screencast / demo of the software URL for downloading the software or at least a runnable demo Deadline: 30th of july Any Smalltalker can apply (students, companies, ...). The presented piece of code/software should be written in Smalltalk or directly support Smalltalk (e.g. Smalltalk VM). All Smalltalk dialects are accepted. The applicant should own the copyright/copyleft of presented code or at least be the official representative of the copyright/copyleft owner. The software should be available on-line for evaluation (time-limited evaluation version, demo version, free for non-commercial use ...). Bests, Jordi

June 19, 2011

Re: [Pharo-project] roadmap for 1.4

by Pavel Krivanek

Hi, I think that the best idea is to have one image for the system developers and end-users (for example, I almost never used full Pharo so it lost one tester). On the other hand we should continue with the modularization to allow to generate headless kernel image, gopher image, basic morphic image etc. on the request with bootstrapping. To have smallest possible image is not the main goal of the effort around PharoKernel. The main goal is to have beauty modular system where all dependencies all described well and packages can be easily loaded and unloaded. The buildserver can generate all the set of images for special purposes so it will be more natural then now when we have two main images. -- Pavel 18.6.2011 v 22:29, Guillermo Polito <guillermopolito(a)gmail.com>: > Hi Stef! > > do you mean integrating all them in the Core? Or maybe follow Markus' idea of having just one image? Maybe that's an important discussion to have too :). > I can give a hand for the repository stuff. Should we replicate repositories + metacello configs in order to be able to freeze them, isn't it? > > Guille > > On Sat, Jun 18, 2011 at 9:59 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > here is a kind of dump of roadmap for 1.4 first level is to make sure that we have only one single image. > > - load FileSystem > -> so that we can start to integrate and improve the fileSystem API > > - Load shout, Ocompletion, RBEngine (not OB) so that we can change what should be changed for RPackage to work > > - Ring > -> so that we can start to integrate it > > - Fuel > -> so that we can deprecate SmartRefStream (there may be a problem with mcz (not sure)). > > - I want Opal in 1.4 too. > > - continue to remove StringHolder hierarchy > > - Morphic improvements > > Comments are welcomed. > > Stef > > >

June 19, 2011

Re: [Pharo-project] User-friendly FFI (was Re: roadmap for 1.4)

by laurent laffont

On Sat, Jun 18, 2011 at 5:59 PM, Dave Mason <dmason(a)mason-rose.ca> wrote: > > On 2011-Jun-18, at 9:07 , laurent laffont wrote: > > + a FFI that a stupid idiot like me can use >> > > I'm working on it, aiming for a paper at IWST. I posted a request for > opinion and help on this yesterday, but got little response (perhaps because > it was part of another thread). > Thank you for this work. The most important for me is to be able to use yaz / Z39.50 (http://www.indexdata.com/yaz) on Linux at least, but my tries have always end to a vm crash ...... Laurent. > > See: http://lists.gforge.inria.fr/**pipermail/pharo-project/2011-** > June/050298.html<http://lists.gforge.inria.fr/pipermail/pharo-project/2011-June/050298.html> > > ../Dave > >

June 18, 2011

Re: [Pharo-project] roadmap for 1.4

by Guillermo Polito

Hi Stef! do you mean integrating all them in the Core? Or maybe follow Markus' idea of having just one image? Maybe that's an important discussion to have too :). I can give a hand for the repository stuff. Should we replicate repositories + metacello configs in order to be able to freeze them, isn't it? Guille On Sat, Jun 18, 2011 at 9:59 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi guys > > here is a kind of dump of roadmap for 1.4 first level is to make sure that > we have only one single image. > > - load FileSystem > -> so that we can start to integrate and improve the fileSystem API > > - Load shout, Ocompletion, RBEngine (not OB) so that we can change what > should be changed for RPackage to work > > - Ring > -> so that we can start to integrate it > > - Fuel > -> so that we can deprecate SmartRefStream (there may be a problem > with mcz (not sure)). > > - I want Opal in 1.4 too. > > - continue to remove StringHolder hierarchy > > - Morphic improvements > > Comments are welcomed. > > Stef > > >

June 18, 2011

Re: [Pharo-project] why (UIManager default newPluggableDialogWindow: 'Pharo is cool') openInWorld

by Alexandre Bergel

Hi Stef, I have no idea about the answers to your question. But looking into this is important. Cheers, Alexandre On 18 Jun 2011, at 15:02, StÃ©phane Ducasse wrote: > > On Jun 18, 2011, at 7:58 PM, stephane ducasse wrote: > >> why >> >> (UIManager default >> newPluggableDialogWindow: 'Pharo is cool') openInWorld >> >> does not work? >> Apparently MorphicUIManager is missing something? >> Stef >> > > > (ExampleBuilderMorph new newPluggableDialogWindow: 'Pharo is cool') openInWorld > > is working because ExampleBuilderMorph inherits from Morph and not from Object > > (UITheme builder > newPluggableDialogWindow: 'Pharo is cool'; > minimumExtent: 200@300) openInWorld > > similarly. > > Now there is something that I do not understand. > What is the use of the builder since I cannot pass it specific setting > > > (UITheme builder > newPluggableDialogWindow: 'Pharo is cool' > for: (RectangleMorph new); > beUnresizeable <<< does not work because the builder (a ComposableMorph does not pass such setting to the PluggableDialogWindow. > ) openInWorld > > I would really like to have a nice kernel that support well such approach. > In fact I imagine that we should not use UITheme builder that way. > > > Stef -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 18, 2011

Re: [Pharo-project] Integer>>#factorial

by Andres Valloud

But unfortunately we do not have tail recursion (that I know)... On 6/16/11 10:46 , Lorenzo Schiavina wrote: > IMHO factorial is a good OO example because you have not the usual > limitation of "traditional" languages and you can understand the OOP power. > Try, for example 1000 factorial in ST and in other languages. > Cheers > Lorenzo > > ----- Original Message ----- > *From:* Hernan Wilkinson <mailto:hernan.wilkinson@10pines.com> > *To:* Pharo-project(a)lists.gforge.inria.fr > <mailto:Pharo-project@lists.gforge.inria.fr> > *Sent:* Thursday, June 16, 2011 5:03 PM > *Subject:* Re: [Pharo-project] Integer>>#factorial > > I agree with Alex, but I don't see why, alex, you say it is a good > example for teaching OO (the smalltalk factorial implementation...) > For me is a good example of a recursive "function" > I think it would be a good OO example it it was using "object > recursion" or the one that could be implemented in a prototyped > language... why do you think it is a good oo example the smalltalk > factorial implementation? > > On Thu, Jun 16, 2011 at 9:52 AM, Alexandre Bergel > <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: > > Hi Sven, > > I am not sure it should replace the standard implementation. > Integer>>factorial is essentially there for teaching purpose in > my opinion. I am not sure how often factorial is used in > practice. The most important for me is not it to be fast, but to > be an excellent example of OOP. > > Your implementation could be next to the standard one though. > > Cheers, > Alexandre > > > On 16 Jun 2011, at 06:38, Sven Van Caekenberghe wrote: > > > Hi, > > > > On Planet Smalltalk I read about this challenge: > http://www.parcplace.net/list/vwnc-archive/1106/msg00080.html > the goal being to optimize the current, naive > Integer>>#factorial implementation. > > > > I had some old Lisp code hanging around, implementing an > algorithm that I once found somewhere, and I ported it to > Smalltalk. I am sure there are faster solutions, but this one is > twice as fast as the original while still being easy to > understand and it has a useful, safe helper method: > > > > Integer>>#svcFactorial > > "Answer the factorial of the receiver." > > > > self = 0 ifTrue: [ ^ 1 ]. > > self > 0 ifTrue: [ ^ 1 productUpTo: self ]. > > self error: 'Not valid for negative integers' > > > > Integer>>#productUpTo: anInteger > > "Answer the product of all integers from the receiver > (non-inclusive) up to anInteger (inclusive)." > > > > | difference split | > > self assert: (self between: 0 and: anInteger). > > "the idea is to multiply LargePositiveIntegers of > approximately the same size" > > difference := anInteger - self. > > difference = 0 ifTrue: [ ^ 1 ]. > > difference = 1 ifTrue: [ ^ anInteger ]. > > difference = 2 ifTrue: [ ^ (anInteger - 1) * anInteger ]. > > difference = 3 ifTrue: [ ^ (anInteger - 2) * (anInteger - 1) > * anInteger ]. > > difference = 4 ifTrue: [ ^ (anInteger - 3) * (anInteger - 2) > * (anInteger - 1) * anInteger ]. > > split := (self + anInteger) bitShift: -1. > > ^ (self productUpTo: split) * (split productUpTo: anInteger) > > > > Would it be a good idea to replace the current implementation > with this one ? > > > > Sven > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > -- > *HernÃ¡n Wilkinson > Agile Software Development, Teaching & Coaching > Mobile: +54 - 911 - 4470 - 7207 > email: hernan.wilkinson(a)10Pines.com > site: http://www.10Pines.com <http://www.10pines.com/>* >

June 18, 2011

[Pharo-project] addCloseBox

by StÃ©phane Ducasse

Hi does anybody have an idea why the close box does not get added? (PluggableDialogWindow new title: 'Pharo is cool'; addCloseBox) openInWorld Stef

June 18, 2011

Re: [Pharo-project] why (UIManager default newPluggableDialogWindow: 'Pharo is cool') openInWorld

by StÃ©phane Ducasse

On Jun 18, 2011, at 7:58 PM, stephane ducasse wrote: > why > > (UIManager default > newPluggableDialogWindow: 'Pharo is cool') openInWorld > > does not work? > Apparently MorphicUIManager is missing something? > Stef > (ExampleBuilderMorph new newPluggableDialogWindow: 'Pharo is cool') openInWorld is working because ExampleBuilderMorph inherits from Morph and not from Object (UITheme builder newPluggableDialogWindow: 'Pharo is cool'; minimumExtent: 200@300) openInWorld similarly. Now there is something that I do not understand. What is the use of the builder since I cannot pass it specific setting (UITheme builder newPluggableDialogWindow: 'Pharo is cool' for: (RectangleMorph new); beUnresizeable <<< does not work because the builder (a ComposableMorph does not pass such setting to the PluggableDialogWindow. ) openInWorld I would really like to have a nice kernel that support well such approach. In fact I imagine that we should not use UITheme builder that way. Stef

June 18, 2011

[Pharo-project] why (UIManager default newPluggableDialogWindow: 'Pharo is cool') openInWorld

by stephane ducasse

why (UIManager default newPluggableDialogWindow: 'Pharo is cool') openInWorld does not work? Apparently MorphicUIManager is missing something? Stef

June 18, 2011