OpenOffice.org Team on OO.org (and Upcoming v2.0)
Aditya Nag writes "I recently got the chance to ask the OpenOffice.org team a few questions about OpenOffice.org in general, and their upcoming release. The questions were answered by Louis Suarez-Potts and Colm Smyth. Louis is OpenOffice.org's Community Manager, member and chair of the Community Council, and lead of many OpenOffice.org projects including the Native Language Confederation. Colm is a StarOffice Architect, and was responsible for defining the product concept for OpenOffice.org 3.0 (or StarOffice 9). The interview is fairly long and detailed, and there are a few interesting tid-bits, like Louis' assertion that there will come a day when there will be no proprietary file formats for Office Suites." This is the full interview from which excerpts were linked in the recent post about OO.o's beta candidate for 2.0.
This is the full interview from which excerpts were linked in the recent post about OO.o's beta candidate for 2.0.
You're a Slashdot regular Timothy, if you want to say your articl'es a dupe then don't beat about the bush just say "Yep, this is a dupe".
Anybody actually using open office in a, er, office? How about some real experiences with it?
Yeah? Well I think you're overrated too.
wouldn't it be nice if there's a better latexOO/doc conversion? One of the biggest problem is with math equations, but isn't mathml also some sort of a standard that shouldn't be that hard to covert into? also there are lots of problems with tables.latex2rtf and some other sharewares are nice, but they don't seem to do the conversion too well...
my blog
OO.org really have their work cut out for them. I'd really like to see OO.org approach computer manufacturers like Dell and present a strong case as to why distributing OO.org with their systems will add value for their customers - perhaps as part of the free software suite Dell customers already recieve with new systems?
Go to Microsoft Office's suggest feature page and ask for
"Please add read/write support for the OASIS document formats found in OpenOffice.org 2.0."
"The interview is fairly long and detailed..."
I must have RTFA in the past too many times, as this seems a rather short interview. Even the ones Slashdot sends out have 10 questions, where this one come in at an overwhelming 6 questions.
dont get me wrong, i love ooo, and i would be sold if it wasnt for the crappy spellcheck. maybe i have been raised wrong, and schooled wrong. but i suck at spelling, and so does ooo. here is the test that i ran. i spelled the word "Meticulously" phonetically, or fonetically if you will. and in ooo 2beta, i get about 10 sugesstions that all start with the letter "r". same thing in ooo 1.1. so i guess that ooo has made no progression in this area. in wordperfect 12, one sugesstion, and it was right. in word i bet it would be the same (i cannot aford to try it). I also tried google, and it sugessted the correct spelling. would be that hard to develop a front end for googles sugesstion service for ooo? so it wouldnt suck? this is the major compalint that i have with ooo, and it is major in my opinion. Kevin
Since everything in the proprietary world of Microsoft and MacOS has to be copied or rejuvinated within the OpenSource community, is it possible that people are forgetting about innovation and focusing too much on mirroring what others do? Apple have come a long way simply through innovating, just like many modern successful businesses but without major goals of innovation, isn't it possible that the OpenSource community may be stuck forever in a game of catch up?
When Microsoft Office is free[ed2k link]?
Considering the utterly prohibitive costs to a small business should they ever be subject to a BSA audit while using the "free" version of MS Office, I'd say it's actually pretty expensive. Honestly, an audit can be a business changing experience. It just isn't worth the risk.
The last small company I worked for was busy transitioning as many staff as they could over to OpenOffice. They weren't doing this because OpenOffice was cheaper, they were doing this because they didn't have to bother with the task of filing and managing licenses - the reduced cost was just a bonus.
Jedidiah.
Craft Beer Programming T-shirts
The main focus of our efforts and the most important benefits that customers will see is improved usability and significantly improved interoperability with Microsoft Office formats. This addresses the day-to-day needs of many more end users and makes
OpenOffice.org/StarOffice a real alternative.
I really hope they mean this. Dealing with MS Office formats has got to be insanely difficult and as of yet no one has really been able to do it well (not even Microsoft!). Life would be so much better if there was another office suite that could handle all the MS formats without choking on everything but the simplest of documents. I've got great hopes for OO.org 2.0 but you'll have to excuse me if I'm still a bit skeptical.
...make the install dummy proof I won't be recommending it again. I recently had the nerve to suggest that my mother-in-law try it out. She is just a regular internet user. She uses email, browses the web, and has used Microsoft Office on occassion so I thought it would be a snap for her. I emailed her a link and small description of Open Office and she was thrilled to give it a shot.
Well the downloads (even the stable) for the office suite are a zip file. The zip file extracts to a directory with a horde of different files. She had no idea what a zip file was and when I finally talked her through extracting it she was baffled by the tons of files.
Installing it this way may seem like a trivial task to the average computer geek but to your casual user this is a very intimidating process and if it weren't for me on the phone with her she would have never figured it out. I don't want to do install support to every person that I think might find use in Open Office so I'm just going to bite my tongue or suggest they shell out some cash for a CD they can pop in and have it hold their hand through the process.
Does the OpenOffice team actually realize there are real and serious interface usability and elegance issues with their program, and desire to fix this?
I think they do. Usability, consistency, and GUI cleanup were some of the major tasks for 2.0. No 2.0 doesn't magically correct everything, but as far as usability goes it makes great strides over 1.0. The other thing to note, of course, is that in the end OpenOffice is aiming to be a fairly close work-alike to MS Office to make transitioning easier. That means that it will have the same GUI and usability issues as MS Office, as well as any of it's own. The MS Office inherited usability issues aren't likely to go away all that soon unfortunately - not util OO get's enough of a userbase that it can forge its own direction in the Office application market.
Jedidiah.
Craft Beer Programming T-shirts
As far as I know, the 'OS X hackers' are working on NeoOfficeJ. I don't actually like NeoOfficeJ though. It's old of date and quite buggy.
My other sig is crap too
It would really be nice if 0.000% of the openoffice.org effort devoted to press releases and promotion went instead to increasing the portability of the code :)
This lack of portability is really a pet peeve of mine. With Linux or NetBSD, you can run the same application on practically any hardware platform, just by recompiling... presuming the software was written without 32-bit assumptions. Linux (and NetBSD) becomes your portability layer, presuming your application meets some minimum standards.
Another pet peeve is that every big application re-invents cross-OS portability, which actually exacerbates the portability problem.
In my position, when you have 1000 packages to get running on Alpha AXP, each application's portability glue becomes a portability hindrance. As an example, Mozilla's portability layer is the reason why Mozilla does not build on alpha today.
Seriously, this is the single reason that I use it over MS Office (except when I can't help it, like with Rational Soda and RequisitePro).. I used to work next to this guy, he would say "Wow, I never expected it to do that!" in joyful glee whenever MS Office did something truly bizarre with his formatting. Sometimes he would cry when undo didn't work. Office Interface
Each processor would proceed sequentially as if it had been better for them not to rise against Saul.
Been there. Done that:
Neo Office/J
The IPCC has purposely engineered a massive scientific fraud.
I don't get why they want to call it "OpenOffice.org". No matter what they, naming your product after your website is just stupid. And then to be all anal about it. "It's .ORG! You have to say the .ORG part!
ugh.
I get that it's marketing, but I don't agree with it.
I run a small computer company and I use OOo for all of my business activity. I also recommend OOo to many of my customers and then also ask for a small donation to help the OOo team. I am also trying to convince a couple of local schools to switch to OOo inorder to save money. Though there is resistance, mainly because people don't want to admit that they have wasted their money. The clients of mine that have tried OOo have all given me positive feedback. I have a few complaints, though that may be a bit strong, when working with embedded tables in documents formatting gets screwed up often, and there is an odd scrolling issue on my system when I work with spreadsheets. But these are fairly minor issues. I can't wait to start playing with OOo 2.0 I just need to wait for the stable version.
Ever tried installing it? It's *incredibly difficult*. It's not an open source package that a sys admin can simply decide to try out quickly. Installing it involves loads of time and all sorts of system-specific tweaks. Our organization investigated moving to that platform but abandoned it when realizing how large of an undertaking it would be (in both time and skills) to even get it running.
I've heard that the 1.0 release's main focus is making installation easier, however, it can't even be installed on RHEL I really don't see the installation improving at all if they continue to ignore one of the most popular platforms out there.
-Fatty
From what I recall, there is another product called 'openoffice' which has a trademark on that name. The openoffice.org team gets around that issue by enforcing the ".org" in their literature and promotion efforts.
creation science book
http://www.openoffice.org/FAQs/faq-other.html#7
creation science book
What strides as 2.0 made in GUI and usability? From the screenshots of the beta, I see none.
What exactly are you looking for? A rough outline of the design goals is here with specific target improvements for 2.0 here. For very specific improvements actually made not just target concepts you can read through this and look for all the "ease-of-use" improvements made. There are actually a lot. Yes, some are small. No, OOo 2.0 is not somehow magically a perfect usability application. It is an issue, and they are focussing on it. It is an incremental process however.
Jedidiah.
Craft Beer Programming T-shirts
You need to get out more. NeoOffice/J is updated monthly and is using the latest release OOo 1.1.x code.
It is being worked on. No, it hasn't made it into 2.0, but it looks like they have a provisional svg2draw translator - it just needs a little more work. It's not like they are completely ignoring the issue.
Jedidiah.
Craft Beer Programming T-shirts
I wish I hadn't replied to this topic so I could mod the parent out of flamebait. He's absolutely right -- OO.o has a worse GUI than the Proxomitron's default psychedelic skin. There are simply too many buttons, the default set seems randomly chosen, and trying to reorganzine the toolbars is like sprinting through quicksand. The devs need to look at AbiWord and Firefox.
Les Miserables Volume 1 now up with my reading of
No. OpenOffice doesn't use Java. OpenOffice does however provide a Java binding to a component model called UNO (Universal Network Objects) which can be used, among other things, to remotely automate OpenOffice. There also used to be some Java components that use a direct Java to C++ bridge to integrate with OpenOffice but I don't know the status of those. Java is less of a requirement and more of an option.
Speaking from experience I know how hard it is to compile OO.o on Slackware :)
/opt/OO_directory_name
First download the tarball.
Now su to root and perform a network install:
tar -zxvf OO_tarball_name
cd OO_source_directory_name
./setup -net
Now return to your user and:
cd
setup
Or see The instructions for full details.
Boy that's hard, I'd rather write a kernel driver using my feet to operate the keyboard anyday of the week. Damned unusable Slackware making me both think & type. It'll never catch on. Never I tells ya.
Sky subscribers are morons. They pay to be advertised at !
I don't much like the sound of the extra .org, and can't see how it frees them from trademark issues, the FAQ only states they don't own the 'OpenOffice' trademark.
Digging around in forums has given me some very muddled answers relating to the ukrane and ripoff copies of openoffice being sold.
I agree with your sentiments, up to a point.
Several years ago, OOorg was dominated on their
mailing lists by persons who essentially wanted
OOo to be an Office (MSFT) look-alike. IMHO,
this detracted from the real benefit of F/OSS,
a common source tree that could be built on any
number of different platforms.
While OOo's decision to focus primarily upon the
X11 platform might be considered to be a drawback,
I would consider a single source tree to be a
real advantage. Maintaining a common look/feel
cross-platform makes it easier to "switch gears"
when using it on another OS. Instead of trying
to match MSFT on the basis of the GUI, the effort
to out-perform MSFT on features and functions
would create a product better than MSFT's.
That said, the OOo project has forked specifically
for the Mac OS X platform in the NeoOffice/J
project, if you insist upon an Aqua interface.
Otherwise, just install the available X11 code
on your Mac OS X, and use the OOo binaries for
the Mac platform (using X11). Simple enough.
in the last answer, colm mentions collaboration features in 3.0 - anyone know where there might be more details on 3.0 features?
pr0n - keeping monitor glass spotless since 1981.