For some, you do still have to style them a little to fit within your page design if you want a seamless look, but for the rest they work fine unmodified. Just drop them right in place and change a few text fields.
That's how long it took to get through the fluff remedial chapters.;)
Re: reviewer
The authors make a real point of reviewing material explained earlier, which generally is an effective approach for this type of book. But the repetition sometimes becomes excessive â" enough to annoy even the greenest novice
In practice, it has not been quite that simple. For one, standard web interfaces have lack-luster and incomplete widget choices. And, different browsers support JS/DOM differently.
X Windows had incomplete widget choices and libraries were written to develop more complex widgets. It's the same with Javascript/CSS. HTML has few widgets, but libraries have been written in Javascript/CSS to develop more complex widgets. If it's OK for one, then it's OK for the other.
Browsers not adhering to standards is a problem, but we can't fault the standards because browser developers fail to implement them faithfully. The only time we can fault standards is when they are ambiguous, ignore current practices, prevent extensibility, or are just plain tedious, confusing or illogical.
Of course a browser serving plain HTML/XHTML is about as thin as it can get, and adding AJAX/Flash/Plugin functionality makes that client thicker, but adopting a negative stance on the basis that it's done in the browser is ridiculous, because the function and purpose of the browser is to be a thin client (since the adoption of CGI and dynamic page serving that is).
Don't say it's bad just because you have some beef with browsers, or thin clients in general, or that the technologies are still immature. Desktop apps were pretty immature in the 1980's as well. Don't expect the progression of web based thin clients to be any different. Thin clients have a purpose and will continue to thrive, particularly on the web.
There's a very good reason why the direction of these thin clients has a foundation on the web--because HTTP is ubiquitous. Every modern machine is guaranteed to have a browser capable of running these web apps, so obviously thin clients are going trend toward using web technologies.
If you're going to argue against web apps, you'd be better off specifying which apps or category of apps should not be web apps. You certainly won't get anywhere arguing against them in entirety, because history has clearly shown thin clients have a rightful place within software development.
Oh.. and one more thing. That would violate the rule of not transporting the checked bags if the passenger isn't on the plane. If what you say is true, that's an ENORMOUS loop hole in security. A terrist could check in 3 hours early for flight B at 10am, the bag gets put on flight A at 8am. Flight A gets destroyed; terrist lives to strike another day.
The fact that you checked them early actually was probably your mistake because you gave them a chance to put them on a different flight
I had to wait 3 days to get my bag. OK. It leaves earlier than I do; then it should show up earlier than me. OK. It takes a different longer route; then it should get to me within hours after I arrive. Not 3 days.
I would assume at the gate security. The guard takes it out of the bag and you don't see him doing it.. you pick up your bag on the other end and off you go.. not realizing your laptop was taken out and still riding through the x-ray.
That is nothing compared to the amount of passenger's luggage that is lost daily by the airlines
They once lost my checked in bag on a direct flight from Chicago to KC. Direct flight--no hops! And worse, I checked the bag early. There was plenty of time to get it on my plane. Fortunately, it was recovered a couple days later.
They definitely care and can show it by giving you an "off the shelf replacement" which turns out to actually be a Kaypro luggable
I've observed a similar thing with replacement Blackberrys...
I think some of that depends on your importance within the team. One of my teammates lost his Treo 650 and they replaced it within days despite having a hard time getting one through Sprint. There were shortages at the time, so they bought one off Ebay--paying extra. They did it because this guy was a key member of the team. Had he been a junior n00b developer, probably not. He'd have had to wait a while.
I thought this was going to be another story about TSA outright stealing laptops. Glad to read it's about people misplacing them instead. Whew.
When I travel with a laptop, I make sure it's my only carry-on. I store extras in the front and inner pockets of the laptop bag. You're less likley to lose something if you've only got 1 thing to remember.
The more mainstream the web becomes, the more bullshit we have to sort through... the more useless it becomes.
Where you see problems, I see opportunity. The higher the ratio of noise gets, the more important human filtered indexing becomes. What that evaluates to is a growing demand for indexing websites that filter, list, recommend, and link to other high quality websites.
Unfortunately, for the money you've already paid, you're probably going to have to see a lawyer, and it just isn't worth it, despite the fact that fraudulent billing is actually a pretty serious offense
Let's assume AOL is $25/month after taxes and surcharges. 1 year is 12 months * $25 = $300. For 2 yeaars, $600. For 5 years, $1500. All are well within small claims court territory. If she could prove she called to disconnect, such as having received a disconnect confirmation, having phone records, or having sent a disconnect notice by registered mail (and still having the receipt), it'd be a slam dunk case.
Actually.. he's half right (ignoring the entire digital camera and digital printing trend). Chemical film printing has been fading away and being replaced by digital film printing--digital minilabs (kiosks). Chemical development of prints, although still done, is fast becoming antiquated.
Just to be clear to onlookers, we're talking about photographic film printing (print development), not photographic film development.
Flash for entire websites is horrible and inaccessible.
My philosophy is flash should be a page element, in other words used as rich media content--not as a page rendering engine, because that's what the browser is for (as well as xhtml/css/xml/xslt/javascript).
I agree with your sentiment but I'll word it in a different way. If one is using flash to structure the document, one is doing it wrong. If one is using flash to deliver elements to implement animation effects, streaming video, logic, or server connectivity that's not feasible (or efficient) with xhtml/css/xml/xslt/javascript, then it's a valid use.
There is one exception to the flash as a full page model. If the site contains a "desktop" application (for example a game, a document editor, a help desk program, or possibly a graphical travel planner, etc), then it's OK, but that application should be placed within a secondary page, clearly separate from general site content. It should not be forced upon the user to view all the remaining documents under the website. The same rules of thumb for when to use Java applets ought to apply for Flash web applications.
When you say inaccessible, I interpret that to mean it's difficult to access the data within flash, as opposed to interface accessibility. I think that's true. You can't "Save As" the document if you pull up a report or tabular data, but you could if the site rendered that data as xhtml. In theory, the flash developer could implement a Print or view as a link feature, but that's no guarantee they will. Whereas Save As works on all xhtml pages regardless of whether the programmer paid attention to it or not. Being forced to screenshot the data, is a crappy inflexible alternative.
I'm speaking from experience. I was lucky enough to find out about it early when the unrequested credit card was "accidentally" sent to me instead of to the ID thieves. So I got an "easier" time than I could have had. I still have to look over my credit report constantly, though, as my information is out there now.
If you're in USA, you can now apply for a credit freeze. It will be annoying, but if you're not planning on opening new accounts for a while it would help you sleep better.
Not available in all states, but available in most.
Nice link. I'm so sick of people dumping on USA for selling arms to Iraq yet portraying France, Soviet Russia, and China as modern day messiah societies. That article is rather illustrative. I wish I had that a while back when debating an idiot righteous America loathing Canadian who was slamming USA for sales of weapons to Iraq on another forum.
I'm a Republican, a Bush and now McCain supporter, and have more troll points on slashdot to prove my right wing cred, and I don't find this offensive at all. Come on people, lighten up. This was -funny-. If I would have been first to the joke, I would have made the same crack going the other way.
The funny thing is... I voted for Bush in 2004, although supported Gore in 2000.
Btw, I'm now independent and 100% undecided on 2008.
Slashdot Mirror
While I understand your point, I don't know why you mentioned it. A low level correlation was not what I intended. I was speaking high level.
There are tons of free frameworks and one off widgets. http://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks
For some, you do still have to style them a little to fit within your page design if you want a seamless look, but for the rest they work fine unmodified. Just drop them right in place and change a few text fields.
That's how long it took to get through the fluff remedial chapters. ;)
Re: reviewer
X Windows had incomplete widget choices and libraries were written to develop more complex widgets. It's the same with Javascript/CSS. HTML has few widgets, but libraries have been written in Javascript/CSS to develop more complex widgets. If it's OK for one, then it's OK for the other.
Browsers not adhering to standards is a problem, but we can't fault the standards because browser developers fail to implement them faithfully. The only time we can fault standards is when they are ambiguous, ignore current practices, prevent extensibility, or are just plain tedious, confusing or illogical.
I suppose.. you've never read any discussions or debates on thin client versus fat client, which is essentially a 30-40 year old discussion.
Remember telnet and terminal clients? Well, a browser is essentially the same thing. They're both thin clients and there are many pros to using them. http://en.wikipedia.org/wiki/Thin_client#Advantages_of_thin_clients
Of course a browser serving plain HTML/XHTML is about as thin as it can get, and adding AJAX/Flash/Plugin functionality makes that client thicker, but adopting a negative stance on the basis that it's done in the browser is ridiculous, because the function and purpose of the browser is to be a thin client (since the adoption of CGI and dynamic page serving that is).
Don't say it's bad just because you have some beef with browsers, or thin clients in general, or that the technologies are still immature. Desktop apps were pretty immature in the 1980's as well. Don't expect the progression of web based thin clients to be any different. Thin clients have a purpose and will continue to thrive, particularly on the web.
There's a very good reason why the direction of these thin clients has a foundation on the web--because HTTP is ubiquitous. Every modern machine is guaranteed to have a browser capable of running these web apps, so obviously thin clients are going trend toward using web technologies.
If you're going to argue against web apps, you'd be better off specifying which apps or category of apps should not be web apps. You certainly won't get anywhere arguing against them in entirety, because history has clearly shown thin clients have a rightful place within software development.
Oh.. and one more thing. That would violate the rule of not transporting the checked bags if the passenger isn't on the plane. If what you say is true, that's an ENORMOUS loop hole in security. A terrist could check in 3 hours early for flight B at 10am, the bag gets put on flight A at 8am. Flight A gets destroyed; terrist lives to strike another day.
I had to wait 3 days to get my bag. OK. It leaves earlier than I do; then it should show up earlier than me. OK. It takes a different longer route; then it should get to me within hours after I arrive. Not 3 days.
I would assume at the gate security. The guard takes it out of the bag and you don't see him doing it.. you pick up your bag on the other end and off you go.. not realizing your laptop was taken out and still riding through the x-ray.
They once lost my checked in bag on a direct flight from Chicago to KC. Direct flight--no hops! And worse, I checked the bag early. There was plenty of time to get it on my plane. Fortunately, it was recovered a couple days later.
I think some of that depends on your importance within the team. One of my teammates lost his Treo 650 and they replaced it within days despite having a hard time getting one through Sprint. There were shortages at the time, so they bought one off Ebay--paying extra. They did it because this guy was a key member of the team. Had he been a junior n00b developer, probably not. He'd have had to wait a while.
I thought this was going to be another story about TSA outright stealing laptops. Glad to read it's about people misplacing them instead. Whew.
When I travel with a laptop, I make sure it's my only carry-on. I store extras in the front and inner pockets of the laptop bag. You're less likley to lose something if you've only got 1 thing to remember.
Where you see problems, I see opportunity. The higher the ratio of noise gets, the more important human filtered indexing becomes. What that evaluates to is a growing demand for indexing websites that filter, list, recommend, and link to other high quality websites.
Let's assume AOL is $25/month after taxes and surcharges. 1 year is 12 months * $25 = $300. For 2 yeaars, $600. For 5 years, $1500. All are well within small claims court territory. If she could prove she called to disconnect, such as having received a disconnect confirmation, having phone records, or having sent a disconnect notice by registered mail (and still having the receipt), it'd be a slam dunk case.
Actually.. he's half right (ignoring the entire digital camera and digital printing trend). Chemical film printing has been fading away and being replaced by digital film printing--digital minilabs (kiosks). Chemical development of prints, although still done, is fast becoming antiquated.
Just to be clear to onlookers, we're talking about photographic film printing (print development), not photographic film development.
My philosophy is flash should be a page element, in other words used as rich media content--not as a page rendering engine, because that's what the browser is for (as well as xhtml/css/xml/xslt/javascript).
I agree with your sentiment but I'll word it in a different way. If one is using flash to structure the document, one is doing it wrong. If one is using flash to deliver elements to implement animation effects, streaming video, logic, or server connectivity that's not feasible (or efficient) with xhtml/css/xml/xslt/javascript, then it's a valid use.
There is one exception to the flash as a full page model. If the site contains a "desktop" application (for example a game, a document editor, a help desk program, or possibly a graphical travel planner, etc), then it's OK, but that application should be placed within a secondary page, clearly separate from general site content. It should not be forced upon the user to view all the remaining documents under the website. The same rules of thumb for when to use Java applets ought to apply for Flash web applications.
When you say inaccessible, I interpret that to mean it's difficult to access the data within flash, as opposed to interface accessibility. I think that's true. You can't "Save As" the document if you pull up a report or tabular data, but you could if the site rendered that data as xhtml. In theory, the flash developer could implement a Print or view as a link feature, but that's no guarantee they will. Whereas Save As works on all xhtml pages regardless of whether the programmer paid attention to it or not. Being forced to screenshot the data, is a crappy inflexible alternative.
We now know you don't look at porn. :)
See also: implants.
If you're in USA, you can now apply for a credit freeze. It will be annoying, but if you're not planning on opening new accounts for a while it would help you sleep better.
Not available in all states, but available in most.
http://clarkhoward.com/topics/credit_freeze_states.html
Nice link. I'm so sick of people dumping on USA for selling arms to Iraq yet portraying France, Soviet Russia, and China as modern day messiah societies. That article is rather illustrative. I wish I had that a while back when debating an idiot righteous America loathing Canadian who was slamming USA for sales of weapons to Iraq on another forum.
I watched it. It was interesting, but nothing earth shattering. Somewhat obvious optimizations. Caching + packing data smartly.
Money.valueOf() > Life.valueOf()
It was not Troll. Someone with mod points didn't take his Rapamycin it seems.
http://science.slashdot.org/article.pl?sid=08/06/27/1210202
I have nothing but fascination for the French, but that in no way means I will refrain myself. :)
You're right. I am cute.
Perceptive.
Now, this was definitely an underrated post. Not because of the concept, but due to your choice of words. LOL.
The funny thing is... I voted for Bush in 2004, although supported Gore in 2000.
Btw, I'm now independent and 100% undecided on 2008.
Your estimate is high. Only 50.7% require it.
http://en.wikipedia.org/wiki/2004_US_presidential_election