Speed issues introduced when we started doing math in dot commands has been resolved.
Color (The basic Wordstar 16 colors) is now supported.
The main reason for this release is to fix a crashing bug when saving/autosaving a new document with no name. See Sourceforge tickets #7 and #8 for details.
This release also does proper font changes when saving to an RTF file.
Headers and Footers now implemented. Set them up, and ^OP to see the end result and print them
A minor bug fixed with printing and .rm, and ^KP is still not done (use ^OP)
I think what I’ll work on next is RTF export, to get it to support all the work done recently and make it easier to extend. Finally getting the Mac/OSX port back into a working state would be great as well.
Another big step for the project. We can now print. Imagine that, a word processor that prints!
Due to a bit of a brain fart, I only implement ^OP (print preview) and forgot ^KP (print). It’ll be in the next release. Both will do the exact same thing anyway. There are also a few squiggly corner cases I may have missed with printing, but I’ll catch them next time.
I also changed the main window display a bit, there’s a progress meter in the status bar when formatting the document, and the bold/italic/etc indicators look a bit different.
That’s it. No bug fixes
I’ll do something new here as well, and tell you what I’m working on next. Because I need it, headers and footers will be implemented next.
This release is a big step for the project. We’ve moved from an in-house Mercurial repo to Sourceforge, so now anyone can look at the code. It’s a bit sloppy in parts. Other changes are:
The addition of math in dot commands means you can do simple things like .rm 8.5-1-1i to set the right margin to 6.5 inches. The math system will also do complex math like 2 * (pi / 4.7) + sqrt(7), but why would you want to?
One bug fix (not really a bug, but…) and a handful of new features like codepage 437 support (partial). Also a new feature not found in the original Wordstar! Check the forum for more information.
A handful of bug fixes surrounding the .pm command and the addition of tabs setting via .tb. See the forum for details.
Besides a few bug fixes, this adds the .pm command and adds proper incremmental changes to .lm and .rm. For example, .lm.25″ will create a left margin of .25″. A .lm+.25″ will add .25″ to the current left margin while .lm-.25″ will subtract .25″ from the left margin.
0.1.73.18 released to fix a huge CPU hogging bug. Sorry.
This release (a long time coming) is an almost complete refactor of the original WordTsar. Many speed increases, and it should be easier to add functionality.
I’m starting to use this version for my daily work, but beware, monsters may lurk in the corners.
For now, please use the forum to report bugs. I’m working on a public bug tracker.
I’ve been using Alpha 0.0.51.2014-10-07 for the last few years on both Linux (very stable), and OSX (somewhat stable). I wrote three novels using that software (http://geraldbrandt.com) and got them published by one of the Big 5. It was software that worked, but had its flaws. For example, when starting a new document, you needed to insert a pages worth of blank lines, go back to the top of the document, and start typing. That kept it stable. Unfortunately, the software had also reached its limits. Adding new features would have been a major pain.
So, I did what any developer would do… I refactored the darn thing. I’m seeing speed increases of 200% – 2000%, depending on what I’m doing. Fonts work a bit bettter. RTF import has a bug with font tables, but kinda works. Battery usage on laptops is great. Memory usage is a bit higher.
I currently have version Alpha 0.1.73.0 running on Windows 10 and Ubuntu 17.10 and 18.04 (GTK2 and GTK3). I’ll be getting OSX running over the next couple of weeks. I believe 0.1.73.0 has feature parity with 0.0.51, but I’ll have to double check. I’m working on stability now — along with the OSX port.
For a project that’s been basically dead for the last three years, this is a positive step. Keep watching, it’ll be up in binary format soon. Source code to follow (it may take awhile… I’d love to have a finished product before I release source. Who knows).
