[Kde-bindings] Viability of Qyoto

[Dimitar Dobrev]

Well, I actually always built it in Debug simply because this is the default configuration in Visual Studio. :) This one also doesn't make any sense, the build config shouldn't affect the output at all.



________________________________
 From: Steven Boswell II <ulatekh at yahoo.com>
To: KDE bindings for other programming languages <kde-bindings at kde.org> 
Sent: Friday, December 16, 2011 5:01 PM
Subject: Re: [Kde-bindings] Viability of Qyoto
 

Interesting...if I build assemblygen in Debug mode under Windows, it runs. It doesn't solve the link problem with InstallListWizardButtonToQListWizardButton.  But at least that's something.



________________________________
 From: Steven Boswell II <ulatekh at yahoo.com>
To: Dimitar Dobrev <dpldobrev at yahoo.com>; KDE for other programming languages <kde-bindings at kde.org> 
Sent: Friday, December 16, 2011 7:37 AM
Subject: [Kde-bindings] Viability of Qyoto
 

Yeah, I'm getting tired of it too.  The change you recommended got past that crash, but now it dies in my Ui_Setup() function when it tries to create the first user-interface element (a QAction, in this case).  Another thing I noticed, from the gdb call stack, is that it seems to be running the .NET 2.0.50727 runtime, even though I have the 3.5 runtime selected in MonoDevelop, and I'm using the 3.5 compiler in assemblygen.

I can't tell you how much I want to recommend to my workplace that we build our app using Qt/Qyoto, but at the rate this is going, I'm probably going to have to panic and learn WinForms really quickly.  Qyoto running only under Linux is fine for the app I'm building at home, but that's not good enough for the app I'm building at work.

I guess we have to wait until Arno has time to help track down these bugs, or until he takes the time to add source-code comments to his code, if ever.

Seriously...how did any open-source project ever come into being without adequate developer documentation?  I can only speak for myself, but my main open-source project (a temporal analog-video denoiser called y4mdenoise, part of the mjpegtools project) is heavily documented.  I consider developer documentation an unspoken requirement, but clearly I'm in the minority.


Steven Boswell



________________________________
 From: Dimitar Dobrev <dpldobrev at yahoo.com>
To: Steven Boswell II <ulatekh at yahoo.com>; KDE for other programming languages <kde-bindings at kde.org> 
Sent: Friday, December 16, 2011 1:41 AM
Subject: Re: [Kde-bindings] Building "assemblies" branch of assemblygen under Windows
 

[...] I'm getting a bit tired of all these bugs especially since the "sender", which turns out to be the "dialog.exec", problem, is still not solved, and not being able to show a dialogue in a GUI tool-kit renders it completely useless.


_______________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-bindings/attachments/20111216/ee8fdc0d/attachment.html>