April 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Drag and drop items between list views

by Goubier Thierry

Hi Martin, yes, most list-like widgets can drag and drop. Feedback when inserting items in lists could be improved, however (i.e. you can drop on a list item, but I've never seen the feedback for dropping between list items). Thierry Le 02/04/2014 16:09, MartinW a Ã©crit : > Hi, > i have to make a UI where users can sort items (sentences) into different > collections by dragging and dropping them between list views. Is this > possible with the widgets currently available in Pharo? > M. > > > > -- > View this message in context: http://forum.world.st/Drag-and-drop-items-between-list-views-tp4752285.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

April 2, 2014

Re: [Pharo-users] lasergame problem with Blankcell

by Roelof Wobben

April 2, 2014

Drag and drop items between list views

by MartinW

Hi, i have to make a UI where users can sort items (sentences) into different collections by dragging and dropping them between list views. Is this possible with the widgets currently available in Pharo? M. -- View this message in context: http://forum.world.st/Drag-and-drop-items-between-list-views-tp4752285.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 2, 2014

Re: [Pharo-users] lasergame problem with Blankcell

by Mark Rizun

The mistake is simple. You have to write as follows (just replace cell for self in two lines before should and shouldnt): testCellOnState | cell | cell := BlankCell new. self should: [ cell isOff ]. self shouldnt: [ cell isOn ]. 2014-04-02 16:12 GMT+03:00 Roelof Wobben <r.wobben(a)home.nl>: > Mark Rizun schreef op 2-4-2014 15:07: > > Could you give me the code of test that fails? >> >> >> > I can but I did already. > > The code is : > > > testCellOnState > | cell | > cell := BlankCell new. > cell should: [ cell isOff ]. > cell shouldnt: [ cell isOn ]. > > And this is a code which succeeced: > > estCellExitSides > | cell exit | > cell := BlankCell new. > exit := cell exitSideFor: #north. > self should: [ exit = #south ]. > exit := cell exitSideFor: #east. > self should: [ exit = #west ]. > exit := cell exitSideFor: #south. > self should: [ exit = #north ]. > exit := cell exitSideFor: #west. > self should: [ exit = #east ]. > > Roelof > > > >

April 2, 2014

Re: [Pharo-users] Question on style

by nacho

Well here is again, the refactored version. "The idea is to have a class to calculate quadratic equations. This second draft still only calculates real roots (leaving aside imaginary roots). But thanks to Damien Cassou I think it has a better style. A QuadraticEquation is a class used to solve Quadratic Equations of the form: ax^2 + bx + c = 0, where a is not 0. You can set the coefficients using the following method setQuadraticCoefficient: linearCoefficient: constant: " Object subclass: #QuadraticEquation instanceVariableNames: 'quadraticCoefficient linearCoefficient constant roots' classVariableNames: '' category: 'IS-Math' "I create accessors (only getters for each term) and then the following method to set the terms" QuadraticEquation>>setQuadraticCoefficient: aNumber1 linearCoefficient: aNumber2 constant: aNumber3 quadraticCoefficient := aNumber1. linearCoefficient := aNumber2. constant := aNumber3 QuadraticEquation>>calculateRoots | checkNegative | checkNegative := linearCoefficient squared - ( 4 * quadraticCoefficient * constant). checkNegative >= 0 ifFalse: [ Error signal: 'Negative square root'] ifTrue: [ ^ self solveRoots: checkNegative] QuadraticEquation>>solveRoots: aTerm | rootA rootB | roots := OrderedCollection new. rootA := (linearCoefficient negated + aTerm sqrt) / (2 * quadraticCoefficient). rootB := (linearCoefficient negated - aTerm sqrt) / (2 * quadraticCoefficient). roots add: rootA; add: rootB. ^ roots " Example: -3x^2+2x+2=0 an OrderedCollection(-0.5485837703548636 1.2152504370215302) print(it) | anEquation | anEquation := QuadraticEquation new. anEquation setQuadraticCoefficient: -3 linearCoefficient: 2 constant: 2. anEquation calculateRoots." Thanks again Best, Nacho ----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://forum.world.st/Question-on-style-tp4752165p4752262.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 2, 2014

Re: [Pharo-users] lasergame problem with Blankcell

by Roelof Wobben

Mark Rizun schreef op 2-4-2014 15:07: > Could you give me the code of test that fails? > > I can but I did already. The code is : testCellOnState | cell | cell := BlankCell new. cell should: [ cell isOff ]. cell shouldnt: [ cell isOn ]. And this is a code which succeeced: estCellExitSides | cell exit | cell := BlankCell new. exit := cell exitSideFor: #north. self should: [ exit = #south ]. exit := cell exitSideFor: #east. self should: [ exit = #west ]. exit := cell exitSideFor: #south. self should: [ exit = #north ]. exit := cell exitSideFor: #west. self should: [ exit = #east ]. Roelof

April 2, 2014

Re: [Pharo-users] lasergame problem with Blankcell

by Mark Rizun

Could you give me the code of test that fails? 2014-04-02 16:05 GMT+03:00 Roelof Wobben <r.wobben(a)home.nl>: > Mark Rizun schreef op 2-4-2014 14:58: > > Does this test fails to assert something or it throws you some error? >> >> > Like I said earlier it fails with this message: > > MessageNotUnderstood: BlankCell >> should. > > > Which I find wierd because I use should: also on the other test methods > off BlankCell and not getting this error. > > Roelof > > >

April 2, 2014

Re: [Pharo-users] lasergame problem with Blankcell

by Roelof Wobben

Mark Rizun schreef op 2-4-2014 14:58: > Does this test fails to assert something or it throws you some error? > Like I said earlier it fails with this message: MessageNotUnderstood: BlankCell >> should. Which I find wierd because I use should: also on the other test methods off BlankCell and not getting this error. Roelof

April 2, 2014

Re: [Pharo-users] lasergame problem with Blankcell

by Mark Rizun

Does this test fails to assert something or it throws you some error? 2014-04-02 15:27 GMT+03:00 Roelof Wobben <r.wobben(a)home.nl>: > Mark Rizun schreef op 2-4-2014 14:22: > > And only on this method the test fail on should: >> >> testCellOnState >> | cell | >> cell := BlankCell new. >> cell should: [ cell isOff ]. >> cell shouldnt: [ cell isOn ]. >> > Yes it does, inasmuch on the bottom of this page ( > http://squeak.preeminent.org/tut2007/html/017.html ) > both methods return *false*. I think later the implementation of this two > methods will be changed so don't worry. > > > Correct but on this page : > http://squeak.preeminent.org/tut2007/html/025.html > some methods are moved to another class. > > and then on this page : http://squeak.preeminent.org/tut2007/html/026.html > The first step is to run Test runner and then it fails and only on this > test. > > Roelof > >

April 2, 2014

Re: [Pharo-users] Few questions about Spec (instance specific layout and skinning)

by Benjamin

On 02 Apr 2014, at 12:10, Thomas Bany <mun.sysdev(a)gmail.com> wrote: > Hi ! > > First, I apologyse for the wall of text. > > I'm trying my hands at Spec and I have few questions: > How can I implement an instance-dependent layout ? The usual solution is to have a method looking like this on instance side rebuildMyLayout | layout | layout := self buildStateDependentLayout. self buildWithLayout: layout. buildStateDependentLayout ^ SpecLayout composed etc... > Regarding the layout method lookup, the documentation states that it "starts on instance side, which allows a UI to have a more specific layout depending on the state of the instance" > > I tried to simply put a layout in an instance method with the <spec: #default> pragma. But not only was it not retrieved by ComposableModel>#defaultSpecSelector but ComposableModel>#retrieveSpec: will send the selector on the class anyway. > > What I ended up doing was overiding #openWithSpec (which worked) but I'm pretty sure that my model is not composable at all. Indeed, overriding openWithSpec may be a bit hackish, but should still work :) Another solution could be to override defaultSpecSelector and/or retrieveSpec: > Is it possible to change the "skin" of the basic widget ? The hooks are basically here, but the Morphs have an issue with this. The âskinâ of a Morph is supposed to be immutable, hence it takes back its default value at each refresh :S > > I would like to implement some sort of toggle button by changing the color of ButtonModel and so far, I failed. I was not able to trace my color change up to the PluggableButtonMorph because it seems to use anoucement and I'm a Smalltalk rookie. > > I tried however to send #color: directly to the morph which does nothing: the #changed method rolls it back to its previous value. So I may be doing something wrong but it doesn't feel like the issue comes from Spec. Any clue ? > So far, it will not work, sorry :( > On a side note, I tried to send an argument to the selector that retrieve a widget in the layout method. > And I came up with this : > > layout add: {#buttonAt: . 1}; add: {#buttonAt: . 2}; add: {#buttonAt: . 3} > > Is it how it's done ? Thatâs a solution. Then if you have a fixed number of buttons, you could also implement a getter for each. If you have an undetermined number of button, then DynamicComposableModel is for you. > Thanks in advance ! You are welcome :) Ben

April 2, 2014