| design "best practices" for IDE plug-ins? [message #276907] |
Tue, 30 November 2004 19:20  |
Eclipse User |
|
|
|
Originally posted by: wscarvie.hotmail.com
Hi all,
I'm working on using Eclipse to create an IDE, by integrating a number of
existing proprietary tools. The project is quite large, so I'm struggling
with how to design my plugin set "correctly." I'd like to do it the Eclipse
way, and design it such that it's appropriately extensible in the future.
I'm not hoping to get specific advice to my exact problems here, but rather
I'm looking for any good books or articles on designing complicated sets of
plugins. I'd love answers to questions like:
When should a large plugin be divided into multiple plugins?
Are there any patterns that apply to plugin design?
What extension points are best practices for various kinds of plugins (or
views)?
When should one use fragments to divide up the work to be done, and when
should one use plugins?
And, I'm sure, many other questions I'm still too new to know to ask. :-)
Any suggestions?
Thanks,
Will
|
|
|
| Re: design "best practices" for IDE plug-ins? [message #277048 is a reply to message #276907] |
Fri, 03 December 2004 09:17  |
| Eclipse User |
|
|
|
Originally posted by: mnaglik.nospam.gazeta.pl
William Scarvie napisał(a):
> Hi all,
>
> I'm working on using Eclipse to create an IDE, by integrating a number of
> existing proprietary tools. The project is quite large, so I'm struggling
> with how to design my plugin set "correctly." I'd like to do it the Eclipse
> way, and design it such that it's appropriately extensible in the future.
>
> I'm not hoping to get specific advice to my exact problems here, but rather
> I'm looking for any good books or articles on designing complicated sets of
I really recomend this book:
Building Commercial-Quality Plug-Ins
http://tinyurl.com/4xfp2
Cheers
Marcin
|
|
|
Powered by
FUDForum. Page generated in 0.04141 seconds
Home