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

Re: [Pharo-users] Question on style

by nacho

Thanks to all for your input. I consider this problem solved and I will write a little tutorial for those who might be interested. I now will be moving to another simple problem and will post the code here to go again with this process. In this way, we can accumulate slowly simple, but usefull problems resolved in a proper way. As I mentioned the idea is to have some sort of 99 problems for Smalltalk, of course everyone is invited to contribute. Best Nacho ----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://forum.world.st/Question-on-style-tp4752165p4752560.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 3, 2014

Re: [Pharo-users] deep into pharo(esug 2013) translate to korean draft version.

by peter yoo

í .. make pdf. but ugly.... sorry. http://onion.onionmixer.net/DeepIntoPharo_TranslateKorean_Draft.7z this file. if possible then i want get a TeX file. me can convert latex to xetex. have xetex then can PDF more to good. who can give TeX file to me?

April 3, 2014

Re: [Pharo-users] Question on style

by Damien Cassou

On Wed, Apr 2, 2014 at 2:34 PM, nacho <0800nacho(a)gmail.com> wrote: > if you don't mind I don't mind, go ahead. And don't hesitate to send us your future code -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

April 3, 2014

Re: [Pharo-users] Complex spec example

by Johan Fabry

Pharo 3.0 comes with multiple Spec UIs for different tools, have a look at the subclasses of ComposableModel, maybe there is something there that suits you. On Apr 3, 2014, at 8:28 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > Is there a rather complex example available that uses spec. I mean a sort of a complex UI that solves some real use cases from where I can steal ideas and patterns how things are done. Iâm just a UI noop and like to have all the guidance available :) > > thanks, > > Norbert > > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

April 3, 2014

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

by Goubier Thierry

Le 02/04/2014 20:44, MartinW a Ã©crit : > First of all thank you for taking the time to explain all this to me! I > already learned a lot about working with the spec widgets.. You're giving me good code to work with, and the things I use are more Morphic than Spec, which is more in my circle of confidence. > I still have a problem. The first version with the hardcoded collections did > obviously change the original collections (that's the desired behaviour). > > The last version though, did change the items in the list views, but not the > original collections. You're right. My problem is that I couldn't see a way to link the ListModel to the collection so that a change to one of them would propagate to the other. I'll go and do some reading on Spec. Another approach, that I would use, is to put more complex objects inside the lists. Thoses objects would know how to get added / removed from their respective collections, and then I would propagate collection changes to the ListModel instances. Does it makes sense? Thierry -- 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 3, 2014

Complex spec example

by Norbert Hartl

Is there a rather complex example available that uses spec. I mean a sort of a complex UI that solves some real use cases from where I can steal ideas and patterns how things are done. Iâm just a UI noop and like to have all the guidance available :) thanks, Norbert

April 3, 2014

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

by Benjamin

On 03 Apr 2014, at 12:50, Thomas Bany <mun.sysdev(a)gmail.com> wrote: > > I will defenitly look into that. The "rebuild" may be missleading, is it also called at first building ? Thatâs your own ,method, call it as/when you want > Well, I can't even manage to tweak it through hardcoding stuff on the adapter :p Yes, itâs hardcoded in the morph themselves > > Do you think it would be hard to use a SimpleSwitchMorph ? As I understood, there is #asSpecAdapter that permis to plug pretty much everything ? Plus, making a specific adapter seems doable (I mean for a rookie like me). Thatâs definitely a solution :) > Well, I definitely have a variable number of buttons, depending on the model instance. Actualy, I want my model to be a matrix of toggle to specify a mask. I create instance with: > > MaskModel class>#maxIndex: anInteger > ^(self basicNew) > maxIndex: anInteger; > initialize; > yourself > > and instantiate a collection of buttons in #initializeWidgets. > > It doesn't change much after that so a DynamicComposableModel didn't seem usefull. But I only though that because I never used it. I will give it a try. In DynamicComposableModel, when you instantiate a model using #instantiateModels: it simulates accessors for you. By example, if you do 1 to: 120 random do: [ :i | self instantiateModels: { (âbâ, i asString) asSymbol . #ButtonModel } Then your layout can be ^ SpecLayout composed add: #b1; add: #b2; etc Ben

April 3, 2014

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

by Thomas Bany

> > 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... > I will defenitly look into that. The "rebuild" may be missleading, is it also called at first building ? 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 > Well, I can't even manage to tweak it through hardcoding stuff on the adapter :p Do you think it would be hard to use a SimpleSwitchMorph ? As I understood, there is #asSpecAdapter that permis to plug pretty much everything ? Plus, making a specific adapter seems doable (I mean for a rookie like me). > 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. > Well, I definitely have a variable number of buttons, depending on the model instance. Actualy, I want my model to be a matrix of toggle to specify a mask. I create instance with: MaskModel class>#maxIndex: anInteger ^(self basicNew) maxIndex: anInteger; initialize; yourself and instantiate a collection of buttons in #initializeWidgets. It doesn't change much after that so a DynamicComposableModel didn't seem usefull. But I only though that because I never used it. I will give it a try. Anyway, thanks again for your time ! Thomas.

April 3, 2014

JPEG support in Artifact

by Stephan Eggermont

Reg Krock took a look at how difficult it would be to port Artefact to Gemstone. He found that JPEG support uses a plugin based reader/writer, and seems to render the JPEG using BitBlt and Form. Why are JPEGs rendered? Iâd think embedding them should be enough (and be better for speed and image quality) Stephan

April 3, 2014

Re: [Pharo-users] Rewiting code: doc?

by HernÃ¡n Morales Durand

2014-04-02 5:05 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>: > Now I do have a ton of new symbols in autocompletion but no class has been > renamed. > > 2.0 image... > Works for me here in a clean 2.0 image.

April 3, 2014