| Beginners Guide to Plugin Modification [message #251964] |
Thu, 20 March 2008 01:37  |
Eclipse User |
|
|
|
I'm non-Java developer and I'm using a plugin to which I have the access
to the source and I want to change it. Are there any beginners guides
specifically for people like me?
|
|
|
|
|
|
| Re: Beginners Guide to Plugin Modification [message #252079 is a reply to message #252065] |
Fri, 21 March 2008 12:32  |
| Eclipse User |
|
|
|
Chris Velevitch wrote:
>
>
> Tom Schindl wrote:
>> Frankly if you are not a JavaDev and want to change anything in a
>> plugin you are going to have a hard time because there are many things
>> to consider.
>>
>> So what do you want us to tell you?
>>
>> A) How to fetch the code?
>
> I have the code.
>
>> B) How to get it into Eclipse-Project?
>
> Yes as the content/structure of an empty plugin project seems to differ
> from the structure I see in the code. Also the new project wizard has
> options which I'm uncertain about which to choose. Or should I simply
> create an general empty project copy files into it?
>
>> C) How to code Java, ... ?
>
> As a developer who codes in a different OO language, how to code and/or
> understand Java is not the issue and is a separate issue.
>
> When I look the source code of this plugin, I want to be able to
> understand what's what, what's common to all plugins, what's mandatory,
> what's optional, the hows and whys of it's structure. Also the
> terminology of plugins.
>
> What resources exist for this sort of thing?
Hi Chris. One obvious place to start would be with the book "Eclipse:
Building Commercial-Quality Plug-Ins" (Clayberg and Rubel). It does not
cover Java programming, but it covers creating plug-ins, start to
finish, along with a good introduction to Eclipse, SWT, and JFace. Hope
this helps. Mark
|
|
|
| Re: Beginners Guide to Plugin Modification [message #252123 is a reply to message #252079] |
Fri, 21 March 2008 20:22 |
| Eclipse User |
|
|
|
I agree that Clayberg and Rubel is the best palce to start. If you can,
catch hold of "Contributing to eclipse" by erich Gamma et al. That explains
a lot of plug-in development stuff very well by taking Junit as an example.
"Mark Dexter" <dextercowley@gmail.com> wrote in message
news:fs0num$45m$1@build.eclipse.org...
> Chris Velevitch wrote:
>>
>>
>> Tom Schindl wrote:
>>> Frankly if you are not a JavaDev and want to change anything in a plugin
>>> you are going to have a hard time because there are many things to
>>> consider.
>>>
>>> So what do you want us to tell you?
>>>
>>> A) How to fetch the code?
>>
>> I have the code.
>>
>>> B) How to get it into Eclipse-Project?
>>
>> Yes as the content/structure of an empty plugin project seems to differ
>> from the structure I see in the code. Also the new project wizard has
>> options which I'm uncertain about which to choose. Or should I simply
>> create an general empty project copy files into it?
>>
>>> C) How to code Java, ... ?
>>
>> As a developer who codes in a different OO language, how to code and/or
>> understand Java is not the issue and is a separate issue.
>>
>> When I look the source code of this plugin, I want to be able to
>> understand what's what, what's common to all plugins, what's mandatory,
>> what's optional, the hows and whys of it's structure. Also the
>> terminology of plugins.
>>
>> What resources exist for this sort of thing?
> Hi Chris. One obvious place to start would be with the book "Eclipse:
> Building Commercial-Quality Plug-Ins" (Clayberg and Rubel). It does not
> cover Java programming, but it covers creating plug-ins, start to finish,
> along with a good introduction to Eclipse, SWT, and JFace. Hope this
> helps. Mark
|
|
|
Powered by
FUDForum. Page generated in 0.10609 seconds
Home