Lists or Outlines
Posted: 2007-03-27 16:14:09
I have been following the various mac wps out there for a few years as we struggle to find an effective replacement for our workhorse of the past decade: AppleWorks.
We have very specific and niche word processing needs. We write plenty of general correspondence and various kinds of reports and all the wps that we have tested work fine with these. Our problem documents are architectural specifications. These are highly structured "outlined" documents. A single spec might have 30 or so individual sections, each one a different file.
So, what is the problem? For years we used AppleWorks. With whatever limitations it had it came with a unique feature: an outline style. The difference between this outline style and the common list style is that the outline style was independent of any paragraph style. In fact you could use an outline style to structure any document without ever using bullets or numbers. It worked differently than word's outline mode as well.
The beauty of it was that highly structured documents like these specifications were a snap to format and keep ordered. If you changed the level of an item it already had all the paragraph info assigned - no need to keep track of two different styles for each level. You could also change the look of all 30 sections by quickly importing a new outline style definition (although they broke this in v6 and never fixed it). We also used outline styles for structuring reports and field reports.
Right now we struggle along with Pages. Pages' implementation of outlines is so broken it makes me ill. Mellel is just geared elsewhere. NeoOffice is the same as Pages and Nisus - you need to have a list style backed up with a paragraph style.
It is hard to believe that as we march down the path of software progress the best word processing offerings we have still don't even match up with lowly AppleWorks, much less the legends of the past like Word Perfect, Full Write Pro, Write Now, and Mac Write Pro. We make progress in some areas but lose functionality elsewhere. Not just functionality, but even the basic know-how.
I like Nisus. Compared to Pages it is extremely nimble and I like the feel of the application. There is one killer feature that has kept Pages in our office and that is the templating system. The placeholder text is great when you are trying to have 14 people create documents that all look like they come from the same office. Even with the templating system I would switch us over to Nisus in a heartbeat if I could get a list style to behave like AW's outline style. It would make my day to even have someone know what I was talking about as when I discussed this feature at MacWorld with a Pages developer on the floor I got an extremely blank look.
This is a plea to Nisus disguised as a rant, BTW.
We have very specific and niche word processing needs. We write plenty of general correspondence and various kinds of reports and all the wps that we have tested work fine with these. Our problem documents are architectural specifications. These are highly structured "outlined" documents. A single spec might have 30 or so individual sections, each one a different file.
So, what is the problem? For years we used AppleWorks. With whatever limitations it had it came with a unique feature: an outline style. The difference between this outline style and the common list style is that the outline style was independent of any paragraph style. In fact you could use an outline style to structure any document without ever using bullets or numbers. It worked differently than word's outline mode as well.
The beauty of it was that highly structured documents like these specifications were a snap to format and keep ordered. If you changed the level of an item it already had all the paragraph info assigned - no need to keep track of two different styles for each level. You could also change the look of all 30 sections by quickly importing a new outline style definition (although they broke this in v6 and never fixed it). We also used outline styles for structuring reports and field reports.
Right now we struggle along with Pages. Pages' implementation of outlines is so broken it makes me ill. Mellel is just geared elsewhere. NeoOffice is the same as Pages and Nisus - you need to have a list style backed up with a paragraph style.
It is hard to believe that as we march down the path of software progress the best word processing offerings we have still don't even match up with lowly AppleWorks, much less the legends of the past like Word Perfect, Full Write Pro, Write Now, and Mac Write Pro. We make progress in some areas but lose functionality elsewhere. Not just functionality, but even the basic know-how.
I like Nisus. Compared to Pages it is extremely nimble and I like the feel of the application. There is one killer feature that has kept Pages in our office and that is the templating system. The placeholder text is great when you are trying to have 14 people create documents that all look like they come from the same office. Even with the templating system I would switch us over to Nisus in a heartbeat if I could get a list style to behave like AW's outline style. It would make my day to even have someone know what I was talking about as when I discussed this feature at MacWorld with a Pages developer on the floor I got an extremely blank look.
This is a plea to Nisus disguised as a rant, BTW.