[Kde-bindings] Viability of Qyoto

[Steven Boswell II]

Yeah, in an earlier panic, I rewrote the GUI layer of my app in GTK#.  It works fine in Linux, but I'm getting some sort of low-level crash in Windows when modifying the data displayed by my tree view.  I haven't gone any further with that port yet.  That's why I was thinking WinForms -- I really don't need to go through all the fun of learning another GUI toolkit, just to have it crash mysteriously under Windows.


I didn't know I could load the .ui file directly!  I thought I had to use uics.  Which API is that?

BTW, dialogs are currently working for me.  I have an open-file dialog and a QMessageBox in my current app; both are showing up in Windows (with the Debug build of Qyoto, at least).

For the record, one problem I'm having in both the old and new version of Qyoto Windows, is that "copy" doesn't seem to work.  Whenever I past into a text view, it's always the last thing I copied from another application.  But if I copy from one of my text views and paste, it pastes the last thing that was in the system clipboard.  Dunno if you've run into that yet.

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 7:56 AM
Subject: Re: Viability of Qyoto
 

Well, I personally began porting some non-dialogue parts of our app (they are quite a few) "hoping" that in the mean time Arno will fix the dialogues. I fully understand how much you want it to work because I do just as much. We are using GTK# now and just don't get me started on GTK, especially its looks on the mac.
As for your error, this one I haven't hit. First of all, which way are you using: generating your C# with uics or loading the ui file with qyoto-gui-tools?



________________________________
 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 4:37 PM
Subject: 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-bindings/attachments/20111216/68b370b4/attachment.html>