FinalWriter bounty?

[Megamig]

I would pay for the source for

InterWord (by far the best text word processor for the Amiga IMHO)
KindWords 3

I always felt that Wordsworth and FinalWriter were too bloated (slow) on standard Amigas.

[Iggy]

Ugh, you guys are too focused  on the past.
 
That's why I'm siding with Fraggle on MorphZone.
 
A clean approach and a new product.
Why would you want to use something this old?
 
BTW - It still runs under MorphOS if you're into pain.
Me, myself - I just use Goggle Docs.

[runequester]

Ugh, you guys are too focused  on the past.
 
That's why I'm siding with Fraggle on MorphZone.
 
A clean approach and a new product.
Why would you want to use something this old?
 
BTW - It still runs under MorphOS if you're into pain.
Me, myself - I just use Goggle Docs.

I can't get google docs to cooperate with loading an odt file from my computer. Any suggestions?

[Iggy]

I can't get google docs to cooperate with loading an odt file from my computer. Any suggestions?

Wow! That's still a problem?
The first time I heard the complaint was about three years ago when they screwed up that capability (it had worked prior to that).
Personally, I do a lot of work with PDFs and they upload fine.
 
I'll take a look into it.
They should have had this one solved a while ago.

[Flipflop]

I would pay for the source for

InterWord (by far the best text word processor for the Amiga IMHO)
KindWords 3

I always felt that Wordsworth and FinalWriter were too bloated (slow) on standard Amigas.

Just for your info: Kindwords3 is the same as an very old version of WordWorth...
In other words, you wont get anything!

To me, Interword seems to be very ugly, and by now it was impossible to reach the
original authors...

Developing a real world Amiga program skeleton and include the stuff from e.g. AbiWord
would be IMHO the best solution. Of course it have to be open sourced from the
beginning...

[whabang]

Bah, wouldn't it be easier to get the Abiword port up to date?

[utri007]

Amiga way to solve problem with doc/docx file types would be build filetype that would support them.

We don't need a whole program, but support for file type would be essential.

[Iggy]

So we're down to
 
a)support a new program...or
 
b)update or port something thats either going to be costly or time consuming (which inthat case,OO has my support).
 
basically we've reached the same point that the guys on MorphZone did

[pampers]

I can't get google docs to cooperate with loading an odt file from my computer. Any suggestions?

Yeah, blame Fab

[desiv]

Why would you want to use something this old?.

Funny quote considering this is an Amiga forum.  ;-)

I'd say, it depends on whether or not it works well.
If it works well and we only need to tweak file formats, then it should still be fine, even tho it's "this old."

desiv

[Iggy]

Funny quote considering this is an Amiga forum. ;-)
 
I'd say, it depends on whether or not it works well.
If it works well and we only need to tweak file formats, then it should still be fine, even tho it's "this old."
 
desiv

Not a bad point.
 
But to the best of my knowledge, we were discussing software for NG machines.
 
But, since word processing doesn't require that much horsepower, I don't see why these same packages couldn't run under AOS3.X or AROS68K.

[Rob]

Ugh, you guys are too focused  on the past.
 
That's why I'm siding with Fraggle on MorphZone.
 
A clean approach and a new product.
Why would you want to use something this old?
 
BTW - It still runs under MorphOS if you're into pain.
Me, myself - I just use Goggle Docs.

There's already Claus Desler's Cinnamon Writer.  The project started life on OS4 but there is already an  AROS build, not sure about MorphOS yet but the intention is to have it working on all 3.  Any money might be better spent supporting that initiative.

http://desler.be/modules/wfchannel/

[desiv]

Yeah, I suppose what I was getting at was that I think the codebase for the older WP programs might be just about fine, if the basic feature set is still good.

Trying to add compatibility for modern formats might (??) to an older codebase might be easier than trying to port more modern (and bloated IMHO) programs...

desiv
I had a friend who always swore that Word for the Mac (version 4 maybe?) was the best word processor ever, and that it's been mostly bloat from there on.. ;-)

[pVC]

Trying to add compatibility for modern formats might (??) to an older codebase might be easier than trying to port more modern (and bloated IMHO) programs...

If we want compatibility with modern formats it might be a massive project with eternal bug fixing with the old programs which weren't designed for that in the first place. Stretching old programs with patch over patch doesn't sound very good option in my opinion. Especially with the amount of coders we'd have for those kinds of projects... they probably lost their interest even before it gets anywhere near the specs of the modern programs.

I think it would be better to port some modern software, even if it's a big job at first. But if the port gets made, then it already has pretty good compatibility with modern formats and maybe applying the new changes would be easier in future.

[Iggy]

There's already Claus Desler's Cinnamon Writer. The project started life on OS4 but there is already an AROS build, not sure about MorphOS yet but the intention is to have it working on all 3. Any money might be better spent supporting that initiative.
 
http://desler.be/modules/wfchannel/

Yeah, Claus is working on the port right now.
And Fraggle has commited to buying Claus a Mac Mini to run MorphOS on.
 
So hopefully, one day, we'll have a word processor that works across all the NG OS'.

[desiv]

If we want compatibility with modern formats it might be a massive project with eternal bug fixing with the old programs

Yes, it might..
Or it might not...  I only mean it is worth considering the options..

they probably lost their interest even before it gets anywhere near the specs of the modern programs.

And that is one of my points..
Are we doing this for what we need?  Or are we doing this to reach the "specs of the modern programs"?  Those might be very different things...

I think it would be better to port some modern software, even if it's a big job at first. But if the port gets made, then it already has pretty good compatibility with modern formats and maybe applying the new changes would be easier in future.

I think sometimes, this is true...
But other times, people end up adding/chasing features that virtually no one will use..  
If you watch the amount of changes that go into things like Open/Libre/{whatever it's called now}Office just trying to "catch" the current products with features I think most people will never use, I think THAT is a HUGE amount of work.

Now true, if you port the development libs over, so you can just use the same codebase with virtually no changes, then you can use the work of others..  Great.
But if you have to keep re-porting major parts whenever an update comes out, it might not be worth it..

And I've always been a fan of native code for native OS/hardware for speed and simplicity...

desiv