[Kde-bindings] branches/work/kdebindings-smoke2
Arno Rehn
arno at arnorehn.de
Wed Jul 18 11:32:29 UTC 2007
Am Mittwoch, 18. Juli 2007 schrieb Richard Dale:
> On Wednesday 18 July 2007, Arno Rehn wrote:
> > SVN commit 689263 by arnorehn:
> >
> > * Made some more or less final changes to smoke.h
> > * Code generation works well, however it could be beautified a bit more.
> > Looks more like a big hack than proper code.
> > Generation for the type list could also be improved, it still has too
> > many redundant types in it.
> > * The code generation for smoke modules with parents currently relies on
> > a text file generated together with each module. Use a smoke
> > introspection tool like the one proposed by Thomas Moenicke instead.
>
> I think we need pass to kalyptus a list of classes to be included for each
> module, along with the module name. Any classes not in that list should
> just be marked as 'external', and looked up in some other module.
That's exactly what kalyptus currently does, just the other way round. At the
end of the code generation for SmokeQt it produces a file
called "qt_smoke_classlist" which contains the name of the module and a list
of classes that are managed within it. This list is passed to kalyptus, when
it generates e.g. SmokeQScintilla. If the class is listed in that text file,
no code for it is generated. If it's needed by some other class / method, a
ParentIndex into SmokeQt is set.
> I still don't see the need for defining parent modules though, as long as
> we can look up the module given a particular class name.
I'll try that. I don't really like this ParentIndex struct and this might
actually be a way to get rid of it.
--
Arno Rehn
arno at arnorehn.de
More information about the Kde-bindings
mailing list