|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
 Gutschein erhalten
Tauschen Sie jetzt Contributing to Eclipse: Principles, Patterns, and Plug-Ins (Eclipse Series) gegen einen Amazon-Gutschein in Höhe von EUR 0,25 ein - einlösbar für Tausende von Artikeln bei Amazon.de. Entdecken Sie mehr eintauschbare Bücher im Bücher Trade-In Shop. Bitte beachten Sie die Teilnahmebedingungen.
 Jetzt für Amazon Student anmelden und um 20% erhöhten Eintauschwert sichern. |
Wird oft zusammen gekauft
Produktinformation
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
Ist der Verkauf dieses Produkts für Sie nicht akzeptabel? |
Mehr über die Autoren
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
Produktbeschreibungen
Amazon.com
Eclipse is an integrated development environment (IDE) for software. It also represents an ideal, incorporating modularity, extensibility, and community. Contributing to Eclipse: Principles, Patterns, and Plug-Ins is therefore significantly more than a book about how to write plug-ins for the Eclipse framework. The book--by software patterns guru Erich Gamma and "extreme programming" exponent Kent Beck--explains how new Eclipse modules should interact with existing software elements, and make themselves further extensible. It also emphasizes the importance of packaging new plug-ins and making them available to others as new Eclipse features. The book's emphasis is on community, and helping the Eclipse project grow and improve.
That said, this book is an excellent how-to guide. Gamma and Beck take the time to carefully detail a couple of model plug-in projects--including the industry-standard Hello World exercise--and take care to explain the highly visual Eclipse development process one step at a time. They don't unleash bushels of source code on the reader, but nonetheless manage to walk the reader through a series of progressively more elaborate extension projects that exercise some of the most exciting parts of the Eclipse framework. As you'd expect from a book involving Gamma, discussion of patterns appears with increasing frequency toward the book's conclusion, enabling the reader to expand on the authors' shared wisdom and understand the Eclipse design better. --David Wall
Topics covered: How to extend the Eclipse development environment--both in the narrow sense of writing code that makes the software do something new, and in the broad sense of participating in the Eclipse community. Specific coverage addresses extension points, markers, perspectives, and help. There's also a guide to the Eclipse architecture, framed as a series of "pattern stories."
Kurzbeschreibung
Written by two world class programmers and software designers, this guide explains how to extend Eclipse for software projects and how to use Eclipse to create software tools that improve development time.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
Vorgeschlagene Tags zu ähnlichen Produkten(Was ist das?)Setzen Sie den ersten relevanten Tag hinzu (ein Schlüsselwort, das mit diesem Produkt in engem Zusammenhang steht).
|
Eine digitale Version dieses Buchs im Kindle-Shop verkaufen
Wenn Sie ein Verleger oder Autor sind und die digitalen Rechte an einem Buch haben, können Sie die digitale Version des Buchs in unserem Kindle-Shop verkaufen.
Weitere Informationen
Kundenrezensionen
Die hilfreichsten Kundenrezensionen
3 von 3 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
Yes, this book is definitly worth it's price. I'm used to have it lying beside my keyboard while coding plugins. Even after a long time of coding in Eclipse you'll see your self spending some time and learning about some special concepts from Eclipse. There are not so much codesections that could be copy&pasted, but they will show you how to gather your information yourself, without long and ugly examples.
The TestDrivenDevelopment was very new to me and so I had my problems extracting some details from the code. There are some Graphs created with their own tool called Spider which I found also not to be that useful.
The TestDrivenDevelopment was very new to me and so I had my problems extracting some details from the code. There are some Graphs created with their own tool called Spider which I found also not to be that useful.
4 von 5 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
I had played around with plugins before, but this book opens you new horizonts. It helps you not only to write eclipse plugins, but to write them WELL-DONE. I was really intrigued by the book, and in particular by the depth and power of the eclipse architecure.
Many practical examples, useful patterns, and a concise, entertaining style round up the picture, not to mention the practical demonstration of implementing XP and Test Driven Development.
Many practical examples, useful patterns, and a concise, entertaining style round up the picture, not to mention the practical demonstration of implementing XP and Test Driven Development.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
15 Rezensionen
26 von 29 Kunden fanden die folgende Rezension hilfreich
What I would expect if there was NO docs for eclipse
5. November 2004
Format:Taschenbuch
I don't like this book as a book on writing plugins for eclipse for the following reasons:
1) This book's 'exploratory' approach tries to show you how to search (the hack approach) through the installed plugins for excerpts that you can copy/paste/edit. It would have been more useful if the authors used a 'tutorial' approach that constrains the example to documented basics (many different examples that then integrate/or not).
2) As expected (and tiring if you have other book from these authors), JUnit integration is the example developed throughout the book. This may satisfy the need for some types of plugins (code oriented plugins), but leaves much to be desired if you want to develop other kinds of tools.
3) The samples are outdated in 3.0, and the main example won't work/run in 3.0 (even if you download their project source). If you try to follow along, you will quickly be disapointed once you run into that snag. I am sure that under 2.x it works great.
4) This book is useful as a way of seeing a small example built up. However, because of #3, this all becomes useless once the plugin doesn't 'work'.
As with most books that cook a long example as a way of teaching, rather than as a way to support other knowledge, much of the time is spent on explaining how to cook things for the example. For me this doesn't work, as I want something focused that instructs me, rather than a evolving code-walkthrough of a particular example. To me this is boring, and has no use after the initial read.
This book would be great if it was 1/2 as long, and focused on the patterns for the plugins instead, not presume to be an intro to plugin development.
1) This book's 'exploratory' approach tries to show you how to search (the hack approach) through the installed plugins for excerpts that you can copy/paste/edit. It would have been more useful if the authors used a 'tutorial' approach that constrains the example to documented basics (many different examples that then integrate/or not).
2) As expected (and tiring if you have other book from these authors), JUnit integration is the example developed throughout the book. This may satisfy the need for some types of plugins (code oriented plugins), but leaves much to be desired if you want to develop other kinds of tools.
3) The samples are outdated in 3.0, and the main example won't work/run in 3.0 (even if you download their project source). If you try to follow along, you will quickly be disapointed once you run into that snag. I am sure that under 2.x it works great.
4) This book is useful as a way of seeing a small example built up. However, because of #3, this all becomes useless once the plugin doesn't 'work'.
As with most books that cook a long example as a way of teaching, rather than as a way to support other knowledge, much of the time is spent on explaining how to cook things for the example. For me this doesn't work, as I want something focused that instructs me, rather than a evolving code-walkthrough of a particular example. To me this is boring, and has no use after the initial read.
This book would be great if it was 1/2 as long, and focused on the patterns for the plugins instead, not presume to be an intro to plugin development.
12 von 12 Kunden fanden die folgende Rezension hilfreich
Different is good
3. September 2004
Format:Taschenbuch
"Contributing to Eclipse" is a great read. More importantly, as someone who is in the middle of their first major Eclipse plugin development project, I learned a lot -- even though I've previously read every other available book on the topic. Gamma and Beck take you through the development of a fairly sophisticated plugin, step by step. Perhaps most welcome, the plugin they develop isn't a syntax-highlighting text editor (an example that's already been done to death,) but a set of tools for running JUnit tests on Java code!
This is the only book I've seen that discusses testing and Test-Driven Development of plugins, a must for serious plugin developers. As you'd expect from the developers of JUnit, they use JUnit to test every piece of functionality they add. Surprisingly, even though you'd expect some confusing in writing about using JUnit to test a JUnit plugin, there's none. Gamma and Beck are both excellent writers, and they know this subject matter inside out.
A word of warning: this is neither an introduction to nor a reference for Eclipse plugin programming. I don't think I would have gotten nearly as much from this book if I hadn't read "Eclipse in Action" and "The Java Programmer's Guide to Eclipse" first. But if you've gotten beyond the novice level with Eclipse, I guarantee you'll learn something by reading this book.
This is the only book I've seen that discusses testing and Test-Driven Development of plugins, a must for serious plugin developers. As you'd expect from the developers of JUnit, they use JUnit to test every piece of functionality they add. Surprisingly, even though you'd expect some confusing in writing about using JUnit to test a JUnit plugin, there's none. Gamma and Beck are both excellent writers, and they know this subject matter inside out.
A word of warning: this is neither an introduction to nor a reference for Eclipse plugin programming. I don't think I would have gotten nearly as much from this book if I hadn't read "Eclipse in Action" and "The Java Programmer's Guide to Eclipse" first. But if you've gotten beyond the novice level with Eclipse, I guarantee you'll learn something by reading this book.
8 von 8 Kunden fanden die folgende Rezension hilfreich
Zen and the Art of Eclipse
31. Juli 2004
Format:Taschenbuch
Once you get past the interesting writing style, this is a pretty cool book written by two of the giants in the industry. This is a particularly good book, if you are interested in Eclipse plugin development and JUnit testing. The tutorial is pretty comprehensive and the book example evolves in a natural way. The only downside is that this book is targeted at Eclipse 2.1 rather than 3.0 (which is no wonder given that it predates 3.0 by more than six months). This doesn't really detract from the book because most of the examples are fairly generic and can be made to run in Eclipse 3.0 with minimal effort.
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
|
|
Ähnliche Artikel finden
Anhand des Sachgebietes nach ähnlichen Produkten suchen:
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
