Preserved Topic: DHTML consortium

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

I'm cool with this, it's a great idea. I know from painful and bitter experince that shared projets of this sort can be a tough thing to pull together, too many Divas and not enough back-up singers usually! I know for my part that grabbing divs and pushing them somewhere else is not the biggest difficulty, it's all those updating functions that get complicated, and are often the hardest to explain.

I think the first thing that needs to be worked on is not so much the actual code, but the "name space" we'd be using, how are standard variables to be named, and what functions are most needed and what *they* should be named. We need to be careful not to step into someone elses name space, already over the years I've had some of my favorite variable names "claimed" by new browsers as reserved words, that was the main reason for the big old capital "Z" in all of my functions and variables, I hope it'll be safe for a while!

So! I've already started, and plan to continue as I've been doing, taking any and all feedback as I go. If we can come to some sort of concensus, I'd be glad to march along to the party line, but my own Znippets project is a quest for understanding as much as a library of coding snippets, and I also plan to use it as a tool to teach Javascript and cross-browser coding to existing users, as well as (hopefully) an entry point newbie coders. I'm anxious to hear what others have to say about this, and how we could make it work!

Your pal, -doc-

As I'm not going to be of too much use in any such project I'd just like to say that the Doc has made a great start towards this thing and it mght be a good idea if enthusiastic people (Ini is clearly boiling over with energy for starters) gave him plenty of feedback (not too much as he has a life to lead unlike some of us) on how to trim down the code, make it as cross-browser as you think, etc.

These kind of projects often diverge with people aiming for different criteria but I'm sure for the time being it would be a good idea to try and make what is already emerging as close to our (various ideals) as is possible.

Emps

Personally, I'm not really sure if this is such a hot idea. Writing a new library that should support most (all?) browsers and should be small in size would require *a lot* of time (especially the cross browser thing). So, my suggestion would be to consider using DynAPI2...

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

There are actualy quite a few DHTML API's around on the net. I've actually downloaded most of them. Pulling them to peices is the primary way I started to learn DHTML. The API maxx mentioned is very good but I've heard some people complaining about how big it is. Which is mainly why the other API's exist. The don't claim to be the be-all and end-all for DHTML, more so just a simple library that makes coding eaiser and much quicker.

I really like the Doc's approach to this, having seperate modules that can be fitted togther depending on you web sites needs which makes his approach very attractive. Besides, he's one of the few super cool DHTML coders I konw that's also a designer. I've seen far to many DHTML driven sites that work extreamly well but sadly, they just look horrible. Furthermore, given his success with Hands-On and general down to earth attitude, the Znippets (I keep wanting to call them Znipplets now.. grrr) site doesn't have that aura of eliteist attitude sourounding it like many other DHTML sites do.

InI: Dan Steinman who wrote the first Dyn Api back in 98 still has a web site up with a huge section of DHTML tutorials for the old v4 browsers. He's bascialy written tutorials for how he made most of his first Dyn Api in which he gives one of the best intorductions to cross browser DHTML scripting I've ever read. If it wasn't for him I'd still be thinking my JS 1.0 image swap script was cool. So, if your still planning on writing DHTML tutes for that Warpod progect then I recommend you go read through these tutes. Not for what he teaches but for how he teaches it.

Hey Drac! You can till call them Zniplets if you want, just use only one "P", OK? (See http://www.Zniplets.com/ to see what I'm talking about, heh.) When I get myself a job again I'll see about buying that extra P also, may as well cover my bases!

Oh, and BTW, since I mentioned it here, yah, I'm putting Primal Content into hibernation, the economy is just too hurting to handle this concept right now. As soon as we get a billable client the bastards go bankrupt, it's getting boring! If anyone knows someone who is a) not going bankrupt, b) in Stockholm, and c) in need of a guy like me, let me know, cool? I have 5 resumés printed out, and I'm hoping that is all I'll need. (I had a hot lead at a top ad agency, did the first interview which went great, then they got the word from the home office to start laying folks off - boring. :/ )

Your pal, -doc-