Skip to main content

After chapter 6: Nodes and Explorer Views

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 ;)


Popular posts from this blog

Course Review: The Bitfountain iOS 8 with Swift Immersive

This is second big iOS learning project. For first one read iOS Programming book review. As I only have two of them done I have to compare them somehow.

I am mindful that it took me a really long time to finish it (since last autumn). For a couple of months this year I didn't even have the internet to learn it, so it could not be helped. But last half of the June I've spent watching the videos every day and managed to finish it before any new internet problems.

So how was it?
In my opinion, it's great if you're starting out. There are a lot of basics, and seeing how to do things in XCode just makes your learning much easier than looking at the photos in the book. On the other hand, learning is more shallow and it is much easier to just follow the videos and learn only the basics without bigger picture about iOS SDK. I somehow missed more challenging exercises (even though I don't like to do them ;)

Course it pretty long but many videos are quite short (1-2…

How to Learn when Life is Short

I haven't really think this through but I have read really interesting articles recently and I just wanted to write for myself later.

Life is Short by Paul Graham

It's just that, learn from people older that you what is most important, and that life actually is short...

Instead of Goals or Resolutions, Try Creating Rules by Leo Babuta

In the time of New Year Resolutions, it's good to read something that is proposing different way of achieving things. Still I see much more value in habits than setting goals. But...

The Easy Way To Learn Hard Stuff by Per Harald Borgen
It's something that I read from time to time and I know it works sometimes for me. The things I learn then are really learned and something Jakub Wasilewski  has told me many times to do. Still it's uncomfortable and for some reason, I have failed to use this method more than once or twice. Writing it here so maybe I can think about it more and figure out how to do that more often.

Towards an understandin…

Hero's Journey in Presentations

Artur Skowroński recommended me: Want a Better Pitch? Watch This. by Andy Raskin and I think it is so great and applicable to all kinds of talks that I want to help it get more popular.
So the plan of presentation is going to follow these steps: Enemy - ProblemWhy now? - call to actionShow how the world will look like without the problemProblemsEvidence that you fixed the problem The image at the top is because it reminds me of Hero's Jurney. It has fewer steps but there is a lot of similarities. Especially #3 made me realize that grand vision of the future is something that I should have used in my talks.  The result at the start of the presentation makes a lot of sense actually. Everyone already knows that I speak about something because I probably fixed it and if you tell about it at the end then it might be hard for some people to see the bigger picture in the solution you're going to present.