So it's a flawed implementation showing through in the GUI. Even so, why not just attempt to open a file, if it fails copy the file, use the repair on it and open the copy as a "repaired copy" transparently to the user.
Nooo... you've bought back my memories of the summer internship I spent writing VBA code in Office 97. I'd been trying to block that out.
After two months flat-out coding, in the last week, most of the company upgraded to Office 2000 . My program just refused to run at all on 2000. I spent the last week trying to make it work, but nothing I did made any difference. I had to scrabble around for an older machine with 97 on it just to do a demonstration to proce I'd done any work at all.
Three years ago? That's a long time in OSS. 3 years ago we had KDE 2, openoffice 1.0 wasn't even released and linux 2.4 was just becoming mainstream. So yes, there have been a few improvements.
If there are any OO.org developers out there, could you tell us what OO is *doing* with that start up time? Abiword and Kword start in less than the time it takes swriter to start displaying its splash screen. I'm not criticising - I know how hard optimiation is, I'm just interested.
It's also $200 or so (unless you get it with a new computer).
I'd call randomly corupting files and moving images around more than annoying quirks. The fact is, Word's only killer feature is 100% Word compatibility. Combine that with a monopoly, saturation advertising and restrictive licensing deals with OEMs and you have a WP that's hard to beat.
I wouldn't say that creating artwork is any more difficult *to an artist* than coding is to a coder. I just think that not so many artists are either aware of or prepared to work for an open source project.
I held up my TiBook, pointing to the zero lines in the Airport icon, and showed the officer that my card was off.
"Why don't you just close that up, sir, or use your computer elsewhere?'
Quite apart from the signal stealing part, isn't the fact that the cop asks him to move on a bit worrying? He's demonstrably not breaking the law and is sitting on public land. Are they just going to ban using laptops with wifi cards near any wireless point?
Does 'appeal' mean something different in your version of English? They were awful devices, not exactly much competition for the GBA SP. Very few people bought them because they were clearly badly designed. A shop near me is trying to get rid of their Ngage game stock at less than half price and still not selling them.
I was thinking that too - I remember using some IBM computer-in-an-LCD-monitor three years ago. Very ugly looking compared to this, I admit, but a similar idea. Basically a laptop with an external keyboard and no battery.
The problem I found with the IBM machine was that the computer off button is in exactly the same place as the monitor off button would be on a normal computer, so I kept switching the computer off by mistake while meaning to just switch the monitor off.
Reading the description of how the system works it's like it was built by a couple of 16 year old kids who've read a book on VBA. It looks like it's just a hacked up interface to Access, for god's sake. The biggest democracy in the world trusts its votes to Access? Scary.
What? We'll have to deal with simple bugs that would have been spotted by any testing in a decent monitoring tool? The bug was a resource leak, nothing more.
More likely you had some uninitialised variables or were overwriting memory somewhere, and the presence of the printfs changed the location or initial value of whatever variables or memory were being used incorrectly to make the bug show up. In general, the compiler is far less likely to have a bug than your code.
Of course, you're actually using a fair chunk of KDE when you run K3b, due to the its integrated nature (KIOslaves, Kparts etc). Not that that is relevant at all here. There's no mention at all of using KDE specific metadata here. There's very little detail, but the use of "google-like" implies an indexing service to generate the metadata from the original files, which is then searched by a separate agent. Of course they're not going to do something that requires the use of a (as in your ridiculous example) KDE text editor to generate "compatible" text files. That would be stupid. I imagine the KDE developers want to use all the nice technology they've developed to make developing the search engine easier. Involving freedesktop in that beyond generating some kind of standard search indexer protocol seems uneccessary.
Who said they're adding it to the windowing environment? They're not adding it to KWin.
It'll be part of KDE - where DE stands for Desktop Environment. KDE is much more than a window manager, it's an entire desktop system, so this is the perfect place to add it.
To some extent I have to say - what do the eMachine-style budget PC users expect? They cost like $399 and come with more processing power, memory and hard disk space they could ever use. The savings have to come from somewhere.
Slashdot Mirror
So it's a flawed implementation showing through in the GUI.
Even so, why not just attempt to open a file, if it fails copy the file, use the repair on it and open the copy as a "repaired copy" transparently to the user.
You don't necessarily write the file to repair it - just opening it doesn't mean you have to write the result out until the user tries to save.
You could just replace the "Open and repair" with a more robust open implementation and the user would never know.
Nooo... you've bought back my memories of the summer internship I spent writing VBA code in Office 97. I'd been trying to block that out.
After two months flat-out coding, in the last week, most of the company upgraded to Office 2000 . My program just refused to run at all on 2000. I spent the last week trying to make it work, but nothing I did made any difference. I had to scrabble around for an older machine with 97 on it just to do a demonstration to proce I'd done any work at all.
Three years ago? That's a long time in OSS. 3 years ago we had KDE 2, openoffice 1.0 wasn't even released and linux 2.4 was just becoming mainstream. So yes, there have been a few improvements.
If there are any OO.org developers out there, could you tell us what OO is *doing* with that start up time? Abiword and Kword start in less than the time it takes swriter to start displaying its splash screen. I'm not criticising - I know how hard optimiation is, I'm just interested.
What a bizarre way to do it - why would the user ever want to *not* repair the file when they try to open it?
On linux, with each WP displaying the same three A4 page document:
OpenOffice 1.1.2 resident set: 49Mb
Abiword:16Mb
(Kword: 36Mb)
That's one reason. Openoffice is extremely processor and memory intensive, without that many features that justify the extra resource usage.
It's also $200 or so (unless you get it with a new computer).
I'd call randomly corupting files and moving images around more than annoying quirks. The fact is, Word's only killer feature is 100% Word compatibility. Combine that with a monopoly, saturation advertising and restrictive licensing deals with OEMs and you have a WP that's hard to beat.
I wouldn't say that creating artwork is any more difficult *to an artist* than coding is to a coder. I just think that not so many artists are either aware of or prepared to work for an open source project.
I suppose that sound almost fair. But you could apply that logic to anyone in the area with a wifi card. What happens if you say no?
I held up my TiBook, pointing to the zero lines in the Airport icon, and showed the officer that my card was off.
"Why don't you just close that up, sir, or use your computer elsewhere?'
Quite apart from the signal stealing part, isn't the fact that the cop asks him to move on a bit worrying? He's demonstrably not breaking the law and is sitting on public land. Are they just going to ban using laptops with wifi cards near any wireless point?
They've recently decided to rename them Emergency Departments in order to make them sound more important so people with minor injuries won't go there.
With n-gage starting to appeal to the masses
Does 'appeal' mean something different in your version of English? They were awful devices, not exactly much competition for the GBA SP. Very few people bought them because they were clearly badly designed. A shop near me is trying to get rid of their Ngage game stock at less than half price and still not selling them.
I suppose I am, in my rambling way.
I was thinking that too - I remember using some IBM computer-in-an-LCD-monitor three years ago. Very ugly looking compared to this, I admit, but a similar idea. Basically a laptop with an external keyboard and no battery.
The problem I found with the IBM machine was that the computer off button is in exactly the same place as the monitor off button would be on a normal computer, so I kept switching the computer off by mistake while meaning to just switch the monitor off.
Oops, second largest democracy (sorry India).
Reading the description of how the system works it's like it was built by a couple of 16 year old kids who've read a book on VBA. It looks like it's just a hacked up interface to Access, for god's sake. The biggest democracy in the world trusts its votes to Access? Scary.
What? We'll have to deal with simple bugs that would have been spotted by any testing in a decent monitoring tool?
The bug was a resource leak, nothing more.
But even then, it's reasonably simple problem - the disk clearly isn't full, so something's wrong.
Grep "Disk Full" src/file_access/*.cpp
and you have a bunch places to start looking for the trouble.
This of course assumes that file access is all in one module, which judging by these guys' apparent ability I doubt.
More likely you had some uninitialised variables or were overwriting memory somewhere, and the presence of the printfs changed the location or initial value of whatever variables or memory were being used incorrectly to make the bug show up.
In general, the compiler is far less likely to have a bug than your code.
Of course, you're actually using a fair chunk of KDE when you run K3b, due to the its integrated nature (KIOslaves, Kparts etc). Not that that is relevant at all here.
There's no mention at all of using KDE specific metadata here. There's very little detail, but the use of "google-like" implies an indexing service to generate the metadata from the original files, which is then searched by a separate agent.
Of course they're not going to do something that requires the use of a (as in your ridiculous example) KDE text editor to generate "compatible" text files. That would be stupid.
I imagine the KDE developers want to use all the nice technology they've developed to make developing the search engine easier. Involving freedesktop in that beyond generating some kind of standard search indexer protocol seems uneccessary.
Yes, I'm a little unsure why they mentioned "google like" search. My point was that there is a place for more advanced search than just find.
doesn't work unless you remember to name files consistently.
Who said they're adding it to the windowing environment? They're not adding it to KWin.
It'll be part of KDE - where DE stands for Desktop Environment. KDE is much more than a window manager, it's an entire desktop system, so this is the perfect place to add it.
To some extent I have to say - what do the eMachine-style budget PC users expect? They cost like $399 and come with more processing power, memory and hard disk space they could ever use. The savings have to come from somewhere.