- Pharo-users - lists.pharo.org

Re: [Pharo-users] Spec Adapter Advice

by Denis Kudriashov

Hi Ben 2017-04-28 4:32 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > > Would your remote IDE [1] be suitable to help Rob to hack around Spec > without blowing up his IDE? > Yes. But I think it is easy to just use Calypso tools to hack Spec. Calypso not depends on Spec. And it would be not a problem to break Spec based MessageBrowser. To use remote tools generally refactorings should be fixed. Right now they are not working from remote browser. > But I think its only available on Pharo 6? > Yes. > > [1] http://forum.world.st/Ann-PharmIDE-Pharo-remote-IDE-to- > develop-farm-of-Pharo-images-remotely-td4930602.html >

April 28, 2017

Basic controls <Normal List> does not change selection

by bachitoph

Hello, porting my digitalk / dolphin application to pharo (www.trimfox.com) I have to port my dialog creation part. Unfortunately I can't use Spec because my dialog creation depends on boundingBox: (Pharo bounds:) by calculation position and extent in pixels. So I have to use Morphic. There is the nice class WidgetExamples which helped me very much. But the Normal List control does not change selection if there is a click on another item. You can see the behavior evaluating the code below, and click maybe on the <Two> item. Same behavior in my Dialog class. Any hint! WidgetExamples exampleBasicControls thanks cjb -- View this message in context: http://forum.world.st/Basic-controls-Normal-List-does-not-change-selection-… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 28, 2017

Modal Menu in Pharo5

by Christoph J. Bachinger

Hello, I'm looking for a modal menu. It should stop method code execution until any left mouse klick. I tried MenuMorph with code like below, but this does not stop execution. Any hint? thank you cjb ComposableModel subclass: #BachitophTestWindow instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'Trimfox'. BachitophTestWindow compile: 'initializeWidgets'. |window menu choice| window := BachitophTestWindow new openWithSpecLayout: SpecLayout composed. menu := MenuMorph new defaultTarget: window; color: (window theme menuColorFor: window); addToggle: 'abcabcabcabc' target: window selector: #yourself"(labels at: 1)"; addToggle: 'cdfgcdfgcdfg' target: window selector: #yourself; addLine; addToggle: 'hijkhijkhijk' target: window selector: #yourself; yourself. choice := menu popUpInWorld. choice selectedItem isNil ifTrue: [ choice := 'abc' ] ifFalse: [choice := choice selectedItem contents]. self halt.

April 28, 2017

Re: [Pharo-users] Spec Adapter Advice

by Stephane Ducasse

This is a cool news. We could have a new adapter for Mars. I'm really interested in getting this working. Stef On Thu, Apr 27, 2017 at 11:10 PM, Rob Rothwell <r.j.rothwell(a)gmail.com> wrote: > Hello, > > I have recently been lucky enough to get the Cocoa portion of Mars working > on Pharo 5.0. While there are some issues, it has a wonderful set of > examples that allowed me create new Cocoa classes and delegate methods and > see a straightforward path to learning how to use Coco widgets from Pharo. > > I'd like to do that by creating appropriate Spec adapters, but > unfortunately the new Spec booklet wasn't designed for that! > > Can anyone give me any insight into creating (and using) a new Spec > adapter? Maybe just some high level steps to help me orient my > investigation into how Spec works? > > Thank you, > > Rob > > >

April 28, 2017

Smalltalk job offer in Germany [ collphir-bewerbung@collogia.de ]

by Stephane Ducasse

Dear Pharoers For our business unit Pension Management we are currently looking for a *Software-Developer (m/w) **About us* Collogia Unternehmensberatung AG is based in Cologne (Germany) and focused on IT-Consulting and software development. Since 1979 we successfully carry out projects and maintain IT-systems for the banking and insurance branch, public organisations or companies in all industries. Our competence centers are SAP-Consulting, Project management, IT-Services und Pension-Management. The business unit âPension Managementâ is specialised on pension administration and actuarial services. CollPhirÂ® (*www.collphir.de <http://www.collphir.de>) *is an in-house development. CollPhirÂ® is an administration system for pension funds and other company pension solutions. *Your Pro le* *â¢ *Successfully completed study of computer science, mathematics oder a comparable quali cation *â¢ *Profound knowledge in object-oriented soft- ware development, software engineering, e.g. methods, technologies, process design, data modeling, OOA/OOD, UML *â¢ *Experience with project management *â¢ *Team-oriented and *w*orking in a structured, systematic and deadline-focused way *â¢ *Good knowledge with MS-Of ce *â¢ *Working language is German, therefore a very good knowledge of the German language (written/spoken) is needed *Your Tasks* â¢ Development of high quality Client-/ Server-Software based on Visual Works Smalltalk â¢ Technological evolution of our in- house development CollPhirÂ® ( www.CollPhir.de) â¢ Development of functional and technical speci cations based on the analysis and requirements of our clients â¢ Consulting of our clients in requests regarding information technology â¢ Technical support CollPhirÂ® *Your Bene ts* â¢ Inviting projects â¢ Attrractive workplace â¢ Mentoring â¢ Targeted training â¢ Fexible working hours model â¢ Attractive salary model Contact *Dr. Michael HÃ¶hnerbach* CEO Pension Management E-Mail: collphir-bewerbung(a)collogia.de Ubierring 11 â¢ 50678 KÃ¶ln Web: collogia.de | collphir.de

April 28, 2017

Re: [Pharo-users] Spec Adapter Advice

by Ben Coman

Hi Dennis, On Fri, Apr 28, 2017 at 7:09 AM, Rob Rothwell <r.j.rothwell(a)gmail.com> wrote: > Hi Peter, > > Thank you very much for that overview! > > It looks like even just creating a window with no other widgets is sort of > "hard-wired" to Morphic through ComposableModel>>defaultWindowModelClass, > so maybe just overriding that and trying to create a Cocoa window model and > adapter is the place to start. > > I need to find a good starting point because you can't poke at the > existing code too much since even the debugger is built with Spec! > Would your remote IDE [1] be suitable to help Rob to hack around Spec without blowing up his IDE? But I think its only available on Pharo 6? [1] http://forum.world.st/Ann-PharmIDE-Pharo-remote-IDE-to-develop-farm-of-Phar… cheers -ben > > It's pretty exciting, though, because it feels like all the right pieces > are there and a lot of this could mostly be "just work" once I get going. > > Thanks again, > > Rob > > On Thu, Apr 27, 2017 at 6:04 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > >> Hi Rob, >> >> I guess the best resource at the moment is to just look at existing >> adapters. >> >> But here are some thoughts to get you started: >> >> (Spec) ComposableModel has as its widget (Spec) Adapter >> Adapter has as its widget the actual visual component, which currently >> means Morphic. >> >> >> The simplest example: LabelModel >> >> 1. model to adapter >> >> LabelModel is adapted by MorphicLabelAdapter: >> >> you can see on the class side in method `defaultSpec`. >> There is only `LabelAdapter` there because there is some extra mapping >> for some classes, but you can specify directly the class of the Adapter, so >> the following would work just as well: >> >> LabelModel class>>defaultSpec >> <spec> >> >> ^ #(MorphicLabelAdapter >> adapt: #(model)) >> >> >> LabelModel -> LabelAdapter direct event propagation (pushing changes) >> >> in Model world you can call changed:with: to execute code on the Adapter, >> e.g. >> >> self changed: #emphasis: with: {emphasis} >> >> which in turn will call the #emphasis: method on the LabelAdapter. >> >> LabelModel -> LabelAdapter events (pulling changes) >> >> preferred alternative is to do the opposite; properties of models are >> often held in ValueHolders, which can be observed on ValueChange, so the >> Adapter can register to event change and react on itself; >> >> you can see this best in MorphicTabAdapter (but you will see that >> TabAdapter looks a bit different from the rest, because I was experimenting >> with cleaning up Adapters...) >> >> 2. adapter to morphic >> >> Every adapter implements #buildWidget method that returns a Morphic >> Object. >> Typically the adapter registers itself as the model of the adapter (so >> adapter's model is Spec, and Morphic's model is the adapter). This depends >> a lot on the API of morphic. (in TabAdapter I'm overriding adapt: so >> there's no buildWidget, and it is in #buildWidgetWith:). >> >> It is all kinds of messy, but if you have other widgets then it will be a >> good test how well Spec can handle it... or rather we'll see how it can be >> improved... >> >> Peter >> >> >> >> On Thu, Apr 27, 2017 at 05:10:39PM -0400, Rob Rothwell wrote: >> > Hello, >> > >> > I have recently been lucky enough to get the Cocoa portion of Mars >> working >> > on Pharo 5.0. While there are some issues, it has a wonderful set of >> > examples that allowed me create new Cocoa classes and delegate methods >> and >> > see a straightforward path to learning how to use Coco widgets from >> Pharo. >> > >> > I'd like to do that by creating appropriate Spec adapters, but >> > unfortunately the new Spec booklet wasn't designed for that! >> > >> > Can anyone give me any insight into creating (and using) a new Spec >> > adapter? Maybe just some high level steps to help me orient my >> > investigation into how Spec works? >> > >> > Thank you, >> > >> > Rob >> >> >

April 28, 2017

Re: [Pharo-users] Spec Adapter Advice

by Rob Rothwell

Hi Peter, Thank you very much for that overview! It looks like even just creating a window with no other widgets is sort of "hard-wired" to Morphic through ComposableModel>>defaultWindowModelClass, so maybe just overriding that and trying to create a Cocoa window model and adapter is the place to start. I need to find a good starting point because you can't poke at the existing code too much since even the debugger is built with Spec! It's pretty exciting, though, because it feels like all the right pieces are there and a lot of this could mostly be "just work" once I get going. Thanks again, Rob On Thu, Apr 27, 2017 at 6:04 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > Hi Rob, > > I guess the best resource at the moment is to just look at existing > adapters. > > But here are some thoughts to get you started: > > (Spec) ComposableModel has as its widget (Spec) Adapter > Adapter has as its widget the actual visual component, which currently > means Morphic. > > > The simplest example: LabelModel > > 1. model to adapter > > LabelModel is adapted by MorphicLabelAdapter: > > you can see on the class side in method `defaultSpec`. > There is only `LabelAdapter` there because there is some extra mapping for > some classes, but you can specify directly the class of the Adapter, so the > following would work just as well: > > LabelModel class>>defaultSpec > <spec> > > ^ #(MorphicLabelAdapter > adapt: #(model)) > > > LabelModel -> LabelAdapter direct event propagation (pushing changes) > > in Model world you can call changed:with: to execute code on the Adapter, > e.g. > > self changed: #emphasis: with: {emphasis} > > which in turn will call the #emphasis: method on the LabelAdapter. > > LabelModel -> LabelAdapter events (pulling changes) > > preferred alternative is to do the opposite; properties of models are > often held in ValueHolders, which can be observed on ValueChange, so the > Adapter can register to event change and react on itself; > > you can see this best in MorphicTabAdapter (but you will see that > TabAdapter looks a bit different from the rest, because I was experimenting > with cleaning up Adapters...) > > 2. adapter to morphic > > Every adapter implements #buildWidget method that returns a Morphic Object. > Typically the adapter registers itself as the model of the adapter (so > adapter's model is Spec, and Morphic's model is the adapter). This depends > a lot on the API of morphic. (in TabAdapter I'm overriding adapt: so > there's no buildWidget, and it is in #buildWidgetWith:). > > It is all kinds of messy, but if you have other widgets then it will be a > good test how well Spec can handle it... or rather we'll see how it can be > improved... > > Peter > > > > On Thu, Apr 27, 2017 at 05:10:39PM -0400, Rob Rothwell wrote: > > Hello, > > > > I have recently been lucky enough to get the Cocoa portion of Mars > working > > on Pharo 5.0. While there are some issues, it has a wonderful set of > > examples that allowed me create new Cocoa classes and delegate methods > and > > see a straightforward path to learning how to use Coco widgets from > Pharo. > > > > I'd like to do that by creating appropriate Spec adapters, but > > unfortunately the new Spec booklet wasn't designed for that! > > > > Can anyone give me any insight into creating (and using) a new Spec > > adapter? Maybe just some high level steps to help me orient my > > investigation into how Spec works? > > > > Thank you, > > > > Rob > >

April 27, 2017

Re: [Pharo-users] Spec Adapter Advice

by Peter Uhnak

Hi Rob, I guess the best resource at the moment is to just look at existing adapters. But here are some thoughts to get you started: (Spec) ComposableModel has as its widget (Spec) Adapter Adapter has as its widget the actual visual component, which currently means Morphic. The simplest example: LabelModel 1. model to adapter LabelModel is adapted by MorphicLabelAdapter: you can see on the class side in method `defaultSpec`. There is only `LabelAdapter` there because there is some extra mapping for some classes, but you can specify directly the class of the Adapter, so the following would work just as well: LabelModel class>>defaultSpec <spec> ^ #(MorphicLabelAdapter adapt: #(model)) LabelModel -> LabelAdapter direct event propagation (pushing changes) in Model world you can call changed:with: to execute code on the Adapter, e.g. self changed: #emphasis: with: {emphasis} which in turn will call the #emphasis: method on the LabelAdapter. LabelModel -> LabelAdapter events (pulling changes) preferred alternative is to do the opposite; properties of models are often held in ValueHolders, which can be observed on ValueChange, so the Adapter can register to event change and react on itself; you can see this best in MorphicTabAdapter (but you will see that TabAdapter looks a bit different from the rest, because I was experimenting with cleaning up Adapters...) 2. adapter to morphic Every adapter implements #buildWidget method that returns a Morphic Object. Typically the adapter registers itself as the model of the adapter (so adapter's model is Spec, and Morphic's model is the adapter). This depends a lot on the API of morphic. (in TabAdapter I'm overriding adapt: so there's no buildWidget, and it is in #buildWidgetWith:). It is all kinds of messy, but if you have other widgets then it will be a good test how well Spec can handle it... or rather we'll see how it can be improved... Peter On Thu, Apr 27, 2017 at 05:10:39PM -0400, Rob Rothwell wrote: > Hello, > > I have recently been lucky enough to get the Cocoa portion of Mars working > on Pharo 5.0. While there are some issues, it has a wonderful set of > examples that allowed me create new Cocoa classes and delegate methods and > see a straightforward path to learning how to use Coco widgets from Pharo. > > I'd like to do that by creating appropriate Spec adapters, but > unfortunately the new Spec booklet wasn't designed for that! > > Can anyone give me any insight into creating (and using) a new Spec > adapter? Maybe just some high level steps to help me orient my > investigation into how Spec works? > > Thank you, > > Rob

April 27, 2017

Spec Adapter Advice

by Rob Rothwell

Hello, I have recently been lucky enough to get the Cocoa portion of Mars working on Pharo 5.0. While there are some issues, it has a wonderful set of examples that allowed me create new Cocoa classes and delegate methods and see a straightforward path to learning how to use Coco widgets from Pharo. I'd like to do that by creating appropriate Spec adapters, but unfortunately the new Spec booklet wasn't designed for that! Can anyone give me any insight into creating (and using) a new Spec adapter? Maybe just some high level steps to help me orient my investigation into how Spec works? Thank you, Rob

April 27, 2017

Re: [Pharo-users] [Ann] Pharo Sprint App to improve coordination during Pharo Sprints

by Juraj Kubelka

Hi, Marcus and I have updated the contribute page: http://pharo.org/contribute-events <http://pharo.org/contribute-events> And I have just released Pharo Sprint App version 0.2.0: http://bit.ly/PharoSprintApp <http://bit.ly/PharoSprintApp> (Discord sprint channel includes the link) To run it, you need Pharo 6.0 VM Thanks everyone for the early feedback. I was able to include some of them to the release. Have a fun. I will join you at 9:00 UTC-4 time. Juraj > On Apr 27, 2017, at 11:03, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > > Nice Juraj! ;-) Thanks Luc :-) > > #Luc > > 2017-04-24 20:51 GMT+02:00 K K Subbu <kksubbu.ml(a)gmail.com <mailto:kksubbu.ml@gmail.com>>: > On Monday 24 April 2017 08:00 PM, Juraj Kubelka wrote: > > Please, can you send me a screenshot? Or submit the screenshot > here https://github.com/JurajKubelka/PharoSprint/issues/new <https://github.com/JurajKubelka/PharoSprint/issues/new> > > Done. I think the error appears because when a login fails, the message causes a horiz scroll bar to be added to the panel pushing the fields beyond the top edge. I stumbled on this error because I tried using my fogbugz id whereas the login field needs the registered email id for login. > > Regards .. Subbu > >

April 27, 2017