Chapter 11. Closing Circle One
Before we move onto the next circle, where we will add enough functionality to our plug-in to fully integrate testing into programming and touch all of the activities necessary to build production-quality plug-ins, let's review what we've seen so far.
Much of the architecture of Eclipse is driven from the desire to build the whole environment out of plug-ins but to maintain fast startup. Startup time should be constant, not proportional to the number of installed plug-ins. In particular, you don't want to pay for plug-ins that are installed but not used. If I have a C++ environment installed but I don't use it, it should have no impact at all on my computing experience. Resolving the conflict between building the ...
Get Contributing to Eclipse: Principles, Patterns, and Plug-Ins now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
