[Digikam-devel] Exposing the QT API in the scripting interface.

[Gilles Caulier]

Why not to let's that as well for the moment, and look if we need to
reduce Qt API visibility later.

How Amarok team do about this subject

Gilles Caulier

2010/7/16 kunal ghosh <kunal.t2 at gmail.com>:
> Hi all,
> Need your opinion for the scripting interface.
> I am exposing the whole Qt API (generated by qtscriptbinding generator) by
> default.So, when ever a script author enters
> var a = QLabel("hello")
> they would be able to access it without importing any modules like
> Importer.imporExtension("qt.qui") etc.
> This makes it very easy for a plugin author to directly use the whole Qt API
> without having to import modules individually.
> I would need suggestions / comments on the approach taken above.
> --
> regards
> -------
> Kunal Ghosh
> Dept of Computer Sc. & Engineering.
> Sir MVIT
> Bangalore,India
>
> Blog:kunalghosh.wordpress.com
> Website:www.kunalghosh.net46.net
>
>
>
> _______________________________________________
> Digikam-devel mailing list
> Digikam-devel at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>