Re: [Pharo-project] default styler is shout
On Jan 24, 2011, at 2:19 AM, Guillermo Polito wrote:
But that imperfect solution won't be a good solution either, since we are not going to have shout styler anywhere :).
So how is that solved in1.1? We need, for 1.2, just a *usable* compromise. Then we can iterate in 1.3 Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
Hi, I opened a ticket. We should move the discussion there: http://code.google.com/p/pharo/issues/detail?id=3583 Cheers, Doru On 24 Jan 2011, at 08:31, Marcus Denker wrote:
On Jan 24, 2011, at 2:19 AM, Guillermo Polito wrote:
But that imperfect solution won't be a good solution either, since we are not going to have shout styler anywhere :).
So how is that solved in1.1? We need, for 1.2, just a *usable* compromise. Then we can iterate in 1.3
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."
Just as an additional comment (don't know if this is related or not): For OB I had to subclass Editor and duplicate all SmalltalkEditor functionality, because the same Morph instance is used different contexts. Previously it was very easy to enable and disable syntax highlighting and other Smalltalk specific functionality. Lukas On 24 January 2011 00:10, Tudor Girba <tudor.girba@gmail.com> wrote:
Hi,
I opened a ticket. We should move the discussion there: http://code.google.com/p/pharo/issues/detail?id=3583
Cheers, Doru
On 24 Jan 2011, at 08:31, Marcus Denker wrote:
On Jan 24, 2011, at 2:19 AM, Guillermo Polito wrote:
But that imperfect solution won't be a good solution either, since we are not going to have shout styler anywhere :).
So how is that solved in1.1? Â We need, for 1.2, just a *usable* compromise. Then we can iterate in 1.3
   Marcus
-- Marcus Denker  -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- www.tudorgirba.com
"In a world where everything is moving ever faster, one might have better chances to win by moving slower."
-- Lukas Renggli www.lukas-renggli.ch
I've posted a change this morning when activating styling is just a message (beStyled) to send to a PluggableTextMorph Ben On Jan 24, 2011, at 4:46 PM, Lukas Renggli wrote:
Just as an additional comment (don't know if this is related or not):
For OB I had to subclass Editor and duplicate all SmalltalkEditor functionality, because the same Morph instance is used different contexts. Previously it was very easy to enable and disable syntax highlighting and other Smalltalk specific functionality.
Lukas
On 24 January 2011 00:10, Tudor Girba <tudor.girba@gmail.com> wrote:
Hi,
I opened a ticket. We should move the discussion there: http://code.google.com/p/pharo/issues/detail?id=3583
Cheers, Doru
On 24 Jan 2011, at 08:31, Marcus Denker wrote:
On Jan 24, 2011, at 2:19 AM, Guillermo Polito wrote:
But that imperfect solution won't be a good solution either, since we are not going to have shout styler anywhere :).
So how is that solved in1.1? We need, for 1.2, just a *usable* compromise. Then we can iterate in 1.3
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- www.tudorgirba.com
"In a world where everything is moving ever faster, one might have better chances to win by moving slower."
-- Lukas Renggli www.lukas-renggli.ch
Hi Lukas, When you say "previously" do you mean with ParagraphEditor or with previous version of Editor/TextEditor/SmalltalkEditor ? Cheers Alain Le 24/01/2011 16:46, Lukas Renggli a écrit :
Just as an additional comment (don't know if this is related or not):
For OB I had to subclass Editor and duplicate all SmalltalkEditor functionality, because the same Morph instance is used different contexts. Previously it was very easy to enable and disable syntax highlighting and other Smalltalk specific functionality.
Lukas
On 24 January 2011 00:10, Tudor Girba<tudor.girba@gmail.com> wrote:
Hi,
I opened a ticket. We should move the discussion there: http://code.google.com/p/pharo/issues/detail?id=3583
Cheers, Doru
On 24 Jan 2011, at 08:31, Marcus Denker wrote:
On Jan 24, 2011, at 2:19 AM, Guillermo Polito wrote:
But that imperfect solution won't be a good solution either, since we are not going to have shout styler anywhere :).
So how is that solved in1.1? We need, for 1.2, just a *usable* compromise. Then we can iterate in 1.3
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- www.tudorgirba.com
"In a world where everything is moving ever faster, one might have better chances to win by moving slower."
I mean with the old ParagraphEditor. I am not saying that the old ParagraphEditor was better (it had lots of other problems), but the separation between Editor and SmalltalkEditor makes the OB code much more complicated. Also having to send #beStyled is kind of tricky. The previous pull mechanism with #shoutWantsToBeStyled: was much more useful as the model of the editor could decide itself how and if it wanted to be styled. Now the model (or some other new entity inbetween) needs to know the view and update the editor all the time. Lukas On 24 January 2011 08:23, Alain Plantec <alain.plantec@free.fr> wrote:
Hi Lukas, When you say "previously" do you mean with ParagraphEditor or with previous version of Editor/TextEditor/SmalltalkEditor ? Cheers Alain
Le 24/01/2011 16:46, Lukas Renggli a écrit :
Just as an additional comment (don't know if this is related or not):
For OB I had to subclass Editor and duplicate all SmalltalkEditor functionality, because the same Morph instance is used different contexts. Previously it was very easy to enable and disable syntax highlighting and other Smalltalk specific functionality.
Lukas
On 24 January 2011 00:10, Tudor Girba<tudor.girba@gmail.com> Â wrote:
Hi,
I opened a ticket. We should move the discussion there: http://code.google.com/p/pharo/issues/detail?id=3583
Cheers, Doru
On 24 Jan 2011, at 08:31, Marcus Denker wrote:
On Jan 24, 2011, at 2:19 AM, Guillermo Polito wrote:
But that imperfect solution won't be a good solution either, since we are not going to have shout styler anywhere :).
So how is that solved in1.1? Â We need, for 1.2, just a *usable* compromise. Then we can iterate in 1.3
   Marcus
-- Marcus Denker  -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- www.tudorgirba.com
"In a world where everything is moving ever faster, one might have better chances to win by moving slower."
-- Lukas Renggli www.lukas-renggli.ch
ok we will have to iterate once more time... :) Tx for the report lukas. Stef On Jan 24, 2011, at 5:37 PM, Lukas Renggli wrote:
I mean with the old ParagraphEditor. I am not saying that the old ParagraphEditor was better (it had lots of other problems), but the separation between Editor and SmalltalkEditor makes the OB code much more complicated.
Also having to send #beStyled is kind of tricky. The previous pull mechanism with #shoutWantsToBeStyled: was much more useful as the model of the editor could decide itself how and if it wanted to be styled. Now the model (or some other new entity inbetween) needs to know the view and update the editor all the time.
Lukas
On 24 January 2011 08:23, Alain Plantec <alain.plantec@free.fr> wrote:
Hi Lukas, When you say "previously" do you mean with ParagraphEditor or with previous version of Editor/TextEditor/SmalltalkEditor ? Cheers Alain
Le 24/01/2011 16:46, Lukas Renggli a écrit :
Just as an additional comment (don't know if this is related or not):
For OB I had to subclass Editor and duplicate all SmalltalkEditor functionality, because the same Morph instance is used different contexts. Previously it was very easy to enable and disable syntax highlighting and other Smalltalk specific functionality.
Lukas
On 24 January 2011 00:10, Tudor Girba<tudor.girba@gmail.com> wrote:
Hi,
I opened a ticket. We should move the discussion there: http://code.google.com/p/pharo/issues/detail?id=3583
Cheers, Doru
On 24 Jan 2011, at 08:31, Marcus Denker wrote:
On Jan 24, 2011, at 2:19 AM, Guillermo Polito wrote:
But that imperfect solution won't be a good solution either, since we are not going to have shout styler anywhere :).
So how is that solved in1.1? We need, for 1.2, just a *usable* compromise. Then we can iterate in 1.3
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- www.tudorgirba.com
"In a world where everything is moving ever faster, one might have better chances to win by moving slower."
-- Lukas Renggli www.lukas-renggli.ch
participants (6)
-
Alain Plantec -
Benjamin -
Lukas Renggli -
Marcus Denker -
Stéphane Ducasse -
Tudor Girba