[Kde-bindings] Replacing kalyptus

[Arno Rehn]

Am Mittwoch 03 Oktober 2007 19:00:05 schrieb Mauro Iazzi:
> gccxml can accept commandline define like -DFOO="bar". Marking the
> attribute "gccxml" will make it visible to it. I still do not know how
> this would come out in the xml, but this is the easy bit.
>
> mauro
That would still require to mark every signal/slot seperatly with the 
attribute, since you cannot include attributes in the access specifier. 
Something like
public __attribute((gccxml("slots"))):
	void foo();
doesn't work.


> On 03/10/2007, Arno Rehn <arno at arnorehn.de> wrote:
> > Am Mittwoch 03 Oktober 2007 18:41:18 schrieb Mauro Iazzi:
> > > in the meanwhile I read of the signal/slot question. It is true that
> > > gccxml discards the Qt tags, so they are not avaliable by the binding
> > > code, but this could be overcome by using attributes.
> >
> > But how can we mark a method with such an attribute without modifying the
> > source?
> >
> > > However I feel that this is not a big issue in any way, because with
> > > lqt I can bind QMetaObjects as well, and obtaining those I have all
> > > the Qt reflection at my disposal. So if I know the signal (slot) I
> > > need at compile time I can write it, If not I can use QMetaObjects,
> > > avoiding the duplication of meta-informations in the runtime.
> >
> > Projects like Qyoto need the information which methods are signals/slots
> > when the sources are generated. So the information should be somehow
> > ready for the generator.
> >
> > --
> > Arno Rehn
> > arno at arnorehn.de
> > _______________________________________________
> > Kde-bindings mailing list
> > Kde-bindings at kde.org
> > https://mail.kde.org/mailman/listinfo/kde-bindings
>
> _______________________________________________
> Kde-bindings mailing list
> Kde-bindings at kde.org
> https://mail.kde.org/mailman/listinfo/kde-bindings



-- 
Arno Rehn
arno at arnorehn.de