Haha, blame the design people. Apparently they really care about how a tittle piece of text looks:) I'll kill the flash off as soon as possible, but we were on a deadline.
What would be even better, is that we offer a self-hosted version. In an ideal world, I'd open source all of abicollab.net right now, but we need to have an business plan discussion first before we decide to do that:)
RTLinuxFree does this. The default scheduler is kinda lame (at least last time I hacked on it), but you can for example replace them with my DMI and EDFI schedulers to get all the fancy features you describe, and more.
AbiWord does hardly depend on GNOME. We have only 1 dependency with GNOME in the name, and that is libgnomeprint (libgnomeprint only depends on gnomecanvas, which in turn depends on nothing GNOMEy).
And this ofcourse only holds for the Linux version, not for our native Windows version for example.
Where did you find XML in my comment? Crossmark is NOT XML. Also, this is I think the first time in history AbiWord is blamed of having bloatness, thanks!:-P
Get AbiWord CVS HEAD (see http://www.abisource.com/developers/), and compile with --enable-libabiword. The get the abiword python bindings from our CVS as well (module pyabiword). Compile and install those as well. Finally, in the pythons module, there is an example directory. Look at that. As for the OLPC AbiWord activity, it is in OLPC's git repository: http://dev.laptop.org/git.do?p=projects/abiword-ol pc;a=summary
AbiWord. We have kicked abiword into a library, with the GUI stripped off. This allows one to build a GUI on top of it in python, like the rest of Sugar is. Seamless integration. This will be the writing Activity the children will use. Then we are working on special import/export filters for abiword to read/write the 'fileformat' of choice of sugar: crossmark. This will allow perfect integration with the Journal. Neat trick is that you can even embed abiword in mozilla to do inline editting.
Also, a collaboration plugin for abiword is being worked on, that will use the mesh infrastructure and sugar presence framework to find and communicate with other users. This will allow realtime collaboration on documents (for example, 2 or more children working on an assingment simultaneously).
So there you have an application that takes full use of the offered platform.
Code is already shared where possible. Take for example the WordPerfect importer. It originally was AbiWord's importer. When it became better and better, we split it off into the libwpd library. These days libwpd is used by AbiWord (naturally), OpenOffice and even KOffice.
AbiWord on *nix uses Gtk2, wv, libpng, libxml2, zlib, fribidi popt, and libiconv. All of which are available in all new distro's, except maybe for wv. If you use the GNOME version, it uses several GNOME libraries as well, such as libgnomeprint.
The Windows version uses the same libraries, except for of course the Gtk2/GNOME libraries, since we use the Windows native widgets and print systems on every platform. Same holds for the native MacOSX version.
Since I saw AbiWord already in the 3rd screenshot, I figured there might be some interest left for an AbiWord 2.x port for BeOS as well. If anyone is interested in such a port, he/she should stand up now and contact the AbiWord Developers Mailing List. If we find no active BeOS developers within the next 2 weeks, we'll drop the currently unmaintained and outdated BeOS port from our tree.
Slashdot Mirror
We are working on making a downloadable "server component" available. Until we do, you'll indeed have to trust us to keep our servers online.
All the technicalities are ofcourse hidden for the normal user. You just click "open" on the webpage, edit the document, and press save.
Haha, blame the design people. Apparently they really care about how a tittle piece of text looks :) I'll kill the flash off as soon as possible, but we were on a deadline.
Creating a new document creates... well.. an empty blank document! You can edit it with abiword, and then after a save it is non-blank :)
No, MS Word does now allow collaborative editing of Word documents (they do for spreadsheets and presentations).
Yes. for sure in a commercial form. If I were the only one to decide, I'd open source all of it right now, but we'll see how that turns out.
What would be even better, is that we offer a self-hosted version. In an ideal world, I'd open source all of abicollab.net right now, but we need to have an business plan discussion first before we decide to do that :)
RTLinuxFree does this. The default scheduler is kinda lame (at least last time I hacked on it), but you can for example replace them with my DMI and EDFI schedulers to get all the fancy features you describe, and more.
AbiWord does hardly depend on GNOME. We have only 1 dependency with GNOME in the name, and that is libgnomeprint (libgnomeprint only depends on gnomecanvas, which in turn depends on nothing GNOMEy).
And this ofcourse only holds for the Linux version, not for our native Windows version for example.
Where did you find XML in my comment? Crossmark is NOT XML. Also, this is I think the first time in history AbiWord is blamed of having bloatness, thanks! :-P
Get AbiWord CVS HEAD (see http://www.abisource.com/developers/), and compile with --enable-libabiword. The get the abiword python bindings from our CVS as well (module pyabiword). Compile and install those as well. Finally, in the pythons module, there is an example directory. Look at that. As for the OLPC AbiWord activity, it is in OLPC's git repository: http://dev.laptop.org/git.do?p=projects/abiword-ol pc;a=summary
AbiWord. We have kicked abiword into a library, with the GUI stripped off. This allows one to build a GUI on top of it in python, like the rest of Sugar is. Seamless integration. This will be the writing Activity the children will use. Then we are working on special import/export filters for abiword to read/write the 'fileformat' of choice of sugar: crossmark. This will allow perfect integration with the Journal. Neat trick is that you can even embed abiword in mozilla to do inline editting.
Also, a collaboration plugin for abiword is being worked on, that will use the mesh infrastructure and sugar presence framework to find and communicate with other users. This will allow realtime collaboration on documents (for example, 2 or more children working on an assingment simultaneously).
So there you have an application that takes full use of the offered platform.
Shameless plug: works fine in AbiWord :)
I don't believe this crap. Name the packages so we can verify your claims (disclaimer: i'm a FC Extras maintainer)
Fedora doesn't have minor numbers, so there is no FC4.1 or 4.2.
Code is already shared where possible. Take for example the WordPerfect importer. It originally was AbiWord's importer. When it became better and better, we split it off into the libwpd library. These days libwpd is used by AbiWord (naturally), OpenOffice and even KOffice.
correction: atm we don't plan to make ODT the default file format. Nokia however is working on improving our support for the format.
You can of course make it the default file format by tweaking your AbiWord profile.
The one thing the board does NOT, is setting the technical direction for GNOME.
AbiWord on *nix uses Gtk2, wv, libpng, libxml2, zlib, fribidi popt, and libiconv. All of which are available in all new distro's, except maybe for wv. If you use the GNOME version, it uses several GNOME libraries as well, such as libgnomeprint.
The Windows version uses the same libraries, except for of course the Gtk2/GNOME libraries, since we use the Windows native widgets and print systems on every platform. Same holds for the native MacOSX version.
Watch the progress of our Native AbiWord Mac OS X port (cocoa)
He submitted one or two patches (which were comitted), and then vanished...
Since I saw AbiWord already in the 3rd screenshot, I figured there might be some interest left for an AbiWord 2.x port for BeOS as well. If anyone is interested in such a port, he/she should stand up now and contact the AbiWord Developers Mailing List. If we find no active BeOS developers within the next 2 weeks, we'll drop the currently unmaintained and outdated BeOS port from our tree.