jessyink-team team mailing list archive

[Egor Zindy <ezindy@xxxxxxxxx>]

Hello Hannes,

> just a quick update: I finally got around to merging Egor's keyboard
> branch into the trunk. Thanks a lot again for the great work!

No problems, I'm glad the changes made it to trunk.

> As Egor mentioned that he wanted to spend some time on the index mode
> code, I thought I get started on the custom key bindings.

Great, I'll start an index branch. Nothing fancy, just enough code to
pack as many slides on the screen as possible.

> I am planning
> on using a similar technique as I employed in the 2.0 prototype. Meaning
> that I'll have the python extension create a new script node with a
> unique id. The script node is then assigned a function that provides the
> key bindings. If no node is found, the default key bindings are used.

Excellent! I like the possibility of fall-back to a default state, makes sense.

> Oh, there was one thing I wanted to ask you: Do you think that we should
> have a separate "drawing mode" (similar to index mode) and use a key for
> toggling between the modes?
> we would have more keys available (as they could be assigned per mode)
> and it would move to code towards a modular design, which I think is
> essential for future development.

I was thinking about that. The mouse button used to forward one slide
but it doesn't anymore because mouse clicks are captured by the
drawing code. Fine by me, but it might make more sense to have the
drawing as a separate mode to keep the "default" presentation mode
uncluttered.

... and with all the modes we're talking about (presentation, index,
timer, drawing, whiteboard, help), there might be enough buttons to
build a toolbar?
https://blueprints.launchpad.net/jessyink/+spec/slide-toolbar

Buttons could also be part of the modular design: toolbar only gets
populated when the module specifies one or more toolbar buttons.

Anyway, I'll look into the index when I find some time :-)

Cheers,
Egor

Attachment: pen_cursor.png
Description: PNG image