WordTsar A Wordstar clone

Time 2020-12-18 01:04:48

Web Name: WordTsar A Wordstar clone

WebSite: http://wordtsar.ca

ID:137579

Keywords:

WordTsar,Wordstar,clone,

Description:

I ve used and am using this version extensively on Windows and Linix. There has been minimal testing under MacOS.Fixed Ticket 18 (MacOS)Fixed Ticket 17 (MacOS)Fixed Ticket 15 (MacOS)Fixed Ticket 16Added full justification of text .ojon^KP not implemented, use ^OP.pt command can only be used once per documentSee Ticket System at SourceforgeI ve been developing various pieces of software in wxWidgets (back when it was called wxWindows!) for a long time. But recently, I ve made the switch to Qt.WordTsar under wxWidgets was stable, and I used it to write quite a few novels (http://geraldbrandt.com), so why the switch? Well, it seems that I always had to do something just a little different based on what platform the software was running on. Don t get me wrong, 99.9% of the code was cross platform and worked well, but there always seemed to be corner cases.The last straw for me was when I tried to get WordTsar running under MacOS. I tweaked here and there. Keyboard input was a pain, but then it was under Qt as well. It was just easier under Qt because I d already fixed the issue under wxWidgets. So, what was it that I couldn t get working?I use timers to update WordTsar s status bar, do word counting, and flash the carat. None of it worked under MacOS. Again, I tweaked here and tweaked there, but I just couldn t get timers to work. Really, timers are a pretty basic function. They should Just Work.About two years back, I did a test port to Qt to help me find an elusive bug. I moved over just enough code to help track down the bug, and stopped. This time around, I didn t.WordTsar is now 100% Qt based, with all the functionality of version 0.1 Release 1977. Well, almost. The Linux version of WordTsar had spell check working, using Hunspell. Non of the other ports did. I ve decided to leave spell check out since I want to do it in a more cross-platform way.What differences will you see with the Qt port? Some of the dialogs look different. Yup, that s pretty much it.The Qt version is SIGNIFICANTLY faster than the wxWidgets version. Why? Two things in particular:Measuring of text under Qt just flies. Under Linux, measuring the widths of 605,814 characters took roughly 1800 ms. With the code optimized to measure strings instead of characters, I got that down to 460 ms. Under Qt, which can only measure individual character widths* the speed is 138 ms. That is a massive speed improvement.QString vs wxString is the second big increase. I do a lot of parsing of strings using .Mid(), .BeforeFirst(), .Left(), etc. I do no in string indexing (i.e. string[x]). Parsing WordTsar dot commands (string heavy) on a 111,000 word novel took 1060 ms under wxWidgets. With Qt, that process took 348 ms. I was planning to optimize the dot command routines to speed things up, and I still will (via some form of caching), but I can postpone that work now.What this all comes out to, is under wxWidgets, laying out a 111,000 word document took 1670 ms. Not bad, really. Under Qt, the same process takes 576 ms. That s a very noticeable difference.I ll be testing the Qt version over the next week by editing a 92,000 word novel and bringing that up to 100,000 words or so. Not a bad stress test. If all works out, there will be a WordTsar 0.2 Release xxxx happening next week for Linux, Windows, and MacOS.* wxWidgets has GetPartialTextExtents() which, when passed in a string, will return an array of character widths. Qt has no such function. You can get the width of an entire string, but not the characters in that string. So, with Qt, I must measure each character.Added RTF export for subscript, superscript, and strikethroughAdded RTF export of columnsChanged RTF right margin to use /ri and not /margrAdded RTF export headers and footersAdded RTF export save hyphenationAdded RTF export margin settingsAdded RTF export of indexesAdded RTF export of kerning on or offAdded RTF export save top, bottom, and paragraph marginsAdded RTF export save page offset ((for odd and even pages, we use .poo to set RTF gutter (RTF only allows one setting))Added RTF export save tabsAdded RTF paragraph alignmentCorrected Wordstar .mb usageFixed Windows scrollwheel useCorrected RTF export unicode character supportSped up RTF savingRemoved use of fontcacheFixed wrong display of pagebreak at top of windowFixed layout speed, especially under LinuxCorrected Linux layout to better match Word and LibreOfficeRTF support for many dot commands is not implemented (see implemented.xlsx)^KP not implemented, use ^OP.pt command can only be used once per document, all others are ignored. (wxWidgets doesn't let you change paper type on the fly)OSX keyboard input does not workSee Ticket SystemUPDATED TO 1572: 1571 had an intermittent hanging bug when moving the cursor up or down and dot commands not displayed. Sorry for the bad release.This is the first release I ve made that I have not tested extensively (through daily use). What is not tested is pretty much all functionality when not displaying dot commands. If something breaks, turn dot command display on and everything should work as expected again.Cleaned up the code a bit by getting rid of uneccesary debugAdded preferences dialog for screen color, etcCenter, left, right, and justify status indicators now workCount of lines per page in status barVertical Line height in status barColor Selection Dialog for text (^P-) (any color chosen get brought down to Wordstar s 16 color palette)Preferences dialog (via F1)Show and Hide Scroll Bar, Ruler, Top Status Line, Bottom Status Bar (via Preferences)Show/Hide dot commands (via Preferences)Show/Hide flag column (via Preferences)RTF support for many dot commands is not implemented (see implemented.xlsx)^KP not implemented, use ^OPGTK print preview displays a black page. Printing still works fine. This is a wxWidgets issue..pt command can only be used once per document, all others are ignored. (wxWidgets doesn t let you change paper type on the fly)OSX keyboard input does not workIf WordTsar starts with Control Codes not showing, you will not see a cursor until you have some text entered.^OB setting not implemented, set them via F1 PreferencesI got tired of working on RTF, so threw in some of the dialogs (color and preferences), Now back to RTF.I d like to move RTF import and export into a first class citizen so it can be a native file format for WordTsar right beside Wordstar files.In the background, I m thinking of adding column support and how to add table support (Comments welcome. Wordstar never had the concept of tables, really).

TAGS:WordTsar Wordstar clone 

<<< Thank you for your visit >>>

Hot Websites