Few bits of update

/
  1. Quit WoW (raiding too stressful, RL work taking up too much time)
  2. Started playing LOTRO (no more raids this time)
  3. Workload is heavy but I'm having fun again, which makes the experience quite a lot better.
  4. I need more food (hmm, when is this not the case)
  5. Sister came home from overseas
  6. Changed ISP to TPG, mainly for the static IP address - I have an earlier rant about this one.
  7. One of my fish died.  Now only 6 fish.  I'm really worried for the other small one.  But the tank is too small to get more fish.  Lina suggests that we get a bigger fish tank.  I think she's loving the idea.

Google-whacking techniques for naming your jira tickets.

/

Because JIRA search just sucks that bad.  We need extra help.

Here's an idea.  When you name a ticket for a task that you need to do in your project, pick a very unique name that you can always remember later.

For example, a web form:

Business Maintenance Form reloaded

or

There are two files here, please pick one and kill the other.

---

Then when you need to find the issue ticket again, it's simple to search for your 'keyword'.

CommunityServer sucks?

/
I think I'm about to give up.

I've spend the last 2 weeks of my life fighting with CommunityServer, and as far as I can determine, this is a product that is NOT designed for other developers.

Lack of documentation.  Lack of up-to-date examples or explanation of the layout of the SDK means that a typical developer spends weeks and weeks in the dark about where things are.

Forums are completely useless - with questions and answers relating to older versions that doesn't apply.

If you are after a good Blog/Forum/CMS software, look elsewhere.

AJAX, Tooltip, World of Warcraft (WoW)

/
Spend a whole day trying to work around a simple issue.
I give myself one html page.  No server side code.
Write a javascript/css based approach to pull data from either Thottbot or Allakhazam and return the data, then render it as a popup.

The AJAX isn't hard, nor is the pop-up page, the problem lies in the "no server side code".

Both IE and FireFox don't like to make XMLHttpRequest cross-domain.  That is, it doesn't like being hosted on a http://localhost/test.html or even file host file:///test.html, making a request to thottbot.com.
On IE, you get a security question pop'up everytime you try to make such a call.  If the user clicks "OK", he'd be let through.
On FireFox, it's automatically denied unless you try to obtain UniversalBrowserRead privilege.  Extremely difficult and potentially a security loophole.

The solution seems bleak.

Use AJAX to query the origin server - without making a cross-domain call.  But use the server to make the 'translation' - possibly caching as well.