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

Re: [Pharo-project] Demo mode in Pharo

by Igor Stasenko

On 28 April 2010 12:21, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> Hi, >>> i'm looking for a way to put Pharo in demo mode with large fonts. >>> There is a menu item in Squeak but i found nothing in Pharo. >>> >> Hi Serge, >> >> in Pharo 1.0 >> Preferences setDemoFonts >> >> in Pharo 1.1 >> from the setting browser, >> style button (top button bar) then load item then you choose demo mode. >> or >> DemoSettingStyle new load > > it would be cool to have a menu like in the old squeak. > it would be cool to have UI zoomable, so you just zoom-in the stuff and don't care about changing font sizes :) > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

April 28, 2010

Re: [Pharo-project] Demo mode in Pharo

by StÃ©phane Ducasse

>> Hi, >> i'm looking for a way to put Pharo in demo mode with large fonts. >> There is a menu item in Squeak but i found nothing in Pharo. >> > Hi Serge, > > in Pharo 1.0 > Preferences setDemoFonts > > in Pharo 1.1 > from the setting browser, > style button (top button bar) then load item then you choose demo mode. > or > DemoSettingStyle new load it would be cool to have a menu like in the old squeak. Stef

April 28, 2010

Re: [Pharo-project] Demo mode in Pharo

by Serge Stinckwich

Ok thank you Alain. Maybe we should add these information in the FAQ ;-) On Wed, Apr 28, 2010 at 4:03 PM, Alain Plantec <alain.plantec(a)free.fr> wrote: > Serge Stinckwich a Ã©crit : >> >> Hi, >> i'm looking for a way to put Pharo in demo mode with large fonts. >> There is a menu item in Squeak but i found nothing in Pharo. >> > > Hi Serge, > > in Pharo 1.0 > Preferences setDemoFonts > > in Pharo 1.1 > from the setting browser, > style button (top button bar) then load item then you choose demo mode. > or > DemoSettingStyle new load > > Alain >> >> Thank you. >> Best regards, >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

April 28, 2010

Re: [Pharo-project] Demo mode in Pharo

by Alain Plantec

Serge Stinckwich a Ã©crit : > Hi, > i'm looking for a way to put Pharo in demo mode with large fonts. > There is a menu item in Squeak but i found nothing in Pharo. > Hi Serge, in Pharo 1.0 Preferences setDemoFonts in Pharo 1.1 from the setting browser, style button (top button bar) then load item then you choose demo mode. or DemoSettingStyle new load Alain > Thank you. > Best regards, >

April 28, 2010

Re: [Pharo-project] Condensing Changes File

by StÃ©phane Ducasse

> Hi! > > Apparently, the change file cannot be condensed in Core 1.1 anymore. I am the only one to experience this? > > Mariano, maybe we could remove temporarily the change condensing from ConfigurationOfPharo? > > It can be done, but I don't like this option of "hiding" or disabling the problems. With this, the bug may be forgotten or loose attention. > If every time to try to build a PharoDev 1.1 on top of a PharoCore 1.1 you get this error, someone will probably fix it ;) this is a severe one it crashes :) Stef

April 28, 2010

[Pharo-project] Demo mode in Pharo

by Serge Stinckwich

Hi, i'm looking for a way to put Pharo in demo mode with large fonts. There is a menu item in Squeak but i found nothing in Pharo. Thank you. Best regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

April 28, 2010

Re: [Pharo-project] Condensing Changes File

by Mariano Martinez Peck

On Tue, Apr 27, 2010 at 9:55 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Hi! > > Apparently, the change file cannot be condensed in Core 1.1 anymore. I am > the only one to experience this? > > Mariano, maybe we could remove temporarily the change condensing from > ConfigurationOfPharo? > It can be done, but I don't like this option of "hiding" or disabling the problems. With this, the bug may be forgotten or loose attention. If every time to try to build a PharoDev 1.1 on top of a PharoCore 1.1 you get this error, someone will probably fix it ;) Cheers Mariano > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 28, 2010

Re: [Pharo-project] FFI in 1.1

by Igor Stasenko

On 28 April 2010 10:24, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Igor, I was wondering whether you or somebody else have a real example where NativeBoost boosts performance. For instance in an often used library class... > It depends. I provided comparisons before. But if you have any real-world example in mind, i will happily implement it and give you the numbers. Apparently there is nothing else, which can run faster than native code. I'm giving you control to implement own primitives using native code. As for FFI interface you will have a full control on how to coerce types between C and Smalltalk worlds and so, it will run as fast as you made it. :) For example, here the FFI plugin code which coercing a smalltalk object to integer value for pushing it on stack: ffiIntegerValueOf: oop "Support for generic callout. Return an integer value that is coerced as C would do." | oopClass | self inline: true. (interpreterProxy isIntegerObject: oop) ifTrue:[^interpreterProxy integerValueOf: oop]. oop == interpreterProxy nilObject ifTrue:[^0]. "@@: should we really allow this????" oop == interpreterProxy falseObject ifTrue:[^0]. oop == interpreterProxy trueObject ifTrue:[^1]. oopClass := interpreterProxy fetchClassOf: oop. oopClass == interpreterProxy classFloat ifTrue:[^(interpreterProxy floatValueOf: oop) asInteger]. oopClass == interpreterProxy classCharacter ifTrue:[^interpreterProxy fetchInteger: 0 ofObject: oop]. oopClass == interpreterProxy classLargePositiveInteger ifTrue:[^interpreterProxy positive32BitValueOf: oop]. ^interpreterProxy signed32BitValueOf: oop "<- will fail if not integer". See , how generic it is? It tries to accept every possible combination which could be translated to native integer value. Now, suppose, that you know _exactly_ that your function will be called only with smallintegers as arguments, and want to fail primitive if it get called with wrong argument. This is what you can do with NativeBoost, but you can't with FFI, because it is C code, compiled and made in stone. > Cheers, > Adrian > -- Best regards, Igor Stasenko AKA sig.

April 28, 2010

[Pharo-project] Xemina Pharo, HÃ ná»i, Viá»t Nam

by Serge Stinckwich

Hi all, i will made a talk about Pharo tomorrow at Viá»n tin há»c phÃ¡p ngá»¯, ngÃµ 42 Táº¡ Quang Bá»u, HÃ ná»i, Viá»t Nam. Regards, ----------- Bonjour Ã tous, Xin chao quy vi, SÃ©minaire IFI du jeudi 29 avril 2010 Ã 14h00 Xemina tai IFI, thu 4 ngay 29 thang 4 2010, luc 14h00 PrÃ©sentÃ© par: Serge Stinckwich Chercheur, UMMISCO, IRD / IFI Nguoi trinh bay: Serge Stinckwich Chercheur, UMMISCO, IRD / IFI Titre : Pharo: an open-source Smalltalk RÃ©sumÃ© : Smalltalk is a dynamic reflective object-oriented programming language. Based at the beginning on Lisp and Simula, it was one of the first programming language to use a bitmap user-interface and an integrated development environment (IDE). Smalltalk has been a great influence in the development of many programming languages, including Objective-C, Java and Ruby. Many innovations in software engineering in the nineties also come from the Smalltalk community, such as Design Patterns, test-driven approach, agile software development like Extreme Programming (XP) and code refactoring. Pharo is a new open-source Smalltalk (under a MIT licence). Pharo's objective is to provide a clean, open-source and innovative Smalltalk implementation with suitable for research and business applications. Several companies and universities are using Pharo for their software development. More information are available here: http://pharo-project.org/ and http://pharobyexample.org/ -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

April 28, 2010

Re: [Pharo-project] FFI in 1.1

by Adrian Lienhard

Igor, I was wondering whether you or somebody else have a real example where NativeBoost boosts performance. For instance in an often used library class... Cheers, Adrian On Apr 27, 2010, at 23:26 , Igor Stasenko wrote: > On 28 April 2010 00:14, Bryce Kampjes <bryce(a)kampjes.demon.co.uk> wrote: >> On Mon, 2010-04-26 at 11:24 +0300, Igor Stasenko wrote: >>> On 26 April 2010 10:57, Lukas Renggli <renggli(a)gmail.com> wrote: >>>> Igor, >>>> >>>> Looks cool, but I really would like to know the exact difference to Exupery? >>>> >>>> For what I understand NativeBoost is no different to Exupery's >>>> low-level code generation infrastructure. >>> >>> You are free to use any code generator you want. NativeBoost plugin is >>> really dumb and will run your code at your will. >>> I am using AsmJit, because its small and dumb too. Mainly its just an >>> x86/x64 instruction database with >>> some convenience class(es) and methods to generate instructions directly. >>> In contrast, Exupery is a full-blown compiler, but supports a very >>> small subset of x86 instructions. >>> Actually, i think that with some effort, an Exupery could use AsmJit as backend. >>> Not sure, if Bryce likes this idea :) >>> >> >> It sounds like NativeBoost is rather similar to Exupery's lower levels. >> Exupery can replace individual methods with native code. >> >> Exupery's design supports the easy removal of all native code which is >> necessary when saving the image if it might be loaded on a platform or >> by a VM which can not run x86 machine code. >> > > NativeBoost does it a bit differently. Each piece of native code > having a special marker - platform id, > which is checked before entering native code. > If native code platform id matching the platform id of currently > running VM, then native code is allowed to run, > and if not, then primitive are just failing, refusing to run it. > In this way, a native code can be saved in image, but having no > chances to run on a wrong target platform. > >> The VM hooks are rather small and the code generator is reasonably small >> and simple. Exploring multiple approaches may be more valuable than >> saving a small amount of duplicate effort. >> > >> Bryce >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 28, 2010