[Pharo-project] PluggableTextMorph changed behavior
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
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
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
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
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
Stef, Yes, what's lacking is the doc. The system in itself is pretty great, once you invest a ton of hours in lighting the dark corners (PluggableTextMorph, OMG, an MVC-Morphic beast ...) How can I contribute to the book? I don't have a clue on how to login. Also, I went through most of your material (Bots, Caro la tortue, other PDFs, well, in fact I siphoned all of the content and read like a mad man ;-) ). There are a lot of treasures in there, especially the turtle geometry (I see that we have the same old book from 86 or so). Statistics coupled with turtle geometry could do a lot of interesting things... Philippe 2012/4/1 Stéphane Ducasse <stephane.ducasse@inria.fr>
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
-- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve" Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil@highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges
get an account on gforge.inria.fr and let us know your login we will add you to the svn and you will have access. Stef
Stef,
Yes, what's lacking is the doc. The system in itself is pretty great, once you invest a ton of hours in lighting the dark corners (PluggableTextMorph, OMG, an MVC-Morphic beast ...)
How can I contribute to the book? I don't have a clue on how to login.
Also, I went through most of your material (Bots, Caro la tortue, other PDFs, well, in fact I siphoned all of the content and read like a mad man ;-) ).
There are a lot of treasures in there, especially the turtle geometry (I see that we have the same old book from 86 or so).
Statistics coupled with turtle geometry could do a lot of interesting thingsâ¦
:) Stef
Philippe
2012/4/1 Stéphane Ducasse <stephane.ducasse@inria.fr>
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
-- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve"
Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil@highoctane.be | Web: http://philippeback.eu | Blog: http://philippeback.be
High Octane SPRL rue cour Boisacq 101 1301 Bierges
done. UID: philippeback 2012/4/1 Stéphane Ducasse <stephane.ducasse@inria.fr>
get an account on gforge.inria.fr and let us know your login we will add you to the svn and you will have access.
Stef
Stef,
Yes, what's lacking is the doc. The system in itself is pretty great, once you invest a ton of hours in lighting the dark corners (PluggableTextMorph, OMG, an MVC-Morphic beast ...)
How can I contribute to the book? I don't have a clue on how to login.
Also, I went through most of your material (Bots, Caro la tortue, other PDFs, well, in fact I siphoned all of the content and read like a mad man ;-) ).
There are a lot of treasures in there, especially the turtle geometry (I see that we have the same old book from 86 or so).
Statistics coupled with turtle geometry could do a lot of interesting thingsâ¦
:)
Stef
Philippe
2012/4/1 Stéphane Ducasse <stephane.ducasse@inria.fr>
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
-- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve"
Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil@highoctane.be | Web: http://philippeback.eu | Blog: http://philippeback.be
High Octane SPRL rue cour Boisacq 101 1301 Bierges
-- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve" Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil@highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges
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
participants (5)
-
Hilaire Fernandes -
Lawson English -
Mark Smith -
phil＠highoctane.be -
Stéphane Ducasse