Help offered

[torkildr]

Hi guys,

I've just switched to using Mac for my hobby development and I would
of course want to continue using my favourite IDE even for OS X
development. I'm an experienced Eclipse developer, having developed
two different IDE's based on Eclipse (http://resheim.no/vdf and
http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4116). So, I
think I'm qualified and hope to be able to help out on this project.
If this sounds interesting, please drop me a line.

Best regards,
Torkild U. Resheim.

[Alex Blewitt]

Please do! A lot of the ObjectivEClipse stuff uses the CDT for its
work, and quite a bit of that uses support that's different from other
Eclipse IDEs (the C source editor abstacts most of the things that
you'd do if you were writing your own).

There are a few things that you could help with; raising and fixing
bugs :-) The google project lists things in the issue tracker already
but of course there are other things that haven't been raised yet.
We've not done any refactorings, for example, and I suspect they work
the same in CDT as other IDEs based on Eclipse.

If you are getting familiar with the OSX samples then one thing we
don't have is a good library of example code or project templates -
that's where XCode is better at the moment. In addition, we don't have
a way of massaging the build output to follow the Foo.app/Contents/
Resources layout which is likely to be an essential part going forwards.

Lastly, if you have experience if putting together editors like the
XML one, then we could use a PList editor.

Alex

Sent from my (new) iPhone

[Torkild Ulvøy Resheim]

Hi Alex,
On Mon, 31 Aug 2009 22:47:23 +0200, Alex Blewitt <alex.b...@gmail.com>
wrote:

>
> Please do! A lot of the ObjectivEClipse stuff uses the CDT for its
> work, and quite a bit of that uses support that's different from other
> Eclipse IDEs (the C source editor abstacts most of the things that
> you'd do if you were writing your own).
>
> There are a few things that you could help with; raising and fixing
> bugs :-) The google project lists things in the issue tracker already
> but of course there are other things that haven't been raised yet.

Of course :-)

> We've not done any refactorings, for example, and I suspect they work
> the same in CDT as other IDEs based on Eclipse.
>
> If you are getting familiar with the OSX samples then one thing we
> don't have is a good library of example code or project templates -
> that's where XCode is better at the moment. In addition, we don't have

I've just spent a lot of time with the templates mechanism in CDT. We used
it as a foundation for a much more complete feature for creating example
projects (and adding/removing libraries and code depending on various
settings). Now, I cannot give away that code, but I think the CDT
mechanism is sufficient. It is also expandable (you can add more
processes) so we're probably good.

> a way of massaging the build output to follow the Foo.app/Contents/
> Resources layout which is likely to be an essential part going forwards.

I believe there is a way using the MBS to handle this.

>
> Lastly, if you have experience if putting together editors like the
> XML one, then we could use a PList editor.

I've written a few Eclipse editors. Well, two to be exact. One simple and
one quite complex with content assist, various annotations etc. so that is
something I could look into.

>
> Alex
>
> Sent from my (new) iPhone
>

[snip]

Thank you Alex,
You've given me the pointers I was needing. I'll certainly look into this
as soon as I get up to speed :-)

Best regards,
Torkild.