Re: [Pharo-project] Can this be improved in Glamourous?
Hello, Can people in general *delete* the quoted email parts to a level that one does need to scroll down 5 pages to read the answer? I start to just delete those mails, sorry. On Oct 16, 2011, at 10:18 PM, Mariano Martinez Peck wrote:
On Sun, Oct 16, 2011 at 10:10 PM, Tudor Girba <tudor@tudorgirba.com> wrote: Hi Mariano,
On 16 Oct 2011, at 21:57, Mariano Martinez Peck wrote:
On Sun, Oct 16, 2011 at 9:53 PM, Tudor Girba <tudor@tudorgirba.com> wrote: Hi Mariano,
On 16 Oct 2011, at 20:39, Mariano Martinez Peck wrote:
On Sat, Oct 15, 2011 at 11:32 PM, Tudor Girba <tudor@tudorgirba.com> wrote: Hi,
On 15 Oct 2011, at 23:13, Stéphane Ducasse wrote:
On Oct 15, 2011, at 10:58 PM, Tudor Girba wrote:
Hi,
On 15 Oct 2011, at 22:36, Mariano Martinez Peck wrote:
Hi Tudor. Today I wanted to give it a try to 'GT-Inspector' 'GT-Playground' hence I did:
I am happy you decided to give them a try :). But, the Playground is not yet ready :).
(ConfigurationOfGlamoroust project version: #bleedingEdge) load: #('GT-Inspector' 'GT-Playground' ).
In a Pharo 1.3 release. To my surprise, it took like half an hour to install, and it even was broken because it installed a different version of refactoring browser that is not working in 1.3.
This is due to a broken ConfiguraitonOfRB. I would actually be very interested in a fix in this area.
what is broken? because I spent one full sprint to fix it.
Actually it is not broken. Something else is broken by loading an older version somewhere in the Moose configuration. I did not have time yet.
So..can I ask.. are all of those projects really needed just for 2 simples things like a cool inspector and a cool workspace? do you need Nile, Grease, RefactoringBrowser, EyeSee, Magritte ??? can I somehow just load a minimal core for those things I need ?
These projects are loaded by the full default ConfigurationOfGlamour. The ConfigurationOfGlamour offers groups, but the GlamorousToolikt one does not yet. If someone can tell me how to do something like this, I would be happy to accommodate the solution.
in the chapter on metacello groups are explained. I can send you the latest version if you want.
I know how they work. I was actually referring to the actual code :). It is such a big mess to deal with the explosion of combinations.
Well, I guess that if you don't know then nobody knows. I mean, Moose is your project ;) you know better than us its dependencies.
This comment was not helpful at all.
It was not my intention to be rude. I am only saying that if you already know the tool there isn't anything I can do to help.
I did not say you were rude. I said it was not helpful.
I am just trying to build my own image with Glamourous since I think it is an important project. All I tried to do is to give you my feedback. Unfortunately, I cannot use that image you mention because I NEED the last 1.3 stable/released image. I can use your one click image, use it 5 minutes and let it. For in order to try it for real, I need to have it in my own images.
Thanks. I understand. Now, we need to get RB stable loadable in the released image.
Stef was updating ConfigurationOfRB last sprint...maybe just updating #stable is enugh ?
Cheers, Doru
Cheers
Doru
Cheers
Doru
Cheers, Doru
Thanks
linear load : linear load : baseline-0.1 [ConfigurationOfGlamoroust] load : ConfigurationOfGlamour atomic load : baseline-0.1 [ConfigurationOfGlamoroust] linear load : default [ConfigurationOfGlamour] load : ConfigurationOfEyeSee linear load : default [ConfigurationOfGlamour] load : ConfigurationOfGrease linear load : default [ConfigurationOfGlamour] load : ConfigurationOfMondrian linear load : default [ConfigurationOfGlamour] load : ConfigurationOfShout atomic load : default [ConfigurationOfGlamour] load : CollectionExtensions load : Glamour-Announcements load : Glamour-Helpers load : Glamour-Core load : Glamour-Presentations load : Glamour-Browsers load : Glamour-Tests-Core load : Glamour-Morphic-Theme load : Glamour-Examples load : Glamour-Tools load : Glamour-Morphic-Widgets load : Glamour-Morphic-Renderer load : Glamour-Tests-Morphic linear load : default [ConfigurationOfMondrian] load : ConfigurationOfProfStef linear load : default [ConfigurationOfMondrian] load : ConfigurationOfHealthReportProducer linear load : default [ConfigurationOfMondrian] load : ConfigurationOfShapeST80 atomic load : default [ConfigurationOfMondrian] atomic load : 0.2-baseline [ConfigurationOfHealthReportProducer] load : HealthReportProducer load : CollectionExtensions load : Nile-Base load : Mondrian-ComplexShape load : Mondrian-Core load : Mondrian-Layouts load : Mondrian-Help load : Mondrian-Easel load : Mondrian-Pharo-Tests load : Mondrian-Shapes load : Mondrian-Events load : Mondrian-Visitor load : Mondrian-Util load : Mondrian-Normalizers load : Mondrian-Example load : Mondrian-ShapeVisitor load : Mondrian-Pharo-Morphic load : Mondrian-Tests load : Mondrian-FADELayout load : Glamour-Mondrian-Presentations load : Glamour-Tests-Mondrian atomic load : default [ConfigurationOfEyeSee] load : EyeSee-Events load : EyeSee-Axis load : EyeSee-Tests-Core load : EyeSee-Support load : EyeSee-Core load : Glamour-EyeSee-Presentations load : Glamour-Tests-EyeSee linear load : 1.0.6.1 [ConfigurationOfGrease] load : ConfigurationOfRefactoringBrowser linear load : 1.0.6.1 [ConfigurationOfGrease] load : Grease-Slime-lr.13 load : Magritte-Model load : Magritte-Pharo-Model load : Magritte-Morph load : Glamour-Magritte-Presentations load : Magritte-Tests-Model load : GT-Playground load : GT-Inspector
-- Mariano http://marianopeck.wordpress.com
-- www.tudorgirba.com
"Every successful trip needs a suitable vehicle."
-- www.tudorgirba.com
"One cannot do more than one can do."
-- Mariano http://marianopeck.wordpress.com
-- www.tudorgirba.com
"Every thing has its own flow."
-- Mariano http://marianopeck.wordpress.com
-- www.tudorgirba.com
"Every now and then stop and ask yourself if the war you're fighting is the right one."
-- Mariano http://marianopeck.wordpress.com
-- Marcus Denker -- http://marcusdenker.de
On Sun, Oct 16, 2011 at 10:20 PM, Marcus Denker <marcus.denker@inria.fr>wrote:
Hello,
Can people in general *delete* the quoted email parts to a level that one does need to scroll down 5 pages to read the answer?
Sorry, I am not use to.... my gmail automatically hide them. I will try to remember next time.
I start to just delete those mails, sorry.
On Oct 16, 2011, at 10:18 PM, Mariano Martinez Peck wrote:
On Sun, Oct 16, 2011 at 10:10 PM, Tudor Girba <tudor@tudorgirba.com>
wrote:
Hi Mariano,
On 16 Oct 2011, at 21:57, Mariano Martinez Peck wrote:
On Sun, Oct 16, 2011 at 9:53 PM, Tudor Girba <tudor@tudorgirba.com>
wrote:
Hi Mariano,
On 16 Oct 2011, at 20:39, Mariano Martinez Peck wrote:
On Sat, Oct 15, 2011 at 11:32 PM, Tudor Girba <tudor@tudorgirba.com>
wrote:
Hi,
On 15 Oct 2011, at 23:13, Stéphane Ducasse wrote:
On Oct 15, 2011, at 10:58 PM, Tudor Girba wrote:
Hi,
On 15 Oct 2011, at 22:36, Mariano Martinez Peck wrote:
Hi Tudor. Today I wanted to give it a try to 'GT-Inspector'
'GT-Playground' hence I did:
I am happy you decided to give them a try :). But, the Playground
is not yet ready :).
(ConfigurationOfGlamoroust project version: #bleedingEdge) load:
#('GT-Inspector' 'GT-Playground' ).
In a Pharo 1.3 release. To my surprise, it took like half an hour
to install, and it even was broken because it installed a different version of refactoring browser that is not working in 1.3.
This is due to a broken ConfiguraitonOfRB. I would actually be very interested in a fix in this area.
what is broken? because I spent one full sprint to fix it.
Actually it is not broken. Something else is broken by loading an older version somewhere in the Moose configuration. I did not have time yet.
So..can I ask.. are all of those projects really needed just for 2 simples things like a cool inspector and a cool workspace? do you need Nile, Grease, RefactoringBrowser, EyeSee, Magritte ??? can I somehow just load a minimal core for those things I need ?
These projects are loaded by the full default ConfigurationOfGlamour. The ConfigurationOfGlamour offers groups, but the GlamorousToolikt one does not yet. If someone can tell me how to do something like this, I would be happy to accommodate the solution.
in the chapter on metacello groups are explained. I can send you the latest version if you want.
I know how they work. I was actually referring to the actual code :). It is such a big mess to deal with the explosion of combinations.
Well, I guess that if you don't know then nobody knows. I mean, Moose is your project ;) you know better than us its dependencies.
This comment was not helpful at all.
It was not my intention to be rude. I am only saying that if you already know the tool there isn't anything I can do to help.
I did not say you were rude. I said it was not helpful.
I am just trying to build my own image with Glamourous since I think it is an important project. All I tried to do is to give you my feedback. Unfortunately, I cannot use that image you mention because I NEED the last 1.3 stable/released image. I can use your one click image, use it 5 minutes and let it. For in order to try it for real, I need to have it in my own images.
Thanks. I understand. Now, we need to get RB stable loadable in the released image.
Stef was updating ConfigurationOfRB last sprint...maybe just updating #stable is enugh ?
Cheers, Doru
Cheers
Doru
Cheers
Doru
Cheers, Doru
Thanks
linear load : linear load : baseline-0.1 [ConfigurationOfGlamoroust] load : ConfigurationOfGlamour atomic load : baseline-0.1 [ConfigurationOfGlamoroust] linear load : default [ConfigurationOfGlamour] load : ConfigurationOfEyeSee linear load : default [ConfigurationOfGlamour] load : ConfigurationOfGrease linear load : default [ConfigurationOfGlamour] load : ConfigurationOfMondrian linear load : default [ConfigurationOfGlamour] load : ConfigurationOfShout atomic load : default [ConfigurationOfGlamour] load : CollectionExtensions load : Glamour-Announcements load : Glamour-Helpers load : Glamour-Core load : Glamour-Presentations load : Glamour-Browsers load : Glamour-Tests-Core load : Glamour-Morphic-Theme load : Glamour-Examples load : Glamour-Tools load : Glamour-Morphic-Widgets load : Glamour-Morphic-Renderer load : Glamour-Tests-Morphic linear load : default [ConfigurationOfMondrian] load : ConfigurationOfProfStef linear load : default [ConfigurationOfMondrian] load : ConfigurationOfHealthReportProducer linear load : default [ConfigurationOfMondrian] load : ConfigurationOfShapeST80 atomic load : default [ConfigurationOfMondrian] atomic load : 0.2-baseline [ConfigurationOfHealthReportProducer] load : HealthReportProducer load : CollectionExtensions load : Nile-Base load : Mondrian-ComplexShape load : Mondrian-Core load : Mondrian-Layouts load : Mondrian-Help load : Mondrian-Easel load : Mondrian-Pharo-Tests load : Mondrian-Shapes load : Mondrian-Events load : Mondrian-Visitor load : Mondrian-Util load : Mondrian-Normalizers load : Mondrian-Example load : Mondrian-ShapeVisitor load : Mondrian-Pharo-Morphic load : Mondrian-Tests load : Mondrian-FADELayout load : Glamour-Mondrian-Presentations load : Glamour-Tests-Mondrian atomic load : default [ConfigurationOfEyeSee] load : EyeSee-Events load : EyeSee-Axis load : EyeSee-Tests-Core load : EyeSee-Support load : EyeSee-Core load : Glamour-EyeSee-Presentations load : Glamour-Tests-EyeSee linear load : 1.0.6.1 [ConfigurationOfGrease] load : ConfigurationOfRefactoringBrowser linear load : 1.0.6.1 [ConfigurationOfGrease] load : Grease-Slime-lr.13 load : Magritte-Model load : Magritte-Pharo-Model load : Magritte-Morph load : Glamour-Magritte-Presentations load : Magritte-Tests-Model load : GT-Playground load : GT-Inspector
-- Mariano http://marianopeck.wordpress.com
-- www.tudorgirba.com
"Every successful trip needs a suitable vehicle."
-- www.tudorgirba.com
"One cannot do more than one can do."
-- Mariano http://marianopeck.wordpress.com
-- www.tudorgirba.com
"Every thing has its own flow."
-- Mariano http://marianopeck.wordpress.com
-- www.tudorgirba.com
"Every now and then stop and ask yourself if the war you're fighting is the right one."
-- Mariano http://marianopeck.wordpress.com
-- Marcus Denker -- http://marcusdenker.de
-- Mariano http://marianopeck.wordpress.com
Em 16/10/2011 18:20, Marcus Denker < marcus.denker@inria.fr > escreveu:
Hello,
Can people in general *delete* the quoted email parts to a level that one does need to scroll down 5 pages to read the answer?
+1 It is really a must for us that want to keep with the volume of e-mails but have to be parsimonious on the time spent for it. -- Cesar Rabak
Hi guys. So...now that ConfigurationOfGrease seem to work (in latest 1.3 from Hudson), I can load: (ConfigurationOfGlamoroust project version: #development) load: #('GT-Inspector' 'GT-Playground' ). However, if I evaluate: GTInspector openOn: 'mariano' I have the attached PharoDebug.log Basically, in GLMMorphicSmalltalkCodeRenderer >> textMorphForModel: aTextModel morph styler: styler; morph DNU styler: . Thanks! On Mon, Oct 17, 2011 at 2:53 PM, <csrabak@bol.com.br> wrote:
Em 16/10/2011 18:20, Marcus Denker < marcus.denker@inria.fr > escreveu:
Hello,
Can people in general *delete* the quoted email parts to a level that one does need to scroll down 5 pages to read the answer?
+1
It is really a must for us that want to keep with the volume of e-mails but have to be parsimonious on the time spent for it.
-- Cesar Rabak
-- Mariano http://marianopeck.wordpress.com
Probably that the GLMMorphicSmalltalkCodeRenderer rely on the old (and buggy way we used to use the styler) and doru may have to look at the shoutexample package to see how to invoke shout. Stef
Hi guys. So...now that ConfigurationOfGrease seem to work (in latest 1.3 from Hudson), I can load:
(ConfigurationOfGlamoroust project version: #development) load: #('GT-Inspector' 'GT-Playground' ).
However, if I evaluate: GTInspector openOn: 'mariano'
I have the attached PharoDebug.log
Basically, in GLMMorphicSmalltalkCodeRenderer >> textMorphForModel: aTextModel
morph styler: styler;
morph DNU styler: .
Thanks!
On Mon, Oct 17, 2011 at 2:53 PM, <csrabak@bol.com.br> wrote: Em 16/10/2011 18:20, Marcus Denker < marcus.denker@inria.fr > escreveu:
Hello,
Can people in general *delete* the quoted email parts to a level that one does need to scroll down 5 pages to read the answer?
+1
It is really a must for us that want to keep with the volume of e-mails but have to be parsimonious on the time spent for it.
-- Cesar Rabak
-- Mariano http://marianopeck.wordpress.com
<PharoDebug.log>
Hi, Thanks. It is fixed now by removing the explicit setting of a styler. However, I do not quite understand why not being able to set the styler on a per PluggableTextMorph instance basis is a good idea. You still have an instance variable for the styler, but you do not have the possibility to set it from the outside. You can only change the styler for the entire image by changing the StylingClass class variable. Cheers, Doru On 18 Oct 2011, at 21:37, Stéphane Ducasse wrote:
Probably that the GLMMorphicSmalltalkCodeRenderer rely on the old (and buggy way we used to use the styler) and doru may have to look at the shoutexample package to see how to invoke shout.
Stef
Hi guys. So...now that ConfigurationOfGrease seem to work (in latest 1.3 from Hudson), I can load:
(ConfigurationOfGlamoroust project version: #development) load: #('GT-Inspector' 'GT-Playground' ).
However, if I evaluate: GTInspector openOn: 'mariano'
I have the attached PharoDebug.log
Basically, in GLMMorphicSmalltalkCodeRenderer >> textMorphForModel: aTextModel
morph styler: styler;
morph DNU styler: .
Thanks!
On Mon, Oct 17, 2011 at 2:53 PM, <csrabak@bol.com.br> wrote: Em 16/10/2011 18:20, Marcus Denker < marcus.denker@inria.fr > escreveu:
Hello,
Can people in general *delete* the quoted email parts to a level that one does need to scroll down 5 pages to read the answer?
+1
It is really a must for us that want to keep with the volume of e-mails but have to be parsimonious on the time spent for it.
-- Cesar Rabak
-- Mariano http://marianopeck.wordpress.com
<PharoDebug.log>
-- www.tudorgirba.com "Don't give to get. Just give."
On Oct 19, 2011, at 8:38 AM, Tudor Girba wrote:
Hi,
Thanks. It is fixed now by removing the explicit setting of a styler.
However, I do not quite understand why not being able to set the styler on a per PluggableTextMorph instance basis is a good idea. You still have an instance variable for the styler, but you do not have the possibility to set it from the outside. You can only change the styler for the entire image by changing the StylingClass class variable.
I do not think but I may be wrong. Have a look at the examples of Alain. Since there was not documentation at all we (ben and me) did some mistakes and passed as idiot (as usual) because we were so stupid not to understand the design of the code that we do not know. This change got waves in editor and that led lukas to complain. So yes documentation, classes comments is a way to make us doing less mistakes and feeling less utterly stupid and frustrated. But people do not get it because this is so cool to code for one self and look so smart. Stef
Cheers, Doru
On 18 Oct 2011, at 21:37, Stéphane Ducasse wrote:
Probably that the GLMMorphicSmalltalkCodeRenderer rely on the old (and buggy way we used to use the styler) and doru may have to look at the shoutexample package to see how to invoke shout.
Stef
Hi guys. So...now that ConfigurationOfGrease seem to work (in latest 1.3 from Hudson), I can load:
(ConfigurationOfGlamoroust project version: #development) load: #('GT-Inspector' 'GT-Playground' ).
However, if I evaluate: GTInspector openOn: 'mariano'
I have the attached PharoDebug.log
Basically, in GLMMorphicSmalltalkCodeRenderer >> textMorphForModel: aTextModel
morph styler: styler;
morph DNU styler: .
Thanks!
On Mon, Oct 17, 2011 at 2:53 PM, <csrabak@bol.com.br> wrote: Em 16/10/2011 18:20, Marcus Denker < marcus.denker@inria.fr > escreveu:
Hello,
Can people in general *delete* the quoted email parts to a level that one does need to scroll down 5 pages to read the answer?
+1
It is really a must for us that want to keep with the volume of e-mails but have to be parsimonious on the time spent for it.
-- Cesar Rabak
-- Mariano http://marianopeck.wordpress.com
<PharoDebug.log>
-- www.tudorgirba.com
"Don't give to get. Just give."
Hi all, If I understand well, Doru just need a PluggableTextMorph>>#styler: so that a specific styler can be directly set to an instance. We can simply add this missing method if this is the point. Cheers Alain On 19/10/2011 09:03, Stéphane Ducasse wrote:
On Oct 19, 2011, at 8:38 AM, Tudor Girba wrote:
Hi,
Thanks. It is fixed now by removing the explicit setting of a styler.
However, I do not quite understand why not being able to set the styler on a per PluggableTextMorph instance basis is a good idea. You still have an instance variable for the styler, but you do not have the possibility to set it from the outside. You can only change the styler for the entire image by changing the StylingClass class variable. I do not think but I may be wrong. Have a look at the examples of Alain.
Since there was not documentation at all we (ben and me) did some mistakes and passed as idiot (as usual) because we were so stupid not to understand the design of the code that we do not know. This change got waves in editor and that led lukas to complain.
So yes documentation, classes comments is a way to make us doing less mistakes and feeling less utterly stupid and frustrated. But people do not get it because this is so cool to code for one self and look so smart.
Stef
Hi Alain, I do not need it at this point. The Glamour code is fixed and relies on the default behavior of PluggableTextMorph. But, I was simply remarking that you have an instance variable to specify the styler per instance, but there is no way to set it. So, yes, I think it would be a good idea to add the styler: method back :). Cheers, Doru On 19 Oct 2011, at 09:15, Alain Plantec wrote:
Hi all, If I understand well, Doru just need a PluggableTextMorph>>#styler: so that a specific styler can be directly set to an instance. We can simply add this missing method if this is the point. Cheers Alain
On 19/10/2011 09:03, Stéphane Ducasse wrote:
On Oct 19, 2011, at 8:38 AM, Tudor Girba wrote:
Hi,
Thanks. It is fixed now by removing the explicit setting of a styler.
However, I do not quite understand why not being able to set the styler on a per PluggableTextMorph instance basis is a good idea. You still have an instance variable for the styler, but you do not have the possibility to set it from the outside. You can only change the styler for the entire image by changing the StylingClass class variable. I do not think but I may be wrong. Have a look at the examples of Alain.
Since there was not documentation at all we (ben and me) did some mistakes and passed as idiot (as usual) because we were so stupid not to understand the design of the code that we do not know. This change got waves in editor and that led lukas to complain.
So yes documentation, classes comments is a way to make us doing less mistakes and feeling less utterly stupid and frustrated. But people do not get it because this is so cool to code for one self and look so smart.
Stef
-- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."
I agree. Issue 4918 <http://code.google.com/p/pharo/issues/detail?id=4918> Cheers Alain On 19/10/2011 09:23, Tudor Girba wrote:
Hi Alain,
I do not need it at this point. The Glamour code is fixed and relies on the default behavior of PluggableTextMorph.
But, I was simply remarking that you have an instance variable to specify the styler per instance, but there is no way to set it. So, yes, I think it would be a good idea to add the styler: method back :).
Cheers, Doru
On 19 Oct 2011, at 09:15, Alain Plantec wrote:
Hi all, If I understand well, Doru just need a PluggableTextMorph>>#styler: so that a specific styler can be directly set to an instance. We can simply add this missing method if this is the point. Cheers Alain
On 19/10/2011 09:03, Stéphane Ducasse wrote:
On Oct 19, 2011, at 8:38 AM, Tudor Girba wrote:
Hi,
Thanks. It is fixed now by removing the explicit setting of a styler.
However, I do not quite understand why not being able to set the styler on a per PluggableTextMorph instance basis is a good idea. You still have an instance variable for the styler, but you do not have the possibility to set it from the outside. You can only change the styler for the entire image by changing the StylingClass class variable. I do not think but I may be wrong. Have a look at the examples of Alain.
Since there was not documentation at all we (ben and me) did some mistakes and passed as idiot (as usual) because we were so stupid not to understand the design of the code that we do not know. This change got waves in editor and that led lukas to complain.
So yes documentation, classes comments is a way to make us doing less mistakes and feeling less utterly stupid and frustrated. But people do not get it because this is so cool to code for one self and look so smart.
Stef
-- www.tudorgirba.com
"Next time you see your life passing by, say 'hi' and get to know her."
Thanks guys. At least now I can use GTInspector :) Cheers On Wed, Oct 19, 2011 at 9:39 AM, Alain Plantec <alain.plantec@yahoo.com>wrote:
I agree. Issue 4918 <http://code.google.com/p/**pharo/issues/detail?id=4918<http://code.google.com/p/pharo/issues/detail?id=4918>
Cheers Alain
On 19/10/2011 09:23, Tudor Girba wrote:
Hi Alain,
I do not need it at this point. The Glamour code is fixed and relies on the default behavior of PluggableTextMorph.
But, I was simply remarking that you have an instance variable to specify the styler per instance, but there is no way to set it. So, yes, I think it would be a good idea to add the styler: method back :).
Cheers, Doru
On 19 Oct 2011, at 09:15, Alain Plantec wrote:
Hi all,
If I understand well, Doru just need a PluggableTextMorph>>#styler: so that a specific styler can be directly set to an instance. We can simply add this missing method if this is the point. Cheers Alain
On 19/10/2011 09:03, Stéphane Ducasse wrote:
On Oct 19, 2011, at 8:38 AM, Tudor Girba wrote:
Hi,
Thanks. It is fixed now by removing the explicit setting of a styler.
However, I do not quite understand why not being able to set the styler on a per PluggableTextMorph instance basis is a good idea. You still have an instance variable for the styler, but you do not have the possibility to set it from the outside. You can only change the styler for the entire image by changing the StylingClass class variable.
I do not think but I may be wrong. Have a look at the examples of Alain.
Since there was not documentation at all we (ben and me) did some mistakes and passed as idiot (as usual) because we were so stupid not to understand the design of the code that we do not know. This change got waves in editor and that led lukas to complain.
So yes documentation, classes comments is a way to make us doing less mistakes and feeling less utterly stupid and frustrated. But people do not get it because this is so cool to code for one self and look so smart.
Stef
-- www.tudorgirba.com
"Next time you see your life passing by, say 'hi' and get to know her."
-- Mariano http://marianopeck.wordpress.com
Please let me know if you have more problems. And let us know if you like it. Maybe others will be enticed to use it as well :) Doru On Wed, Oct 19, 2011 at 12:20 PM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
Thanks guys. At least now I can use GTInspector :)
Cheers
On Wed, Oct 19, 2011 at 9:39 AM, Alain Plantec <alain.plantec@yahoo.com>wrote:
I agree. Issue 4918 <http://code.google.com/p/**pharo/issues/detail?id=4918<http://code.google.com/p/pharo/issues/detail?id=4918>
Cheers Alain
On 19/10/2011 09:23, Tudor Girba wrote:
Hi Alain,
I do not need it at this point. The Glamour code is fixed and relies on the default behavior of PluggableTextMorph.
But, I was simply remarking that you have an instance variable to specify the styler per instance, but there is no way to set it. So, yes, I think it would be a good idea to add the styler: method back :).
Cheers, Doru
On 19 Oct 2011, at 09:15, Alain Plantec wrote:
Hi all,
If I understand well, Doru just need a PluggableTextMorph>>#styler: so that a specific styler can be directly set to an instance. We can simply add this missing method if this is the point. Cheers Alain
On 19/10/2011 09:03, Stéphane Ducasse wrote:
On Oct 19, 2011, at 8:38 AM, Tudor Girba wrote:
Hi,
Thanks. It is fixed now by removing the explicit setting of a styler.
However, I do not quite understand why not being able to set the styler on a per PluggableTextMorph instance basis is a good idea. You still have an instance variable for the styler, but you do not have the possibility to set it from the outside. You can only change the styler for the entire image by changing the StylingClass class variable.
I do not think but I may be wrong. Have a look at the examples of Alain.
Since there was not documentation at all we (ben and me) did some mistakes and passed as idiot (as usual) because we were so stupid not to understand the design of the code that we do not know. This change got waves in editor and that led lukas to complain.
So yes documentation, classes comments is a way to make us doing less mistakes and feeling less utterly stupid and frustrated. But people do not get it because this is so cool to code for one self and look so smart.
Stef
-- www.tudorgirba.com
"Next time you see your life passing by, say 'hi' and get to know her."
-- Mariano http://marianopeck.wordpress.com
-- -- www.tudorgirba.com "Every thing has its own flow"
On Wed, Oct 19, 2011 at 2:21 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Please let me know if you have more problems.
Sure I will :)
And let us know if you like it. Maybe others will be enticed to use it as well :)
Yes, I like it. Well, if my talk of Smalltalks is accepted, I guess all the audience will see it :)
Doru
On Wed, Oct 19, 2011 at 12:20 PM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
Thanks guys. At least now I can use GTInspector :)
Cheers
On Wed, Oct 19, 2011 at 9:39 AM, Alain Plantec <alain.plantec@yahoo.com>wrote:
I agree. Issue 4918 <http://code.google.com/p/**pharo/issues/detail?id=4918<http://code.google.com/p/pharo/issues/detail?id=4918>
Cheers Alain
On 19/10/2011 09:23, Tudor Girba wrote:
Hi Alain,
I do not need it at this point. The Glamour code is fixed and relies on the default behavior of PluggableTextMorph.
But, I was simply remarking that you have an instance variable to specify the styler per instance, but there is no way to set it. So, yes, I think it would be a good idea to add the styler: method back :).
Cheers, Doru
On 19 Oct 2011, at 09:15, Alain Plantec wrote:
Hi all,
If I understand well, Doru just need a PluggableTextMorph>>#styler: so that a specific styler can be directly set to an instance. We can simply add this missing method if this is the point. Cheers Alain
On 19/10/2011 09:03, Stéphane Ducasse wrote:
On Oct 19, 2011, at 8:38 AM, Tudor Girba wrote:
Hi,
Thanks. It is fixed now by removing the explicit setting of a styler.
However, I do not quite understand why not being able to set the styler on a per PluggableTextMorph instance basis is a good idea. You still have an instance variable for the styler, but you do not have the possibility to set it from the outside. You can only change the styler for the entire image by changing the StylingClass class variable.
I do not think but I may be wrong. Have a look at the examples of Alain.
Since there was not documentation at all we (ben and me) did some mistakes and passed as idiot (as usual) because we were so stupid not to understand the design of the code that we do not know. This change got waves in editor and that led lukas to complain.
So yes documentation, classes comments is a way to make us doing less mistakes and feeling less utterly stupid and frustrated. But people do not get it because this is so cool to code for one self and look so smart.
Stef
-- www.tudorgirba.com
"Next time you see your life passing by, say 'hi' and get to know her."
-- Mariano http://marianopeck.wordpress.com
-- -- www.tudorgirba.com
"Every thing has its own flow"
-- Mariano http://marianopeck.wordpress.com
On Wed, Oct 19, 2011 at 2:21 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Please let me know if you have more problems.
And let us know if you like it. Maybe others will be enticed to use it as well :)
I know you told me that playground was not ready....what I really miss there is a right click (context menu) Doru
On Wed, Oct 19, 2011 at 12:20 PM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
Thanks guys. At least now I can use GTInspector :)
Cheers
On Wed, Oct 19, 2011 at 9:39 AM, Alain Plantec <alain.plantec@yahoo.com>wrote:
I agree. Issue 4918 <http://code.google.com/p/**pharo/issues/detail?id=4918<http://code.google.com/p/pharo/issues/detail?id=4918>
Cheers Alain
On 19/10/2011 09:23, Tudor Girba wrote:
Hi Alain,
I do not need it at this point. The Glamour code is fixed and relies on the default behavior of PluggableTextMorph.
But, I was simply remarking that you have an instance variable to specify the styler per instance, but there is no way to set it. So, yes, I think it would be a good idea to add the styler: method back :).
Cheers, Doru
On 19 Oct 2011, at 09:15, Alain Plantec wrote:
Hi all,
If I understand well, Doru just need a PluggableTextMorph>>#styler: so that a specific styler can be directly set to an instance. We can simply add this missing method if this is the point. Cheers Alain
On 19/10/2011 09:03, Stéphane Ducasse wrote:
On Oct 19, 2011, at 8:38 AM, Tudor Girba wrote:
Hi,
Thanks. It is fixed now by removing the explicit setting of a styler.
However, I do not quite understand why not being able to set the styler on a per PluggableTextMorph instance basis is a good idea. You still have an instance variable for the styler, but you do not have the possibility to set it from the outside. You can only change the styler for the entire image by changing the StylingClass class variable.
I do not think but I may be wrong. Have a look at the examples of Alain.
Since there was not documentation at all we (ben and me) did some mistakes and passed as idiot (as usual) because we were so stupid not to understand the design of the code that we do not know. This change got waves in editor and that led lukas to complain.
So yes documentation, classes comments is a way to make us doing less mistakes and feeling less utterly stupid and frustrated. But people do not get it because this is so cool to code for one self and look so smart.
Stef
-- www.tudorgirba.com
"Next time you see your life passing by, say 'hi' and get to know her."
-- Mariano http://marianopeck.wordpress.com
-- -- www.tudorgirba.com
"Every thing has its own flow"
-- Mariano http://marianopeck.wordpress.com
participants (6)
-
Alain Plantec -
csrabak＠bol.com.br -
Marcus Denker -
Mariano Martinez Peck -
Stéphane Ducasse -
Tudor Girba