Gang Aft Agley

Another bug free microsoft product ready for consumers

I verified that the file created in textmate was a textile entry, though upon saving it it changed to a markdown with smartypants filtered entry.

At this point I have gone into the admin and verified that textile is the preferred filter. This entry is being created through the admin interface to isolate the error, either in backend or the content controller.

I’ve just upgraded to the latest, greatest rev. 1175 and noticed that my last post, although Textile is the default filter se t in the admin, the post was sent as markdown smartypants. Not sure if I hit the wrong keys in textmate, or if its an actual bug. So this post is jsut the follow up to duplicate the error.

How they manage to sell that thing I have no idea. Working within it is unbelievably complex, for no good reason. Every action takes twice as many clicks as necessary. Required information is spread out across two tabs so that you need to go back and forth to even open a ticket. The client name is required, so you click add, which opens up a new window, within that you search, select the radio button, hit add again and that populates the initial window. If you are opening several tickets on the same client you still need to go through all those steps each time, even knowing the information, there is no way to shorten the process as presented.

Last week I received a crash course in Flash, yes that Flash. I didn’t do anything to the design or the accesibility, but I poked around in the ActionScript that drives it. I suspect the rational behind that was that I am the Javascript expert so I must know actionscript, right. Actually it was reported as a Javascript isssue initially, passing querystring variables into the flash piece to play prerecorded songs.

Other than struggling to figure out the little idiosyncratic differences, I felt right at home working in the Actionscript.