Hei Bob

Robert B. Waltz wrote:
On 9/8/05, Martin Edelson wrote:
In fairness we need to remember that NWE is not intended as a
replacement for Nisus Writer. It is a small application (getting
larger!) designed for simple tasks. Let's not ask too much of it.

This is no answer. If NisusWriter the Real Thing existed, it would
be an answer, but NisusWriter the Real Thing *doesn't exist*, and
now there is reason to think it soon won't work in Classic.

Of Course NisusWriter Express is 'the real thing' as you call it. But what *you* demand is a full-featured and ever ready 'most-advanced' text processor at once... - This 'demand' is a non sense demand. _any_ program has begon somewhere - even your 'real thing' Nisus Writer. Even this has had a ver. 1.0...

I have been a NisusWriter user since ver. 3.3, and what has happened from that version to the latest ver. 6.5.1 is as much as from a NWE beta 0.1 to the NWE 2.5, - or if you pr3fer it this way - as far as Word 2.0 is from Word 11, - that far is NW 3.3 from the NW 6.5.1!

The most disturbing thing about Charles Jolley leaving Nisus Software
is that this is *his software*, and he's leaving it behind. So the
old NisusWriter Classic code is dead, and the chief author of NWE is
gone, too.

Oh stop this monkey talk Bob! - Charles has developed the Okoto Composer and the two companies fusioned to one. Nisus Software got Charles as well as his program, and Charles has been one of the leading in that developing project of NisusWriter Express. Some parts of Composer is part of NWE, but just as much isn't!

Charles has gotten NisusWriter 'on the rails' at the time, wehre we were beginning to think that the Nisus team were about giving up on a brand new program. - I think at that time many of us wished that the Nisus team would just carbonize the NisusWriter 6.5.1, - which I also meandt and partially still mean. - With such a carbonized ver. of the 6.5.1, we would have had a full-featured text processor at hand. But I also now know that this would have given many problems with such a carbonizing.

And if you are that keen on having a finished and full-featured program, why don't you then carbonize it yourself?!

The problem is, the NisusWriter user base has always had an impossibly
long wish list. But the people who *care* about NisusWriter are the
ones who were happy with the old version. And, for the most part,
they haven't gotten what they wanted.

For heaven's sake! Bob! - If you are that much to the classic Nisus Writer, - why do you then at all switch to Mac OS X? - If you don't know it, then I can tell you that when the day of the Apple switching to the Intel processors, then it will be impossible to even install, load and use a classic Mac OS 9.x version! - When that day arrives you'll be forced to either to stay way back or switch to the newest software, - then the Nisus Writer is totally useless - and only the NisusWriter Express will be there.

Se come up with our wishes, wants, needs and demands, but as I wrote in my answer to Martin, - we come with these, but it is the team that decides how many that will be implemented in which version and when this will be so.

In my best opinion - If it hasn't been for Charles and us - the users, - then I think that the NisusWriter Express still would have been somewhre in a ver. 1.x. And as the software market is right now, this would probably also have been the death of the company. The market is hard, and the wars between the different companies are just as hard. With a company like Nisus Software and other smaller ones, the the big 'monster' will still have someone to bite the heals.

And what Nisus Software do, I have never seen in any company. Can you name any company that directly asks the users to participate in the development process by asking for our wishes and needs? I have been involved in many projects through the years now, but I have never seen any company that has worked so close together with the users of the product developed.

I do think the Nisus Software folks need a rest; that incredible cycle
of late betas means that they were doing all-nighters to squash
last-minute bugs. (I've *been* there.) If they don't take a break,
it will probably make it harder, not easier, for them to get the
next release out. But they really do need to think about where the
program is going.

Of course they need a break. But such a break must not be too long. As I see it, the team has been in a good rool the last months, and the 2.5 is the result of this. But I also still think that they'll need us - the users - to 'keep them to the fire' as we say here. This we can do by our wants and wishes, but it is still the team that decides how to, when and why this or that feature to come before that or this.

To get and to give good ideas can also be what'll give the team the curage and strength to continue the real good work. I think that you also could say it so, - that Charles has 'educated' the team to stand on their own feet now. And if we can still feed this team with ideas, this can be the 'bread' that can keep their strength and also the will to continue this good work.

"A man has to eat bread, not to be weak" - We must do so by supporting the team. This we don't do by saying "Ah, mi lads, sit down and rest now, you've already done what to do"... No, we shall encurage them by saying "Take a break and get your strength back, 'tomorrwo' the next step begins..."

- Charles, Mark, Dave, Martin, Jerzy and all the rest of you - You have done a real great job until now! And a big, big wish that the next step will be just as successful!

Cheers, Erik Richard

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
K.M.L. Denmark by Erik Richard S¿rensen, Member of ADC
<[EMAIL PROTECTED]>
*Music Recording, Editing & Publishing - Also Smaller Quantities
*Software - For Theological Education - And For Physically Impaired
*Nisus - The Future In Text & Mail Processing <http://www.nisus.com>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

_______________________________________________
Nisus-interactive-nisus.com mailing list
[email protected]
http://lists.nisus.com/listinfo.cgi/nisus-interactive-nisus.com

Reply via email to