I think that some roassal parts can be unified both to reduce the code publication and define some kind of common interface.
For example there there are mouse and key event classes for RT, R3, RW, they can be unified, as they have nothing special to do with the different frameworks. Also the Traits with a common protocol can be introduced. Despite the different implementations all elements should understand #translateTo: for example. Having this defined in a trait as an explicit requirement can help to have a clearer view on the design. Because despite being similar, all roassal versions implement different protocols, and I think that this is not because of design decisions, but because someone needed that specific shortcut/functionality while developing in a certain version of roassal.
Uko
On 12 May 2015, at 18:48, Alexandre Bergel <alexandre.bergel@me.com> wrote:
I am not sure about this.
In the previous version of Roassal3D we had this. In the version based on Woden we do not have it.
Give me a bit of time to evaluate this. Having popup is essential.
Which highlighting do you need?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On May 12, 2015, at 11:27 AM, Natalia Tymchuk <natalia.tymchuk@unikernel.net> wrote:
Hello.
I started to work with Woden. Unfortunately I cannot find the interaction I need.
Does RWoden has the interaction as popup, highlighting and menu activating?
Best regards,
Natalia
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.chhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev