/// the ramblings of, where typos count and complaints don't ///
i am reliably informed that the following will fix this issue.
Please fix this by
1. Closing Dreamweaver
2. Set your clock to the correct time if it isn’t already so
3. delete WinFileCache*.dat from
C:\Documents and Settings\[Your username]\Application Data\Adobe\Dreamweaver 9\Configuration
4. Start Dreamweaver and use it as usually
Enjoy
J 
while in a meeting today a discussion invariably took place the subject of which i am sure your familiar, at least if you are “in the business”.
Which browsers do we support and for what platform?
The usual suspects were MSIE 6 & 7, Firefox for Win & Mac.
This seems fine to me, although a little more effort goes into supporting Firefox for mac and therefore a little more time and finally a little more money is spent.
I’m not convinced 1.7% of the user base is sufficient reason enough to warrant the extra work required. I throw the question out to you. what are your thoughts about browser / platform support. what numbers and percentages motivate your companies development strategies?
J
I’m not sure how to start this post so im going to shoot from the hip and hope im true.
d-tnt is my creation, a dream and a vision, it had it’s day and that day was fun. we laughed we played and everyone gained a little somthing. I more than most. d-tnt was more than a site, it was a project to disapear into; you see im a geek and geeks love nothing more than to have an excuse to not get involved in “real life” and this was mine. I worked hard even managed to get into PC plus magazine and onto the cover disk. Kudos 
More than this, it satisfied my karmic belief that what goes around comes around, and you get out of life what you put in. I believe i got a ton from the project and i hope that a ton got spread out.
I learnt that there are great people out there willing to help, advise and generally chat. they ask nothing in return. although i suspect they too feel the karmic force the way i do. I have never really thought about myself as a hippy but i sure sound like one when i read this back.
moving on… back to shooting from the hip….
d-tnt is no more, sadly and i mean sadly; I am closing the d-tnt.com website. Make no mistake, not because I have to but because there is a part of me that thinks its time to pull the plug, shut the life support down, put the poor thing out of its misery. better it goes now while it has a small amount of dignity than when it can no longer control its own bladder and mumbles its own name while dribbling scrambled egg down its own chin.
and so, here we are saying a fond farewell to a site that i think was good, honest and real. it did not fall to advertising banners and third party spammers. although i might add regretfully I did consider the lure of this tantalising revenue stream.
he (d-tnt.com) will be remembered in my heart and i’m sure many others too. I hope that the friends I have made and the contacts i have gained will stay in touch and visit here once in a while in loving memory of a past friend he (d-tnt.com) served us well.
Thank you to everyone, i wont say names for fear I will inadvertently forget one and offend. you know who you are and you know i know who you are. Thanks and Thank you again.
it’s been a blast.
J
I understand that writing cross browser javascript is important. But, why has Firefox just made my life a little crappier? While it is running my script without a hitch in windows it has decided to not run the code in firefox for the mac. to be fair this is ok and I almost expected it; as we all do i open the debug window to follow the errors. what no errors? anywhere? Im now left pissing in the proverbial wind.
Humph.
:: UPDATE ::
Ok, i fixed it!
lets assume you have filled a variable full of childNodes, in this case the child nodes we are after are DIV tags. You want to loop through them. should be simple right?
using the javascript below works in firefox for windows.
var Collection = HTMLElement.childNodes;
for (var i=0; i <= Collection.length -1; i++) {
alert( Collection(i).innerHTML );
}
not so in Firefox for the mac, not in OS X 10 Anyways.
you have to use the following, replace the parenthesis with square brackets haha that simple, this one had me blowing a fuse.
note. the check for the DIV tags too, for some reason mac fox adds everything to the collection including textRanges and so on, what this means as that each item may not be a DIV.
var Collection = HTMLElement.childNodes;
for (var i=0; i <= Collection.length -1; i++) {
if (ingDivs[i].tagName == ‘div’) {
alert( Collection[i].innerHTML );
}
}
obviously further checks could be taken such as to ensure we have anything in our Collection in the first place but that wasnt the scope of this post so dont be smart asses and tell me this.
I hope this helps somone.
J
Today is not a good day for dreamweaver to die.
I discovered this morning that due to the date/time change over the weekend dreamweaver crashes on opening certain files. primarily files that contain asp/vbscript code that includes server behaviors.
This is incredibly frustrating, my searches have revealed no official response from Adobe. I trust they are aware of the problem and are busting their balls to provide a fix.
If anyone is interested my debug console pointed to this location in the Assembly >>[00ADAB57 F6863604000004 test byte ptr [esi+$00000436],$04]. forgive me my assembly knowledge is almost non existant but this looks like a test(comparison) of some values is taking place here. one value appears at least to me to be a pointer to a memory location. i’m going to put my money on that location has become invalid for some reason and thus we have our AV.
so why does the date effect this Jason? good question, reader! the answer is simply that I have no idea. I’ll take a punt at a guess though and wager that dreamweaver CS3 performs some algorythm while executing an undefined function or procedure. In this algorythm the date is possibly used to provide a unique value to work against. Any thoughts on this?
Have fun.
Recent Comments