On Wed, Nov 24, 2010 at 6:10 PM, Igor Stasenko wrote:
> On 25 November 2010 03:45, Juan Vuletich wrote:
> > Igor Stasenko wrote:
> >>
> >> IMO SimpleMorphic, minus 'color' ivar in Morph class is a way to go.
> >> (i mean get rid that 'color' thing in base class) :)
> >>
> >>
> >
> > Yep. I full
Now I will see who will port/rewrite what we have on top of a cleaned
SimpleMorphic.
> Stéphane Ducasse wrote:
>> Indeed. I mean
>> I can't help, but feel free to go ahead
>>
>> Stef
>>
>>
> Great! Thanks for the clarification.
>
> Cheers,
> Juan Vuletich
>
this is just for state. You have traits for methods.
For me the way to go is first clean the classbuilder, have first class instance
variables,
what you want is just
hashSubclass:
instead of variableSubclass:
Stef
>
> IMO SimpleMorphic, minus 'color' ivar in Mor
Igor Stasenko wrote:
I think, for things like Morphic, where there are dozens of various
properties expected
to be in basic morph class, we should use dictionaries, backed up by
clever VM semantics.
I cannot stop thinking about extending object format to allow a
dynamic number of slots per object
On 25 November 2010 03:45, Juan Vuletich wrote:
> Igor Stasenko wrote:
>>
>> IMO SimpleMorphic, minus 'color' ivar in Morph class is a way to go.
>> (i mean get rid that 'color' thing in base class) :)
>>
>>
>
> Yep. I fully agree.
>
I think, for things like Morphic, where there are dozens of var
Igor Stasenko wrote:
IMO SimpleMorphic, minus 'color' ivar in Morph class is a way to go.
(i mean get rid that 'color' thing in base class) :)
Yep. I fully agree.
Cheers,
Juan Vuletich
Stéphane Ducasse wrote:
Indeed. I mean
I can't help, but feel free to go ahead
Stef
Great! Thanks for the clarification.
Cheers,
Juan Vuletich
IMO SimpleMorphic, minus 'color' ivar in Morph class is a way to go.
(i mean get rid that 'color' thing in base class) :)
On 24 November 2010 16:49, Stéphane Ducasse wrote:
> Indeed. I mean
> I can't help, but feel free to go ahead
>
> Stef
>
>
>> "I do not think that we can build so
Indeed. I mean
I can't help, but feel free to go ahead
Stef
> "I do not think that we can build something on simpleMorphic, what we can do
> is look at the kernel and see how the changes can be applied to Morphic",
>
> it really means that it should better not be done. It means "I
Hi Stef,
Stéphane Ducasse wrote:
- clean again all the MVC dependencies
FillInTheBlank? PopUpMenu?
Those might be not pretty, and I agree they can be replaced by something
better, but they are not MVC dependencies.
Well, that doesn't stop Mariano from fighting
>
...k that we can build something on simpleMorphic,
>>> Why? That would be a huge disappointment.
>>>
>>
>> so it means that we should - throw/redo polymorph extensions (because even
>> if some code of polymorph sucks because gary did it to turn around
>>morphic
Hi Stef,
Stéphane Ducasse wrote:
...
k that we can build something on simpleMorphic,
Why? That would be a huge disappointment.
so it means that we should
- throw/redo polymorph extensions (because even if some code of polymorph sucks because gary did it to turn around
morphi
>>>
>>>We should get in the sophie events hierarchy. no ?
>>> It depends of the amount of work it would requires...
>>> what about working on SimpleMorphic for that ?
>>>
>>
>> I do not think that we can build something on simpleMorphic,
>
> Why? That would be a huge disappoi
Hi Stef,
Stéphane Ducasse wrote:
On Nov 20, 2010, at 2:21 PM, Alain Plantec wrote:
Le 20/11/2010 10:21, Stéphane Ducasse a écrit :
We should get in the sophie events hierarchy. no ?
It depends of the amount of work it would requires...
what about working on SimpleMorphic for t
On Nov 20, 2010, at 2:21 PM, Alain Plantec wrote:
> Le 20/11/2010 10:21, Stéphane Ducasse a écrit :
>> We should get in the sophie events hierarchy. no ?
> It depends of the amount of work it would requires...
> what about working on SimpleMorphic for that ?
I do not think that we can build some
Le 20/11/2010 10:21, Stéphane Ducasse a écrit :
We should get in the sophie events hierarchy. no ?
It depends of the amount of work it would requires...
what about working on SimpleMorphic for that ?
Alain
Stef
Cheers
Alain
On Nov 19, 2010, at 1:07 PM, Alain Plantec wrote:
> Le 19/11/2010 08:21, Fernando Olivero a écrit :
>> Hi Alain, i took a better look at the changes and have to say...once
>> again..excellent!
> Thanks Fernando!
>> I think the next step is to improve the keybindings hardcoding in
>> TextEditor>>
What I would like is to be able to control all alt-ctrl-cmd-shift etc
possible combinations for any morph.
It implies to review the way events are handled by Morph/HandMorph and
to remove the ugly "control and alt key" setting (Full matching,
partial matching, Swapped).
For example, it is c
Le 19/11/2010 08:21, Fernando Olivero a écrit :
Hi Alain, i took a better look at the changes and have to say...once
again..excellent!
Thanks Fernando!
I think the next step is to improve the keybindings hardcoding in
TextEditor>>initialize
self initializeCmdKeyShortcuts.
self
Yes! we were discussing with alain about that.
Please sync with alain.
Fernando here is also what I would like to have :)
A classVar Binding and an instance var binding.
**All** the methods only access binding
binding get initialized with the default table defined in Binding
=> we can have table b
I agree :).
Doru
On 19 Nov 2010, at 08:21, Fernando Olivero wrote:
> Hi Alain, i took a better look at the changes and have to say...once
> again..excellent!
>
> I think the next step is to improve the keybindings hardcoding in
> TextEditor>>initialize
> self initializeCmdKeyShortcuts.
>
Hi Alain, i took a better look at the changes and have to say...once
again..excellent!
I think the next step is to improve the keybindings hardcoding in
TextEditor>>initialize
self initializeCmdKeyShortcuts.
self initializeShiftCmdKeyShortcuts.
I have a keybindings/command model i
Due to a change in PragmaMenuBuilder, the world menu is not well updated
anymore.
Simply evaluating
World resetWorldMenu
fixes that.
So it should be done before the next release is published.
Cheers
Alain
oh yes!
Thanks a lot alain.
Stef
> Wow this looks great, thanks!
Wow this looks great, thanks!
On Wed, Nov 17, 2010 at 6:09 PM, Alain Plantec wrote:
> Le 17/11/2010 21:29, Fernando Olivero a écrit :
>
> Hi Fernando
>
> Hi Alain, this is great work! Improving text editor is must.
>> I'm looking forward to see your changes.
>>
>> Just one remark, please use eng
Hi Alain, this is great work! Improving text editor is must.
I'm looking forward to see your changes.
Just one remark, please use english next time!
Fernando
2010/11/17 ph...@googlecode.com :
> Status: Accepted
> Owner: stephane.ducasse
> CC: aplantec
> Labels: Milestone-1.2
>
> New issue 3266 by
Updates:
Status: Closed
Comment #2 on issue 3266 by stephane.ducasse: Clean TextEditor
http://code.google.com/p/pharo/issues/detail?id=3266
integrated in 12243
Comment #1 on issue 3266 by stephane.ducasse: Clean TextEditor
http://code.google.com/p/pharo/issues/detail?id=3266
Did you make the changes parametrized?
Status: Accepted
Owner: stephane.ducasse
CC: aplantec
Labels: Milestone-1.2
New issue 3266 by stephane.ducasse: Clean TextEditor
http://code.google.com/p/pharo/issues/detail?id=3266
voila ce que j'ai fait:
* nettoyage de TextEditor (plus que 2 variables d'instances, plus de
variables de classe
29 matches
Mail list logo
