New blog domain: kula.blog

By K -
It's still work in progress but new posts will be published on  https://kula.blog/ Thanks to 11ty base blog RSS is working from the start so it should be easy to add to your reader if you still use any :) If now then I hope you can sign up to the newsletter where I'll be publishing new posts and interesting articles to it from time to time. Please use  kula.blog  from now on.
Post a Comment

After chapter 6: Nodes and Explorer Views

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

Comments

Post a Comment

Comments:

Popular posts from this blog

How to use NPM packages from private repositories on bitbucket

By K -
Image
Using Node.js you want to use NPM packages for reusable parts of the apps you create, that is a common sense. At the same time not everything makes sense as a public module unfortunately. Right now we are using Bitbucket at work for private repositories but there is a problem. How to use them as NPM modules? We do not want to publish them to the public npmjs.org but still want to have an ability to install them easily. After googling and experimenting I have found simple solution. First create new user in your organization with obscure password and give it read access to the repo. It is best to assign really obscure password but do not fool yourself. This is convenient but you must sacrifice security a bit. You should always consider how in your context that would be important. Change example from below to: user - username PASS - password of the user organization - owner of the project (you can find it in bitbucket url to your project) project - your project name "de
Read more

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

By K -
Image
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 mode   Choose Network type. Refresh the page https://developer.chrome.com/devtools/docs/device-mode  Proxy: 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. https://github.com/nodejitsu/node-http-proxy 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:
Read more