"the zooming flash demo is interesting - but why should i have my hands on the keyboard AND the mouse to navigate a document?"
Because you didn't pay attention and the introduction document says that Flash can't work with both mouse buttons--they wanted one to zoom in and one to zoom out but couldn't.
I've never been able to get the eth1394 driver to work under Red Hat 9. Anyone have any pointers for getting it going between an OS X system and Red Hat 9?
The point of the comment about rumor sites being bad is that Apple has taken steps *against* rumor sites getting into Macworld and things like that. Apple doesn't like rumor sites, but it apparently likes parody sites. That was the point. pudge wasn't literally giving his opinion on rumor sites...
Yeah, when they say "The instant message application will come from Jabber..." they most likely mean Jabber, Inc., so I would imagine they are using that commercial server. That doesn't mean they have to use their clients, though.
Actually, France TeleCom and SwissCom both provide Jabber-enabled cell phones. It may be using an SMS gateway of some kind, but it doesn't have to. Jabber clients don't have to be using linux...
Eh? When I tried to use Inkwell, it didn't seem particularly impressive at all. It usually saw my l's as/'s and inserted lots of extra spaces and things like that.
Even better, it seems likely that Jabber is going to deprecate the current method of authentication altogether in favor of SASL.
Even before that happens, though, it's not *that* hard to change the code for a client to not allow plaintext password authentication. In an enterprise environment it shouldn't be that big of a deal to do, either.
Just because the Jabber protocol allows for a base common denominator for authentication doesn't mean the client software has to allow it.
Um, no the IETF has not endorsed SIP and SIMPLE for IMPP yet.
http://www.ietf.org/html.charters/impp-charter.h tm l
There are only two RFCs there, and they are not SIP and SIMPLE. SIP is very low-level and leaves anything important to IM interoperability undefined or up to the implementation, in fact there's no reason you couldn't just do Jabber on SIP instead of Jabber on TCP.
Anyway, my point is that the IETF is far from deciding and Jabber is a lot closer to an open IM standard right now than SIMPLE is, just because it's actually being used.
Jabber is an open IM standard. If there's anything Jabber's protocol is, it's open. You may argue that it's not a standard, but that's the reason the Jabber Foundation was formed. We're fighting quite hard to make the Instant Messaging and Presense Protocol (IMPP) group of the IETF make up its mind. We've submitted Jabber to the IETF twice and are continuing to press forward. The IMPP group has been in a standstill for *years*
I'd argue that the only useful open IM standard would be a decentralized one. Keeping IM centralized makes no sense if you want everyone to be able to talk to one another
1) There isn't one yet... that was considered "Advanced" functionality and therefore wasn't given priority. Kill your current window manager, start the new one, then save the session.
2) Clock is under Accessories. The rest probably weren't ported.
3) Remembering window positions is up to your window manager.
Then how would this help prevent "googlebombing"? googlebombing involves creating a lot of *new* pages... so wouldn't reducing the bias against newly created pages actually help googlebombing?
There aren't really very many "OS hackers" working on Sawfish, and most people already acknowledged that after GNOME 2.0, Metacity would probably become the default anyway...
Sun's not taking a radical departure from the GNOME "mainstream" here -- just because Sawfish is the recommended default for GNOME 2.0 doesn't mean it's the one-and-only.
The only reason Metacity was not chosen for GNOME 2.0 was that it is still pretty young and incomplete compared to Sawfish.
Sounds to me a lot like the last episode(s) of Seinfeld, where they got to go through a bunch of repeat footage as they explained what the characters were doing the past few years.
Re:can it copy and paste between apps yet?
on
GNOME 2.0 Beta
·
· Score: 1
Copying and pasting between any decently modern apps works perfectly fine. The only problems lately have been Qt2, which did not conform with the X clipboard standard. GNOME has conformed with it for quite some time, and Qt3 will supposedly conform as well.
I definitely have noticed a huge difference in the load times and responsiveness of applications. X and my desktop start up in like 2/3 the time they used to take.
The thing is... the way the stupid stock market works, if IBM suddenly didn't have anywhere near as many patents as they used to get, their stock would fall sharply and they'd lose money.
Slashdot Mirror
"the zooming flash demo is interesting - but why should i have my hands on the keyboard AND the mouse to navigate a document?"
Because you didn't pay attention and the introduction document says that Flash can't work with both mouse buttons--they wanted one to zoom in and one to zoom out but couldn't.
No, DivX was, as far as I know, just a play on the "Divx" video system, which stood for the company name: Digital Video Express.
s to ry/0,24330,3368584,00.html
http://www.techtv.com/screensavers/answerstips/
As opposed to all those other, fair, narrow-in-scope, not-out-to-get-anyone software patents that everyone else files. Right.
Well, Konfabulator *is* Arlo's, so saying it's a "clone" of Arlo's own work is kind of stretching it. ;)
No, Karamba came out after Konfabulator, and its original intent was to be like Konfabulator.. but they also included some samurize-ish things.
I've never been able to get the eth1394 driver to work under Red Hat 9. Anyone have any pointers for getting it going between an OS X system and Red Hat 9?
That's not new to Safari at all. It is at least as old as 10.2... I don't know about before then.
The point of the comment about rumor sites being bad is that Apple has taken steps *against* rumor sites getting into Macworld and things like that. Apple doesn't like rumor sites, but it apparently likes parody sites. That was the point. pudge wasn't literally giving his opinion on rumor sites...
No, GTK+ 1.2 is no longer maintained and supported, the GTK team is only doing bugfixes on the 2.x versions.
Yeah, when they say "The instant message application will come from Jabber..." they most likely mean Jabber, Inc., so I would imagine they are using that commercial server. That doesn't mean they have to use their clients, though.
Actually, France TeleCom and SwissCom both provide Jabber-enabled cell phones. It may be using an SMS gateway of some kind, but it doesn't have to. Jabber clients don't have to be using linux...
Eh? When I tried to use Inkwell, it didn't seem particularly impressive at all. It usually saw my l's as /'s and inserted lots of extra spaces and things like that.
Even better, it seems likely that Jabber is going to deprecate the current method of authentication altogether in favor of SASL.
Even before that happens, though, it's not *that* hard to change the code for a client to not allow plaintext password authentication. In an enterprise environment it shouldn't be that big of a deal to do, either.
Just because the Jabber protocol allows for a base common denominator for authentication doesn't mean the client software has to allow it.
Um, no the IETF has not endorsed SIP and SIMPLE for IMPP yet.
h tm l
http://www.ietf.org/html.charters/impp-charter.
There are only two RFCs there, and they are not SIP and SIMPLE. SIP is very low-level and leaves anything important to IM interoperability undefined or up to the implementation, in fact there's no reason you couldn't just do Jabber on SIP instead of Jabber on TCP.
Anyway, my point is that the IETF is far from deciding and Jabber is a lot closer to an open IM standard right now than SIMPLE is, just because it's actually being used.
1) There isn't one yet... that was considered "Advanced" functionality and therefore wasn't given priority. Kill your current window manager, start the new one, then save the session.
2) Clock is under Accessories. The rest probably weren't ported.
3) Remembering window positions is up to your window manager.
Then how would this help prevent "googlebombing"? googlebombing involves creating a lot of *new* pages... so wouldn't reducing the bias against newly created pages actually help googlebombing?
There aren't really very many "OS hackers" working on Sawfish, and most people already acknowledged that after GNOME 2.0, Metacity would probably become the default anyway...
Sun's not taking a radical departure from the GNOME "mainstream" here -- just because Sawfish is the recommended default for GNOME 2.0 doesn't mean it's the one-and-only.
The only reason Metacity was not chosen for GNOME 2.0 was that it is still pretty young and incomplete compared to Sawfish.
Sounds to me a lot like the last episode(s) of Seinfeld, where they got to go through a bunch of repeat footage as they explained what the characters were doing the past few years.
Copying and pasting between any decently modern apps works perfectly fine. The only problems lately have been Qt2, which did not conform with the X clipboard standard. GNOME has conformed with it for quite some time, and Qt3 will supposedly conform as well.
I definitely have noticed a huge difference in the load times and responsiveness of applications. X and my desktop start up in like 2/3 the time they used to take.
Bah. I would be beta testing a Danger device right now if the person in charge of the beta tests would allow people under 18 to do so. Bah.
Bah.
The thing is... the way the stupid stock market works, if IBM suddenly didn't have anywhere near as many patents as they used to get, their stock would fall sharply and they'd lose money.
99.99% uptime...
Um, just FYI, he said OpenBSD, not FreeBSD. I think most people would agree about the security of OpenBSD.