KDevelop 2.0 Objective-c support, progress report

[Richard Dale]

I've spent today getting Objective-C working with KDevelop 2.0. I have added a
KDE Objective-C ProjectSpace kpart, and an Objective-C appwizard plugin. It now
parses Objective-C source and header files, and they appear ok in the class
browser. I left the 'programmingLanguage()' attribute of the project space to
"C++", so Objective-C can just use the standard GNU compiler and linker without
needing to change anything.

> On Fri, 1 Dec 2000, Richard Dale wrote:
>I would
>say adding 'elegant interfaces' for alien language support might be more work
>than 'just doing it'. 
No, I was talking rubbish! It took no longer than it would have done to change
KDevelop 1.2. I like this KParts/KTrader xml everywhere stuff - it's a really
nice dynamic programming environment. So no questioning quotes needed on the
words 'elegant interfaces'  - they are elegant interfaces in my opinion. 

I haven't studied the code enough yet to comment on jbb's review of the KParts
event handling stuff.

-- Richard 

On Fri, 01 Dec 2000, Bernd Gehrmannwrote:
> What do you think is not ready? The earlier we get feedback about
> it, the better the chances are that we get the necessary interfaces

> On Fri, 1 Dec 2000, Richard Dale wrote:
> It wasn't parsing the C++ classes and putting them in the class browser, and I
> couldn't create a new project then. I also wasn't sure if the tokenizer and
> parser were going to be the same for the final 2.0 release (ie the same as the
> 1.3 ones). But it isn't a problem - I think it makes sense get the C++ support
> really solid first, before others can come along and adapt (steal!) it for any
> other language(s). I've just checked out the current KDevelop 2.0 and KDE 2.0
> libs, so I'll have another go this week.
-------------------------------------------------------

-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«