[Kde-bindings] Re: Kde-bindings Digest, Vol 18, Issue 23

[Arkar Kyaw Win]

kde-bindings-request at kde.org wrote:

>Send Kde-bindings mailing list submissions to
>	kde-bindings at kde.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://mail.kde.org/mailman/listinfo/kde-bindings
>or, via email, send a message with subject or body 'help' to
>	kde-bindings-request at kde.org
>
>You can reach the person managing the list at
>	kde-bindings-owner at kde.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Kde-bindings digest..."
>
>
>Today's Topics:
>
>   1. KDevelop ruby support (Thibauld Favre)
>   2. Re: KDevelop ruby support (Richard Dale)
>   3. Re: KDevelop ruby support (Thibauld Favre)
>   4. Re: is sip pyqt and pykde include in latest version of
>      kdebinding? (Simon Edwards)
>   5. Re: is sip pyqt and pykde include in latest version of
>      kdebinding? (Simon Edwards)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Fri, 22 Oct 2004 12:40:05 +0200
>From: Thibauld Favre <thibauld.favre at laposte.net>
>Subject: [Kde-bindings] KDevelop ruby support
>To: Richard Dale <Richard_Dale at tipitina.demon.co.uk>
>Cc: kde-bindings at kde.org
>Message-ID: <200410221240.05754.thibauld.favre at laposte.net>
>Content-Type: text/plain;  charset="us-ascii"
>
>Hi Richard,
>
>I've seen that you've been enhancing KDevelop ruby support lately.
>I wanted to give you a few feedbacks about your Korundum template :
>- First, it seems weird that we have to "build" a project based on a scripting 
>language :) I suppose there's no choice if you want to fit in the kdevelop 
>framework.
>- Then I had problems running the application because your class names all 
>begin with a small letter ("testPreferences") instead of a capital letter 
>("TestPreferences"). On my system, ruby refuses to execute with this type 
>error :
>-------------------
>main.rb:5:in `require': ./testiface.rb:1: class/module name must be CONSTANT 
>(SyntaxError)
>class testIface < KDE::DCOPObject
>                 ^      from main.rb:5
>-------------------
>- Once you get rid of those errors, I'm still unable to execute the program :
>--------------------
>main.rb:10: undefined method `I18N_NOOP' for main:Object (NoMethodError)
>--------------------
>I suppose it's working on your system, what am I supposed to do to have it 
>work on mine ?
>
>Thanks a lot for your great work !
>
>thibs
>
>
>------------------------------
>
>Message: 2
>Date: Fri, 22 Oct 2004 12:08:06 +0100
>From: Richard Dale <Richard_Dale at tipitina.demon.co.uk>
>Subject: Re: [Kde-bindings] KDevelop ruby support
>To: KDE bindings for other programming languages
>	<kde-bindings at kde.org>
>Message-ID: <200410221208.07206.Richard_Dale at tipitina.demon.co.uk>
>Content-Type: text/plain;  charset="iso-8859-1"
>
>On Friday 22 October 2004 11:40, Thibauld Favre wrote:
>  
>
>>Hi Richard,
>>
>>I've seen that you've been enhancing KDevelop ruby support lately.
>>I wanted to give you a few feedbacks about your Korundum template :
>>- First, it seems weird that we have to "build" a project based on a
>>scripting language :) I suppose there's no choice if you want to fit in the
>>kdevelop framework.
>>    
>>
>Yes, it uses automake and it took me a bit of puzzling out how all that 
>worked. It needs some install rules so that you can run the app like a normal 
>KDE one. I wondered if it might be a good idea to have a top level shell 
>script to start the ruby code, install that in the KDE bin dir with the ruby 
>under $KDEDIR/share/apps/<appname>..
>
>I would say the advantage of the build step is that you can invoke the make 
>rules to generate ruby source from the .ui files via rbuic. I think there is 
>a run button, so that probably builds and runs. It doesn't quite work yet 
>because I think it is expecting the ruby scripts to be in the top level of 
>the project, rather than under src.
>
>  
>
>>- Then I had problems running the application because your class names all
>>begin with a small letter ("testPreferences") instead of a capital letter
>>("TestPreferences"). On my system, ruby refuses to execute with this type
>>error :
>>-------------------
>>main.rb:5:in `require': ./testiface.rb:1: class/module name must be
>>CONSTANT (SyntaxError)
>>class testIface < KDE::DCOPObject
>>                 ^      from main.rb:5
>>    
>>
>You need to type a name starting with upper case, in the Application Name 
>field in the Create New Project wizard. It should then convert that to lower 
>case for the project directory, but leave it as it is for the class names.
>
>  
>
>>-------------------
>>- Once you get rid of those errors, I'm still unable to execute the program
>>: --------------------
>>main.rb:10: undefined method `I18N_NOOP' for main:Object (NoMethodError)
>>--------------------
>>I suppose it's working on your system, what am I supposed to do to have it
>>work on mine ?
>>    
>>
>Yes, I've only recently added that to the HEAD branch - you'll need to update 
>your cvs.
>  
>
>>Thanks a lot for your great work !
>>    
>>
>Thanks. I've only spent about a day or so on it, but I think I already prefer 
>it to Kate because class browser makes it so much easier to find things. Next 
>I want to add slots/signals declaration navigation to the class browser, and 
>allow multi-line attr declarations. And a few more templates, like a DCOP 
>service, and improve the existing qtruby one so it is a port of the C++ 
>qmakeapp with a main window and menus etc.
>
>Nested classes are a problem with the way the parser works - I haven't decided 
>what to do about them yet.
>
>-- Richard
>
>
>------------------------------
>
>Message: 3
>Date: Fri, 22 Oct 2004 15:16:31 +0200
>From: Thibauld Favre <tfavre at mandrakesoft.com>
>Subject: Re: [Kde-bindings] KDevelop ruby support
>To: KDE bindings for other programming languages
>	<kde-bindings at kde.org>
>Message-ID: <200410221516.31945.tfavre at mandrakesoft.com>
>Content-Type: text/plain;  charset="iso-8859-1"
>
>Le Vendredi 22 Octobre 2004 13:08, Richard Dale a écrit :
>  
>
>>>I've seen that you've been enhancing KDevelop ruby support lately.
>>>I wanted to give you a few feedbacks about your Korundum template :
>>>- First, it seems weird that we have to "build" a project based on a
>>>scripting language :) I suppose there's no choice if you want to fit in
>>>the kdevelop framework.
>>>      
>>>
>>Yes, it uses automake and it took me a bit of puzzling out how all that
>>worked. It needs some install rules so that you can run the app like a
>>normal KDE one. I wondered if it might be a good idea to have a top level
>>shell script to start the ruby code, install that in the KDE bin dir with
>>the ruby under $KDEDIR/share/apps/<appname>..
>>    
>>
>That would definitely be cool because so far we cannot execute the program 
>without calling ruby. This would definitely be a plus to be able to 
>transparently run ruby apps.
>
>  
>
>>I would say the advantage of the build step is that you can invoke the make
>>rules to generate ruby source from the .ui files via rbuic. I think there
>>is a run button, so that probably builds and runs. It doesn't quite work
>>yet because I think it is expecting the ruby scripts to be in the top level
>>of the project, rather than under src.
>>    
>>
>Ok but I have another pb with executing my app (==clicking first button on the 
>left) that you might have already faced : Even if I set up kdevelop to 
>execute the app from the app directory ("where the executable is"), KDevelop 
>launches "ruby /home/[path]/project.rb" and of course it cannot start as the 
>program doesn't find its required classes. The solution I found is to use the 
>other button (there are 2 "KDE wheel" button, I'm talking about the one on 
>the right) which launches "./main.rb" but from the BUILD directory. To make 
>that work, I had to change a project option to have KDevelop call ruby with 
>"-C" argument : "ruby -C [path]"
>Did you have the same problem ? If yes, how did you solve it ?
>By the way, what is the name of those 2 buttons in english ? In french, the 
>translation is bad because they both have the same name : one is "execute" 
>and the other one is "execute the program" ...... eh ??? :)
>
>  
>
>>>- Then I had problems running the application because your class names
>>>all begin with a small letter ("testPreferences") instead of a capital
>>>letter ("TestPreferences"). On my system, ruby refuses to execute with
>>>this type error :
>>>-------------------
>>>main.rb:5:in `require': ./testiface.rb:1: class/module name must be
>>>CONSTANT (SyntaxError)
>>>class testIface < KDE::DCOPObject
>>>                 ^      from main.rb:5
>>>      
>>>
>>You need to type a name starting with upper case, in the Application Name
>>field in the Create New Project wizard. It should then convert that to
>>lower case for the project directory, but leave it as it is for the class
>>names.
>>    
>>
>Oh ok ! I didn't notice that Kdevelop was using the name I gave to the project 
>to generate the template classes.
>
>  
>
>>>main.rb:10: undefined method `I18N_NOOP' for main:Object (NoMethodError)
>>>--------------------
>>>I suppose it's working on your system, what am I supposed to do to have
>>>it work on mine ?
>>>      
>>>
>>Yes, I've only recently added that to the HEAD branch - you'll need to
>>update your cvs.
>>    
>>
>Ok fine ! Works great !
>
>  
>
>>Thanks. I've only spent about a day or so on it, but I think I already
>>prefer it to Kate because class browser makes it so much easier to find
>>things. Next I want to add slots/signals declaration navigation to the
>>class browser, and allow multi-line attr declarations. And a few more
>>templates, like a DCOP service, and improve the existing qtruby one so it
>>is a port of the C++ qmakeapp with a main window and menus etc.
>>    
>>
>
>Great ! I also put I list of features I'd like to implement in Kdevelop when I 
>have time. That includes :
>- Support ruby code folding in kate.(that will be the first thing I'll do)
>- Doc generation
>- Code completion : do you think it's doable with ruby ? So far I have 
>absolutely no clue about how that works so I really can't tell if it's 
>realistic
>- Being able to execute the last version launched that didn't crash (even if 
>we changed some code since then). It's a normal behavior for compiled 
>language (as long as you don't try to rebuild) but it's a feature for 
>scripting languages...
>- Manage cross references in an entire project to be able to quickly see if 
>you wrote a wrong variable name. Indeed, the error I do most when I code is 
>mispelling (ex : I use "@ContratLbl" instead of "@ContratsLbl"...). As 
>there's no compile time check, it's difficult to spot these errors and worst 
>of all, as long as you don't execute the portion of code with an error, you 
>don't even notice that your program has a bug. This scares me and I try to 
>find ways to check that my code seems to be correct without having to code 
>and run a lot of tests :
>1) Code completion, this way you're sure you're using the right variable. But 
>you cannot use code completion everywhere....
>2) Cross references : I'd like to have a left panel in kdevelop where I can 
>see the number of occurences of each variable I use in my code. This way we 
>can immediatly see the variables used only once : they are probably variables 
>mispelled.
>
>I'd be interested to have your views on this problem. Script languages are 
>great but they become a lot more error prone to  sleeping bugs due to syntax 
>errors when code grows. Of course we can fix the problem real quick but "only 
>once we found it".
>
>thanks,
>
>thibs
>
>
>------------------------------
>
>Message: 4
>Date: Fri, 22 Oct 2004 18:55:46 +0200
>From: Simon Edwards <simon at simonzone.com>
>Subject: Re: [Kde-bindings] is sip pyqt and pykde include in latest
>	version of	kdebinding?
>To: kde-bindings at kde.org
>Cc: kde-bindings at mail.kde.org, Arkar Kyaw Win <ngan_yine at softhome.net>
>Message-ID: <200410221855.47057.simon at simonzone.com>
>Content-Type: text/plain;  charset="iso-8859-1"
>
>Hello,
>
>On Thursday 21 October 2004 19:02, Arkar Kyaw Win wrote:
>  
>
>>Hi I would like to confirm whether this is true or not ?I read it in 
>>kde.org that in new kde 3.3.1 they include sip pyqt and pykde in 
>>kdebinding .I just upgrade to kde 3.3.1 including kdebining .I left none 
>>of the old kde file in my computer but I still couldn't use program that 
>>include sip or pyqt or pykde like superkaramba slickbar theme.So I try 
>>to insall all those manually but I couldn't compile any more.When I ask 
>>around they said that it is because of kde 3.3.1 kdebinding.So I would 
>>like to know that it is true they got sip ,pyqt and pykde in kdebinding 
>>and if it true how can we use the sip ,pyqt and pykde ?
>>    
>>
>
>Yes, Sip, PyQt and PyKDE are distributed as part of kdebindings.
>
>As for superkaramba, I can't say what is going on there. If I were you I would 
>ask whoever makes the distribution that you are using, about the status of 
>PyQt+PyKDE in thier kdebindings package.
>
>cheers,
>
>  
>
I use slackware 10 and I had tried to install kdebinding manually.Frist I
removepkg kdebinding and then I tried to compile the kdebinding.I tried 
it from tar ball source file ,as I read readme file I read that python 
is broken in kdebinding but I tried install it anyway .After runing 
./configure and in make it stop compiling and said that after compile 
sip in python they couldn't go much further because sip would need this 
switch -l qt-mt to compile pykde further on.It the normal procedure to 
compile sip for pykde manually but I can't compile pykde now because of 
this new kde 3.3.1 version .
Ohh!when I check kdebinding.tgz file I found that they didn't include 
python folder which include pykde int it.They must have cut it out.I 
don't know how to install kdebinding with python support for switch -l 
qt-mt in sip folder .
any idea?