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 ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access