Bug 12474 - how might I help?

[Graham Perrin]

I'd love to do whatever I can to help progress <https://bugzilla.osafoundation.org/show_bug.cgi?id=12474>,

alt-arrow key combinations must navigate text only; MUST NOT navigate other aspects of Chandler Desktop for Mac OS X

It may be an edge case, but bugs of this type — conflict with key combinations that are proper to Mac OS X — severely retard my use of affected applications.

Put simply: the conflict makes it difficult for me to type.

How can I help? Can someone offer a URL to the relevant piece of code?

If chat is appropriate, I'm often at <irc://irc.freenode.net/#chandler> and nearby.

TIA
Graham

[Grant Baillie]

On 11 Jan, 2009, at 06:59, Graham Perrin wrote:

>
> I'd love to do whatever I can to help progress
> <https://bugzilla.osafoundation.org/show_bug.cgi?id=12474>,
>
>
>
>> alt-arrow key combinations must navigate text only; MUST NOT navigate
>> other aspects of Chandler Desktop for Mac OS X
>>
>
> It may be an edge case, but bugs of this type — conflict with key
> combinations that are proper to Mac OS X — severely retard my use of
> affected applications.
>
> Put simply: the conflict makes it difficult for me to type.
>
> How can I help? Can someone offer a URL to the relevant piece of code?

Hi, Graham

I believe most of the almost all of our key combinations are set in  
menu.py:

http://svn.osafoundation.org/chandler/trunk/chandler/parcels/osaf/views/main/menus.py

In particular, if you search for "accel" in that file, you'll see  
where key combinations are set. (Note that these are as specified in  
wxPython: "Ctrl+A" will get mapped on the Mac to Apple+A (no shift).  
Mostly, though, if you want to help, maybe you could suggest a new set  
of key combinations that makes sense on all platforms ... So far as I  
remember, it's hard to override Chandler's event dispatch mechanism so  
that thos arrow-key combinations would work correctly in all cases.

--Grant

> If chat is appropriate, I'm often at <irc://irc.freenode.net/
> #chandler> and
> nearby.
>
> TIA
> Graham
> --
> View this message in context: http://n2.nabble.com/Bug-12474---how-might-I-help--tp2141609p2141609.html
> Sent from the chandler-dev mailing list archive at Nabble.com.
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

[Graham Perrin]

Grant Baillie wrote:

Mostly, though, if you want to help, maybe you could suggest a new set of key combinations that makes sense on all platforms ... So far as I remember, it's hard to override Chandler's event dispatch mechanism so that thos arrow-key combinations would work correctly in all cases.

Many thanks.

Some screen shots that I captured for an OOo bug  <http://www.brighton.ac.uk/centrim/Members/gjp4/ooo/qa/92224> will probably help me in this task. At least, the shots might help to indicate the combinations that must/should be *avoided*.

Note to self: <https://bugzilla.osafoundation.org/show_bug.cgi?id=5730>

[Graham Perrin]

Grant Baillie wrote:

I believe most of the almost all of our key combinations are set in menu.py:

http://svn.osafoundation.org/chandler/trunk/chandler/parcels/osaf/views/main/menus.py

Happily, only two Alt accelerators in menus.py.

Changing the two from Alt to Ctrl should do the trick.

Touch wood, as I'm thrashing around in Chandler Desktop, no other conflicts have been noticed.

There's one other GoTo… related suggestion at
<https://bugzilla.osafoundation.org/show_bug.cgi?id=12474#c4>.

---

Beyond GoTo…
for the broader range of key combinations, to guide me I'm building a list <http://www.diigo.com/list/grahamperrin/cdn> then I'll have a think then … come back to chandler-dev with suggestions?

Or would you prefer me to throw it open to chandler-users?

No rush. It'll probably be a while before I attend to the broader stuff. My (selfish) priority was the alt key conflicts.

Best,
Graham

[Graham Perrin]

Grant Baillie wrote:
>
> … Mostly, though, if you want to help, maybe you could suggest a new set
> of key combinations that makes sense on all platforms …
>

<http://www.brighton.ac.uk/centrim/Members/gjp4/chandler/accel/>

--
View this message in context: http://n2.nabble.com/Bug-12474---how-might-I-help--tp2141609p2209415.html
Sent from the chandler-dev mailing list archive at Nabble.com.

[Graham Perrin]

(Please ignore the previous message, sent accidentally whilst drafting, since deleted from Nabble.)

Grant Baillie wrote:

… Mostly, though, if you want to help, maybe you could suggest a new set of key combinations that makes sense on all platforms …

The table at <http://www.brighton.ac.uk/centrim/Members/gjp4/chandler/accel/> is sparsely populated, I'll fill some gaps in due course.

A Mac OS X perspective should consider behaviours in iCal; in at least some situations running iCal is the cornerstone to effective synchronisation (through Sync Engine and device conduits) with iPhone and other devices.

A Linux perspective might consider behaviours of a comparable cornerstone application. I assume Mozilla Sunbird but other suggestions are welcome.

A Windows XP perspective might consider behaviours of a comparable cornerstone application. I assume Microsoft Office Outlook 2008 but other suggestions are welcome.

A Windows Vista perspective is not tabled. If tabled, it should probably consider behaviours of Windows Calendar.

In any case: I'll probably table no more than one non-Chandler application per OS.

Obviously, not all gaps will be filled, and many discrepancies will be negligible, but the table should at least highlight things that are impossible in Chandler.

Best regards
Graham

[Graham Perrin]

Graham Perrin wrote:

Grant Baillie wrote:

… Mostly, though, if you want to help, maybe you could suggest a new set of key combinations that makes sense on all platforms …

The table at <http://www.brighton.ac.uk/centrim/Members/gjp4/chandler/accel/> is sparsely populated, I'll fill some gaps in due course.

This task is not forgotten. I'm watching and occasionally contributing to <http://wiki.services.openoffice.org/wiki/Mac_OS_X_Porting_-_Keyboard_Shortcuts> (referred from <http://qa.openoffice.org/issues/show_bug.cgi?id=99080>); from that joint effort in the OpenOffice.org area it should become easier to make decisions on conflicts/grey areas that may appear in the Chandler area.