|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
商品の説明
内容説明
This book encourages tool building by laying bare the design of an excellent tool platform, Eclipse, and encourages design by building a typical tool extending Eclipse. This tutorial on creating custom tools also provides an explanation of a highly effective software design philosophy. The authors revive the lost art of supporting existing work by building tools. This book improves the software developers skill set by building little tools, and gradually growing those tools into better-than-professional quality products to help a whole community of developers. This book revives that highly-effective practice of tool writing and provides lessons along the way that tool building and design are two of the most leveraged skills for software developers.
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."
登録情報
|
この商品にタグをつける(詳細)タグは、商品との関連性が非常に強いキーワードまたはラベルのようなものです。
タグにより、すべてのお客様がお気に入りの商品の整理と確認を行うことができます。 ※タグは初期設定で公開になっています。詳しくはこちら |
カスタマーレビュー
最も参考になったカスタマーレビュー
8 人中、7人の方が、｢このレビューが参考になった｣と投票しています。
形式:ペーパーバック
内容はEclipseの使い方でなく、プラグインの開発についてです。ケント・ベックらしく、プラグイン開発のサンプルとしてJUnitネタを全般にわたって利用しています。これはこれで、現実的なサンプルで良しです。また、最終章はエリック・ガンマっぽく、パターンネタが続きます。Eclipseの基本機能(?)のIAdaptableをこれだけ解説してる文献ははじめて見ました。この本は、"ポイントを押さえて"解説されています。Eclipseのフレームワークは一見とっつきにくいですが、"どうしてそうなの"というのが書かれていてGoodです。逆に、手取り足取りの教え方ではないので、プラグインをまったく知らない人がいきなりこれを読んでも難しいかもしれません。GoF本のときは、裏表紙にデザインパターン一覧があったと思いますが、この本では、プラグインルール(ex. Everything is Contribution)というものが一覧されています(けっこう好き)。この本でもまだ入門レベルかもしれませんが、私は役に立ちました。
Amazon.com で最も参考になったカスタマーレビュー (beta)
Amazon.com:
15件のカスタマーレビュー
29 人中、26人の方が、｢このレビューが参考になった｣と投票しています。
What I would expect if there was NO docs for eclipse
2004/11/6
形式:ペーパーバック
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 人中、12人の方が、｢このレビューが参考になった｣と投票しています。
Different is good
2004/9/3
形式:ペーパーバック
"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 人中、8人の方が、｢このレビューが参考になった｣と投票しています。
Zen and the Art of Eclipse
2004/7/31
形式:ペーパーバック
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.
これらのレビューは参考になりましたか？
ご意見はクチコミでお聞かせください。
リストマニア
関連商品を探す
- 洋書 > Computers & Internet > Computer Science > Software Engineering
- 洋書 > Computers & Internet > Programming > Languages & Tools
- 洋書 > Computers & Internet > Programming > Software Design, Testing & Engineering
- 洋書 > Computers & Internet > Software
- 洋書 > Professional & Technical > Engineering > Electrical & Electronics > Electricity Principles
- 洋書 > Special Features > all foreign books
同じキーワードの商品を探す
フィードバック
- カタログ情報、または画像について報告
- 著者からのコメント
- 出版社からのコメント
|
