redllama.net » Programming

Fajax

Boofer — Thu, 05 Feb 2009 20:39:39 +0000

I was searching the Googles for a fix that randomly started happening to a web site I was working on. Well, it might not had been random but I don’t feel like reverting back to versions just to find the culprit. IT might be the table. Might be something else.

“ie page flicker” took me to “Stop IE Flickering Between Pages”. OK, nice, I’m clicking, I’m reading. Turns out that IE sucks. No, really.

I really didn’t care to read into exactly what this snippet of code does. It just fixed my problem. My problem being, when submitting a page in IE the browser goes blank (all white) for a split second while it tries to load the new page. This is not an issue in Firefox.

Calling it Fajax for the mere fact it looks like an Ajax load? I guess. Anyways, here’s the HTML for your cutting and pasting pleasures.

Digitally Assisted Billiards

Boofer — Fri, 12 Dec 2008 07:52:52 +0000

Holy crap, I had this idea five year ago. Oh well, they did an OK job with what they had. And I’m too lazy to make my own. Although mine had a laser light show to draw the lines. They were a tad smarter and used a projector. Cool, regardless. Here’s the website.

JQuery: FancyBox

Boofer — Mon, 19 May 2008 20:48:58 +0000

FancyBox? No! It’s not the script on my mom’s new Tupac style “Thug Life” tattoo with an additional arrow pointing downwards.

[align=center][img]http://imagecache2.allposters.com/images/pic/SCR/1081A~Tupac-Posters.jpg[/img]
[/align]

It’s another lightbox clone but I think it might be a fancyzoom clone. I dunno, who cares, I didn’t have to write it, and it’s pretty. I just pointed Mav to fancyzoom the other day for an image gallery he was slapping together. IT’s easy to get working and so is this one. I think this should replace any implementations of fancyzoom. It looks the same as fancyzoom but has better options: nicer title support, color overlays, animated & non-animated popups, IE pngfix already incorporated, image set support (aka previous/next) and some iframe support if you want. Check out few demos on the web site.

Link: [url=http://fancy.klade.lv/fancy/index/110]FancyBox – fancy image zooming tool.[/url]

P.S. That’s got to be the gayest picture of Tupac ever.

I'm going to catch HELL for this …

Upasaka Yin Cai — Wed, 12 Dec 2007 23:09:47 +0000

… but I don’t care. When the HELL will Perl 6 be released?

Basics of Templatizing

Boofer — Tue, 10 Apr 2007 01:25:02 +0000

There’s a standard way of creating templates. We all know it. We all don’t know how we learned it. My question is; is it documented?

The programming language used in the base implementation for a templating system shouldn’t dictate how it’s structured. Templating is generic, very generic. I’m also under the impression that templates used in any server-side scripting language should also be broken down in the same manner as any server-side template is done.

I raised the issue that the templates created at my job were (a joke|retarded|in need of a rewrite). They have a main template for a basic HTML page and a template for pop-up windows. So far so good. Within the basic template there is hard-coded crap for printer friendly type pages and some crap for pages that would be hosted on a secure site. Not so good but, whatever. The main issue is that they created a template and then cut that file in to section, and not modularly. The cut it like you’d saw a woman in half. Meaning is in the first file and is in the last file. Why am I making a fuss? They really have 5 websites with about 10 different formations of pages. All which should be there own templates regardless of what domain they reside.

There’s the red-tape and hoops I’d have to go through to even think about fixing this crap. I guess, “barely working in a manner that’s confusing to everyone and involves hacking different files every week” is whats good for everyone. You’d thing they would know the difference between increased productivity and being productive. Besdies, where’s the documentation that says that what originally was created was the perfect approach?

Since this subject is culinary equivalent of boiling water, there is no “Templatetizing for Dummies” book. And if there was, it would be a pamphlet that read, “Turn off the computer. Go watch TV.” So, if anyone has seen a quick write up let me know because I’m not wasting my time and searching for this crap just to beg them to let me fix their screwed up shit. Since this would be a, let me guess, “When we have time in the future” project. Filed under the “If it ain’t broke, don’t fix it” list.

A JavaScript Compressor/Obfuscator

Boofer — Thu, 08 Feb 2007 02:24:01 +0000

[url=http://dean.edwards.name/packer/]http://dean.edwards.name/packer/[/url]

None, numeric, normal and high ASCII encoding with or without special characters. Compresses up to 50-60% smaller.

Cross Domain AJAX

Boofer — Fri, 26 Jan 2007 21:27:31 +0000

I thought that you might be able to do this but, I also knew it was still JavaScript. So, this is the best [url=http://snook.ca/archives/javascript/cross_domain_aj/]write up[/url] I found, that answered my confused question and a little more. We all know of the proxy method. The JSON method I think uses meta tags and isn’t the cleanest of solutions. The Flash method just made me say, “Duh, I should had though of that.” but then your relying on flash to work. Then I saw I cross domain example using Dojo and iFrames that seemed to work but I saw two things with it: it was slow, from what I read, and I hate iFrames. Enjoy.

[quote="[url=http://snook.ca/]snook.ca[/url]“]Cross Domain Ajax: a Quick Summary
~ in JavaScript ~
2006 | Aug 18

Here are a few of the most popular ways to do cross domain calls via JavaScript: proxies, JSON, and Flash.

Cross domain proxy

This is one of the most common approaches. Your script calls your server, your server makes the call to the remote server and then returns the result back to the client. There are some definite advantages to this approach: you have more control over the entire lifecycle. You can parse the data from the remote server, do with it what you will before sending it back to the client. If anything fails along the way, you can handle it in your own way. And lastly, you can log all remote calls. WIth that you can track success, failure and popularity.

Cross domain JSON

For this to work, the remote server needs to be set up to handle this. It needs to accept an additional parameter: a callback function. Then, to make the remote request, you insert a new script tag into your page with which will allow you to specify a remote URL. The reponse back will load a JSON object as a parameter of the callback function you specified in the request. Yahoo, for example, has implemented this feature in their web services API’s. This is great because you can implement web service calls without ever needing a scripting language on your server. Check out Jason Levitt’s article, JSON and the Dynamic Script Tag, on XML.com for more information.

Cross domain using Flash

Flash, by default, is much like Ajax in that you cannot request data from a remote server. However, you can enable this capability by placing a special XML file on the remote server to accept requests from other domains. With JavaScript’s capability to interact with Flash, we can use Flash as a bridge for sending cross-domain requests. (XML.com has a nice write-up of this technique.) There are still some limitations to this technique, most of which seems to be limited to older versions of Flash. There’s also the issue with users having Flash installed and enabled.

Sub-domains are still cross domains

One point to note and it’s fairly subtle. Plenty of us have our sites running at www.example.com and at example.com. They both point to the very same place. To us, we see them as the same thing. But to an Ajax call, it’s considered cross domain. Therefore, if you have to make an Ajax call to the same server, don’t code the domain as part of the request; just use the path.

The Future

Some have already begun looking into establishing standards that could be implemented into future browsers, such as JSONRequest and ContextAgnosticXMLHttpRequest. JSONRequest seems the most promising but that could be because I prefer JSON over XML and see it as really gaining traction over the next couple years.[/quote]

If you missed the link the first time, [url=http://snook.ca/archives/javascript/cross_domain_aj/]http://snook.ca/archives/javascript/cross_domain_aj/[/url]

Sweet Titles

Boofer — Thu, 03 Nov 2005 06:38:07 +0000

Here’s a clean way to create CSS’ed tooltips. Very nicely done. The even fade. I’m using them at work. This was a great idea but I would had thought of it sooner or later if I hadn’t found this today.

Basically, all you need to do is set the title attribute of an href. This script crawls across the page onload and assigns show/hide div dunctions to the onmouseover/onmouseout attributes of an href then removes the title attribue so the default browse tooltip doesn’t pop up when this CSS’ed version is up. It works on ‘a’s,’abbr’s and ‘acronym’s. Don’t worry, this doesn’t hijck your onload, it finds your onload and concats it’s startup function to it.

I was looking to hack/addon some scripts that read the dynamic Struts validation functions to initalize validation of a fields onblur. Same concept as to how Sweet Titles works.

I had to hack Sweet Titles little to not show a tooltip if title was null or empty. Plus I set the em’s display style to none, to not show the link in the tooltip.

Check this out, it might be useful. If not, it’s an easy way to add an extra feature to any project.

[url=http://www.dustindiaz.com/sweet-titles]click here for the website[/url]

HTML: Fun With TR's

Boofer — Mon, 06 Jun 2005 20:35:30 +0000

I needed to create a list with columns and below each item to have a details list using the same columns. As much as I rather use DIV’s more often. I decided to use a single table. I fgued to just give every TR an Id and hide the child rows based on that.

First my parent rows and named “detail_1″. The child rows are named “detail_1_1, detail_1_2, detail_1_3, ect…”. I just did a simple loop to get threw and touch them all. I past in a row count to avoid any confusion of with to stop.

This was all easy till I got to referencing an elemets style and the value for the display property. I knew that if the element doesn’t have a style property that you just refer to the property directly. The main problem was what to set the display property to. In Mozilla “block” displays as a cell. In IE “table-row” is not supported. Which all confused me because this is the first JavaScript function that I’ve written and it didn’t work in IE but did in Mozilla. It all threw me off and I spent two days trying to figure it out. So, if you need to hide and TR, this is how you do it.

[code]1 function getreference(_id) {
2 if( document.layers ) return document.layers[_id];
3 if( document.getElementById ) return document.getElementById(_id);
4 if( document.all ) return document.all[_id];
5 if( document[_id] ) return document[_id];
6 return false;
7 }
8
9 function toggledetail(_row_id, _row_count) {
10 element = getreference(_row_id + "_1");
11 element_display = (element.style) ? element.style.display : element.display;
12 display_value = (document.all) ? "block" : "table-row";
13 showhide = (element_display == display_value || element_display == "") ? "none" : display_value;
14 plusminus = (element_display == display_value || element_display == "") ? "plus" : "minus";
15 for (i = 1; i <= _row_count; i++) {
16 element = getreference(_row_id + "_" + i);
17 if(element.style) element.style.display = showhide;
18 else if(element.display) element.display = showhide;
19 }
20 document.images["toggle_" + _row_id].src = "images/icon_details_" + plusminus + ".gif";
21 }[/code]

My code explained.
Line 10 gets the element from what ever broswer is being use.
Line 11 gets the element display.
Line 12 determines to use “block” (IE) or “table-row” (Moz).
Line 13 determines if the element is hiding or shown.
Line 14 is the toogling for the tooge image.
Line 15 is the loop to hide all the rows within the row count.
Line 20 switched the toogle images src.