If, instead of using <a href="#" onclick="foo"> or <a href="javascript(foo)"> type constructs, web designers would use <a target="_blank" href="something.html" onclick="javascript(stuff)"> type constructs, then if the user HAS Javascript active, then the web master can micromanage the newly created window. If not, then the user STILL gets a new window, just not one that the web master can remove all the chrome from.
Sorry, this is incorrect. For better or worse, according to the W3C, opening windows via JavaScript is the only proper way to create new windows. In fact, the target attribute has been removed from standard HTML since at least HTML 4.01 strict.
If you remove the target="_blank" from your second example, you'd actually be doing it right. In this case -as you said- the user would get to the new link regardless. If they had JavaScript turned on, they would get whatever niceness the web developer wanted. If not, they would just get the raw page.
How do you think the court system would handle...
on
Reading Lips In Software
·
· Score: 2, Interesting
...someone recording to video a person *speaking* the source code of DeCSS and then using this tool in combination with gcc to generate libDVDCSS?
Would this tool then be declared a "circumvention device" under the DMCA, or would the courts finally realize that code can be considered protected speech? The code was, after all, spoken in its original form in this case.
This same question could also be applied to audio-to-text converters as well. Maybe there's hope the DMCA will be declared unconstitutional after all.
is it really that hard for Opera to fix their "various display" problems?
It is when the display problem is the web page's fault. I took a look at the page in Konq 3.1. By default, it rendered wrong. Then, I told Konq to lie to the web server and report that it was IE. Behold, a perfectly rendered page!
As an ISP, they should know better...
David
Re:Separating Content from Presentation a Good Thi
on
Office 2003 and XML
·
· Score: 5, Informative
This may be bad (keeping in mind the jury is still out on exactly how Microsoft is making this work) because in the case of office documents, the style is actually *part* of the content, from the perspective of Joe Office User.
If Microsoft just puts the raw text data into a.xml file, then that.xml file is practically useless to anyone who wants to collaborate with the original author since all of the styling information is lost.
As an example of a good way to do this (IMHO), take a look at how OpenOffice.org builds their files. When you make a.sxw (the default writer format) you're actually taking the raw data of the document, the styling rules for the document and a few other important bits and pieces and zipping them up into a single file.
After unzipping this file, the following directory structure was exposed:
content.xml META-INF/manifest.xml meta.xml mi metype settings.xml styles.xml
With this type of design, you can get the best of both worlds. Technically, there is a separation between your presentation and content which allows simple programatic access to the data when necessary. At the same time, this design allows for full collaboration between people who also consider the styling of the data to be part of the content because the style rules for the content are included with the document.
With xml-saved Office documents containing only data and no style, collaboration between non-office users (and apparently Win9x users as well) will be no better off than before. Perhaps worse, assuming the binary.doc,.xls etc formats have changed and will need to be reverse-engineered again.
If this article is true and Microsoft has decided to remove the styling of their xml-saved office documents, I see two possible reasons for this:
The first is obvious. You're not using Office? Ok, second class citizen, here's the data but in a format that is next to useless for you to use.
The second possibility involves Microsoft just not being where they want to be with the Office XML sharing. Keep in mind that it took OpenOffice.org something like a year and half or so to define their XML interchange format. Microsoft may be going there, but due to overwhelming inertia, it just might not be going there very quickly.
Personally, I think the first option is the most likely. However, with OpenOffice.org working with OASIS and others on a common XML interchange format, I'm hoping Microsoft will be forced by the marketplace into option 2.
Here's the page that I use when I want both a "stable" KDE and a "alpha/development" KDE on my system. It goes through the process for you step by step. Kudo's to the author...
Yes it does, it even supports the KDE print system if you're creative...
I've created a printer who's print command is "kprinter" (if memory serves). Whenever I hit "print" it pops up the nice KDE print dialog with all of the neat features it offers.
This is real support from the Hiermenus product. The actual 4.2.3 release of these menus is slated for tomorrow morning.
Please note, the text of the article isn't fully complete yet.The complete copy will be posted sometime April 2nd London time. ElitusPrime jumped the gun a little bit in reporting this to Slashdot. Something about the Email I sent to him that contained the phrases "pre-release stuff" and "mix it [the final text] in with what's already there and you'll have a picture of what will be there tomorrow" seemed to confused him:)
Now *I* have to explain to an editor at Internet.com who doesn't know me from a hole in the ground why an incomplete article about an unreleased product is being slashdotted.
Happy birthday, by the way Elitus!
On to the menus.
Again, yes this is real support. For those of you with Konq 3.0 (it has been released in source form btw - the binary packages are being built right now) you can keep clicking the next article button to finally get to a page with a demo of the menus. They are rather impressive actually.
The Konq team has been working to get these menus to work for the past few months. Basically, I've been using them as a JavaScript/DOM/CSS test bed. Whenever I would find a problem with the scripts, I would report it to the kde-devel mailing list and go to bed. More than once, the problem I reported the night before would be fixed before I got up the next morning. Thanks especially to David Faure of Mandrake with his bug fixes and kind words of support.
These menus are *very* complex. They use an extensive collection of CSS, JavaScript and DOM manipulation to achieve the menu effect. It's important to note that for this release, the Hiermenus guys didn't have to change a single line of code in their scripts save for browser sniffing. Everything that these menus do now works in Konqueror out of the box (or out of the compile for those of you noting KDE doesn't come in a box). A big congratulations are in order for the Konqueror team for pulling this off. I'm proud to have been a part of it.
I plan on writing a story about these menus and what it took to get Konqueror to support them for dot.kde.org sometime in the next few weeks. This time, I'll tell Elitus about it *after* it's final...
No, it's because Caldera (and Apple for that matter) believe that it would be best to move the discussion out of the relatively small group of people who have been talking about it recently into the public domain.
Similar to what happend with the W3C and their patent policies recently.
While I wish they would have voted no, they do have a good point that this issue is one that should be discussed with the general computing public.
There actually is a basis for this name. Intel has a large presence in the state of Oregon and has a tendency to give their products code names from that state.
For example, there's the Willamette (a major river, incidentally one of only a handful in the world that run south to north), the Klamath (a county) and the Deschutes (another county and also a national forrest).
There may be others, but they don't come to mind at the moment.
As a former Oregonian, I find this kind of cool...
**Why? Does it look any better than watching it on Windows? Was it easier? **
Dunno. Don't have Windows. Don't need it anymore thanks in part to CodeWeavers and TransGaming.
**Why not just get Windows? Why support a software vendor that refuses to support your favorite platform? **
Because I'm realistic enough to realize that Linux is nothing more than a blip on most people's desktop radars at the moment. Also, if you would bother to read more about the product you are dissing, you would find that Apple was actually very helpful to the CodeWeavers team during the development of CrossOver. In fact, Apple went so far as to change some of the wording in the license to allow QuickTime to be run legally in WINE.
**Or do you consider "it doesn't break under Wine" to be good enough?**
For WINE, yes I consider it doesn't break "good enough". Since I don't pay for WINE, I'm willing to take my chances. However, that's not good enough for a product I pay for. Thankfully, CrossOver does everything it says it does and is considerably better than just "good enough"
First, I would like to bestow a heartfelt "thanks" to you and your company for all the wonderful work you do. Too often, you've had to defend yourself against the trolls who don't get economics 101. It's not often enough that I see people thanking you for the contributions you have given us. Thank you.
My question lies in the status of your projects. I'm sure some people here on Slashdot don't know about all of the software that you're working on. It would be neat if you could give us a status report on your projects as well as a brief summary of what they do and what we can expect in the future.
I'm especially interested in the integration of your work with KOffice. I know that you donated the base version of Kivio to KOffice (again, thanks) and I was wondering if you had similar plans for Aethera, Kugar and/or Rekall.
Well, let's see. Anybody else see this as the likely way this situation panned out?.
Kodak develops software with MICROSOFT Visual Studio using MICROSOFT Windows 2000 clients.
Kodak discovers their new software doesn't work the way they want in XP.
CEO sits down at his MICROSOFT Windows workstation, opens up MICROSOFT Word and types a letter of complaint. CEO then opens up MICROSOFT Outlook and sends the letter through his MICROSOFT Exchange and MICROSOFT proxy servers.
Sorry Kodak. In all likelyhood, you played a roll in growing this giant. Now you have to learn to deal with it.
I had this problem too: it just came out of nowhere. I fixed it by going in to the control panel's font section and specifying the exact fonts that I wanted, overriding the defaults.
TD's site is not only incompatible, but it relies on all sorts of client-side JavaScript to do things that could 99% of the time be just as easily done on the server side...Ideally I want to be able to log in from a text console using lynx and do my banking... and it seems to me with a little planning there's no reason I shouldn't be able to do so.
Baloney. You don't develop web applications do you? Glitz is what wins customers. If they loose you, so what? They get 100 more because it looks good on their system.
Do you realize what this bank would have to do to make their site work with Lynx or a console? Let's talk re-write from scratch. Let's talk increasing the server horsepower so all of the things that should be done on the client are now done on the server because your client can't handle it. Finally, let's talk doing this (in addition to their regular site) for the tiny percentage of their clients who choose to run a non standards-compliant browser that is incompatible with their system.
Businesses exist to make money. The return on investment for such a system would be nearly nothing. Why should they build it?
Don't get me wrong here. I develop cross platform web applications for a living, even when I don't have to. Between Netscape 6 and IE 5.5, it is still a pain. IE isn't as standards compliant and Netscape 6 is still too immature. When you add the generation 4 versions into the picture, the task of developing anything remotely useful with one code base becomes nearly impossible.
This is why standards are so important. Except for unavoidable hacks, all of my applications use 100% standard code. Do any of them work with Lynx? Hell no. Why? Because Lynx isn't standards compliant. I need ECMAScript, DHTML, CSS, DOM and all of the other TLA's to make my application work and look right. If you choose to use a browser that doesn't support these standards when others are available that do, that's your perogative. Just don't come running to me when you can't do everything you want. I won't re-write my entire application just for you. On the other hand, if you have a disability that forces you to use such a browser, then we can talk.
That being said, if the problem with the bank is just a little JavaScript, it's silly for them not to fix it. It also shows a real lack of understanding on how the web should work.
How, pray tell, can the MPAA make money with DeCSS?
At least, with VCRs, the answer was pretty freaking obvious.
Obviously, it wasn't at the time (early 80's)...
How can they make money with DeCSS? Dunno. I'm not a marketdroid. A first guess would be to increase their market penetration for legally purchased DVDs.
Besides, who says it has to be the MPAA making money off of the DeCSS source code? Why couldn't a company create a DVD add-on for the HandSpring or WinCE in the future? How about a selling and supporting DVD playback capability for less than a licence from the DVD-CCA? Hey, maybe there's a market for some T-Shirts with source code on them! The possibilites are endless.
Don't dismiss what corporate -insert country here- can think of to make money when they are forced to actually think about product development rather than sit back and milk an existing monopoly/product line.
Slashdot Mirror
After all, how on earth could you target a frame with an anchor or a link without using the "target" attribute?
e t.dtd">
You would use an appropriate doctype for a framed page:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN"
"http://www.w3.org/TR/html4/frames
Note: This doctype is not the same as the HTML Strict doctype
David
If, instead of using <a href="#" onclick="foo"> or <a href="javascript(foo)"> type constructs, web designers would use <a target="_blank" href="something.html" onclick="javascript(stuff)"> type constructs, then if the user HAS Javascript active, then the web master can micromanage the newly created window. If not, then the user STILL gets a new window, just not one that the web master can remove all the chrome from.
Sorry, this is incorrect. For better or worse, according to the W3C, opening windows via JavaScript is the only proper way to create new windows. In fact, the target attribute has been removed from standard HTML since at least HTML 4.01 strict.
If you remove the target="_blank" from your second example, you'd actually be doing it right. In this case -as you said- the user would get to the new link regardless. If they had JavaScript turned on, they would get whatever niceness the web developer wanted. If not, they would just get the raw page.
David
Nasa, next time take a lesson from the past and harness the power of the atom...
Next time, they will...
Or "Fair and Balanced Reporting".....
...someone recording to video a person *speaking* the source code of DeCSS and then using this tool in combination with gcc to generate libDVDCSS?
Would this tool then be declared a "circumvention device" under the DMCA, or would the courts finally realize that code can be considered protected speech? The code was, after all, spoken in its original form in this case.
This same question could also be applied to audio-to-text converters as well. Maybe there's hope the DMCA will be declared unconstitutional after all.
Interesting food for thought...
David
is it really that hard for Opera to fix their "various display" problems?
It is when the display problem is the web page's fault. I took a look at the page in Konq 3.1. By default, it rendered wrong. Then, I told Konq to lie to the web server and report that it was IE. Behold, a perfectly rendered page!
As an ISP, they should know better...
David
This may be bad (keeping in mind the jury is still out on exactly how Microsoft is making this work) because in the case of office documents, the style is actually *part* of the content, from the perspective of Joe Office User.
.xml file, then that .xml file is practically useless to anyone who wants to collaborate with the original author since all of the styling information is lost.
.sxw (the default writer format) you're actually taking the raw data of the document, the styling rules for the document and a few other important bits and pieces and zipping them up into a single file.
i metype
.doc, .xls etc formats have changed and will need to be reverse-engineered again.
If Microsoft just puts the raw text data into a
As an example of a good way to do this (IMHO), take a look at how OpenOffice.org builds their files. When you make a
After unzipping this file, the following directory structure was exposed:
content.xml
META-INF/manifest.xml
meta.xml
m
settings.xml
styles.xml
With this type of design, you can get the best of both worlds. Technically, there is a separation between your presentation and content which allows simple programatic access to the data when necessary. At the same time, this design allows for full collaboration between people who also consider the styling of the data to be part of the content because the style rules for the content are included with the document.
With xml-saved Office documents containing only data and no style, collaboration between non-office users (and apparently Win9x users as well) will be no better off than before. Perhaps worse, assuming the binary
If this article is true and Microsoft has decided to remove the styling of their xml-saved office documents, I see two possible reasons for this:
The first is obvious. You're not using Office? Ok, second class citizen, here's the data but in a format that is next to useless for you to use.
The second possibility involves Microsoft just not being where they want to be with the Office XML sharing. Keep in mind that it took OpenOffice.org something like a year and half or so to define their XML interchange format. Microsoft may be going there, but due to overwhelming inertia, it just might not be going there very quickly.
Personally, I think the first option is the most likely. However, with OpenOffice.org working with OASIS and others on a common XML interchange format, I'm hoping Microsoft will be forced by the marketplace into option 2.
Best regards,
David
Somewhere, in a dark and smoky Redmond meeting room, an internal Microsoft slogan is born...
All your next-generation secure computing base are belong to us
root@127.0.0.1
Here's the page that I use when I want both a "stable" KDE and a "alpha/development" KDE on my system. It goes through the process for you step by step. Kudo's to the author...
David
Yes it does, it even supports the KDE print system if you're creative...
I've created a printer who's print command is "kprinter" (if memory serves). Whenever I hit "print" it pops up the nice KDE print dialog with all of the neat features it offers.
Best regards,
David
This is real support from the Hiermenus product. The actual 4.2.3 release of these menus is slated for tomorrow morning.
:)
Please note, the text of the article isn't fully complete yet.The complete copy will be posted sometime April 2nd London time. ElitusPrime jumped the gun a little bit in reporting this to Slashdot. Something about the Email I sent to him that contained the phrases "pre-release stuff" and "mix it [the final text] in with what's already there and you'll have a picture of what will be there tomorrow" seemed to confused him
Now *I* have to explain to an editor at Internet.com who doesn't know me from a hole in the ground why an incomplete article about an unreleased product is being slashdotted.
Happy birthday, by the way Elitus!
On to the menus.
Again, yes this is real support. For those of you with Konq 3.0 (it has been released in source form btw - the binary packages are being built right now) you can keep clicking the next article button to finally get to a page with a demo of the menus. They are rather impressive actually.
The Konq team has been working to get these menus to work for the past few months. Basically, I've been using them as a JavaScript/DOM/CSS test bed. Whenever I would find a problem with the scripts, I would report it to the kde-devel mailing list and go to bed. More than once, the problem I reported the night before would be fixed before I got up the next morning. Thanks especially to David Faure of Mandrake with his bug fixes and kind words of support.
These menus are *very* complex. They use an extensive collection of CSS, JavaScript and DOM manipulation to achieve the menu effect. It's important to note that for this release, the Hiermenus guys didn't have to change a single line of code in their scripts save for browser sniffing. Everything that these menus do now works in Konqueror out of the box (or out of the compile for those of you noting KDE doesn't come in a box). A big congratulations are in order for the Konqueror team for pulling this off. I'm proud to have been a part of it.
I plan on writing a story about these menus and what it took to get Konqueror to support them for dot.kde.org sometime in the next few weeks. This time, I'll tell Elitus about it *after* it's final...
David
No, it's because Caldera (and Apple for that matter) believe that it would be best to move the discussion out of the relatively small group of people who have been talking about it recently into the public domain.
Similar to what happend with the W3C and their patent policies recently.
While I wish they would have voted no, they do have a good point that this issue is one that should be discussed with the general computing public.
David
I would want a member-only Slashdot mirror of all links in front page articles. Oddly enough, I would be paying Slashdot to avoid the Slashdot effect!
David
I did. Does Klamath lake still stink as bad as it did 10 years ago
Forgot about the fact they were also rivers
David
There actually is a basis for this name. Intel has a large presence in the state of Oregon and has a tendency to give their products code names from that state.
For example, there's the Willamette (a major river, incidentally one of only a handful in the world that run south to north), the Klamath (a county) and the Deschutes (another county and also a national forrest).
There may be others, but they don't come to mind at the moment.
As a former Oregonian, I find this kind of cool...
Best regards,
David
Noticable as dimmer, yes. But not as flashing. The original poster was correct.
David
**Why? Does it look any better than watching it on Windows? Was it easier? **
Dunno. Don't have Windows. Don't need it anymore thanks in part to CodeWeavers and TransGaming.
**Why not just get Windows? Why support a software vendor that refuses to support your favorite platform? **
Because I'm realistic enough to realize that Linux is nothing more than a blip on most people's desktop radars at the moment. Also, if you would bother to read more about the product you are dissing, you would find that Apple was actually very helpful to the CodeWeavers team during the development of CrossOver. In fact, Apple went so far as to change some of the wording in the license to allow QuickTime to be run legally in WINE.
**Or do you consider "it doesn't break under Wine" to be good enough?**
For WINE, yes I consider it doesn't break "good enough". Since I don't pay for WINE, I'm willing to take my chances. However, that's not good enough for a product I pay for. Thankfully, CrossOver does everything it says it does and is considerably better than just "good enough"
David
Yes. Read the announcement linked above. Its about a third of the way down.
David
Hi Shawn,
First, I would like to bestow a heartfelt "thanks" to you and your company for all the wonderful work you do. Too often, you've had to defend yourself against the trolls who don't get economics 101. It's not often enough that I see people thanking you for the contributions you have given us. Thank you.
My question lies in the status of your projects. I'm sure some people here on Slashdot don't know about all of the software that you're working on. It would be neat if you could give us a status report on your projects as well as a brief summary of what they do and what we can expect in the future.
I'm especially interested in the integration of your work with KOffice. I know that you donated the base version of Kivio to KOffice (again, thanks) and I was wondering if you had similar plans for Aethera, Kugar and/or Rekall.
Best regards,
David
Well, let's see. Anybody else see this as the likely way this situation panned out?.
Kodak develops software with MICROSOFT Visual Studio using MICROSOFT Windows 2000 clients.
Kodak discovers their new software doesn't work the way they want in XP.
CEO sits down at his MICROSOFT Windows workstation, opens up MICROSOFT Word and types a letter of complaint. CEO then opens up MICROSOFT Outlook and sends the letter through his MICROSOFT Exchange and MICROSOFT proxy servers.
Sorry Kodak. In all likelyhood, you played a roll in growing this giant. Now you have to learn to deal with it.
David
I had this problem too: it just came out of nowhere. I fixed it by going in to the control panel's font section and specifying the exact fonts that I wanted, overriding the defaults.
HTH
David
TD's site is not only incompatible, but it relies on all sorts of client-side JavaScript to do things that could 99% of the time be just as easily done on the server side...Ideally I want to be able to log in from a text console using lynx and do my banking... and it seems to me with a little planning there's no reason I shouldn't be able to do so.
Baloney. You don't develop web applications do you? Glitz is what wins customers. If they loose you, so what? They get 100 more because it looks good on their system.
Do you realize what this bank would have to do to make their site work with Lynx or a console? Let's talk re-write from scratch. Let's talk increasing the server horsepower so all of the things that should be done on the client are now done on the server because your client can't handle it. Finally, let's talk doing this (in addition to their regular site) for the tiny percentage of their clients who choose to run a non standards-compliant browser that is incompatible with their system.
Businesses exist to make money. The return on investment for such a system would be nearly nothing. Why should they build it?
Don't get me wrong here. I develop cross platform web applications for a living, even when I don't have to. Between Netscape 6 and IE 5.5, it is still a pain. IE isn't as standards compliant and Netscape 6 is still too immature. When you add the generation 4 versions into the picture, the task of developing anything remotely useful with one code base becomes nearly impossible.
This is why standards are so important. Except for unavoidable hacks, all of my applications use 100% standard code. Do any of them work with Lynx? Hell no. Why? Because Lynx isn't standards compliant. I need ECMAScript, DHTML, CSS, DOM and all of the other TLA's to make my application work and look right. If you choose to use a browser that doesn't support these standards when others are available that do, that's your perogative. Just don't come running to me when you can't do everything you want. I won't re-write my entire application just for you. On the other hand, if you have a disability that forces you to use such a browser, then we can talk.
That being said, if the problem with the bank is just a little JavaScript, it's silly for them not to fix it. It also shows a real lack of understanding on how the web should work.
David
Happily, its been a while since I coded in VB, but I think the following would work.....
if (foo is nothing) then
do something
else
do something else
end if
I seem to recall doing that in VB5 at some point and having it work.
HTH
David
How, pray tell, can the MPAA make money with DeCSS? At least, with VCRs, the answer was pretty freaking obvious.
Obviously, it wasn't at the time (early 80's)...
How can they make money with DeCSS? Dunno. I'm not a marketdroid. A first guess would be to increase their market penetration for legally purchased DVDs.
Besides, who says it has to be the MPAA making money off of the DeCSS source code? Why couldn't a company create a DVD add-on for the HandSpring or WinCE in the future? How about a selling and supporting DVD playback capability for less than a licence from the DVD-CCA? Hey, maybe there's a market for some T-Shirts with source code on them! The possibilites are endless.
Don't dismiss what corporate -insert country here- can think of to make money when they are forced to actually think about product development rather than sit back and milk an existing monopoly/product line.
David