29 Mar
2009
29 Mar
'09
2:27 a.m.
Jon A. Cruz wrote:
The one-to-one of one Gtk::Action per will work in some cases, but breaks down in others. So forcing one-to-one will complicate implementation of many of them.
Also Gtk::Action is a very UI-centric class. We need something abstract that can represent an action on
- a document
- a desktop
- the "Application" itself.
the case of #2 can be replaced by Gtk::Action appropriately, but the others don't really match conceptually.
I followed some of that discussion. The main idea is to use one action group per document. For case #3, we use a separate global action group that does not act on any document but rather on the entire application.
I don't really understand the distinction between #1 and #2.
Regards, Krzysztof Kosiński
--
View this message in context: http://www.nabble.com/GSOC%3A-Cross-platform-WMF-and-EMF-IO-and-other-ideas-...
Sent from the Inkscape - Dev mailing list archive at Nabble.com.