On Fri, 2004-03-12 at 12:10, adrian.wells wrote:
I think you are comparing SO 5.2 with OO.o 1.1. The important thing to realise is that this software is not static its constantly improving and if you like 1.1 just wait until 2.0 hits the net and then 3.0 then 4.0.
Your quite right :-) Although I did understand that the core code was similar.
However a WP, is a WP is a WP, there are only so many things that you want it to do (unless you want to integrate other functions, e.g proper DTP etc.) So what do you change? Tighter/faster code, fiddle with the interface (lots of scope for likes/dislikes here) or add yet another wizard :-)
I think that is an interesting point. In a scenario such as MS Office, its in the vendor's interest for the code to get larger because then it forces users to buy a new machine with a new OS. In the case of an OS project hackers pride in doing it right and making it efficient is at least part of the equation. So as applications reach maturity and there is not much left to improve, you can add a load of worthless gimmicks that bloat the code or you can make the code more efficient. I think the latter is more likely to be the cae with OO.o development.
The killer, that will ensure the success of OO.o is it's ability to SEAMLESSLY import and export documents from and to other apps. One of my clients, a company of patent attorneys, will not use OO.o because they are worried about compatibility when exchanging documents with clients, and yet they use different versions of office & works with which they struggle to exchange files within the office! :-) Doh! The irony is that most of their WP could be handled by the simplest of WPs and translation wouldn't be a problem for OO.o!
Well ignorance is probably the toughest obstacle to tackle. But on the + side kids are learning more IT at school and the youngsters tend to be more open to FLOSS.
Yes, pressing companies to bundle OO.o would be a great leap forward, unfortunately the big 'uns are tied in with MS, Dell et al. I'm going to have a word (no pun intended) with my local supplier and offer him a copy.
I have seen PCs in Tescos with StarOffice pre-loaded. We tend to put OpenOffice.org on the ones we build if the customer doesn't specify something. I can't really see why DELL should worry too much about upsetting MS. If MS actually tried to put pressure on them it would be illegal and they just need to squeal to the OFT. I think its more likely just a mindset. If we keep tapping away it will eventually shatter. -- ian <ian.lynch2@ntlworld.com>