January 2013 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 2.0] #20466
by Marcus Denker Jan. 11, 2013

Jan. 11, 2013

20466 ----- Issue 7202: Nautilus icon mechanism http://code.google.com/p/pharo/issues/detail?id=7202 Issue 6057: Nautilis: when clicking in history the Class button changes font size http://code.google.com/p/pharo/issues/detail?id=6057 Issue 7046: Cant right click on package list after following sequence http://code.google.com/p/pharo/issues/detail?id=7046 Diff information: http://ss3.gemstone.com/ss/Pharo20/Nautilus-MarcusDenker.387.diff http://ss3.gemstone.com/ss/Pharo20/MonticelloGUI-MarcusDenker.206.diff

1 0

[Pharo-project] Show buttons if
by J. P. L. MartÃn Jan. 10, 2013

Jan. 10, 2013

Hello, anyone could tell me how do I set buttons to display only if an specific button is pressed? Thanks

1 0

[Pharo-project] How to Meta-Click on Windows
by Euan M Jan. 10, 2013

Jan. 10, 2013

I've just installed Pharo 1.4 and Pharo By Example (PBE) 1 on my Windows Vista laptop (with two button track-pad). I've attempted every modifier key (Shift-, Ctrl-, Fn-, Alt- and AltGr-) on both of the trackpad buttons, and I cannot bring up the Morphic halo (as an example use of meta-clicking) PBE suggests using the Preference Browser (System > Preferences > Preference Browser) to change the swapControlAndAltKeys option in the keyboard category. ( This is now System > Settings > Settings Browser, then System > Keyboard > Control and Alt Keys ) I've tried setting it to "Swapped" and to "Handled apart", but nothing brings up the Morphic halo. How do I meta-click in Windows? -- View this message in context: http://forum.world.st/How-to-Meta-Click-on-Windows-tp4662780.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 5

[Pharo-project] [update 2.0] #20465
by Marcus Denker Jan. 10, 2013

Jan. 10, 2013

20465 ----- Issue 7225: Failing Test: testMethodsWithUnboundGlobals http://code.google.com/p/pharo/issues/detail?id=7225 Issue 7229: two tests failing in CompilerTest http://code.google.com/p/pharo/issues/detail?id=7229 Issue 7228: Undeclare in SpecLayoutAdd (testUndeclared fails) http://code.google.com/p/pharo/issues/detail?id=7228 Diff information: http://ss3.gemstone.com/ss/Pharo20/Spec-Layout-MarcusDenker.25.diff http://ss3.gemstone.com/ss/Pharo20/CompilerTests-MarcusDenker.131.diff

1 0

[Pharo-project] [update 2.0] #20464
by Marcus Denker Jan. 10, 2013

Jan. 10, 2013

1 0

[Pharo-project] Zinc-WebSockets Live Demo
by Sven Van Caekenberghe Jan. 10, 2013

Jan. 10, 2013

Hi, Yesterday I deployed a live demo of Zinc-WebSockets http://websocket.stfx.eu Since most proxies and load balancers, most notably Apache, don't handle the WebSocket protocol very well, the only solution is to arrange for direct connections to the Smalltalk image. Deploying and running this code in your own image is pretty easy: ConfigurationOfZincHTTPComponents project latestVersion load: 'WebSocket'. ZnServer startDefaultOn: 1701. ZnWebSocketDelegate installExamplesInDefaultServer. Then open http://localhost:1701/ws-demo with your browser. Sven PS: You can read more about Zinc-WebSockets here https://github.com/svenvc/docs/blob/master/zinc/zinc-websockets-paper.md PS: This demo, like the standard Zn and SSO demos run in the very latest Pharo 2.0 version http://zn.stfx.eu/status http://sso.stfx.eu/status http://websocket.stfx.eu:9999/status http://websocket.stfx.eu:9999/ws-status-client -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

3 6

[Pharo-project] NativeBoost design and deployment
by Igor Stasenko Jan. 10, 2013

Jan. 10, 2013

On 4 January 2013 08:54, Torsten Bergmann <astares(a)gmx.de> wrote: > When one deploys an image one usually requires ONLY > the image - not the source or changes file. An "image locker" > code would look like this: > > SmalltalkImage checkSourcesFileAvailability: false. > SmalltalkImage checkChangesFileAvailability: false > > do disable acording warnings when source/changefile is removed. > > If one uses NativeBoost in such a deployment scenario, for > instance the > > NBWin32Shell shellBrowse: 'http://www.google.de' > > functionality the internal code (due to missing source) now > looks like this > > shellExecute: t1 file: t2 parameters: t3 directory: t4 show: t5 > <primitive: 'primitiveNativeCall' module: 'NativeBoostPlugin'> > ^ self nbCall: #(#HINSTANCE #ShellExecuteA #(0 #, #LPCTSTR #lpOperation #, #LPCTSTR #lpFile #, #LPCTSTR #lpParameters #, #LPCTSTR #lpDirectory #, #INT #nShowCmd ) ) module: 'Shell32.dll' > > Hence the t1 ... t5 parameters. > > NativeBoost is in this situation not able to match the > FFI parameters and throws an error "Could not find accessor for variable ..." > > Try yourself without a changes and source file. This makes > NativeBoost not very deployment friendly and unusable in > such a "minimal deployment" scenario ... > > Any comments? > yes it needs sources (indirectly) to bind method's argument names during code generation. To avoid that, i can imagine that one must modify a compiler to detect if compiled method primitive requires arg names, and store them in method properties. Like that later code generator can use them without need to access the source code. > Thanks > T. -- Best regards, Igor Stasenko

4 9

[Pharo-project] jenkins slave disk space
by Camillo Bruni Jan. 9, 2013

Jan. 9, 2013

our pharo-linux64 bit slave is down due to disk space limitations. this is mainly caused by the ~6GB android SDK ;) which takes around the same space as the whole workspace under /builds Solutions: ========== a) condense the android sdk b) create a slave with a bigger disk

2 2

[Pharo-project] FileSystem inconsistency
by Jimmie Houchin Jan. 9, 2013

Jan. 9, 2013

Hello, I was writing a small utility using FileSystem. I had never used FileSystem before. So I am browsing the code trying to learn where to start and how to use it. It took me a little while to learn to do something like: fs := FileSystem store: (DiskStore activeClass createDefault). It would be nice if there were an instance creation method like FileSystem createDefault which would do the above. My utility was renaming some files. Once I had acquired a FileSystemDirectoryEntry instance I needed to examine the name. I see #basename and #fullName. As I browse other classes I see #childNamesAt: and #pathName, etc. I was just curious why #basename and not #baseName? Thanks. Jimmie

7 14

Re: [Pharo-project] Smalllint for Traits
by Fernando Olivero Jan. 9, 2013

Jan. 9, 2013

Cool work! It would be nice to have in the latest Pharo 2.0, so it can be integrated. Think about integrating it into SmallLint, if not, your nice work maybe will get lost. Saludos, Fernando On Wed, Jan 9, 2013 at 2:04 AM, aizcorbe <juansebastian.aizcorbe(a)gmail.com>wrote: > Hi all, as part of a thesis I have been working on, I extended Smalllint to > let it check Traits and Traits specific errors. > > The enviroment objects and the refactoring scope browsers now handles and > list classes and traits (before they just handled classes). The new > refactoring scope selection is available at "refactoring scope>selection > all behaviors" menu option. > > The smalllint framework have been extended and is available at > "refactor>code critics extended". > These are some of the changes: > smalllint rules can now check traits and traits methods. > a new rule presentation schema is available, which lets to spot the place > where the error is actually located and also add extra information to the > rule result (but is more difficult to define the rules in this way). > > For extra information about the changes and how can they be used you can > refer to: > > http://dc.uba.ar/inv/tesis/licenciatura/2012/aizcorbe.pdf (refer to > chapter > 4 if you want to bypass all the conceptual background ) > > there was also added some rules to check Traits specific errors. > > The Smalllint for Traits extension is available for pharo 1.3 and is > located > in: > > http://www.squeaksource.com/TesisTraitLint > > the packages are organized as follows: > > OBLintTraitExtension.1.3 (the smalltalk environment extension to add Traits > handling capabilities). > TraitLint.1.3 (the Smalllint extension itself and the > Traits > rules implementation). > TraitLintTest.1.3 (the unit tests for the Smalllint extension and > the rules implementation, it is not mandatory). > > I hope you find this useful. > cheers > > > > -- > View this message in context: > http://forum.world.st/Smalllint-for-Traits-tp4662559.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

1 0