October 2014 - Pharo-dev - lists.pharo.org

gt issues
by Tudor Girba Oct. 7, 2014

Oct. 7, 2014

Hi, >From the feedback so far, I could not the following issues: - menus for copy/paste/cut (which I still wonder why they need to exist for a developer, but we will add them) - possibility of save/open - Cmd+g instead of Cmd+o (already fixed) - position of the cursor is sometimes messed up - possibility to change the title of the Playground - possibility to group the windows (this will likely not be fixed in the same way) (did I miss any?) - icons and text background are not ready for the dark theme Did I miss anything? Could the people that want to see any of these issues done open tickets for them? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

9 24

DNUs in the styler
by Thierry Goubier Oct. 7, 2014

Oct. 7, 2014

I'm encountering DNUs in the Styler in Pharo 4.0. Is someone else encountering those as well? A way to reproduce: RBParser parseFaultyMethod: 'test ^ ()' Whereas: RBParser parseFaultyMethod: 'test ^ ^ self' correctly returns an AST with RBParseErrorNode(s) inside. Thierry

3 5

GT-Inspector silly titles
by Sven Van Caekenberghe Oct. 7, 2014

Oct. 7, 2014

I think the titles of GT-Inspector windows/panes are a bit silly: Notice the 'a ZnClient(a ZnClient)' and 'a Dictionary(a Dictionary(...))' where the class name is repeated. I think it is very important to honour the standard/general Smalltalk approach and assume the #printString already contains the class name. If not, you are basically punishing everybody who went through the trouble of writing custom #printString implementation (like me, I do this for most classes). I saw the whole #display thing, but you can't force everybody to rewrite #printString to #gtDisplayString or whatever. Sven

3 6

Issue 14160: Introduce isXXX dialect testing methods to SmalltalkImage to ease cross-dialect development
by Jan Vrany Oct. 7, 2014

Oct. 7, 2014

Hi guys, I've just opened: https://pharo.fogbugz.com/f/cases/14160/Introduce-isXXX-dialect-testing-met… Introduce isXXX (isPharo, isVisualWorks, ...) dialect testing methods to SmalltalkImage to ease multi-dialect development. RATIONALE: Commonly used approach to solve differences among dialect is to use a sort of platform object and dispatch there for troublesome operations that has to be specialized. This platform object is usually in platform specific package. Other option is to load some library like Grease or Sport. The problem of the first approach is that brings to much (unnecessary) burden when used for two, three things. The amount of of the code and management is way to bigger then the amount of the code that has to be specialized. Loading Grease/Sport on the other hand introduces a dependency on an external package - not worth of for two or three things. The proposed dialect testing messages would allow for simple, #ifdef-like idiom like: | stream | ... ((Smalltalk respondsTo: #isSomeCoolDialect) and:[Smalltalk isSomeCoolDialect]) ifTrue:[ stream := CharacterWriteStream on: (String new: 10) ] ifFalse:[ stream := WriteStream on: (String new: 10) ] The #respondsTo: check, while not nice, is required as at the moment not all dialects could be trusted to have these testing messages. Putting these methods may not stick with Pharo standard (whatever it is), but Smalltalk global is probably one of the very few that are present in pretty much every Smalltalk implementation. Other option would be to place them to the class side of an Object (which is amost certainly present everywhere), however Smalltalk isPharo reads better than Object isPharo. Best, Jan

7 10

Re: [Pharo-dev] ANNC: QR Code (v.2)
by Pablo R. Digonzelli Oct. 6, 2014

Oct. 6, 2014

excellent! thanks Ing. Pablo Digonzelli Software Solutions IP-Solutiones SRL Metrotec SRL 25 de Mayo 521 Email: pdigonzelli(a)softsargentina.com pdigonzelli(a)gmail.com Cel: 5493815982714 ----- Mensaje original ----- De: "Esteban A. Maringolo" <emaringolo(a)gmail.com> Para: "Pharo Development List" <pharo-dev(a)lists.pharo.org> Enviados: Lunes, 6 de Octubre 2014 14:21:58 Asunto: Re: [Pharo-dev] ANNC: QR Code (v.2) Cool! Thank you Jeff. Esteban A. Maringolo 2014-10-06 12:49 GMT-03:00 J.F. Rick <self(a)je77.com>: > I've got a new version of the QR Code generator: > http://smalltalkhub.com/#!/~JochenRick/QRCode > > This one includes support for MicroQR, for UTF-8 encoding and other aspects > of the latest QR standard (e.g., mirroring). I've also written a small Zinc > web app which makes it easy to try out. > > Enjoy! > > Jeff > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick

1 0

GT-Inspector presentations for Core Zn objects
by Sven Van Caekenberghe Oct. 6, 2014

Oct. 6, 2014

Name: GT-InspectorExtensions-Core-SvenVanCaekenberghe.65 Author: SvenVanCaekenberghe Time: 6 October 2014, 4:20:04.98872 pm UUID: 3f4e93c1-eed7-4769-81c1-9c2ac6c48702 Ancestors: GT-InspectorExtensions-Core-SvenVanCaekenberghe.64 Added multiple presentations for all Core Zinc HTTP Components objects Sven

2 3

Patch GTInspector>>#printObjectAsAnItem:
by Sven Van Caekenberghe Oct. 6, 2014

Oct. 6, 2014

=== Name: GT-Inspector-SvenVanCaekenberghe.243 Author: SvenVanCaekenberghe Time: 6 October 2014, 4:26:27.106938 pm UUID: c415dc4f-5808-4b0f-99ab-bef45287e5c8 Ancestors: GT-Inspector-AndreiChis.242 Patch GTInspector>>#printObjectAsAnItem: to no longer add a class name when it is already present === I don't think this can be done in Object>>#gtDisplayOn: because of the stream involved. In any case, things look *way* better now ;-) Sven

2 2

Font & Theming of GT 'composite rubricText' is weird
by Sven Van Caekenberghe Oct. 6, 2014

Oct. 6, 2014

The font and theme rendering of GT 'composite rubricText' (like when inspecting Strings) is a bit off, IMHO: The font is different, does not appear in the settings and is not influenced by the theme. Sven

3 3

Re: [Pharo-dev] WhatsUp from: 2014-10-06 until: 2014-10-19
by Stephan Eggermont Oct. 6, 2014

Oct. 6, 2014

### Here's what I've been up to since the last WhatsUp: - Showed "the lessons we have not yet learned from smalltalk" at Global Scrum Gathering in Berlin (fast feedback loop with debugger-driven development, increased transparency by visualizing code, scaling down by increasing the abstraction level with DSLs) - Added a Storyboard build for Pharo 3 & 4 - Verified that PostgresV3 driver works in Pharo. PostgresV3 mirrors a database scheme and supports writing stored procedures in the browser. In Pharo the highlighting is different, parser too. - Migrated OverviewPyramid in Moose - Added #'Pharo4.x' in several Moose configurations. The SmalltalkImporter needs to be split as Pharo4 no longer has PackageInfo Stephan

1 0

Presetting variables to Spec's TextModel.
by Peter UhnÃ¡k Oct. 6, 2014

Oct. 6, 2014

Hi, I'm trying to preset variables to TextModel but I'm not sure if/how can such thing be achieved. With Workspace (in pre-GT Pharo) I could do ws := Workspace openContents: 'a'. b := Dictionary new. b add: (WorkspaceVariable key: #a value: 42). ws setBindings: b. Unfortunately Workspace isn't Spec's ComposableModel so I can't just reuse it. Is something similar possible with TextModel? Perhaps somehow changing model to Workspace (without actually opening the workspace) or something? Inspector seems to do something like that but my investigation ended up in OpalCompiler which is way over my head. :( Thanks, Peter

4 5