Gobe Productive To Be GPLed
ParisTG writes "The Gobe Productive office suite is to be re-licensed under the GPL, according to an interview by OSNews. "FreeRadical has purchased the gobeProductive source code and plans to continue to develop the product under a GPL license."" The people who wrote Gobe, are also the folks who wrote ClarisWorks ? , if you remember back to that. I've used Gobe a few times before - great office suite.
...and I still hear people calling for the open sourcing of WordPerfect. How many office suites do we need?
Finally! A year of moderation! Ready for 2019?
It's very noble of Gobe to release the source after the product's financial demise, rather than sell it on for a pittance. Hopefully the clean and bloat-free source will live on.
See osnews for a comment by one of Gobe's developers Tom Hoke.
I'm rolling out 30 P166s and this will be on it :)
Relly nice program! I just tested it on Windows and now i wonder why anyone would want MS office. Especially the graphics module is impressive, and I can't believe how fast this app is, yet has tons of features. It really make MS office look old, even XP. This is one of these nice suprises :-)
Bruce Hammond: We are planing to rename it somehow. I would love to get feedback from the community as to what the name should be
:) and for business users, call it PCD Productivity Suite.
gobeProductive...an obvious anagram is: Pivot Core Debug
Would be nice, but not gonna happen. There is a lot of code in the BeOS codebase that Be licenced from third parties- they cannot release that code to the public. Efforts like OpenBeOS are looking good though.
slashdot!=valid HTML
In a way, it's a little sad that open source fans can't all get behind one specific office suite. I mean, choice is good, but we also need to hammer in to the minds of office managers (via mantra) that StarOffice is "just as good as" and "a suitable replacement for" MS Office. There are many people doing just this, and there is finally a little bit of buzz in the non-techie world about StarOffice.
Gobe office will complicate this, because in many ways, it's as good as StarOffice (better at some things, worse at others). Techies who advocate a GPL office suite will no longer speak with a single voice, and managers who are contemplating a MS-software purge in their offices get scared because now they must undergo the agony of deciding which suite to train their staff on. This might make them more likely just to say "aw, forget it" and fork up the MS licensing fees. I mean, there will be flames all over the internet to the effect that "Now that GOBE is free, there is no point in maintaining OpenOffice anymore" and others that say "GOBE will die an ungraceful death because OpenOffice is just too far ahead." Managers will freak out and start worrying that the horse they pick will die mid-race, and then they'll have to retrain their staff again. Well, anyway, it's a thing to watch out for.
Having said that, I have a feeling I'll be a GOBE user real soon. I've played with it at a friend's house and I was pretty impressed by the performance.
Make perfect sense for more people to start looking at Linux as a desktop alternative (*gasp*). The recent news that we can't buy computers without an OS (welcome to the United States of Amerikka), leads me to belive that MS is starting to get scared.
Recent reviews of Gobe have shown it to be a good office suite, and one that understands native MS binary formats. I hope that the OS community can continue development and make it a real competitive force unlike mozilla. IMHO the non GPL browser OPERA is a much better product than the open source Mozilla, and I have no quams with paying for good software. I'd just like to see more world class software open source.
cluge
"Science is about ego as much as it is about discovery and truth " - I said it, so sue me.
One common complaint about free software development is the waste of effort reproducing functionality with different, distinct projects that rarely share code. Text editors, desktop environments, browsers, window managers....there are tons of each, ostensibly to fit individual's needs. Unfortunately, it seems to me that only a handful, probably two, actually end up with the majority of users in each category. Either vim or Emacs. GNOME or KDE. Konqueror or Mozilla. Windows managers...well there are more, but there are certainly a ton of window managers that got (half-)developed that hardly anyone uses. Why we didn't stop with twm, I'll never understand! ;^)
Now, we have OpenOffice, GNOME Office, KOffice, and eventually this project it seems. At least two of these, OpenOffice and the new Gobe guy, have some commercial push behind them. Not all of these can possibly pull in the full benefit that the GPL (or other free licenses...I seem to recall that OO might be a mixed license) would normally grant them as they try to draw from the community. That pool of potential eyeballs all checking source and potential fingers typing in patches and extra functionality...it's all going to be split up.
Heck, just look at the Mozilla project. It's been my impression that most code is getting done by the paid professionals and that Mozilla draws on the community primarily for bug testing and evangelism.
Anyway, this is all to say that two years ago I might have cheered a company with commercial backing buying up the source to a decent office suite and releasing it. (In fact, I was happy to have Sun take over StarOffice, and moreso when they freed the source.) But now this Free Radical could be just one more company that goes down the tubes basing their product on a GPLed source code. They can blame the community for not helping out and the cheap-ass users for not paying for the product that could be had for free. Other than that negative press, the net result will have been that resources (users, coding, testing, time) would have been diluted, being split up among this and the other projects, and those projects that did survive would be less well-developed as a result. Cooperation is needed to guarantee that GPL source that lives forever is actually useful source that lives forever. Modules that can be picked up and shared, like one that imports and exports MS DOC format files.
Not that it'll do any good for me to be a nattering naybob of negativity on this subject. Someone probably just filed a new window manager on freshmeat as I was typing this.
Curmudgeon Gamer: Not happy
Comment removed based on user account deletion
Hey, this is great stuff. A couple years ago, people were saying that Linux didn't stand a chance in business computing unless a good office productivity suite was available ... and now we have several in the pipeline, a couple of which are actually quite reasonable. Give 'em another year or two, and I think we'll have some solid cross platform products.
.. ?
...
So, I'm curious: Releasing GP under an open source license is certainly The Right Thing To Do, but what specific benefits might we get from it? Are office suites as layered as operating systems, with code on higher levels fairly portable, or are the only standards at the file format level?
Also, is it a "from scratch" rewrite of ClarisWorks, or might there be some sticky licensing issues with Apple popping up in the near future
Regardless, having different ways of doing the same things, so long as there's open and stable file formats, is always a good thing
After installing BEOS on my old quad cpu mac, I installed the no longer available version 2 of GOBE Productive on my machine see here for a snapshot here . This inspired me so much that I purchased the windows version and run it on windows 2000. I can honestly say that I no longer need any MS suite at home now, and that is a great thing. The ability to save as a PDF is a real bonus as well. The flexability of the "family license" (can install on all your home machines) is a real bonus to those of us that have many machines at home.
...and buy Microsoft Windows source code! I bet the GNU project can handle that.
:)
No wait, they said it's too dangerous for national security to publish it. Whops.
-- There are two kind of sysadmins: Paranoids and Losers. (adapted from D. Bach)
One of the TechNotes contained this;
Besides, as reported on AtAT recently, Clarus is very much alive and appears in MacOS X 10.2 - aka 'Jaguar'*moof!* :)
Alison
"It is a miracle that curiosity survives formal education." - Albert Einstein
Would be nice, but not gonna happen. There is a lot of code in the BeOS codebase that Be licenced from third parties- they cannot release that code to the public.
id Software's Doom and SciTech's Watcom C++ had the same problem of proprietary code licensed from third parties, but id solved the problem by releasing a crippled version (without sound) and Sybase plans to solve it by rewriting the third-party parts before releasing the code, but that's still taking a long time.
Will I retire or break 10K?
Unfortunately, Apple only pre-loads AppleWorks on their "consumer" Macs (iMac, eMac, and iBook), and not any of their Pro line (PowerMac G4 and PowerBook). AppleWorks would be a lot nicer if it was installed by default on every Mac - but then again that would hurt Microsoft's ability to sell Office.
Then again, that might not be such a bad thing, the way their relationship seems to be heading right now. Office is a nice package on the Mac, actually, but MS could use a good kick in the pants to inspire them to cut prices to the point where Apple users are more willing to buy it.
-- Josh Turiel
"2. Do not eat iPod Shuffle."
Some of the free word processing programs including Kword have their own Automation-like interface, but not using COM. Those allow scripting under Linux using CORBA or DCOP or whatever, but probably doesn't help your vertical app under Windows.
Based on my own goals of using a computer with 100% free software, I don't see much point in precisely emulating Word's Automation interface, since I don't want to run Windows or anyone's proprietary COM-dependent app. However, if the app simply launches Word and handles a few simple operations, it might be possible to put some COM wrapper around KWord that turns the COM calls into appropriate DCOP calls. If you really want something like that, I know people who might be able to do it for you, though not for free. However, if you only need a minimal interface to support your vertical app, it might be pretty simple to implement. It would certainly cost more than a single copy of Word, but might be worth it if you want to run it on 10's or 100's of machines.
Mozilla is licensed sort of similarly (the MPL gives Netscape special rights to the code) and it's not attracting so many volunteers either. I'm not real surprised. While the letter of the GPL doesn't prevent dual licensing, it's not really in the GPL spirit, which is that the original author of a piece of code doesn't have special rights that others don't have.
If I add features to an FSF GPL'd program, I'm doing volunteer work for the free software community and it makes me happy. If I add features to a BSD-licensed program, I become an unpaid employee of anyone who feels like forking the code--I don't find that so attractive. If I add features to Gobe Office, I possibly become an unpaid employee of just one company, Free Radical. Once again, life's too short for that.
I'm not a total free software zealot and I am willing to work on proprietary code. But when I do that, I expect to get paid, just as the vendor expects to get paid. So I'm not terribly impressed by these commercial dual licensed semi-GPL projects.
(Man, topic drift inside a single post! Forgive me.)
I mean, choice is good, but we also need to hammer in to the minds of office managers (via mantra) that StarOffice is "just as good as" and "a suitable replacement for" MS Office.
The only problem with this idea is that StarOffice-- as anybody who has actually tried to use it in a business setting knows-- isn't "just as good as" or "a suitable replacement for" MS Office.
Evangelizing about StarOffice-- or any of the open source office software products-- right now would do serious damage to the reputation of open source software. When serious business users look at an open source office suite, they're not going to say, "This software, while unfinished, has a lot of potential. I'm excited and intrigued!" Instead, they're going to say, "Those open source nuts clearly don't get it. I've tried their software, and found it wanting. I will ignore them from now on and stick with what works: good old Office XP."
Evangelizing a new product or technology too early can result in its failure rather than its adoption.
Arstechnica did a review of it a while back http://arstechnica.com/reviews/02q2/gobe/gobe-1.ht ml
In a way, it's a little sad that open source fans can't all get behind one specific office suite.
This attitude, that "There can be only one" is a sure fire recipe for making Open Source software suck as badly as closed source software. The competition between KDE and Gnome has been nothing but good for both sides. M$ succeeded in the first place by the desire that many people had 10 years ago for 1 OS, 1 Word Processor and so on. Well, we have it now, and only people with an MCSE like it.
The desire for a single Office Suite, Desktop System, etc. comes from the desire to "Beat Microsoft". We have one strength over M$ - They are a marketing machine, not a technology machine. If we try to beat them at their own game, we will lose. If we play our own game - Free software competing with ITSELF, then we will win. And we won't get stuck with software that was developed for its marketing value. The idea that we ought to all work together is rubbish; for all its ugliness the KDE vs. Gnome war made both sides better. And they will continue to get better because of the competition. The same chance exists with Office Suites. Don't tell me we ought to "work together" ; tell me why "yours" is great, and mine "sucks". "Mine" will be better for it. And so will "yours"
-- Recon
Free your mind and your Ass will follow -- George Clinton
A very salient point. I've been using OpenOffice on Windows and Linux since pre-1.0, and quite frankly it's not ready for primetime business use (tinkering, sure...where the hell do you think I'm writing this from?). There are some graphics bugs in their Excel-clone that, to me, would be show-stoppers if implemented in our busy office (column headers and recently-changed data simply disappear).
I think we should throw our support behind these open-source Office suites, but squarely behind the development. The deployment can wait, at least until I don't have to worry about getting fired for implementing software that hasn't been solidly debugged.
This wasn't just plain terrible, this was fancy terrible. This was terrible with raisins in it. - Dorothy Parker
You can get the 14-day demo of gobeProductive here. (Windows version.)
Comment removed based on user account deletion
Comment removed based on user account deletion
Comment removed based on user account deletion
Comment removed based on user account deletion
Comment removed based on user account deletion
It doesn't matter as long as they all can understand each other's formats.
This isn't a collection of APIs, it's an Office suite.
Comment removed based on user account deletion
Comment removed based on user account deletion
Comment removed based on user account deletion
Comment removed based on user account deletion
Comment removed based on user account deletion
I have written a few hokey papers and I ended up writeing them in vi/emacs then doing the formating on a mac in Quark
lets face it in terms of layout all these editors suck
if you just want to write something then emacs/vi get you there the main problem is makeing something that people who are used to MS word want to use
Open Office does a good job but it needs its Visaul Component Libs (VCL) sorted
this is what you have to hack in order to get native widgets like the aqua interface they had to hack the VCL for aqua so that the widgets would look right rather than just useing a Xlib solution
(that was what all the open Office on MacOS X was all about currently they just use the Xlib interface)
open office needs to convert VCL to aqua and GTK 2 as well as MFC to look right and appeal to the mass's
regards
John Jones
Comment removed based on user account deletion
Comment removed based on user account deletion
Comment removed based on user account deletion
Comment removed based on user account deletion
Comment removed based on user account deletion
People always tells me there "a number of office suites that run under Linux".
So I know there's openoffice, there's siag office, and some not-so-complete suites like "gnome office", or single-application thingies such as abiword.
So, exactly how many of the "complete suites" out there that runs under Linux ?
And if anyone is reading this so far, what's the other "office-related" applications that you know of, that may be not as famous as abiword or gnumerics, but still worth to be mentioned ?
Thanks for any and all your inputs.
Muchas Gracias, Señor Edward Snowden !
I wrote a review of Productive 3 for my Web site a while back... Check it out at msboycott.com/thealt/reviews/gobeproductive.shtml.
This is great news for everyone because gobeProductive is slim and trim - it is to office suites what Opera is to Web browsers.
== Paul Rickard, Editor of The Microsoft Boycott Campaign ====
How so? I'm working with a small company right now that's already committed to switching all new computer users to Star Office. They are open to desktop Linux on some desktops as well. This is a technical company, and the CEO (PhD. physicist) was quite impressed when he imported a Word document and all the formulas came through flawlessly.
They figure they'll have one workstation with Office for document export, when HTML or PDF isn't sufficient.
Microsoft pricing has finally gotten far enough out of sync with small business budgets, that I think you'll see quite a few switching. Sun made a smart move charging a nominal price, now businesses are starting to see Star Office as a serious product.
Galileo: "The Earth revolves around the Sun!"
Score: -1 100% Flamebait
I think I need to have been more explicit in my points.
No one outside of Free Radical will blame the license and freeness of the software, with the possible exception of non-free promoters. The company, however, may well feel a ripe case of sour grapes at failing to get the kind of support they expected from the free software community.
An executive trying to explain the failures of his company may grab at an easy scapegoat, and I think that the free software mode/community are easy to blame because the benefits are often somewhat intangible and difficult to explain to normals.
Will the community be upset that there is more code there? No. Will Free Radical probably benefit from the open development model? Maybe. Will they be quick to blame someone else if/when they fail? Damn right, and GNU is first in line for that fall.
People can develop different window managers all they want. For window managers, that works for the community. For the demand in the workplace, there will probably be only two options: KDE & GNOME. All others, like Flowe, are probably not going to go anywhere and won't be taken up by the community. The same will be true here, but office suites are much more high-profile that desktops and if a big project sinks, because of the effects of having multiple efforts, then it can have fallout.
For the last time: I'm not telling anyone what to do. I am, however, saying that if people choose to follow these paths they've staked out (multiple, disparate office suites) then there will be consequences and some of them may be bad for the community itself. If you decide to take that as "Hey, bud, stop doing what you're doing!" then so be it.
Curmudgeon Gamer: Not happy
We also need an open format for editable drawings. Flash, maybe?
The first time Bill Gates tried a web browser, his memo noted "I was was on for three hours and didn't see a single Microsoft file format." He's fixed that "problem". The open source community hasn't pushed back hard enough on that issue.
Now, of course, I'm not really a big fan of "office suites" when it comes to word processing and the like (go LaTeX!!), but it's great to see more and more companies using GPL'ed code as a tool against M$ monopoly oppression. Overall, OpenOffice has been very disappointing thus far. It's buggy, it's slow, it's bloated, it uses its own widget library, and the code is spaghetti at it's best. Maybe the OpenOffice team will 'pull a mozilla' a couple years from now, but that seems a ways off. Parts of the 'Gnome Office' collection are great tools, but are also rather disjointed and have terribly buggy import/export filters it seems. KOffice 1.2 is slick, efficient, and very promising, but needs more developers. (it's my long term bet, actually) Now along comes (formerly-Gobe) Productive. By the looks of it, Productive won't become a 'competitor' to the other open projects for some time, but at least we'll have more code base to draw on. Perhaps it should be merged with the now-fragmented Gnome Office (and get rid of the uselessly anorexic AbiWord that doesn't even support tables). Perhaps the code contains some insight on making better import filters for M$ office formats. Perhaps we can agree on a standard XML format for vector graphics too. And of course, that's the biggest issue in all of this -- standardization. We need ONE file format that all Open Source office tools can use seemlessly.. a format that is feature-extensible, straight-forward, and consistant. And we need to agree on a single name for this format so that it can become recognized and comfortable, just as most non-clued business people now say "send me a Word document" or the like.
How would this be any better than the monolithic bloat we now know as M$ office? I don't think there's anything wrong with having 12 different office packages to choose from - what sucks is when they each have their own format, and can't share information easily with other packages. What would be quite awesome is if these applications became mere interfaces to the data itself. This way, it wouldn't matter which app you used- any document you create would be compatible with any of the apps that handle that kind of document.
It depends on what your needs are. Test it thoroughly with what you actually do. Don't expect that features that you haven't checked will work in the current release. (Many will, but there are some that don't, and some that "sort of work".)
I would recommend running a few systems in duplicate for a week or so before beginning a real switch. It's a real nuisance, but often if you catch a bug at that point you can either fix it or work around it, but after deployment it would just be a killer, and leave everyone with a really bad taste in their mouth. (First impressions are very important. People who know that they are testers are willing to be a bit more forgiving than those who expect that this is the for-real version.)
I think we've pushed this "anyone can grow up to be president" thing too far.
This isn't clear. The number of Linux users has been increasing rapidly, and many of them are programmers. The acutal teams of developers are pretty small, we may talk about thousands of developers, but that's not actual practice. There may be thousands of debuggers, and people who make suggestions, but not too many developers.
The truth is, we don't know what the right number of project is. We only know that it's larger than one. Two is a definite improvement. If the projects can swap code with each other, then I suspect that the idea number is over ten. Unfortunately, what I have heard about the Gobe license implies that the Gobe code won't be freely swappable (I heard that Free Radical has special rights above and beyond the GPL permitted), so probably the Gobe project won't be able to accept code from the other projects. This limits their viability, but as they are one of the first four, perhaps not fatally. When you want to diversify in a crowded area, you specialize. Somebody will come up with a word processor that's like one of the other project, except that it specializes in being a Mozilla plug-in. And it uses Mozilla to do the page layout and printing. (You can sort of do that with anything that generates html, but I bet there's a better way.) And since it's "parasitic" on Mozilla, it can quickly port to any platform that runs mozilla. (Mozilla handles all the system specific stuff.)
OK. That's one word processor specialty that no one's addressed yet. I bet you there are other reasonable ideas just waiting to be developed.
I think we've pushed this "anyone can grow up to be president" thing too far.
I agree that an automation interface is important. AbiWord doesn't currently have anything, but automation is planned. They will expose stuff via CORBA, which should be great in a GNOME environment.
They also will do something with scripting. I'm not sure what, because I haven't found a recent discussion of that; if you do a google search, you will find dozens of messages two years old or older, from flame wars on what is the best way to do scripting. (Some guys want Perl, some guys want Python, some guys want a free clone of Visual Basic, and no doubt there are LISP fanatics out there who want SCHEME. And so on.)
You must admit that automation isn't a requirement for the vast majority of word processor users; it made sense for the AbiWord developers to focus on core features, and add automation later. I assume that since they knew they would be automating later, they didn't make any stupid designs that will be hard to automate. At least I hope so.
steveha
lf(1): it's like ls(1) but sorts filenames by extension, tersely
Huh? How do you figure this?
I don't see that happenning.
Comment removed based on user account deletion
Comment removed based on user account deletion
Comment removed based on user account deletion
Comment removed based on user account deletion
Comment removed based on user account deletion
I don't think of having two alternatives in GNOME and KDE as having a "choice" but rather as a fork in the operating system platform.
As for me, I've made a few small bugfixes to Apache and sent them in, since I'd done them already anyway. I wrote a larger extension for Apache because someone hired me to do it, but I wouldn't have done it for free. If Apache was GPL'd, I might have done it for free.