What do we have now?
- Can provide settings for a set of morphs
- Can provide settings for a TextEditors (Smalltalk editor and related)
- Settings integration
I added some methods to the Settings Tree Builder in order to avoid
references from the users code.
- I ran Slint over it and cleaned it
On Sat, Feb 26, 2011 at 5:42 AM, Guillermo Polito wrote:
> What do we have now?
>
> - Can provide settings for a set of morphs
>
> - Can provide settings for a TextEditors (Smalltalk editor and related)
>
> - Settings integration
> I added some methods to the Settings Tree Builder in order to avo
Guille i was using 1.4 and worked excellent, just tried 1.5 and on
every stroke i made i've got a DNU on #realtarget
Installed on last PharoCore 1.2, should i try it on 1.3?
Great work,
Fran
On Sat, Feb 26, 2011 at 5:29 AM, laurent laffont
wrote:
>
> On Sat, Feb 26, 2011 at 5:42 AM, Guillermo P
Hi,
I am currently writing a more complete set of commands for the editors. I ll
post soon.
m(^_-)m
camillo
On 2011-02-26, at 14:12, Francisco Ortiz Peñaloza wrote:
> Guille i was using 1.4 and worked excellent, just tried 1.5 and on
> every stroke i made i've got a DNU on #realtarget
>
> Ins
Thanks this is still on my todo to have a look at them.
I want a good keymapper in the system... :)
Stef
On Feb 26, 2011, at 5:42 AM, Guillermo Polito wrote:
> What do we have now?
>
> - Can provide settings for a set of morphs
>
> - Can provide settings for a TextEditors (Smalltalk editor and
Laurent, do you mean bindings like:
Cmd + a followed by Cmd + b?
Yes, you can and it's written like
$a cmd, $b cmd
On Sat, Feb 26, 2011 at 4:29 AM, laurent laffont
wrote:
>
> On Sat, Feb 26, 2011 at 5:42 AM, Guillermo Polito <
> guillermopol...@gmail.com> wrote:
>
>> What do we have now?
>>
>>
Mmm, If you had 1.4 and updated to 1.5, you will have some problems because
I did some refactorings on that... :/.
On Sat, Feb 26, 2011 at 10:12 AM, Francisco Ortiz Peñaloza <
patchi...@gmail.com> wrote:
> Guille i was using 1.4 and worked excellent, just tried 1.5 and on
> every stroke i made i'
Camillo,
What's a more complete set of commands? Can you be more Specific? hehe.
Next thing I want to do is get rid of every hardcoded mapping (i.e from
Editor and SmalltalkEditor) and configure it this way... But It's a lot of
work I couldn't do. Maybe this two weeks I can do something on it s
Hey Guille,
Step by step I will try to add most of the TextEditor / SmalltalkEditor
keymappings. so far I have committed a basic set.
generally I commit on a 1h basis, so that should be sufficient to track
progress ;)
camillo
On 2011-02-26, at 18:54, Guillermo Polito wrote:
> Camillo,
>
> W
You're telling me that if i do a clean installation of 1.5 it would work?
Thanks in advance,
Francisco
On Sat, Feb 26, 2011 at 3:50 PM, Guillermo Polito
wrote:
> Mmm, If you had 1.4 and updated to 1.5, you will have some problems because
> I did some refactorings on that... :/.
>
> On Sat, Feb 2
I also I cannot load Keymapping 1.5 in Pharo 1.2. I get DNU for Character>>+.
This is due to an initialization in KMKeyEvent (see the attached debug log).
I did the followings:
Gofer it
squeaksource: 'Keymapping';
package: 'ConfigurationOfKeymapping';
load.
(ConfigurationOfKeymapping project ver
Hi,
I am very interested to get Keymapping integrated into Glamour. Could someone
help me to load it?
I tried:
- in Pharo 1.2:
Gofer it squeaksource: 'Keymapping'; package: 'ConfigurationOfKeymapping'; load.
(ConfigurationOfKeymapping project version: #stable) load
- in Pharo 1.3:
Gofer it sque
Right,
the stable has a preconditio which limits it to pharo 1.2.
Furthermore the initialization code seems to be incompatible as it uses to:do:
on Character which is AFAIK not implemented in the core image Pharo 1.3. Hence
apply the following changes:
KMKeyEvent class >> initializeControlSeque
I started on the last Lille sprint a complete rewrite of the Keymapping
package. As of now it is not yet functional but the growing test-coverage
should help to solve this issue.
m(^_-)m
camillo
On 2011-03-03, at 15:16, Camillo Bruni wrote:
> Right,
>
> the stable has a preconditio which limi
Camillo, I was fixing some tests and going to refactor some ugly parts of
the package.
Is there a way to join forces so we don't step into the other work?
Guille
On Sun, Mar 13, 2011 at 6:04 PM, Camillo Bruni wrote:
> I started on the last Lille sprint a complete rewrite of the Keymapping
> pac
I can push my changes. but I don't think we should rely too much on your old
code.
Im trying to keep the structure of the classes, that was already very nice IMO.
I manly adress the following issues:
- use of arrays as result (dedicatet results object)
- string to match the shortcuts with the i
furthermore, lets use a single repos/package (or whatever this is called in MC).
I do not like to commit 3 times while refactoring.
later on we can still split it up so people can actually decide on what to load.
camillo
On 2011-03-13, at 22:20, Camillo Bruni wrote:
> I can push my changes. but
On Sun, Mar 13, 2011 at 6:20 PM, Camillo Bruni wrote:
> I can push my changes. but I don't think we should rely too much on your
> old code.
>
Hehe, my old code is not completely mine. I'll not be responsible of that
:P. I just did a lot of renaming, cleansing, (and make it usable) over the
ori
Excellent initiative Camillo!
Regarding multiple packages: Having multiple packages limits the conflicts, and
saving them individually (for now) it's a small price to pay.
Cheers,
Doru
On 13 Mar 2011, at 22:28, Camillo Bruni wrote:
> furthermore, lets use a single repos/package (or whatever t
I pushed everying into a single Keymapping package for now. As soon as there is
full functionality we should separate it again.
camillo
On 2011-03-13, at 22:40, Tudor Girba wrote:
> Excellent initiative Camillo!
>
> Regarding multiple packages: Having multiple packages limits the conflicts,
I saw :). Just two questions:
- Is the ConfigurationOfKeymapping updated?
- Is it already usable?
Cheers,
Doru
On 14 Mar 2011, at 15:15, Camillo Bruni wrote:
> I pushed everying into a single Keymapping package for now. As soon as there
> is full functionality we should separate it again.
>
>
The last version of the configuration (1.5 I guess, I don't remember now) is
usable. It just have some ugly inner parts, but it's usable.
On Mon, Mar 14, 2011 at 11:17 AM, Tudor Girba wrote:
> I saw :). Just two questions:
> - Is the ConfigurationOfKeymapping updated?
> - Is it already usable?
On 2011-03-14, at 15:17, Tudor Girba wrote:
> I saw :). Just two questions:
> - Is the ConfigurationOfKeymapping updated?
that I pushed to the existing branch
> - Is it already usable?
not yet, didn't have too much time so far, but the basic tests are working.
the interface will stay the same,
Add keymappings to
http://book.pharo-project.org/book/PharoTools/
On Mon, Mar 14, 2011 at 3:20 PM, Camillo Bruni wrote:
>
> On 2011-03-14, at 15:17, Tudor Girba wrote:
>
> > I saw :). Just two questions:
> > - Is the ConfigurationOfKeymapping updated?
>
> that I pushed to the existing branch
>
The keymapping framework is already close to be completely rewritten. Most
tests work (except for 3). Half of the methods are gone and the event matching
works directly on Event level, no more evil string matching.
I'll ping as soon as the rest of the tests work properly.
camillo
On 2011-03-19
Excellent!
I can't wait to use it when it's ready :)
Doru
On 20 Mar 2011, at 17:33, Camillo Bruni wrote:
> The keymapping framework is already close to be completely rewritten. Most
> tests work (except for 3). Half of the methods are gone and the event
> matching works directly on Event le
26 matches
Mail list logo
