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

How to simulate slow connection (developer proxy in Node.js)

Update: If you use Chrome then you can use "Throttling" so simulate slow network for all your assets. This should be easier than proxy.

Toggle device modeChoose Network type.Refresh the page 


For some time I wanted to use some proxy for development and testing of eg. slow internet connection, but it was hard to find something useful and free. I know there is Charles but buy it to use it at most one in a month is not for me.

I started thinking about Node.js, maybe I can write proxy for me? But fortunately I found one.

With this module I can write really short code to create slow server:

var http = require('http'), httpProxy = require('http-proxy'); httpProxy.createServer(function (req, res, proxy) { var buffer = httpProxy.buffer(req); setTimeout(function () { proxy.proxyRequest(req, res, { host: 'localhost', port: 8080, …

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…