mcfly

Cool thread, I learned a lot.Where I grew up in western Canada, the Daddy Long Legs is a spider that doesn't spin a web, at least not that I'd ever seen. They just run along the ground..or up the wall, as the case may be. Imagine my suprise after moving to Illinois to find the Daddy Long Legs' here using webs all the time. I once watched one actually capture another and wrap it's legs up in a web strand.

I got a nice laptop a couple of years ago because I liked the idea of lugging it all over and having it with me whenever I needed it. Well, the lugging part lasted about a year before I got tired of it. And why was I lugging it to work, where I've got the company machine? During lunch hour I can use the work computer for my own projects anyway.So, though I still like my HP Pavilion, it's replacement will almost certainly be a desktop.

It's tough to compare. I'm a huge Photoshop fan, and still use it personally, but for the last 9 months or so at work I've been using Fireworks (they gave my Photoshop lisence to someone else!!), and it's not a bad product at all. It doesn't handle text quite as well as Photoshop, imho, but generally speaking it does the job. Mind you, I'm a developer, not a desinger, so my reliance on graphics software at work is much lighter than it might be for some of you guys.I'd break out the "killer apps" by vendor this way:Adobe: Photoshop, Illustrator, After EffectsMacromedia: Flash, DirectorSomeone said the company, after the proposed merger, would simply be called Adobe. Personally, I'd have gone with Macrobe, or maybe Adomedia. MacroAdoMediBe?

I agree with most everyone else...I prefer a lighter background. But if there's a compelling design reason to go with a dark bg, then that's fine. Without that reason, though, I kind of just assume a light background.I think it might stem in part from the fact that a great deal of the printed material we see is often on a light or white background, and the web is still largely rooted--for better or worse--in that model.It seems that sites that break with the "printed page" model, such as sites where images, animations or video surpass the importance of the written word, more often sport a darker design than sites where text is paramount. Just a subjective observation. :-)

When I first encountered PHP about 5 years ago (can't even remember which version it was...an early 4.x, I think) it had some issues. We were thinking of switching from CF to PHP, but in our testing one of the dll's related to PHP kept throwing errors and gumming up the works. But that was a long time ago and PHP has seen some pretty serious changes since then.A few days ago, Marc Andreeson was quoted as saying he thinks PHP will surpass Java as the "standard" server-side language (perhaps he specified "web-services language," I can't recall).To be brutally honest, I think one of Java's biggest problems is Sun. I'd have more faith in it's longevity if it were an IBM product (which may be the case, some day).

Filtering out the"bad stuff" is essentially what you want to do, but how can you know what all the bad stuff is? A better way to approach this, imho, is to only permit the "safe stuff" and therefore by default you omit anything unsafe. Regular expressions are really useful for this...allow only a-zA-Z0-9 as legal input. Any other character gets rejected. Well, ok, in practce you might have to permit other characters like the single quote (for names like O'Hare) and the hyphen, maybe one ot two others depending on the app. I have to admit I often also strip out certain character sequences like "exe", "select", "where", etc. If it messes up a user's input to the point that it's unusable, then they might have to use another channel of communication. I think that's a fair price to ask for security. What I do is strip out any offending character and then send the input through, *maybe* giving the user a peek at it with a short explanation as to why it's different from the original input. Frankly, if they try to slip a pipe into a query, they're lucky if I don't add their IP to a banned list ;-)

setInterval might be a better choice when you want a chunk of code to run repeatedly. But for a script running in a browser, 30 minutes might as well be 30 years. You may well get that annoying box warning about long script execution times. Maybe not, though, because the script is "idling." It'd be an interesting experiment anyway, despite the fact that there are likely better ways to accomplish it than by using javascript.

My first was an Eagle "luggable" that my brother gave me. It had two integrate 5.25 floppy drives, no HD, a monochrome (green) screen, 8086 processor running about 4MHz if I recall correctly. GAWD I loved that thing. It was called a luggable because, though it weighed about 50lbs, it had a handle and the keyboard could be latched to it so that it covered the screen and floppy drives. I ran MS QuickPascal on it, got me through first-year programming. When I bought myself a used 286, I gave it back to my brother, and to be honest I still miss it. It's like the first junker car you get...it hardly runs, but it doesn't matter because it's summer, the windows are down, you love driving and it's the greatest thing ever.*sigh*

Phishing is HUGE. I work for a bank and it seems each day more of my time is spent dealing with it. Everyone seems to agree, education is the key. Banks do not, will not send emails to clients asking them for sensitive personal or financial infomation. It staggers me how many people will willingly submit their credit card info simply because they get an email directing them to a website that asks for it. Once your numbers have been sent, phishers can have a fake card coded and at an ATM within half-an-hour.

Dreamweaver's good, no doubt. Leaves Frontpage (shudder) in the dust. But I prefer Homesite over all of them. And if I'm feeling particularly sadistic, I'll code webpages in Komodo.

ROAR!!Er, sorry...I meant RAR

It kills me to agree with this, but I think it might be right. The Chinese are very focussed right now and are making massive strides. If they can keep it up, it's gonna take everything we have to keep pace. There are people in-the-know who are saying the VSE is simply not supportable, and will certainly collapse after 2008. If we do somehow manage to make it back to the moon, there's a reasonable chance that the Chinese will already be there to welcome us. But the NASA Admin recently said that though he expects the US to lead the way back to the moon, it'll likely happen as part of a cooperative international effort. Perhaps that makes the most sense.

This might be kind of an overly-obvious, brute-force approach, but could you not simply pass a list from the form to the function on the action page? That is, the function accepts the list as a parameter (and I specify a list because on the face of it, a list seems the most likely structure to use in a case like this...though I could be wrong). But if you're looking for a way for a CF function to actually accept the click event...I'm not sure that's possible. The function can, I beleive, only receive data as a result of an event. Maybe I'm not understanding your question correctly...

I hear you brother I've got the dev edition of CFMX running quite nicely with PHP/Apache on this computer. I access CF only through it's built-in dev server, though, so I keep interaction to a minimum. Years ago I ran CF4.5 and PHP both under Apache, and had no problems except for CF's (then a C++ app) memory leaks.

After you upload a file, quite a number of cffile "status variables" are available to you. Some of the ones you will probably be interested in are (snipped from the Macromedia docs): serverDirectory Directory of the file saved on the server serverFile Filename of the file saved on the server serverFileExt Extension of the uploaded file on the server (without a period) serverFileName Name of the uploaded file on the server (without an extension) A little bit of experimentation with these should allow you to do what you want. HTH