On Thu, 2007-08-23 at 15:29 +0200, Kay Ramme - Sun Germany - Hamburg wrote: > Ian, > > Ian Lynch wrote: > > Hi, > > > > I know this has come up before but I think one of the biggest things > > holding back OOo in the market is the size of the code. I just used > > Inkscape to do a flyer recently and got someone in the office to just > > download and install it to print the flyer. There was no anti-reaction > > yet when I asked someone to do the same on a different occasion with OOo > > there was reluctance because of the size of the download and the thought > > that it would somehow clutter up their computer. So its not easy to do > > but we have to bear in mind that things like Google apps are going to be > > a lot more palatable to some people than downloading 100 meg of OOo > > code. Delivery of OOo through a web browser from a remote server might > > be easier than slimming the code down. Sun's global desktop type > > technology but focussed on OOo and with a simple sign up but seems more > > likely to be developed as a service eg integrated with a Web2.0 business > > than something the community can tackle on its own. > > you are at least right regarding the code and installation size, and > some people are aware of this already. Though the page needs to be > updated, we have a project started to analyze the OOo code basis in more > detail (see > http://wiki.services.openoffice.org/wiki/Analysis/Source_Code_Inventory) > , to actually get an understanding why its so huge ...
Noticed the page is blank. Is this aspirational to reducing the code :-) Seriously, I think the dilemma is that the shared code in OOo should make the individual apps collectively smaller so separating the apps to eg WP, SS, Draw, Base would overall make the code bigger unless there is some fundamental inefficiency somewhere. Not everyone needs every component and I should think a WP would be good enough for many. However, if separating out Writer made it say 50% of the existing code it probably still wouldn't be much good in improving take up so not worth the effort. If you can get Writer down to around 20 meg I think you are in business but that is going to be very difficult. That is why I was thinking a web based approach might be a better use of resources. If OOo was running server side with an Ajax type technology in a web browser I can't see too much problem with WP/SS apps. Graphics might become a bit of an issue but if You Tube can manage concurrent video pretty well surely office apps can't be impossible with appropriate local caching to smooth out latency. In environments where tech support is lacking eg primary schools, not having to install an office suite and maintain it locally has some major advantages. I'm sure the people developing Sun's Global Desktop realise this, I just wonder whether OOo access through web browsers on existing systems might not help provide confidence to move on to more radical change such as remotely provided thin clients. Ian -- New QCA Accredited IT Qualifications www.theINGOTs.org You have received this email from the following company: The Learning Machine Limited, Reg Office, 36 Ashby Road, Tamworth, Staffordshire, B79 8AQ. Reg No: 05560797, Registered in England and Wales. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
