Oh yeah, we had that on my last contract. I'd totally forgotten it. Thanks!
'Just Rewards (2)'
Buffistechnology 2: You Made Her So She Growls?
Got a question about technology? Ask it here. Discussion of hardware, software, TiVos, multi-region DVDs, Windows, Macs, LINUX, hand-helds, iPods, anything tech related. Better than any helpdesk!
There's also Photoshop Elements.
Front Page is horrible. (But that said, I don't have a lot of non-Dreamweaver experience in Windows, so I can't recommend anything else)
For graphics, Illustrator and Photoshop do completely different things. If what you need is a photoshop analogue, look at Photoshop Elements instead -- it's a simplified version that costs much less and does everything you'd commonly need to do for web work.
The Gimp is a very powerful and free (open source) graphics program, but it's difficult to learn to use (at least for me).
Also, I don't remember if you still need Xfree86 or somesuch to run it on a Mac.
Crap. I am so confused. (Yeah, what else is new?)
A web browser (IE 6) should never cache an .asp page, right? A web server (IIS) should never cache the result of a .dll component, right?
eta: Nebber mind. I am an idiot, but not for reasons related to the questions here.
The Therac is (and I devoutly hope will remain so) the all-time champeen.
What. The. Fuck.
I broke something on this very complex web application we wrote for a client. So I reverted half a dozen files to their original state. Except the application was still broken. I debugged and found the error in a script file which is included in the main file like so:
<SCRIPT src="SCRIPTS/combos.js"></SCRIPT>
It was erroring because the main page still had the new version of combos.js, even though I could look at that file directly and see that it was now the old version. So I killed IE, restarted the application - same thing. (Did this several times.) It was acting like it had cached combos.js. Finally I just renamed combos.js on the server, which produced an (expected) error on the web client. Then I renamed it back, and at this point the browser was loading the correct (old) combos.js.
WTF? Are javascript include files supposed to be cached? I've done this sort of thing before without a problem....
eta: A quick google shows that javascript include files are cached. Huh. Any idea how to prevent this, or how to force a reload of the include file if it's been changed?
how to force a reload of the include file if it's been changed?
tommyrot, I've found IE to be pretty brain-dead when it comes to detecting changes to webpages. You might try going into Tools > Internet Options > Settings (under Temporary Internet files) and select "Every visit to the page" rather than the default "Automatically". In theory this will reduce your browsing performance, but I've never really noticed any change in practice.
Firefox 1.5 beta just did an upgrade on my XP box. it's now beta 2.