Hey, I know how tough it is for a small artist to make it big. If burning cd's like this can help the little guys (like myself) get exposure, I'm all for it. And if you want to check out my style of electronic music, go to wickedallstars.com and download a free, high quality 192kbps mp3 of the third track on my cd. Feel free to burn it to cd and share it with friends if you like it.
-mike bell
www.wickedallstars.com
cec.wustl.edu/~mwb1/
The Document Object Model. This means that we are developing a model in which the document or Web page contains objects (elements, links, etc.) that can be manipulated. So you will be able to delete, add, or change an element (as long as the document is still valid, of course!), change its content or add, delete or change an attribute. You will be able to get a list of all the H1 elements in the document, or all the elements with an attribute CLASS="foo".
Why should I support or use the DOM?
The DOM API provides a standardized, versatile view of a document's contents. By supporting the DOM API, a program not only allows its data to be manipulated by other routines, but does so in a way that allows those manipulations to be reused with other DOMs, or to take advantage of solutions already written for those DOMs. This interoperability also allows programmers who invest in learning to use the DOM calls to apply those skills to other DOMs.
The intent is that -- if you stick with the standardized APIs -- any DOM implementation can be plugged together with any DOM-based application. The original example of this was dynamic-HTML scripts; by agreeing on the DOM as their standard representation of the document, scripts can be be written that will work properly on all browsers. But this applies to larger-scale programming as well; for example, a server-side solution might be built out of the following reusable components, which may or may not all share a single DOM implementation:
A database which presents its contents as a DOM tree. (Note that the underlying data presented via a DOM need not itself be DOM-like. The DOM is a tool for manipulating data, not a data structure itself.) An XML parser which generates a DOM tree, used to read a stylesheet. An XSLT processor which combines these, producing a new DOM tree. ("Extension routines" in the XSLT stylesheet may also access the source document via the DOM.) A routine which writes a DOM's contents out to the network in the desired syntax (XML, HTML, or other). If a better implementation of one of these modules becomes available (a faster XML parser, for example) or if an additional/different processing stage is required, you should be able to unplug the existing connections and plug in the new component with minimal recoding.
(The goal is "no recoding", and that is already the case for many applications, but at this writing the DOM Level 2 APIs are not yet complete enough to promise this for all applications. In particular, some of the tools needed to construct a DOM "from scratch" are not yet exposed in the published APIs, and the DOM has not yet defined a representation for the DTD/Schema information.)
Similarly, while all DOM implementations should be interoperable, they may vary considerably in code size, memory demand, and performance of individual operations. So the ability to unplug and replace the DOM itself may also be very useful. For example, since some parsers can write into a user-provided DOM, you may be able to parse a document directly into the above-mentioned database.
There is one potential downside to using the DOM: As with any generalized set of interfaces, the DOM calls can be used to solve a very wide range of problems, but may not be the optimal solution for any specific problem. The advantages of interoperability and familiarity to users will more than compensate for this in many applications, but you will find that some tasks may call for other interfaces in addition to, or instead of, the DOM. For example, your application may wish to use custom interfaces internally for performance reasons, yet be able to import/export/expose its data via the DOM for convenient access from outside.
I am developing a product using the DOM specification. What must I do when the product is released?
Full details are in the DOM specification. A brief summary follows:
if you are copying the DOM specification into the documentation of your product, then you must cite the source (including the URL) and include the W3C copyright notice and the status of the specification if you are intending to build technologies based on the DOM specification, then you are free to use these. W3C specifications and sample code are freely available for any use by anyone. If you are going to change the DOM bindings in any way, you must document that the bindings have been changed and change, for example, the Java package names.
Why doesn't the DOM specify anything regarding memory management?
The DOM specification does not define any methods related to memory management (such as to release an object). This is because while the DOM is a programming language independent API, the way one deals with memory is very language specific. Therefore any method related to memory management that is required by a particular language, needs to be specified in that language binding. Due to the way memory is managed in Java and ECMAScript, none of the bindings included in the DOM specification have such methods.
This is the first really exciting product announcment of Fall Comdex '00 thus far, though Comdex doesn't officially kick-off till tomorrow morning.
The actual figures that pertain to the GeForce2 Go chipset are not that impressive off the bat, especially when compared with Nvidia's GeForce2 and GeForce2 Ultra products. However, one must keep in mind that this chipset is aimed at the mobile market, and its performance is truly geared in that direction. For instance, Nvidia has tried to reduce the power consumption of their chip, making for increased battery life of the overall mobile system.
Heres a feature list:
---------------------
Built on a.18 micron manufacturing process
Based on the GeForce2 core
143/166MHz (core/memory) speed
17.2 million triangles per second
4 Texels/clock
286Mpixel/s, 572 Mtexel/s, 2.6GB/s memory bandwidth
0.8watts typical power consumption, 2.4watts maximum power consumption
AGP 4x support, with FastWrites
HD Video Processor/DVD decode
Nvidia Shading Raserizer (NSR)
TwinView & Digital Vibrance Control
32/64/128-bit SDR/DDR configurations
8 - 32MB of memory
Integrated dual-channel LVDs
Well, I think that most would aggree that black holes do exist. There has been alot of proof that there are highly dense objects that do not emit visible light but suck up huge quantities of matter. They still do emit other forms of energy (i believe in the form of x-rays) in order to conserve mass/energy. Just because we don't have all the answers right now about what actually occurs at a singularity, doesn't mean that black holes do not exist. At a singularity (such as a black hole or the very beginning of the universe if you believe big bang theory) relativity breaks down. The mathematics simply give uninformative results (infinities and such). We've had problems like this in the past. Einstein won a noble prize (in 1903 i think) for describing the photoelectric effect. This is the emmision of electrons from metals when they are stimulated by light. Classical physics was shown to be wrong by countless experiments and no-one before Einstein could figure out the what the correct theory was. I'm rambling here, but my point is that we will eventually find an explanation that describes phenomena such as black holes. We always do.
wtf is the deal with all these Haikus? I don't know about anyone else, but I'm already sick of them. It seems every article has at least 4 or 5 haikus moderated up as funny? Anyway, just had to get that off my chest. -Mike Bell
"Bitchslapping is wrong.". It seems that if you moderate someone with high karma's posts down as a troll, you're karma drops to a negative amount, this is stupid. I have triple digit karma, does this mean that I can't post blatantly inflammatory material from my account? No. So why shouldn't people be able to mod me down?
If you read those posts, you will find that Malda himself has to 'bitchslap' someone. It does NOT happen automatically. I do, however, agree that bitchslapping is wrong. My main problem is with the fact that it changes the scores on all previous posts to -1.
I just tested this with Windows 2000 running IE5. I saw my cookies from many web sites in a split second. This is sorta scary, but I'm really not so woried about it that I'll turn off javascript. If I did turn off javascript, it would break many sites that I frequent.
Sure, there could be some malicious code to steal cookies from me, but the chances are extremely small. First, the attacker would have to know what sites I have cookies from on my computer. Even if it did find those cookies, what is the worst it could do? Steal your hotmail account? (I'm sure they couldn't do THAT already). If you use cookies to keep track of really sensitive data, then its your own damn fault.
So, I'm not turning off javascript, and I'm sure MS will release some patch in a few days fixing this 'feature' of windows and ie.
It's assanine, MP3s aren't even of really great quality they are about as good as a decent cassette recording.
Umm, it's been pretty well proven that mp3s are better than 'decent' quality. I think anyone would be hard pressed to tell the difference between a 192kbps mp3 and the original.wav. Yeah, there are some small artifacts at 128, but even then, they are still better than cassette tape.
I haven't seem OS/2 in a really long time, when I last saw it, it seemed comparable to mabey win95 without any service packs. What has changed in that time? Has it kept up with the advances (usb, directX 7, etc.)?
Also, that Project Odin stuff looks real interesting. That would almost make OS/2 an easy to use replacement for current win9x users to get away from b. gates.
Slashdot Mirror
-mike bell
www.wickedallstars.com
cec.wustl.edu/~mwb1/
I didn't know so I found out...
What does DOM stand for?
The Document Object Model. This means that we are developing a model in which the document or Web page contains objects (elements, links, etc.) that can be manipulated. So you will be able to delete, add, or change an element (as long as the document is still valid, of course!), change its content or add, delete or change an attribute. You will be able to get a list of all the H1 elements in the document, or all the elements with an attribute CLASS="foo".
Why should I support or use the DOM?
The DOM API provides a standardized, versatile view of a document's contents. By supporting the DOM API, a program not only allows its data to be manipulated by other routines, but does so in a way that allows those manipulations to be reused with other DOMs, or to take advantage of solutions already written for those DOMs. This interoperability also allows programmers who invest in learning to use the DOM calls to apply those skills to other DOMs.
The intent is that -- if you stick with the standardized APIs -- any DOM implementation can be plugged together with any DOM-based application. The original example of this was dynamic-HTML scripts; by agreeing on the DOM as their standard representation of the document, scripts can be be written that will work properly on all browsers. But this applies to larger-scale programming as well; for example, a server-side solution might be built out of the following reusable components, which may or may not all share a single DOM implementation:
A database which presents its contents as a DOM tree. (Note that the underlying data presented via a DOM need not itself be DOM-like. The DOM is a tool for manipulating data, not a data structure itself.)
An XML parser which generates a DOM tree, used to read a stylesheet.
An XSLT processor which combines these, producing a new DOM tree. ("Extension routines" in the XSLT stylesheet may also access the source document via the DOM.)
A routine which writes a DOM's contents out to the network in the desired syntax (XML, HTML, or other).
If a better implementation of one of these modules becomes available (a faster XML parser, for example) or if an additional/different processing stage is required, you should be able to unplug the existing connections and plug in the new component with minimal recoding.
(The goal is "no recoding", and that is already the case for many applications, but at this writing the DOM Level 2 APIs are not yet complete enough to promise this for all applications. In particular, some of the tools needed to construct a DOM "from scratch" are not yet exposed in the published APIs, and the DOM has not yet defined a representation for the DTD/Schema information.)
Similarly, while all DOM implementations should be interoperable, they may vary considerably in code size, memory demand, and performance of individual operations. So the ability to unplug and replace the DOM itself may also be very useful. For example, since some parsers can write into a user-provided DOM, you may be able to parse a document directly into the above-mentioned database.
There is one potential downside to using the DOM: As with any generalized set of interfaces, the DOM calls can be used to solve a very wide range of problems, but may not be the optimal solution for any specific problem. The advantages of interoperability and familiarity to users will more than compensate for this in many applications, but you will find that some tasks may call for other interfaces in addition to, or instead of, the DOM. For example, your application may wish to use custom interfaces internally for performance reasons, yet be able to import/export/expose its data via the DOM for convenient access from outside.
I am developing a product using the DOM specification. What must I do when the product is released?
Full details are in the DOM specification. A brief summary follows:
if you are copying the DOM specification into the documentation of your product, then you must cite the source (including the URL) and include the W3C copyright notice and the status of the specification
if you are intending to build technologies based on the DOM specification, then you are free to use these. W3C specifications and sample code are freely available for any use by anyone. If you are going to change the DOM bindings in any way, you must document that the bindings have been changed and change, for example, the Java package names.
Why doesn't the DOM specify anything regarding memory management?
The DOM specification does not define any methods related to memory management (such as to release an object). This is because while the DOM is a programming language independent API, the way one deals with memory is very language specific. Therefore any method related to memory management that is required by a particular language, needs to be specified in that language binding. Due to the way memory is managed in Java and ECMAScript, none of the bindings included in the DOM specification have such methods.
-mbell
This is the first really exciting product announcment of Fall Comdex '00 thus far, though Comdex doesn't officially kick-off till tomorrow morning.
.18 micron manufacturing process
The actual figures that pertain to the GeForce2 Go chipset are not that impressive off the bat, especially when compared with Nvidia's GeForce2 and GeForce2 Ultra products. However, one must keep in mind that this chipset is aimed at the mobile market, and its performance is truly geared in that direction. For instance, Nvidia has tried to reduce the power consumption of their chip, making for increased battery life of the overall mobile system.
Heres a feature list:
---------------------
Built on a
Based on the GeForce2 core
143/166MHz (core/memory) speed
17.2 million triangles per second
4 Texels/clock
286Mpixel/s, 572 Mtexel/s, 2.6GB/s memory bandwidth
0.8watts typical power consumption, 2.4watts maximum power consumption
AGP 4x support, with FastWrites
HD Video Processor/DVD decode
Nvidia Shading Raserizer (NSR)
TwinView & Digital Vibrance Control
32/64/128-bit SDR/DDR configurations
8 - 32MB of memory
Integrated dual-channel LVDs
Well, I think that most would aggree that black holes do exist. There has been alot of proof that there are highly dense objects that do not emit visible light but suck up huge quantities of matter. They still do emit other forms of energy (i believe in the form of x-rays) in order to conserve mass/energy. Just because we don't have all the answers right now about what actually occurs at a singularity, doesn't mean that black holes do not exist. At a singularity (such as a black hole or the very beginning of the universe if you believe big bang theory) relativity breaks down. The mathematics simply give uninformative results (infinities and such). We've had problems like this in the past. Einstein won a noble prize (in 1903 i think) for describing the photoelectric effect. This is the emmision of electrons from metals when they are stimulated by light. Classical physics was shown to be wrong by countless experiments and no-one before Einstein could figure out the what the correct theory was. I'm rambling here, but my point is that we will eventually find an explanation that describes phenomena such as black holes. We always do.
-Mike Bell
wtf is the deal with all these Haikus? I don't know about anyone else, but I'm already sick of them. It seems every article has at least 4 or 5 haikus moderated up as funny? Anyway, just had to get that off my chest.
-Mike Bell
"Bitchslapping is wrong.". It seems that if you moderate someone with high karma's posts down as a troll, you're karma drops to a negative amount, this is stupid. I have triple digit karma, does this mean that I can't post blatantly inflammatory material from my account? No. So why shouldn't people be able to mod me down?
If you read those posts, you will find that Malda himself has to 'bitchslap' someone. It does NOT happen automatically. I do, however, agree that bitchslapping is wrong. My main problem is with the fact that it changes the scores on all previous posts to -1.
-Mike bell
I just tested this with Windows 2000 running IE5. I saw my cookies from many web sites in a split second. This is sorta scary, but I'm really not so woried about it that I'll turn off javascript. If I did turn off javascript, it would break many sites that I frequent.
Sure, there could be some malicious code to steal cookies from me, but the chances are extremely small. First, the attacker would have to know what sites I have cookies from on my computer. Even if it did find those cookies, what is the worst it could do? Steal your hotmail account? (I'm sure they couldn't do THAT already). If you use cookies to keep track of really sensitive data, then its your own damn fault.
So, I'm not turning off javascript, and I'm sure MS will release some patch in a few days fixing this 'feature' of windows and ie.
-Mike Bell
It's assanine, MP3s aren't even of really great quality they are about as good as a decent cassette recording.
.wav. Yeah, there are some small artifacts at 128, but even then, they are still better than cassette tape.
Umm, it's been pretty well proven that mp3s are better than 'decent' quality. I think anyone would be hard pressed to tell the difference between a 192kbps mp3 and the original
-Mike Bell
I haven't seem OS/2 in a really long time, when I last saw it, it seemed comparable to mabey win95 without any service packs. What has changed in that time? Has it kept up with the advances (usb, directX 7, etc.)?
Also, that Project Odin stuff looks real interesting. That would almost make OS/2 an easy to use replacement for current win9x users to get away from b. gates.
-Mike Bell