- Pharo-users - lists.pharo.org

[spotter] How do I get all the pragmas of the system?
by stepharo May 21, 2016

May 21, 2016

How do I get all the pragmas of the system with Spotter?

2 2

StampClient produce only and dealing with heartbeat
by Holger Freyther May 20, 2016

May 20, 2016

Dear Sven, I started to use the StampClient and intend to use it to produce data but for heartbeat and other parts I need to read from the socket as well. I wonder about the best strategy to deal with it. The naive approach. [ | event sendFrame | event := sharedQueue next. sendFrame := self newSendFrameTo: queueName sendFrame text: event convertToText. stampClient write: sendFrame. ] fork. But now the StampClient enforces a non-zero hearbeat.. so I could write something like this [ | event sendFrame | event := sharedQueue nextWaitFor: stampClient timeout * 3. event isNil ifTrue: [stampClient writeHeartBeat] ifFalse: [self convertAndSendEvent: event]. ] fork. But now I face the issue (but maybe I had it before as well) that the server will itself send an empty frame as its heartbeat function and I need to read it. So I could write... [ event := sharedQueue... "try to read all pending events? How often to repeat it read everything??" stampClient readNextFrame. ... ] fork Or to make it more involved? And create a reader and writer? procConsume := [ [stampClient runWith: [:msg | " do nothing " ]] ifCurtailed: [connectionClosed...handling]. ] fork. procProduce := [ [ | event sendFrame | event := sharedQueue next. sendFrame := self newSendFrameTo: queueName sendFrame text: event convertToText. stampClient write: sendFrame. ] ensure: [procConsume... do what exactly? ] fork. So the last options seems to be the best. But how to deal with with re-connects? How to not have have "procConsume" write the heartbeat data in the middle of the produced event? After all How did you solve that? Is the problem space clear enough? holger

3 3

Why is split: implemented in the separator rather than the string?
by Andy Burnett May 20, 2016

May 20, 2016

> > > > Message: 1 > Date: Thu, 19 May 2016 20:18:09 -0700 > From: John Pfersich <jpfersich(a)gmail.com> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] Why is split: implemented in the separator > rather than the string? > Message-ID: <C3F79F22-5675-4E29-97AC-A630D9ADA2E0(a)gmail.com> > Content-Type: text/plain; charset=us-ascii > > If you want to do it reversed, do it like this: > > '1969-07-20' splitOn: '-' > > > Thanks to both of you for responding. Makes sense. Cheers Andy

1 0

Spec layout
by Marion Noirbent May 20, 2016

May 20, 2016

Hi, I'm trying to create a widget whith Spec, managing a collection of RadioButton. But I have a problem with defaultSpec (the accessor of the collection is the methods "buttons") : If i put defaultSpec on class side, i can't acces the collection of the instance. (the following code iterate on the string) defaultSpec <spec: #default> ^ SpecLayout composed newColumn: [ :column | #buttons do: [ :item | column add: item ] ]; yourself If i put it on instance side, the lookup don't find it (in the book Building UI with Spec, it said the lookup begin by the instance side and it allow to have specific UI, in part about layout) defaultSpec <spec: #default> ^ SpecLayout composed newColumn: [ :column | self buttons do: [ :item | column add: item ] ]; yourself Any idea ? Marion Noirbent,

4 13

DSLDI'16: Call for Talk Proposals
by Tijs van der Storm May 20, 2016

May 20, 2016

********************************************************************* CALL FOR TALK PROPOSALS DSLDI 2016 Fourth Workshop on Domain-Specific Language Design and Implementation October 31, 2016 Amsterdam, Netherlands Co-located with SPLASH http://2016.splashcon.org/track/dsldi2016 https://twitter.com/wsdsldi ********************************************************************* Deadline for talk proposals: August 1, 2016 *** Workshop Goal *** Well-designed and implemented domain-specific languages (DSLs) can achieve both usability and performance benefits over general-purpose programming languages. By raising the level of abstraction and exploiting domain knowledge, DSLs can make programming more accessible, increase programmer productivity, and support domain-specific optimizations. The goal of the DSLDI workshop is to bring together researchers and practitioners interested in discussing how DSLs should be designed, implemented, supported by tools, and applied in realistic contexts. The focus of the workshop is on all aspects of this process, from soliciting domain knowledge from experts, through the design and implementation of the language, to evaluating whether and how a DSL is successful. More generally, we are interested in continuing to build a community that can drive forward the development of modern DSLs. An additional goal of this year's workshop is to encourage discussion about the usability of DSLs, and to establish connections with researchers in related areas, such as end-user software engineering, who have studied human factors of programming languages and tools. *** Workshop Format *** DSLDI is a single-day workshop and will consist of moderated audience discussions structured around a series of talks. The role of the talks is to facilitate interesting and substantive discussion. Therefore, we welcome and encourage talks that express strong opinions, describe open problems, propose new research directions, and report on early research in progress. Proposed talks should be on topics within DSLDI's area of interest, which include but are not limited to: * solicitation and representation of domain knowledge * DSL design principles and processes * DSL implementation techniques and language workbenches * domain-specific optimizations * human factors of DSLs * tool support for DSL users * community and educational support for DSL users * applications of DSLs to existing and emerging domains * studies of usability, performance, or other benefits of DSLs * experience reports of DSLs deployed in practice *** Call for Submissions *** We solicit talk proposals in the form of short abstracts (max. 2 pages). A good talk proposal describes an interesting position, open problem, demonstration, or early achievement. The submissions will be reviewed on relevance and clarity, and used to plan the mostly interactive sessions of the workshop day. Publication of accepted abstracts and slides on the website is voluntary. * Deadline for talk proposals: August 1, 2016 * Notification: September 5, 2016 * Workshop: October 31, 2016 * Submission website: https://dsldi16.hotcrp.com/ *** Workshop Organization *** Organizers: * Eric Walkingshaw (Oregon State University) * Tijs van der Storm (CWI) Program committee: * Iman Avazpour (Deakin University) * Christopher Bogart (Carnegie Mellon University) * Andy Gill (University of Kansas) * Sylvia Grewe (TU Darmstadt) * Kate Howland (University of Sussex) * Lindsey Kuper (Intel Labs) * Darya Kurilova (Carnegie Mellon University) * Ralf LÃ¤mmel (University of Koblenz-Landau) * Tanja Mayerhofer (Vienna University of Technology) * Marjan Mernik (University of Maribor) * Sarah Mount (King's College London) * Justin Pombrio (Brown University) * Tillmann Rendel (University of TÃ¼bingen) * Tiark Rompf (Purdue & Oracle Labs) * Sonja Schimmler (Bundeswehr University Munich) * Markus VÃ¶lter (itemis) * Peng Wu (Huawei America Lab)

1 0

Why is split: implemented in the separator rather than the string?
by Andy Burnett May 20, 2016

May 20, 2016

I keep getting this wrong, which makes me wonder why we send split: to the separator rather than the thing to be split. Is there a benefit to doing $- split: '1969-07-20' rather than '1969-07-20' split: $- (which somehow seems more natural to me). Cheers Andy

3 2

Scrollable Spec Model
by Peter UhnÃ¡k May 19, 2016

May 19, 2016

Hi, anyone has any experience with scrollable (arbitrary) Spec Model? e.g. I have a long list of buttons and fixed outer container windowâ¦ â As far as I can see scrolling is only available on morphic side, so I am not sure how to augment itâ¦ (Although we should probably allow scrolling on Spec side in some way) Thanks, Peter

2 2

[ANN] Pharo Sprint 27 May
by Marcus Denker May 19, 2016

May 19, 2016

We will organize a Pharo sprint / Moose dojo Friday, 27 May, starting at 10:00am. (Local Time Lille). It will be at the Inria Lille, Building B, third floor (RMoD offices). Remotely, you can join us on Slack or the IRC channel #pharo on irc.freenode.net <http://irc.freenode.net/> server. During the sprint, we will try to synchronize local and remote Pharo sprinters. As the building is not open to the public, please contact us before if you plan to come.

2 3

Re: [Pharo-users] Retina support in Pharo
by Thibault Raffaillac May 19, 2016

May 19, 2016

> > What happens if Pharo is launched on a retina computer? > You get the same thing as on a non-retina display, except instead of each > fuzzy pixel you get a visibly sharper square made of 2*2 retina pixels. > From sufficiently far away there's no difference, but when you're right in > front of it you can see the pixelation, especially for text and compared to > HiDPI-enabled apps in nearby windows. I have the same problem too. When working on OpenGL demo in C I noticed SDL2 does output the same ugly pixels by default, yet should support Retina screens (https://wiki.libsdl.org/SDL_CreateWindow - did not try, switched to GLFW which supports Retina out of the box). Is Pharo window created with native calls or SDL2? Cheers, Thibault

4 3

GLMFormatedPresentation>>format bug?
by Alistair Grant May 18, 2016

May 18, 2016

Hi All, I'm currently porting my personal documentation system from Python / Django to Pharo and am trying to display formatted text in a new pane in the inspector. If I execute something like: | text | text := 'Hello World' asText. text addAttribute: TextColor green from: 1 to: 6. text in a playground using "Do it and go", the text is displayed correctly (with formatting). If I add a method in the object I want to inspect: gtInspectIn: composite <gtInspectorPresentationOrder: 30> ^ composite text title: 'Meme'; display: [self asText]. the formatting disappears. I'm able to "fix" the problem by changing: GLMFormatedPresentation>>format ^ format ifNil: [ format := #asString ] to: GLMFormatedPresentation>>format ^ format ifNil: [ format := #asText ] Is someone more knowledgable about Glamour able to confirm that this is really a bug? If so, I'll submit a formal bug report on fogbugz. (If there's a better solution, that would be great too). Thanks! Alistair

4 7