Get your facts straight.
Actually, when MS was sued it was using both these formats in Office. And MS had the strange reaction to pull both formats out of Office making it look like Adobe was pushing for PDF to be excluded from Office. Adobe never wanted that (and must really hate MS pulled it).
Why not?
There were some bugfixes since rc1 that make KWord a lot faster for big documents. I don't see any reasons or open bugreports on why a big doc would be hard to create.
What you say sounds very weird and certainly is not what happens for me. Did you take a look at the docs, the forums or even asked the user lists?
Please don't just dismiss KWord like that; the styles support actually has been used to markup really big and professional documents, so it can't be all bad:)
In some tests I loaded 300 page documents in KWord that worked pretty fast and editing them worked just fine and again, very fast.
I have heard stories like yours about MSWord and if KWord has the features you want then I do suggest you use it, yes. The features that are there tend to be quite stable.
Just, please, stay away from tables; use embedded KSpread documents instead if you really need a table.
Re:OpenDocument As Default is Great!
on
KOffice 1.5 Released
·
· Score: 2, Interesting
I'm sure Open Office will support everything including the kitchen sink, while Koffice will support mostly a subset of that
There are various little things that KWord does support that OOo does not (yet) support. The ODF standard was created by both office suits and KOffice people did request features like Frames and some numbering-types , as a fast example, that made it into the spec but that OOo still does not support. I'm sure there is more.
I feel its a nice expectation you have, KDE devs tend to be fast, but not that fast.
KDE can not use features in an X.org version that has not been finalized at the time of the KDE release. There are some really cool things being done for the next KDE releases, though. I could almost say 'hold your breath';-) But that would be unhealthy.
PERFECT OPPORTUNITY TO DEMONSTRATE WHY F/OSS IS THE RIGHT CHOICE.
I agree; and I have seen a flurry of activity around KOffice, including a cool screenshot for better accessibility in the upcoming release. See this page;
KOffice preview
There are a number of suites they can use, each supporting ODF as well as the other by the '07 deadline. The beauty of the deal is that the different office suites now get to compete on features like accessibility.
For instance; a KOffice preview noted many accessibility features are already going into the devel-version of KOffice.
See;
This Month in SVN
This is just the first sign that leveling the playing field is good for innovation.
I don't see it as flailing around in the dark, its rather predictable behavior, actually. (at least with 20/20 hindsight:)
Forcing a band to shut up and run the story yourself is an obvious strategy to keep things in your own hands. Sony can say whatever they want, their bands have to keep their mouths closed, seems to be the message.
The fact that they now say you can get around the protection seems to me to be about statistics. At the end of the year only a sample of the CDs were returned, so the DRM thing was accepted by the consumer, right? Sounds like a ploy to use on the politicians who can come up with more DRM usage based on that statistic.
More importantly; not bringing the CDs back means Sony can say at the end of the year they only had a couple of returned CDs, so the consumers accepted the DRM!
Just suffering and working around the problem means you accept the way things are and accept you are incapable of changing that.
As Ghandi said; What you do will be very insignificant, but it is very very important that you do it.
Scenario 2: [snip]
Try re-reading the licence. The JRE is freely redistributal. I have seen a great many software package installs that come in versions with or without the JRE included.
When an application is 200Kb it suddenly grows about 7Mb in size to include the JRE. I know of quite some people that illegally strip the JRE of parts they don't need. Its a bit silly to have to do something that makes your app shippable illegally.
Next to that; including the JRE in your package does not make sense on systems that have good installation-managers that handle dependencies for you. So it only makes sense on Windows or when the user downloads the package, which surely is a very tiny part of the userbase.
Its easy to say that apache is quite large; but its also quite new and doesn't have such a long history for many of its subprojects.
In fact the kde repository consist of a lot more then the apache repositories both in codelines and history. After conversion its about 220% the amount of revisions.
So; no. You're wrong. KDE is the biggest one by far to adopt svn.
I'm really wondering how big a percentage of people like black wearable tech.
The most successful applications are not black, and when a new product is released this should really be one of the things they research.
Also; where do you hold it? I surely can't hold it with my thumb on the screen, and all the other parst have buttons. If I'm watching a video (the latest game, or something) I have to hold it in my hands for a long time, in an akward position...
Why do I sense so much hatred and ungrattitude against SUN?
Suns past has kept it out of trouble from many for quite some time, but like most companies also do; its time to re-evaluate their commitment. And Sun is not giving enough to make Java grow the way it can. All these people are not asking Sun to give more, they are asking Sun to let their child out in the open where it will interact with others and gain new experiences.
Right now Sun is limiting the growth of Java more then stimulating it. All the kids on the block see it, but like any parent the last one to see it is Sun itself.
Your attempt at humor is nice; except for the fact that the message was in Dutch which has nothing to do with the Deutch (aka German) words you wrote above:}
A good start would be to either fix your homepage URL or not show it. Oh; and a short explenation why said proposal did not work in (for instance) Russia would also be nice...
Reading all these highly moderated answers I am aw-struck and at the same time it explains why so little is being contributed by companies..
The point is simple; you need a solution to a problem, your company can code it in its entire or grab an open source tarball to get to 90% in one day. The only drawback is that the other 10% does not belong to your company.
Put up 2 stats with the numbers based on spend hours and let them make the decision. The beautiful part of this is that most managers will care more about short term 'profits' then the long term profits. So for something that is not directly a 'product' as such I suspect the result will be more 'ok' then 'no way!'
For those little bugfixes in apache or KDE or whatever; just email them from your home address; those kind of fixes are just for your working environment:)
I am supervising a group of programmers and have helped many students into real life programming (schools arn't what they used to be;).
In this time I learned that teaching is all about limiting complexity. Thats a mantra guys; Limit complexity!
The blackbox idea is a very good way to get there; it has (alas) been mistaken as the only solution. Successful programmers learn to make a system that contains just enough complexity to do exactly what the problem demands.
The most common mistakes are:
Designing for future use by using expensive design patterns when a simple solution would work just fine.
Creating one system that is too big to oversee, instead of creating a number of smaller systems that are seperate black boxes (thus limiting complexity)
Guessing about an APIs usage instead of reading the API docs.
When a bug occurs in the system people just rewrite the method since understanding the code allready there is hard. (learn to read code!)
Desiging a system should be about connecting black boxes, and basically that is what ObjectOrientation was designed for..
Slashdot Mirror
Get your facts straight.
Actually, when MS was sued it was using both these formats in Office. And MS had the strange reaction to pull both formats out of Office making it look like Adobe was pushing for PDF to be excluded from Office. Adobe never wanted that (and must really hate MS pulled it).
I know, going off topic. But its little known that KWord can open and edit PDF files, so you should try that one out.
Did you consider that the KWord devs said this release made things a LOT more stable for a reason?
Why not?
There were some bugfixes since rc1 that make KWord a lot faster for big documents. I don't see any reasons or open bugreports on why a big doc would be hard to create.
No, we didn't work on Table support very much, we just made it crash less on tables. You, for example, still can't have a table bigger then a page.
Tables will be re-done in 2.0, most probably.
What you say sounds very weird and certainly is not what happens for me. Did you take a look at the docs, the forums or even asked the user lists?
Please don't just dismiss KWord like that; the styles support actually has been used to markup really big and professional documents, so it can't be all bad :)
Please, actually try Krita from KOffice 1.5 (and not a 7 months old one); the filter menu looks a LOT bigger there. And more organized as well :)
In some tests I loaded 300 page documents in KWord that worked pretty fast and editing them worked just fine and again, very fast.
I have heard stories like yours about MSWord and if KWord has the features you want then I do suggest you use it, yes. The features that are there tend to be quite stable. Just, please, stay away from tables; use embedded KSpread documents instead if you really need a table.
There are various little things that KWord does support that OOo does not (yet) support. The ODF standard was created by both office suits and KOffice people did request features like Frames and some numbering-types , as a fast example, that made it into the spec but that OOo still does not support. I'm sure there is more.
I feel its a nice expectation you have, KDE devs tend to be fast, but not that fast. ;-)
KDE can not use features in an X.org version that has not been finalized at the time of the KDE release. There are some really cool things being done for the next KDE releases, though. I could almost say 'hold your breath'
But that would be unhealthy.
I agree; and I have seen a flurry of activity around KOffice, including a cool screenshot for better accessibility in the upcoming release. See this page; KOffice preview
For instance; a KOffice preview noted many accessibility features are already going into the devel-version of KOffice. See; This Month in SVN
This is just the first sign that leveling the playing field is good for innovation.
I don't see it as flailing around in the dark, its rather predictable behavior, actually. (at least with 20/20 hindsight :)
Forcing a band to shut up and run the story yourself is an obvious strategy to keep things in your own hands. Sony can say whatever they want, their bands have to keep their mouths closed, seems to be the message.
The fact that they now say you can get around the protection seems to me to be about statistics. At the end of the year only a sample of the CDs were returned, so the DRM thing was accepted by the consumer, right?
Sounds like a ploy to use on the politicians who can come up with more DRM usage based on that statistic.
More importantly; not bringing the CDs back means Sony can say at the end of the year they only had a couple of returned CDs, so the consumers accepted the DRM!
Just suffering and working around the problem means you accept the way things are and accept you are incapable of changing that.
As Ghandi said; What you do will be very insignificant, but it is very very important that you do it.
But, but. It works wonders for Apple, so why do you feel its a bad thing? Have you considered the language is chosen for this purpose?
- Scenario 2: [snip]
When an application is 200Kb it suddenly grows about 7Mb in size to include the JRE. I know of quite some people that illegally strip the JRE of parts they don't need. Its a bit silly to have to do something that makes your app shippable illegally.Try re-reading the licence. The JRE is freely redistributal. I have seen a great many software package installs that come in versions with or without the JRE included.
Next to that; including the JRE in your package does not make sense on systems that have good installation-managers that handle dependencies for you. So it only makes sense on Windows or when the user downloads the package, which surely is a very tiny part of the userbase.
Cheers!
Its easy to say that apache is quite large; but its also quite new and doesn't have such a long history for many of its subprojects.
:)
In fact the kde repository consist of a lot more then the apache repositories both in codelines and history. After conversion its about 220% the amount of revisions.
So; no. You're wrong. KDE is the biggest one by far to adopt svn.
Now lets see if its any good
I'm really wondering how big a percentage of people like black wearable tech.
The most successful applications are not black, and when a new product is released this should really be one of the things they research.
Also; where do you hold it? I surely can't hold it with my thumb on the screen, and all the other parst have buttons. If I'm watching a video (the latest game, or something) I have to hold it in my hands for a long time, in an akward position...
No, the design is not nearly good enough for me.
Why do I sense so much hatred and ungrattitude against SUN?
Suns past has kept it out of trouble from many for quite some time, but like most companies also do; its time to re-evaluate their commitment. And Sun is not giving enough to make Java grow the way it can. All these people are not asking Sun to give more, they are asking Sun to let their child out in the open where it will interact with others and gain new experiences.
Right now Sun is limiting the growth of Java more then stimulating it. All the kids on the block see it, but like any parent the last one to see it is Sun itself.
There is no hatred; just frustration.
Your attempt at humor is nice; except for the fact that the message was in Dutch which has nothing to do with the Deutch (aka German) words you wrote above :}
A good start would be to either fix your homepage URL or not show it. Oh; and a short explenation why said proposal did not work in (for instance) Russia would also be nice...
So all those free IRC clients (over 400) on freshmeat are really good quality because there was no incentive to create them?
:)
I have a feeling you're missing something
I'm not much of a writer for this kind of stuff; but I hope this link will make others interested to the possebilities!
The point is simple; you need a solution to a problem, your company can code it in its entire or grab an open source tarball to get to 90% in one day. The only drawback is that the other 10% does not belong to your company.
Put up 2 stats with the numbers based on spend hours and let them make the decision.
The beautiful part of this is that most managers will care more about short term 'profits' then the long term profits. So for something that is not directly a 'product' as such I suspect the result will be more 'ok' then 'no way!'
For those little bugfixes in apache or KDE or whatever; just email them from your home address; those kind of fixes are just for your working environment :)
In this time I learned that teaching is all about limiting complexity. Thats a mantra guys; Limit complexity!
The blackbox idea is a very good way to get there; it has (alas) been mistaken as the only solution.
Successful programmers learn to make a system that contains just enough complexity to do exactly what the problem demands.
The most common mistakes are:
- Designing for future use by using expensive design patterns when a simple solution would work just fine.
- Creating one system that is too big to oversee, instead of creating a number of smaller systems that are seperate black boxes (thus limiting complexity)
- Guessing about an APIs usage instead of reading the API docs.
- When a bug occurs in the system people just rewrite the method since understanding the code allready there is hard. (learn to read code!)
Desiging a system should be about connecting black boxes, and basically that is what ObjectOrientation was designed for..