November 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] About keyboard event :(

by StÃ©phane Ducasse

Hi guys I'm looking for the following information and I do not find it. I thought that I could ask a keyboardEvent for the character I typed in the following case: When I press shift ' I should obtain " self keyValue 39 but Character value: 39 is ' and not double quote self keyCharacter $' self modifiedCharacter $' but this is wrong modifiedCharacter self flag: #hack. "Hack me. When Ctrl is pressed, the key ascii value is not right and we have to do something ugly" ^(self controlKeyPressed and: [ (#(MacOSX Windows) includes: Smalltalk os current platformFamily) and: [ keyValue <= 26 ]]) ifTrue: [ (self keyValue + $a asciiValue - 1) asCharacter ] ifFalse: [ self keyCharacter ] Frankly the event logic is messy. I do not understand, why we cannot have ' the key that was pressed and shift and also " as an interpretation and that the system should not be most of the time using this high level operation. Then I do not understand why when I pressed shift ' I get a CMD -'>' character it looks so bogus. When I see performCmdActionsWith: aKeyboardEvent shifted: aBoolean return: return | asciiValue actions action| asciiValue := aKeyboardEvent keyValue + 1. ^^^^^^^^^^^^^ hardcoded in the smalltalkEditor logic actions := aBoolean ifTrue: [self class shiftCmdActions] ifFalse: [self class cmdActions]. action := (actions at: asciiValue). action == #noop: ifTrue: [ ^ false ]. return value: ( self perform: action with: aKeyboardEvent). and this really ugly code breaking any principle of layeringâ¦. dispatchCommandOn: aKeyboardEvent return: return |asciiValue honorCommandKeys char| asciiValue := aKeyboardEvent keyValue. honorCommandKeys := self cmdKeysInText. "Special keys overwrite crtl+key combinations - at least on Windows. To resolve this conflict, assume that keys other than cursor keys aren't used together with Crtl." ((self class specialShiftCmdKeys includes: asciiValue) and: [ asciiValue < 27]) ifTrue: [ ^ self performCmdActionsWith: aKeyboardEvent shifted: aKeyboardEvent controlKeyPressed return: return]. "backspace, and escape keys (ascii 8 and 27) are command keys" ((honorCommandKeys and: [aKeyboardEvent commandKeyPressed]) or: [self class specialShiftCmdKeys includes: asciiValue]) ifTrue: [ ^ self performCmdActionsWith: aKeyboardEvent shifted: aKeyboardEvent shiftPressed return: return]. "the control key can be used to invoke shift-cmd shortcuts" (honorCommandKeys and: [aKeyboardEvent controlKeyPressed]) ifTrue: [ ^ self performCmdActionsWith: aKeyboardEvent shifted: true return: return]. ^ false Then of course shiftEnclose: aKeyboardEvent "Insert or remove bracket characters around the current selection." | char left right startIndex stopIndex oldSelection which text | char := aKeyboardEvent keyCharacter. char = $9 ifTrue: [ char := $( ]. char = $, ifTrue: [ char := $< ]. char = $[ ifTrue: [ char := ${ ]. char = $' ifTrue: [ char := $" ]. And in addition smart character use characters while textEditor methods such as enclose: â¦. require a keyboardEvent. I will start to fix that part so that we can think a bit instead of been block in a rat hole. Stef

Nov. 27, 2012

Re: [Pharo-project] just help :)

by Sven Van Caekenberghe

Hi Sebastion, Excellent ! Please go ahead ;-) Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill On 27 Nov 2012, at 19:56, Sebastian Nozzi <sebnozzi(a)gmail.com> wrote: >> 2012/11/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> just help :) > > This is what I would like to get involved in. Hopefully it can benefit > the project. > > In order of personal interest: > > == > > 1) Positioning Pharo as THE language to learn programming. With a "fun" touch. > > Smalltalk is still an excellent language/environment to learn > programming and I think: if it can be learnt while having fun, the > better! > > My idea is to write simple game-programming tutorials (board games, > puzzles, etc. like this - http://inventwithpython.com/ - but cooler). > I already started working on this, that's why I bugged you guys with > Morphic questions in the past. > > What I would like to offer is the knowledge and tools to use Pharo as > a post-Scratch (http://scratch.mit.edu/) for creative projects (games, > animations, stories, etc.). Conceptually similar to: > http://www.greenfoot.org/home - only it would be it would be Smalltalk > based ;-D. > > I also would love to write educational software (disclaimer: I'm not a > school teacher or anything similar - although I imagine getting > involved in the area). > > From the spirit I know that maybe Squeak is more the place to go... > And also that Pharo aims to be more enterprise/research oriented. I > don't discard my code running in Squeak, but I just happen to find > Pharo easier to use / develop in. > > == > > 2) Writing small (but attractive/useful) sample apps > > ... to be useful for people/small companies and get devs hooked > (return-on-investment might be low?). > > Examples: a TestLink clone, a time-tracker, a corporate > contact-database, a room reservation system, etc. > > The idea is to use these apps as "troyan horses", and get devs > interested in Smalltalk/Pharo (the apps would be free and open-source, > to guarantee usage/adoption). Maybe to extend / customize them for > their needs. Increase mind-share (I assure you, it's needed! None of > my past/current colleagues knew what Smalltalk was, some confused it > with Lisp). > > But I'm sure this won't happen without... > > == > > 3) Writing (documenting) Pharo > > From an "enterprise" point of view (how can I do X, because I need > this for a real-life project asap?). > > I think there is a lot of work to be done here also. Documenting > classes, working on external documentation. Like how to interact with > OS processes/io, databases, deployment strategies, persistence > strategies, how to work in a team, etc. > > For this I would like to collaborate in the "collaborative book". I > already have a list of things that could be added/improved, and I > think I would also learn a lot in the process. The only thing that > worries me is me not being a native English speaker (writer). > > == > > Some work involved in these areas overlap. Ideally I would combine all three. > > So, these are the areas I would like to get involved in. It would be > great if it could benefit the project at large :-) > > Best regards, > > > Sebastian >

Nov. 27, 2012

Re: [Pharo-project] GSoC: ARM jitter for Squeak VM

by Eliot Miranda

On Fri, Nov 23, 2012 at 12:56 PM, Carla F. Griggio <carla.griggio(a)gmail.com>wrote: > Hello! > I'm copying Lars and Eliot, who worked on this project during the summer, > so maybe they can update everyone on the state of the project. > It is in progress. Lars has completed the code generator and is working on the C calling interface. There are some changes required to the inline cache machinery to accomodate the ARM's use of a link register (essentially the contents of the link register needs to be pushed on and popped from the stack at the right points so that the rest of the VM sees the same stack layout as on x86). So the system isn't ready yet, but it isn't a long way away either. Lars is actively working on it when time allows. HTH Eliot > > Cheers, > Carla. > > > On Fri, Nov 23, 2012 at 12:04 PM, Frank Shearar <frank.shearar(a)gmail.com>wrote: > >> On 23 November 2012 10:49, Dan Corneanu <cdan(a)savatech.ro> wrote: >> > Hi, >> > I would really like to have a CogVM for ARM. I am a rookie in this >> field but I >> > own a raspberry pi and would love to help in any way possible to move >> this >> > forward. Testing maybe ? >> >> The interpreter VM works perfectly on the Raspberry, so you can at >> least get your Smalltalk fix while folks work on Cog. >> >> frank >> >> > -- best, Eliot

Nov. 27, 2012

[Pharo-project] just help :)

by Sebastian Nozzi

> 2012/11/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > just help :) This is what I would like to get involved in. Hopefully it can benefit the project. In order of personal interest: == 1) Positioning Pharo as THE language to learn programming. With a "fun" touch. Smalltalk is still an excellent language/environment to learn programming and I think: if it can be learnt while having fun, the better! My idea is to write simple game-programming tutorials (board games, puzzles, etc. like this - http://inventwithpython.com/ - but cooler). I already started working on this, that's why I bugged you guys with Morphic questions in the past. What I would like to offer is the knowledge and tools to use Pharo as a post-Scratch (http://scratch.mit.edu/) for creative projects (games, animations, stories, etc.). Conceptually similar to: http://www.greenfoot.org/home - only it would be it would be Smalltalk based ;-D. I also would love to write educational software (disclaimer: I'm not a school teacher or anything similar - although I imagine getting involved in the area). >From the spirit I know that maybe Squeak is more the place to go... And also that Pharo aims to be more enterprise/research oriented. I don't discard my code running in Squeak, but I just happen to find Pharo easier to use / develop in. == 2) Writing small (but attractive/useful) sample apps ... to be useful for people/small companies and get devs hooked (return-on-investment might be low?). Examples: a TestLink clone, a time-tracker, a corporate contact-database, a room reservation system, etc. The idea is to use these apps as "troyan horses", and get devs interested in Smalltalk/Pharo (the apps would be free and open-source, to guarantee usage/adoption). Maybe to extend / customize them for their needs. Increase mind-share (I assure you, it's needed! None of my past/current colleagues knew what Smalltalk was, some confused it with Lisp). But I'm sure this won't happen without... == 3) Writing (documenting) Pharo >From an "enterprise" point of view (how can I do X, because I need this for a real-life project asap?). I think there is a lot of work to be done here also. Documenting classes, working on external documentation. Like how to interact with OS processes/io, databases, deployment strategies, persistence strategies, how to work in a team, etc. For this I would like to collaborate in the "collaborative book". I already have a list of things that could be added/improved, and I think I would also learn a lot in the process. The only thing that worries me is me not being a native English speaker (writer). == Some work involved in these areas overlap. Ideally I would combine all three. So, these are the areas I would like to get involved in. It would be great if it could benefit the project at large :-) Best regards, Sebastian

Nov. 27, 2012

Re: [Pharo-project] Athens OpenGL backend - what does it mean?

by Sebastian Nozzi

2012/11/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > May be you did not see it but adding polymorph was the first things we did > even if the code was not perfect. No no, I realized the addition of Polymorph. Although it is only now that I am starting to get active in open-source Smalltalk, I have been following it since the days of Squeak 3.X (maybe earlier - I heard about Smalltalk for the first time in 1998). I lived through the announcement of Pharo (without understanding, at that time, why all the fuzz). In my head I kept coming and going to/from Smalltalk, never being able to give it up ;-) No matter how hard I tried, or how disappointed I sometimes was, I was also hooked. I knew somewhere that there is something true and unique to it. My heart was/is somehow tied to Smalltalk, I guess, even if I'm painfully aware of many of its (current) shortcomings... But I digress... Yes, I noticed about Polymorph. > I often said to my students if you want to faint or vomit when you open > Squeak (at that time I was maintaining squeak3.8or9) then this is normal > we are working on it and one day it will be cool. Hahaha! Well, it definitely looks ahem... different... than anything out there. But Squeak also took notice and somehow improved its looks a little bit in the last versions (since 4.2 or so). It took a lot of "faith", I guess. To look it to the face and in spite of the visual shortcomings say: but it will look cool in the future. Sometimes I think it would be awesome to be able to attract great designers. So many people designing great web-widgets, or Gnome/KDE skins, or even Winamp Skins... The visual aspect must not be underestimated. Fortunately Pharo right now has, for me, reached the state where I "can live with it" (visually). One thing I would like to investigate is how easy (or not) is to write new Polymorph-aware widgets. > So these is years that I want to get a vector graphics based ui and a lot more :) That's great :-) > just help :) > There are a lot of little tasks that can help us. > Like checking if a bug is still a bug in the current version. > I'm still learning a lot by trying (and I fail often) to fix something but I nearly always learn something. Since you mention "helping" I would like to take this opportunity to mention what my plans for Smalltalk/Pharo are, and see if it can be beneficial to the project. For this, I better create a new topic...

Nov. 27, 2012

[Pharo-project] Halo fly by help broken: an analysis -> MorphicEventHandler is not initialized

by StÃ©phane Ducasse

Nov. 27, 2012

Re: [Pharo-project] Getting started with Athens

by Esteban Lorenzano

be sure to install the 32bits version On Nov 27, 2012, at 5:37 PM, Sebastian Nozzi <sebnozzi(a)gmail.com> wrote: > Hello Araya, > > you might still need to install the library for your host operating system. > > See here: > > http://www.pharocasts.com/2012/06/athens-and-native-boost-at-work.html > > For Debian/Ubuntu systems you would need to do: > > apt-get install libcairo2 # as root in Debian > > Or: > > sudo apt-get install libcairo2 # as non-root in Ubuntu > > Hope this helps! > > Sebastian > > P.S. Future versions of Pharo, if I'm not mistaken, will include this > dependency... ? > > > 2012/11/27 Vanessa PeÃ±a Araya <van.c.pena(a)gmail.com>: >> Hi, >> >> I'm trying to get started with Athens but I'm having the following errors: >> >> Pharo 1.4, loaded last version configurationOfAthens: >> 'failed to get a symbol address: cairo_image_surface_create' >> >> I also tried in this in a 2.0 image and I got the same error. >> >> I'm trying with this VM: >> >> https://ci.lille.inria.fr/pharo/view/Cog/job/NativeBoost-Cog-VM/Architectur… >> >> Any help, please? :) >> >> Thanks, >> Vanessa. >

Nov. 27, 2012

Re: [Pharo-project] Getting started with Athens

by Sebastian Nozzi

Sorry... I meant "Hello Vanessa" ;-) 2012/11/27 Sebastian Nozzi <sebnozzi(a)gmail.com>: > Hello Araya,

Nov. 27, 2012

Re: [Pharo-project] Getting started with Athens

by Sebastian Nozzi

Hello Araya, you might still need to install the library for your host operating system. See here: http://www.pharocasts.com/2012/06/athens-and-native-boost-at-work.html For Debian/Ubuntu systems you would need to do: apt-get install libcairo2 # as root in Debian Or: sudo apt-get install libcairo2 # as non-root in Ubuntu Hope this helps! Sebastian P.S. Future versions of Pharo, if I'm not mistaken, will include this dependency... ? 2012/11/27 Vanessa PeÃ±a Araya <van.c.pena(a)gmail.com>: > Hi, > > I'm trying to get started with Athens but I'm having the following errors: > > Pharo 1.4, loaded last version configurationOfAthens: > 'failed to get a symbol address: cairo_image_surface_create' > > I also tried in this in a 2.0 image and I got the same error. > > I'm trying with this VM: > > https://ci.lille.inria.fr/pharo/view/Cog/job/NativeBoost-Cog-VM/Architectur… > > Any help, please? :) > > Thanks, > Vanessa.

Nov. 27, 2012

[Pharo-project] Getting started with Athens

by Vanessa PeÃ±a Araya

Hi, I'm trying to get started with Athens but I'm having the following errors:<https://ci.lille.inria.fr/pharo/view/Cog/job/NativeBoost-Cog-VM/Architectur…> Pharo 1.4, loaded last version configurationOfAthens: 'failed to get a symbol address: cairo_image_surface_create' I also tried in this in a 2.0 image and I got the same error. I'm trying with this VM: https://ci.lille.inria.fr/pharo/view/Cog/job/NativeBoost-Cog-VM/Architectur… Any help, please? :) Thanks, Vanessa.

Nov. 27, 2012