Slashdot Mirror

sorry, http://irt.org/

my fingers are faster than my brain, then again most things are.

There is a lot more than just javascript on their site, but I use them just for the javascript (here's a link to the actual page I use http://irt.org/script/script.htm)

Look through the whole site, you might find some other areas I've not seen. They've been around for a long time and the content always seems consistent in the areas I frequent.

sorry, http://irt.org/

my fingers are faster than my brain, then again most things are.

There is a lot more than just javascript on their site, but I use them just for the javascript (here's a link to the actual page I use http://irt.org/script/script.htm)

Look through the whole site, you might find some other areas I've not seen. They've been around for a long time and the content always seems consistent in the areas I frequent.

Yes, all too familiar. When I teach C, lesson 1 is Preprocess, Compile, Assemble, Link. Then we do 'Hello World' with notepad, compiling by stages from the CLI, looking at all of the intermediate files. Only after that do we talk about C programming.

The benefit is that from the outset, everyone understands the process, and from the outset, if something doesn't work, you can talk about did the compiler fail or the linker - which you have no meaningful basis to do without explaining the process.

The problem wth doing 'Hello World' first is that learning a programming language is like climbing glass mountain. There is so much to learn before you can do anything useful, so conventionally, teachers are very tempted to miss things out. The thing you can afford to miss out is the IDE, going through the Preprocess Compile Assemble and Link process is far more essential. By setting that scene, your students have a context against which to understand everything else.

Trust me it works. With groups of 3 on a 3 day course, after 1.5 days we do a Yourdon analysis of the mastermind game [see this if you don't know what it is - we don't do graphics, we do it with numbers on the CLI], then we split it into 3 modules and each student codes a module. Then they share their object modules NOT the C code, they link them and we always get a working program either first time or after 20 mins.

JavaScript PDFs

The CSS guide is good, and the JavaScript FAQ is VERY comprehensive.

Ok, so Microsoft is coming out with a product that is 90% the same as an existing product from another vender, but 10% optimized for windows only, and probably *just* different enough that it's easy to get in to, but hard to switch back. It'll be included with every copy of windows (when it's released sometime towards the end of the decade).

Good theory, expect Microsoft was one of the original developers involved in the creation of SVG. Oh, how soon everyone forgets...

"SVG is currently a working draft at the W3C, with working group members coming from key industry leaders such as Adobe, HP, IBM, Macromedia, Microsoft, Netscape, Quark, Sun and Visio." (Source)

There is always IRT.org
or
WebMonkey

Yup! But some people still don't get it

Here's a good place to start for things XUL. Luxor borrows a bit from XUL and show some of the XML advantages over the API approach we all have been using.

Note how easy it is to develop a web site. XUL and other XML technologies will do the same for the interface.

Since this is a real issue for anyone that does a fair amount of web development, I thought maybe I should point out a good resource that really supplements any JS book you use..

The IRT JavaScript FAQ is a surprisingly comprehensive list of FAQ and "how do I..." type questions for JavaScript. I find myself relying very heavily on it for snippets of code.

Once you've "learned" JavaScript, a site like this is great when you don't want to reinvent the wheel or spend 20 minutes skimming a book trying to figure out why something works in Netscape but not IE...

irt.org has always gotten me out of tight jams when trying to implement fancy JavaScript. They have a HUGE section for almost any question/trick/hack you need for DHTML, JavaScript, and a few other languages.

irt.org has always gotten me out of tight jams when trying to implement fancy JavaScript. They have a HUGE section for almost any question/trick/hack you need for DHTML, JavaScript, and a few other languages.

irt.org has always gotten me out of tight jams when trying to implement fancy JavaScript. They have a HUGE section for almost any question/trick/hack you need for DHTML, JavaScript, and a few other languages.

http://www.jalfrezi.com
Whenever I need to lookup a quick command spec, he's got it there for me.

As for Javascript:
http://developer.irt.org/script/script.htm
Always has answers to many different aspects of JS.

So who cares about compression. Personally, I'd much prefer the open and obvious standards of XML to some obfuscated form. Data is confusing enough already; at least XML gives a clear description that I can use with a packet sniffer when trying to debug something.

You're kidding right? Most CS people I know cringe at the fact that XML can more than double the size of a document with largely redundant tags. The only thing to be thankful for is that the documents typically compress very well due to the large number of redundant tags and that HTTP 1.1 supports compression especially know that XML over HTTP (i.e. web services) is being beaten to death by a lot of people in the software industry. Numerous articles about XML compression also tend to disagree with you that it is not an issue.

PS: If bandwidth is so cheap how come DSL companies are going out of business and AOL owns Time Warner? This would tend to imply that low bandwidth connections are still the order of the day.

Irt.org, man. They saved my life many times over about a year ago.

An MS plugin for Netscape exists, if you're running Netscape on a system which is compatible with the plugin.

Actually, even Exchange Server has problems if not running on same server as IIS.