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

Re: [Pharo-users] The Rationale behind Spec - questions

by stephane ducasse

On Apr 16, 2013, at 8:13 PM, kmo <voxkmp(a)gmail.com> wrote: > Thanks to everyone who replied to my query. You've really helped me > understand the purpose of Spec. > > I suppose Spec is still a work in progress and its power will become more > and more apparent as time moves on. I'm using Spec myself now to build > interfaces but until you can set a font in LabelModel, add the functionality and we will integrate it. > I'll be using it > mainly to assemble and position morphs. > > > > -- > View this message in context: http://forum.world.st/The-Rationale-behind-Spec-questions-tp4681363p4681989… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

April 17, 2013

Fwd: [Sprint] Sprint Lille May 3rd

by Marcus Denker

Begin forwarded message: > From: Marcus Denker <marcus.denker(a)inria.fr> > Subject: [Sprint] Sprint Lille May 3rd > Date: April 17, 2013 1:12:29 PM GMT+02:00 > To: "Pharo-project(a)lists.gforge.inria.fr ML" <Pharo-project(a)lists.gforge.inria.fr> > > Hi, > > We are planning a sprint the 3rd of May: > > http://rmod.lille.inria.fr/web/pier/blog/2013-04-17 > > When? Friday May 3 > Where? Inria Lille Building B, RMoD Offices > > If you want to join, please send a mail so we can plan and open the > door for you. > > Marcus > > > >

April 17, 2013

Re: [Pharo-users] The Rationale behind Spec - questions

by kmo

Thanks to everyone who replied to my query. You've really helped me understand the purpose of Spec. I suppose Spec is still a work in progress and its power will become more and more apparent as time moves on. I'm using Spec myself now to build interfaces but until you can set a font in LabelModel, I'll be using it mainly to assemble and position morphs. -- View this message in context: http://forum.world.st/The-Rationale-behind-Spec-questions-tp4681363p4681989… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 16, 2013

Videos: Quicksilver & Fuel+Tanker

by Stephan Eggermont

I wondered how many views the movies would get without being announced: 0. Demo: Handling hierarchical datasets with Quicksilver https://www.youtube.com/watch?v=pOxKVVoCH3A Handling Objects with Fuel and Tanker https://www.youtube.com/watch?v=-UQ35SOsuaY rendering & uploading Custom architectural assessment of a large enterprise system Stephan

April 16, 2013

Re: [Pharo-users] TreeListMorph or MorphTreeMorph

by Hilaire Fernandes

Once I get done witjh it I will write a small note on the collaboractive book. Btw, I never feel it is crap, just a big piece of library code without much documentation. Hilaire Le 15/04/2013 17:54, Benjamin a Ã©crit :> I am saying that because I have this kind of question when I spend days > documenting Morphic infrastructure :) > > Everyone is like "Yeah, but we will throw away this crap", and that's > perfectly true. -- Dr. Geo http://drgeo.eu

April 16, 2013

Re: [Pharo-users] TreeListMorph or MorphTreeMorph

by Hilaire Fernandes

Le 15/04/2013 19:54, Alain Busser a Ã©crit : > Very promising, this example ;-) > > Does this mean that xml will be deprecated too? > No, it is just an alternate way to present the attributes in the drgeo UI. What primary interest me is to present to the user the math items in a chronological/historical list. Hilaire -- Dr. Geo http://drgeo.eu

April 16, 2013

Re: [Pharo-users] Programming desktop applications in Morphic

by S Krish

Pick the Pharo By Example book and you can do the first set of examples. Carry through and browse through the Morphic hierarchy , methods and debug through all examples / the IDE actions too. On Fri, Apr 12, 2013 at 6:09 PM, Zeeshan Ansari <zeeshan.k.ansari(a)gmail.com>wrote: > Hi All, > > I'm writing a desktop application and wanted to know what is the best way > to do this in Morphic. For example, in .Net I would have event-handlers for > specific events from the different window components (dialog, menu, etc) > for which I would code the behavior I wanted. Does Morphic follow a similar > paradigm? Are there any examples to look at? > > Thanks. >

April 16, 2013

Re: [Pharo-users] TreeListMorph or MorphTreeMorph

by Ben Coman

+1 - There is really no such thing as a temporary solution! :) From my industrial/mining experience, many "temporary" solutions can be found in operation years later... Benjamin wrote: > Exactly :) > > I am saying that because I have this kind of question when I spend days documenting Morphic infrastructure :) > > Everyone is like "Yeah, but we will throw away this crap", and that's perfectly true. > But in mid-time so poor guys have to stuck with the existing infrastructure (like you in this case), > and I really think it makes perfect sense to document something even if it will be deprecated in 6 months. > First because even deprecated it will still be used during 1 year and a half. > Moreover I deeply do not believe in a perfect system where nothing need to be changed anymore, so at some point > everything will be deprecated and rewritten, that's why I said that even if something will be deprecated, it worth to be documented :) > > Sorry if my message was not understood as I wanted :) > > Ben > > On Apr 15, 2013, at 4:55 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > > >> On Apr 15, 2013, at 4:45 PM, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: >> >> >>> When you fell unproductive -- stuck -- because you read library code you >>> have to use but you don't understand it, or at least not deeply enough, >>> it is not funny. >>> >> Yes this is why ben said that this is always worth to document. >> >> STef >> >> >>> Le 15/04/2013 12:18, Benjamin a Ã©crit : >>> >>>> It always make sense :) >>>> >>>> At the end, everything will be deprecated once :) >>>> >>> -- >>> Dr. Geo http://drgeo.eu >>> >>> >>> >> > > >

April 16, 2013

Re: [Pharo-users] TreeListMorph or MorphTreeMorph

by Alain Busser

Very promising, this example ;-) Does this mean that xml will be deprecated too? On Mon, Apr 15, 2013 at 1:08 PM, Hilaire Fernandes < hilaire.fernandes(a)gmail.com> wrote: > Le 15/04/2013 11:02, Goubier Thierry a Ã©crit :> You mean a single column > tree display ? Yes. Just do not create > > additional columns. > > > > Thierry > > > If I understand correctly the logic, it should be two columns. > At columns 2, the nodes attributes you can edit-in-place. > > For example > > [-]-Point A(1;2) > | | > | |--- Free point > | |--- Name: A > | |--- position: 1@2 > | |--- shape: =o v= > | |--- size: round > | |--- color: red > | > [+]-Point B(5;5) > | > [+]-Segment [AB] > > > Hilaire > > -- > Dr. Geo http://drgeo.eu > > >

April 15, 2013

Re: [Pharo-users] TreeListMorph or MorphTreeMorph

by stephane ducasse

+1 On Apr 15, 2013, at 5:54 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Exactly :) > > I am saying that because I have this kind of question when I spend days documenting Morphic infrastructure :) > > Everyone is like "Yeah, but we will throw away this crap", and that's perfectly true. > But in mid-time so poor guys have to stuck with the existing infrastructure (like you in this case), > and I really think it makes perfect sense to document something even if it will be deprecated in 6 months. > First because even deprecated it will still be used during 1 year and a half. > Moreover I deeply do not believe in a perfect system where nothing need to be changed anymore, so at some point > everything will be deprecated and rewritten, that's why I said that even if something will be deprecated, it worth to be documented :) > > Sorry if my message was not understood as I wanted :) > > Ben > > On Apr 15, 2013, at 4:55 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > >> >> On Apr 15, 2013, at 4:45 PM, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: >> >>> When you fell unproductive -- stuck -- because you read library code you >>> have to use but you don't understand it, or at least not deeply enough, >>> it is not funny. >> >> Yes this is why ben said that this is always worth to document. >> >> STef >> >>> >>> Le 15/04/2013 12:18, Benjamin a Ã©crit : >>>> It always make sense :) >>>> >>>> At the end, everything will be deprecated once :) >>> >>> >>> -- >>> Dr. Geo http://drgeo.eu >>> >>> >> >> >

April 15, 2013