Here is a quick overview, in case you don't know much about them:
Let me translate this for you: Worker threads are a pain to even package in their own files, you can't call something like:
No, that would be too easy, since from that method I could be able to access shared state, so let's make it awkward and weird, why not:
and from the new file call:
All the libraries, that you use both in your worker, or in your main code? Better load them twice.
But wait, there's more!
There is a new object visible named self, that is the worker reference (if it's a script inside a window, self == window).
So let's say you would want to process async a bunch of data, whenever it's being sent from the parent - again, there is no shared context, well why not go with:
Looks simple, isn't it? Except it's in a different bloody file, and did I mentioned that breakpoints in the worker thread code don't stop?
So in order to start, let's build first an utility class that we'll use in several places, the onceMany utility function:
As you can see at line 3, we will keep everything in the ciplogic namespace. From this moment on, we can call:
And we don't need to keep a new array for join operations.
So I was checking how's the bruteforce going on my website:
My hosting has shorewall (or some form of it), that automatically bans people who have too many atempts, and my config has for sshd:
Yes, you read the title correctly. Bear with me, it's not a marketing ploy.
IE's history is a sour point in the memory of any legitimate web developer. But in all honesty there are quite a few things I would love other browsers to have them as well.
So without further due, let's start with sweet point number 1:
Major updates, especially for the corporate world, are not always an option. I love the fact that IE allows you to pick from its developer tools the version of IE to target. This can also be controlled via request headers, meta tags, or company policy, and it's reasonably easy to set-up. Comparing with Firefox ESR - which is the only other option (why?) that offers stability over upgrades over years, IE is a breeze.
Check this HTML:
The beautiful thing is that you don't need to use a timer, and keep checking if the element changed its position. Sweet, sweet, sweet.
How do you do that?
For example if you want to disable resizing of images in content editable regions you need a CSS selector:
and the noresize.htc:
Now even if you add a NEW image, this code will be executed for every instance. How amazing is this?
Sample 3 courtesy of this nice post: http://nickw101.wordpress.com/2011/02/25/disabling-image-resizing-in-ie-contenteditable-elements/
Aren't you tired of editing <pre/> tags just to add a trivial code sample into your article? Or escape it as HTML? Or escape characters like < from it?
Wouldn't you want buttons like these into your editor, that just open you a dialog to simply add your code sample into the article?
Something like, you click the button, a dialog opens, you select the programming language and get stuff like this:
Click update and you get this output:
No seriously, that's all I did.
It brings me great joy to announce the availability of this application.
Available as both a plugin for Wordpress or Joomla, it's available to download at: http://codeeditor.ciplogic.com
The one to rule them all. The browsers that is.
SharpKnight is an Android chess game.
MagicGroup is an eclipse plugin.