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

Re: [Pharo-project] problem with obsolete classes in latest core

by Marcus Denker

On Mar 24, 2011, at 7:25 PM, Mariano Martinez Peck wrote: > Compiler recompileAll. > Smalltalk fixObsoleteReferences. > > SystemNavigation default obsoleteClasses ->>> an Array(AnObsoleteWordArray) > > But I cannot get rid of that final obsoletClass. > If you check for the users of WordArray, they are stored in some class vars... BalloonEngine initialize. DataStream initialize. DeflateStream initialize. FastInflateStream initialize. ZipConstants initialize. ZipWriteStream initialize. PNGReadWriter initialize seems to solve it. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 25, 2011

Re: [Pharo-project] GUIs with Pharo / how to learn smalltalk

by Schwab,Wilhelm K

Re learning about the GUI, look for Polymorph examples, the ProfessorStef browser, etc. The GUI section of the CollaborActive Book looks good too, as are the screen casts. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of GÃ¶ran Krampe [goran(a)krampe.se] Sent: Friday, March 25, 2011 8:12 AM To: pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] GUIs with Pharo / how to learn smalltalk On 03/25/2011 06:48 AM, Daniel Lyons wrote: > Hi, > > I have two questions, a technical one and a more general one. > > In broad strokes, what are people doing for GUIs? Basically: - For tools inside Pharo/Squeak, for research and for hobby projects etc, we use Morphic. If you want it running inside Pharo there is only Morphic (discounting MVC). - For getting paid we probably use Seaside, web stuff. In *broad strokes*. > The general question I have is basically, am I the problem? Basically yes :). No, just kidding. But this is open source and we typically like hacking more than spewing out documentation :). But *there is* docs, as others have pointed out. But as others also have pointed out - Smalltalk code is great for reading and *running*. Learn to use the tools for: - Code navigation. alt-shift-N, alt-n, alt-m are especially your friends. - Debugging. And halos are good to rip something apart that you wounder how the hell it is built. :) - Running and *reading* unit tests. Also, the best way to build a Morphic UI, especially if you want to build say a tool - is to copy code from a tool that seems similar and learn from there. But if you do that, try to verify that the code you are copying is reasonable *new* code so that you don't learn how to build stuff 10 years ago. ;) When I built the Squeakmap Package Loader I copied from the SystemBrowser I think. ;) > I hope none of this comes across as negative; I think surely it's that I'm missing something. Nah, not really. We don't typically have great docs, but we do have very good tools and the code is often very readable and easy to copy and adjust etc. regards, GÃ¶ran

March 25, 2011

Re: [Pharo-project] Issue 3880 in pharo: Balloon Tests not categorized/commented in 1.3

by pharo＠googlecode.com

Updates: Status: FixToInclude Comment #1 on issue 3880 by Torsten....(a)astares.de: Balloon Tests not categorized/commented in 1.3 http://code.google.com/p/pharo/issues/detail?id=3880 Fixed in SLICE-Issue-3880-Balloon-Tests-not-categorizedcommented-tbn.1 (additionally attached the changeset) Attachments: CategorizeBalloonTests.1.cs 1.2 KB

March 25, 2011

[Pharo-project] Issue 3880 in pharo: Balloon Tests not categorized/commented in 1.3

by pharo＠googlecode.com

Status: Accepted Owner: Torsten....(a)astares.de Labels: Milestone-1.3 New issue 3880 by Torsten....(a)astares.de: Balloon Tests not categorized/commented in 1.3 http://code.google.com/p/pharo/issues/detail?id=3880 uncategorizes methods in category "Balloon-Collections-Tests"

March 25, 2011

Re: [Pharo-project] Jtalk, a Smalltalk for web developers

by Nicolas Petton

Le lundi 21 mars 2011 Ã 10:17 +0100, Richard Durr a Ã©crit : > As far as I can see, the only way to call external Javascript is by > writing Javascript-Code directly into a method like so: > doSomethingWith: anObject > {'return SOMELIBRARY.doSomething(anObject); '} > > > is this correct? No, you can call JS functions with: #basicPerform: and #basicPerform:withArguments: Cheers, Nicolas > The OMETA based Smalltalk->JS translator seem to let one use st-syntax > for direct access to javascript like so: > > > doSomethingWith: anObject [ > SOMELIBRARY doSomething: anObject. > ] > > > and CoffeeScript can use JS seamlessly in the same way. > > > Best regards, > RD > > On Mon, Mar 14, 2011 at 7:36 PM, Nicolas Petton > <petton.nicolas(a)gmail.com> wrote: > Hi, > > I would like to share a project I'm working on on my spare > time: Jtalk > Smalltalk. > > http://nicolaspetton.github.com/jtalk > https://github.com/NicolasPetton/jtalk > > Jtalk is an implementation of the Smalltalk language that > compiles into > JavaScript. > > Some features: > - it is written in itself (including the parser/compiler) > - it is self-contained > - it compiles into efficient JS code > - it uses the Squeak chunk format > - Pharo is considered as the reference implementation > > I think Jtalk can be compared to CoffeeScript[1], > Objective-J[2] or > Clamato[3], from which it reuses some ideas and code. > > Jtalk includes an IDE with a class browser, transcript and > workspace, an > HTML canvas similar to Seaside and a jQuery binding. > > It is still a young piece of code, and some important features > are still > missing/incomplete. > > Cheers, > Nicolas Petton > > [1] http://jashkenas.github.com/coffee-script/ > [2] http://cappuccino.org/ > [3] http://clamato.net > > > >

March 25, 2011

Re: [Pharo-project] Issue 3715 in pharo: Workspace shouting after switching between shout/unshout

by pharo＠googlecode.com

Comment #7 on issue 3715 by Benjamin...(a)gmail.com: Workspace shouting after switching between shout/unshout http://code.google.com/p/pharo/issues/detail?id=3715 Done Attachments: BetterImplementationOfShouting.2.cs 2.0 KB

March 25, 2011

Re: [Pharo-project] Issue 3715 in pharo: Workspace shouting after switching between shout/unshout

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #6 on issue 3715 by Benjamin...(a)gmail.com: Workspace shouting after switching between shout/unshout http://code.google.com/p/pharo/issues/detail?id=3715 Once this fix is integrated, you can load the last version of shout :) Attachments: BetterImplementationOfShouting.1.cs 2.2 KB

March 25, 2011

Re: [Pharo-project] Issue 3879 in pharo: Wipe out positional arguments cruft from compiler

by pharo＠googlecode.com

Updates: Labels: Milestone-1.3 Type-Patch Comment #1 on issue 3879 by siguc...(a)gmail.com: Wipe out positional arguments cruft from compiler http://code.google.com/p/pharo/issues/detail?id=3879 (No comment was entered for this change.)

March 25, 2011

[Pharo-project] Issue 3879 in pharo: Wipe out positional arguments cruft from compiler

by pharo＠googlecode.com

Status: FixToInclude Owner: siguc...(a)gmail.com New issue 3879 by siguc...(a)gmail.com: Wipe out positional arguments cruft from compiler http://code.google.com/p/pharo/issues/detail?id=3879 Removes the #positionalArgument from Scanner and Parser So, now #(foo(bar)) is parsed correctly Attachments: Compiler-ar.197.1.cs 1.9 KB

March 25, 2011

Re: [Pharo-project] Issue 3715 in pharo: Workspace shouting after switching between shout/unshout

by pharo＠googlecode.com

Updates: Status: Accepted Comment #5 on issue 3715 by stephane...(a)gmail.com: Workspace shouting after switching between shout/unshout http://code.google.com/p/pharo/issues/detail?id=3715 in the shout initialize or load method we should have something like PluggableTextMorph shoutStylerClass: SHTextStylerST80 PluggableTextMorph>>shoutedStyler shoutStylerClass ifNil: [ ^ self nullStyler] ifNotNil: [^ self shoutStylerClass new view: self]

March 25, 2011