Exposing the QT API in the scripting interface.

[kunal ghosh]

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
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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 <[hidden email]>:

> 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
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[kunal ghosh]

On Sat, Jul 17, 2010 at 2:12 PM, Gilles Caulier <[hidden email]> wrote:

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

The amarok team has an Importer class which has a function called "include" which takes the API to be included

as a QString argument. The function then calls QScriptEngine object -> importExtension (QString variable).

I feel that , as of now let us leave it as it is. I will focus on getting the script manager.

Also exposing the whole Qt API by default is user friendly as the script author doesn't need to know

which qt modules to import.

 

Gilles Caulier

2010/7/16 kunal ghosh <[hidden email]>:

> 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
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

--
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
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel