As in title there is only sixth chapter I ended also earlier ones, but this one was Huge!
I can't understand why author make his one big chapter where I can see at leas 2-3 relatively autonomous parts, at least properties and Visual Library can make a separate chapter. I am complaining because I really like small chapters which I can read in one evening or even morning ;)
Chapter 4: Lookup
Lookups are certainly a heart of modules system in NetBeans. Using scopes Modules can search for public classes(using this developers can add functionalities to existing modules) and communicate with other modules without knowing exactly to which module they are talking
Chapter 5: Actions
Pretty straight-forward, creating Actions(as global and reusable for toolbar, menu). More advanced is creating actions that are enabled with custom conditions, eg. Task object available in lookup to edit it :)
Chapter 6: Nodes and Explorer Views
Longest chapter (65 pages), about... everything from Explorer and Tress, context sensitive actions and ending at Property sheet and Widgets form Visual Library API.
Finally I downloaded the source code and started reading it instead of writing everything... There was simply too much of code to write, I write some methods in wrong class and can't find what is wrong. Certainly what was impossible for me to discover what is wrong without comparison to complete code. Everything was compiling but new NetBeans instance was 'dying' during startup and even debug mode wan't display any errors. This is not about book, but i think that it is really hard to fix application that doesn't tell me what is wrong... (or maybe there is something I can do in that situation?) NetBeans simply starts, and then display message that it's finished and closed. I that situation I would preffer a stacktrase ;)
Feedback or Comments?
Want to learn more?
Sign up to get a digest of my articles and interesting links via email every month.