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

[Pharo-project] a probably stupid question on canvas
by StÃ©phane Ducasse Nov. 28, 2012

Nov. 28, 2012

Hi guys I was wondering why we need a separate class named AlphaBlendingCanvas Igor can you have a look and depending on your answer I will put it on my todo list. Stef ?

2 4

[Pharo-project] who are "cipt" and "tbh"?
by Esteban Lorenzano Nov. 28, 2012

Nov. 28, 2012

Hi, Can I ask people to use real names instead name initials? Otherwise I get lost about who pushes changes :) Esteban

2 1

[Pharo-project] [ANN] NativeBoost v 1.7
by Igor Stasenko Nov. 28, 2012

Nov. 28, 2012

Hi, there i'd like to announce new version of NativeBoost - 1.7. Here's an overview of changes comparing to previous version: - indirect argument in signatures. You can now use special syntax to indicate that argument to external function should be taken from n-th element of variable object (like Array) from method's argument or instance variable. Syntax: myMethod: args <primitive: .... > ^ self nbCall: #( void funFoo( int args@1 , float args@2 )) Usage: self myMethod: { 1 . 1.2 } Thanks to Ciprian Teodorov who proposed and implemented it. - Win32, features and examples: NBWin32Shell - an interface to use windows shell api (executing commands, showing control panel settings) different examples for using HDC, message box etc. Thanks to Torsten Bergmann for contribution! And last bits, from me: A public API changes to avoid use of NBFFICallout global, and instead use message(s) to denote FFI callout. Old syntax: NBFFICallout cdecl: #(...) emitCall: [ â¦ ] New syntax: self nbCallout function: #(â¦) emit: [â¦] Old syntax: NBFFICallout cdecl: #(...) module: .. New syntax: self nbCallout cdecl function: #(â¦) module: â¦ or: self nbCallout function: #(â¦) module: â¦ because cdecl is default Old syntax: NBFFICallout cdecl: #(...) module: .. options: #(â¦) New syntax: self nbCallout cdecl; options: #(â¦); function: #(â¦) module: â¦ Old syntax: NBFFICallout stdcall: #(...) module: .. options: #(â¦) New syntax: self nbCallout stdcall; options: #(â¦); function: #(â¦) module: â¦ ---- New API and syntax: self nbCallout function: <signature> address: [ address block ] generate code for calling a function located at given address with given signature. The address of function is provided by user in address block, which should return a pointer to the function (NBExternalAddress or Unsigned integer value, representing an absolute address of function). This API is useful, when you need to call some function which is not exported by via DLL symbol directly, but indirectly. The old NBFFICallout API is still there, but use of it is strongly discouraged. And it will be removed eventually. So be warned! :) -- Best regards, Igor Stasenko.

4 8

[Pharo-project] mess in package extensions
by Pavel Krivanek Nov. 28, 2012

Nov. 28, 2012

Hi, we have got some problems with package extensions and merging of them during updates. This problems became evident in this issues: - http://code.google.com/p/pharo/issues/detail?id=6956 - http://code.google.com/p/pharo/issues/detail?id=7036 In the first one we several times tired to move the methods to the correct package. At the end we tried to remove them in a fixing slice but how can you see in the latest image, this methods are still there. This methods cause 5 of 6 test failures in the Pharo Kernel (the last one is the Undeclared test with 5 undeclared classes) In the second issue the Form class methods are in the correct method category but as you may see in the Monticello browser, they are not in the Graphics-Files package. The Pharo Kernel shrinking removes packages with respect to method category and doesn't take an opinion of Monticello into account. So this methods are (correctly) removed during shrinking. But because they are not part of the Graphics-Files package by Monticello, they are not correctly loaded with the rest of the Morphic and thus the Jenkins job "Pharo Kernel 2.0 Reload by Monticello" is failing. Cheers, -- Pavel

2 2

[Pharo-project] almost ready for 2.0 beta
by Esteban Lorenzano Nov. 28, 2012

Nov. 28, 2012

Hi, I've been working last days to put pharo 2.0 ready to beta. So far we have just two missing integrations: - NativeBoost - Key Chain we deferred Opal to first cycle of next year release (february), because is not ready for inclusion yet. So. we will be on beta as soon as Igor and Ben give me the proper version for their inclusion :) Esteban

1 0

[Pharo-project] [update 2.0] #20421
by Marcus Denker Nov. 28, 2012

Nov. 28, 2012

20421 ----- Issue 7060: New Spec version http://code.google.com/p/pharo/issues/detail?id=7060 Issue 7054: InputEventHandler unregistering should nil the eventFetcher http://code.google.com/p/pharo/issues/detail?id=7054 Issue 7041: remove theme UIThemeStandardSqueak http://code.google.com/p/pharo/issues/detail?id=7041 Issue 7036: move Form class>>#fromFileNamed and fromBinaryStream to Graphic-Files http://code.google.com/p/pharo/issues/detail?id=7036 Issue 7031: Package HistoryCollection should be merged into Nautilus http://code.google.com/p/pharo/issues/detail?id=7031 Diff information: http://ss3.gemstone.com/ss/Pharo20/Spec-Core-MarcusDenker.66.diff http://ss3.gemstone.com/ss/Pharo20/Polymorph-Widgets-MarcusDenker.739.diff http://ss3.gemstone.com/ss/Pharo20/Nautilus-MarcusDenker.380.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1259.diff http://ss3.gemstone.com/ss/Pharo20/HistoryCollection-MarcusDenker.16.diff http://ss3.gemstone.com/ss/Pharo20/Graphics-Files-MarcusDenker.37.diff http://ss3.gemstone.com/ss/Pharo20/Graphics-Display Objects-MarcusDenker.98.diff -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

1 0

[Pharo-project] fixed smartcharacters
by StÃ©phane Ducasse Nov. 27, 2012

Nov. 27, 2012

Hi guys now with this change set the behavior when selected a piece of code is the same with smart char than the default behavior. aaaa + ' -> 'aaaa' 'aaaa' + ' -> aaaaa Stef

1 0

[Pharo-project] just help :)
by Sebastian Nozzi Nov. 27, 2012

Nov. 27, 2012

> 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

3 2

[Pharo-project] would it be possible to get the sender highlighted when we do senders of?
by StÃ©phane Ducasse Nov. 27, 2012

Nov. 27, 2012

Hi I noticed that we lost the selection when doing senders of. Any chance to get that back? We will have to address that in 2.0. If somebody can enter a bug entry it would be greatâ¦ right now in the train with no internet. And I do not want to forget. Stef

1 0

Nov. 27, 2012

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

1 0