April 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] PluggableTextMorph changed behavior

by StÃ©phane Ducasse

A bit of french culture for marcus :) L'arlesienne: the one that we endlessly wait for. http://www.expressio.fr/expressions/l-arlesienne.php coming from a novel of Alfonse Daudet. Stef PS: note that we are not waiting for Spoon. We are building our system and slowly but steadily arriving there. We are working step by step on making the system more modular and easier to change. We hope to have a bootstrap soon.

April 1, 2012

Re: [Pharo-project] PluggableTextMorph changed behavior

by StÃ©phane Ducasse

On Apr 1, 2012, at 4:46 PM, Hilaire Fernandes wrote: > Le 01/04/2012 15:22, StÃ©phane Ducasse a Ã©crit : >> Well the problem is that Morph is so complex and the API totally obscure. > > > I know I know, all this morphic stuff really really looks cryptic and > dusty, refactoring was due for many years but did not take place until > pharo. So it results in this big mess, but yet we can get something > useable in Pharo. yes (this is not such a mess, it is just lacking proper documentation). > Some time I would love to document somewhere my finding to achieve a > given result. if you send some examples we will add them (or you could add them directly to the basicWidgets chapter). > A kind of web service where each of us could document, > then this document could turn in comment in each class... kind of magic > stuff. May be the documentation class effort is the place to contribute, > but my workflow does not really match it. We started with benjamin to work on a basic widget chapter. I would love to document the basic api of each of the basic widgets. The problem is that I have to learn it first. So may be joining the effort on that chapter would be already a big plus. Stef

April 1, 2012

Re: [Pharo-project] PluggableTextMorph changed behavior

by Schwab,Wilhelm K

That's the problem - it's been "any day now" for a LONG time. As much as I don't enjoy pointing it out, don't wait for spoon. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Marcus Denker [marcus.denker(a)inria.fr] Sent: Sunday, April 01, 2012 9:33 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] PluggableTextMorph changed behavior On Apr 1, 2012, at 3:29 PM, Mark Smith wrote: > > On 1 Apr 2012, at 14:22, Lawson English wrote: > >> On 4/1/12 5:40 AM, Hilaire Fernandes wrote: >> [...] >>> We should have a way to track and document the changes we make in the image. >> >> Spoon will have a very fine-grained solution for this issue. >> Spoon will solve all of Squeak's problem since 10 years ;-) Marcus -- Marcus Denker -- http://marcusdenker.de

April 1, 2012

Re: [Pharo-project] PluggableTextMorph changed behavior

by Hilaire Fernandes

Le 01/04/2012 15:22, StÃ©phane Ducasse a Ã©crit : > Well the problem is that Morph is so complex and the API totally obscure. I know I know, all this morphic stuff really really looks cryptic and dusty, refactoring was due for many years but did not take place until pharo. So it results in this big mess, but yet we can get something useable in Pharo. Some time I would love to document somewhere my finding to achieve a given result. A kind of web service where each of us could document, then this document could turn in comment in each class... kind of magic stuff. May be the documentation class effort is the place to contribute, but my workflow does not really match it. Hilaire -- Dr. Geo -- http://www.drgeo.eu

April 1, 2012

Re: [Pharo-project] PluggableTextMorph changed behavior

by Marcus Denker

On Apr 1, 2012, at 3:29 PM, Mark Smith wrote: > > On 1 Apr 2012, at 14:22, Lawson English wrote: > >> On 4/1/12 5:40 AM, Hilaire Fernandes wrote: >> [...] >>> We should have a way to track and document the changes we make in the image. >> >> Spoon will have a very fine-grained solution for this issue. >> Spoon will solve all of Squeak's problem since 10 years ;-) Marcus -- Marcus Denker -- http://marcusdenker.de

April 1, 2012

Re: [Pharo-project] PluggableTextMorph changed behavior

by Mark Smith

On 1 Apr 2012, at 14:22, Lawson English wrote: > On 4/1/12 5:40 AM, Hilaire Fernandes wrote: > [...] >> We should have a way to track and document the changes we make in the image. > > Spoon will have a very fine-grained solution for this issue. > How much interest is there in Spoon from the Pharo community? Personally I'd love to see Spoon technology adopted by Pharo. Mark. > > L > >

April 1, 2012

Re: [Pharo-project] PluggableTextMorph changed behavior

by Lawson English

On 4/1/12 5:40 AM, Hilaire Fernandes wrote: [...] > We should have a way to track and document the changes we make in the > image. Spoon will have a very fine-grained solution for this issue. L

April 1, 2012

Re: [Pharo-project] PluggableTextMorph changed behavior

by StÃ©phane Ducasse

Well the problem is that Morph is so complex and the API totally obscure. Last time we spent 2 hours to find that the ghost text did not work because of not initialized correctly somewhere else. So we should slowly clean the API. Now for this change I have no idea. What you should see is that there was a lot of work to bring a new and better text. Stef On Apr 1, 2012, at 2:40 PM, Hilaire Fernandes wrote: > Le 01/04/2012 14:29, Hilaire Fernandes a Ã©crit : >> Hello, >> >> As far as PluggableTextMorph can be understandable, I used the code >> bellow to 'manipulate' text field the user can edit. >> The code bellow was working recently: >> >> morph := PluggableTextMorph >> on: builder text: #title accept: #title:. >> morph acceptTextInModel. >> morph >> color: Color white; >> acceptOnCR: true; > > Changing to > > autoAccept: true; > > > get it work. > > > We should have a way to track and document the changes we make in the image. > > > > -- > Dr. Geo -- http://www.drgeo.eu > >

April 1, 2012

Re: [Pharo-project] PluggableTextMorph changed behavior

by Hilaire Fernandes

Le 01/04/2012 14:29, Hilaire Fernandes a Ã©crit : > Hello, > > As far as PluggableTextMorph can be understandable, I used the code > bellow to 'manipulate' text field the user can edit. > The code bellow was working recently: > > morph := PluggableTextMorph > on: builder text: #title accept: #title:. > morph acceptTextInModel. > morph > color: Color white; > acceptOnCR: true; Changing to autoAccept: true; get it work. We should have a way to track and document the changes we make in the image. -- Dr. Geo -- http://www.drgeo.eu

April 1, 2012

[Pharo-project] PluggableTextMorph changed behavior

by Hilaire Fernandes

Hello, As far as PluggableTextMorph can be understandable, I used the code bellow to 'manipulate' text field the user can edit. The code bellow was working recently: morph := PluggableTextMorph on: builder text: #title accept: #title:. morph acceptTextInModel. morph color: Color white; acceptOnCR: true; hResizing: #spaceFill; height: 16; hideScrollBarsIndefinitely. When user edit text, the model (builder) was updated. Now not anymore with recent 1.4. What's wrong? Hilaire -- Dr. Geo -- http://www.drgeo.eu

April 1, 2012