- Was Mandrake 7.0... legal question

Serge Lussier lusse at videotron.ca
Sun Feb 13 01:33:40 GMT 2000


On Sun, 13 Feb 2000, Serge Lussier wrote:
>>
>> HI jbb anf All - This is a long message.
>>  - I want to apologize for the late response, and more important
>> the fact that I did not install the latest ( Kdevelop  ) version to
test
>> against Mandrake 7.0 . I'm sorry.
>>
>I've now tested against version Mandrake7.0 and I believe the debugger
code in
>cvs works.
>
>--
>Regards,
>
>jbb
>http://homepages.ihug.co.nz/~jbb
>ICQ: 60412209

Thank you jbb. I'm looking forward for  KDE2.0 and Kdevelop 2.0
releases.
As soon as my rush is finished,  I'll be free for Kdevelop code
exploration and tests...
don't hesitate to ask me for help  in "field" tests also.

In the meantime, I have a dream: Let me tell you what I wish to look
for:
- In the dialog editor I would want to add:
   The ability to let the user tells that the widget, when generating
code,  will be a new class
    derivated from the current edited widget. ( sorry for my english ).
I know this is done for
    the QDialog but not for the individual child widgets. And of course
the user will be able to control
    wich member function to be reimplemented in that new class and
generate the extended skeleton
    source code. Of course, this will implies to know ALL the class's
member functions of QT and KDE.
   This is HUGE!  Woohoo!  With the help of a  kind of a database it is
feasible.

But before I do any thing, I  know I have to be confortable with the
Kdevelop sources code. I have to study
carefully the sources. This is what I would want to do for Kdevelop.
(version 3.0 maybe -;)  hehe).


>Jerry L Kreps wrote:
>
> > Serge Lussier wrote:
> During the development , I wrote a GUI for testing the first two parts

> to visualize my tests.
>

oops! I should have written " I wrote a GUI program to visualize my
tests " -:)
but I'm sure you understood what I meant

> And yes, I've made it with the help of Kdevelop under KDE/QT on my
Linux
> workstation at work AND at home.
>
> "internal use only" says it all.  As I understand the GPL,
> as long as your don't  sell or give your binaries to a third
> party you can use GPL tools till the Sun stops shining. If,
> on the other hand, you are distributing the binaries to
> individuals who are NOT working for your company, then you
> must release your modified source code  with the binaries or
> give the source to anyone who asks for it AND you must
> purchase a Qt license to continue using KDevelop for
> commerical production.  IMHO, but IANAL.


By the way, what does < IMHO; IANAL;  and  AFAIK >  abrevs.  mean?  (
remember i'm not english ).



> KDevelop is a great tool, isn't it!

- Oh yes!  Now I'm completly  addicted I just can't code without
Kdevelop .


---- Just for laugh : ----
I'm not an advanced programer.  A few days ago,  I 've made a GUI front
end for data presentation from a remote
server. I've used the KSocket and its SIGNAL interface for the TCP/IP
client stuff.  I wanted to remove the KSocket interface and see if
I could use the pthread lib with QT/KDE  .  I mean one thread blocs on
select, read socket stream  and update the GUI,  and the other is free
for the GUI i/o.  So after coding TCP/IP setup by hands, setup threads,
guess what happened when one thread tried to update the GUI while the
other thread was also updating the same object ....(CRASH)  Woohoo!  I
made it without knowing about mutex and semaphore....Even now I'm still
screwed.





Sincerly,

Serge Lussier
ICQ#:53409121
Long live to KDevelop!






More information about the KDevelop mailing list