Iko[N]otE

Developing a new Warcraft guild website gave me a handful of good opportunities to construct and recreate/imitate some edge features used in modern apps today. One of them is a "Saving" status display when you are editing a Google document. So here are the steps I wanted to mirror in my own app: when the app is constantly saving what the user inputs when it is just done saving every piece of data when some time passed and it wants to inform the user about real time status information These are the steps for the frontend side. On the server side, well just look at this network traffic below, this absolutely has to be custom tailored to everyones infrastructure Let's look at my original code that was born to recreate this action The above code looks like this in the browser (sorry, it's the Hungarian version) Now let me sum up the crucial points in the above code. Javascript is good in using callbacks, async calls. This behaviour could lead to tricky "bu...

My best choice when I want to extend the system path is to create a profile shell script in the /etc/profile.d/ directory with and extension of .sh . The content is something like this: export PATH=$PATH:/home/ikon/bin This way my ~/bin directory is added to the system path.  Check it with $ echo $PATH

This is a recent problem now, so if you are reading it years later try to adopt your numbers on these lines. Version ruby 1.9.3-p327 using RVM , debugger and debugger-linecache restisted the bundle install command. Workaround: gem install debugger-linecache -v '1.1.2' -- --with-ruby-include=\$rvm_path/src/ruby-1.9.3-p374 gem install debugger -v '1.2.3' -- --with-ruby-include=\$rvm_path/src/ruby-1.9.3-p374

I wanted to have my VM built on Windows to be hosted on an Ubuntu linux Virtualbox headless. The VM had a bridged interface and when I tried to fire it up after a plain import I got this: Error: failed to start machine. Error message: Configuration error: Failed to get the "Trunk" value (VERR_CFGM_NOT_ENOUGH_SPACE). Failed to attach the network LUN (VERR_CFGM_NOT_ENOUGH_SPACE) The solution is simple: check the host's main network interface name (or the one you want to bridge to), e.g. eth1 modify the VM's bridge interface to that with: vboxmanage modifyvm vm_name --bridgeadapter1 eth1 After this adjustment is done and the bridge interface knows where to point to the VM will surely fire up.