Viktor Szakáts wrote:
>
> We've decided to not support the plugin architecture of QT lib
> for various reasons detailed back then.
>
:buildKey() only generates a key which are essential for a plugin
to be linked in a version of Qt.
As far as my understanding extends, this class has nothing to do with plugin
architecture of Qt by "itself". It simply retreives the licensing info and
provides access
to some paths. For that matter, Harbour wrappers can never support plugins
in any manner.
It is a difficult class to generate dynamically so I failed on many
occassion to develop it. And still I do not know how to?
Also I do not see the real benefits of this class, taken especially
the LGPL licensing issues.
Probably CarozoDeQuilmes want to issue some commands based on
Qt library version. That can be the only valid reason for this request.
-----
enjoy hbIDEing...
Pritpal Bedi
_a_student_of_software_analysis_&_design_
--
View this message in context:
http://n2.nabble.com/Class-QLibraryInfo-in-HbQt-tp4641413p4641755.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
