imho it would be good to have support to specify the profile linked to a vapi. so vala will generate custom code depending on which vapi you use.
it will be obvious a limitation in comunicating classes between those profiles. but calling methods and instantiating objects should be cross profile. this will enable vala to create gtk apps with dova. what do you think? instead of having a global profile setup we will have a per namespace profile configuration. On 01/02/2011, at 1:19, Gavrilov Maksim <[email protected]> wrote: > 01.02.2011 08:49, Maga Abdurakhmanov пишет: >> I have a question about Dova and it's future. At this moment Dova is in the >> experimental state and incompatible with glib. Is there any real compelling >> reason that makes dova incompatible with glib? > > Dova is now created to be another huge framework (just like now GLib is), but > fully integrated in Vala and using all its features. Why SHOULD it be > compatible with GLib? That's the better question, I think. > > Why should Dova follow all that durty low-level rules and abstractions used > in GLib, if it has its own support of interfaces, classes, etc.? > >> If we could base a program on dova but still have access to the very rich >> set of glib based libraries it opens door for the dova in real applications. > > Again, Dova is created to fully replace GLib/GObject. Your question is > something like you ask why is GLib incompatible with Qt? If you want to use > both of them, you should (am I right?) encapsulate GLib-related and > Qt-related logics into different modules compiled into different libraries > and then used by your app. > > -- > Gavrilov Maksim <[email protected]> > _______________________________________________ > vala-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/vala-list _______________________________________________ vala-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/vala-list
