MfGames GtkExt Text Editor CIL

Author Intrusion 0.4.0 "Frederik Pohl"

2013-10-02T05:00:00Z

It's now time for the fourth release of Author Intrusion. This is my attempt to have a monthly release of the text editor and, as the previous release, it isn't exactly stable enough to write without a lot of patience.

It is fairly capable though, but mostly as a pure text editor with spell-checking. I've written a novella and seven short stories since I started developing the project. For a sake of curiosity, I used the associated Linux tools to convert my weekly serial (624k words) into the program and navigate around. It's slow to start, but once loaded, it ran rather zippy and I could write almost at my full typing speed in the middle.

The bulk of the changes are related to technical debt, cleaning up code to make it easier to develop in the long run. Mostly, these changes were to fix things like "select all", or selecting text and then typing.

As you can tell from the screenshot, I shifted a few things around. These are completely arbitrary changes until I can figure out docking panes. The project pane on the right is not functional at this point, but I needed it on screen to verify that I had a bug; this will also lead into the changes I'm planning on for October.

Author Intrusion

Updated changes to use MfGames.Commands.TextEditing structures. +Changed
- Changed integer indexes to LinePosition and CharacterPosition.

MfGames GtkExt Text Editor CIL

Removed legency references to BufferPosition and the integer-based system for MfGames.Commands.TextEditing LinePosition and CharacterPosition. +Changed
Various corrections to get Select All, copying, and pasting working properly. +Changed
Corrections to get the abstract text commands working with end of buffers and lines. +Changed
Added extension methods to wrap the GetCharacterIndex and GetLineIndex in LineBuffer-specific calls. +Changed

MfGames Commands CIL

Bumped version to MfGames.Commands 0.2.0
Added the concept of "first" and "last" for text ranges to ensure ordered usage. +New
Added more logic to the generic text commands to bring it more in line with Microsoft Word. +Changed
Removed the white space while joining next and previous paragraphs. +Changed
Renamed properties to give them consistent names across positions and lines. +Changed
Renamed NormalizeIndex into GetLineIndex and GetCharacterIndex to allow them to be merged at the position and line ranges. +Changed

Dependencies

MfGames.Commands 0.2.0
MfGames.GtkExt.TextEditor 0.4.0

Technical debt

2013-09-27T05:00:00Z

This week I've been working on Author Intrusion. I needed a break from trying to get my novel out and I'm trying to maintain a once a month release schedule for the program, so it was pretty obvious I needed to spend some time on it.

The wishlist for Author Intrusion is fairly high. The next step is sizable and may actually take more than a month to complete. So, I figured I could get started with the framework and just start chipping away at the large task.

Before that, I decided to fix some "easy" bugs that were bothering me. The first one was Select All command caused the system to crash. That shouldn't be too hard to fix, I'm sure its minor.

Six days later and I'm still not done fixing the mass destruction of that little command.

The cause

When I was trying to get Author Intrusion 0.1.0 out, I made a number of libraries to encapsulate logic. One of them was MfGames Commands CIL which was an abstraction for text editors. Mostly, I know that Author Intrusion will have different front ends and it has its own internal, text-editor-like state. Having a common code base for these things made my life easier, but there were some complexity involved with an abstracted system.

Abstracted systems always increase complexity.

The problem with Select All came from how to identify a location in the document. In MfGames GtkExt Text Editor, I had a class-based implementation that used Int32.MaxValue for "end of line" and very little type safety.

The new commands version took what I learned in two years of writing a text editor and used a struct-based system that had symbolic values for "End" of a line or buffer and "Word" for character. These classes were also immutable (once created, they couldn't be changed).

Side note: The magic values was the preferred system because I encountered a couple "plus one" problems where I accidently added or subtracted one from MaxValue. With a number that large, I couldn't identify the problems easily. Now, I have -113 as the "end of line" and -1053 as the "word" symbol. This way, I know if there is a plus one problem because both -112 and -114 are always invalid.

Make it work

This change broke a lot of things when I integrated the two systems together (Author Intrusion and the text editor). Since I was running out of time for an arbitrary release, I wrote some hack layers to translate between the two layers and jammed it into the places that broke.

In programming terms, this is technical debt. I was writing crappy code on purpose. True, I didn't know exactly what I was doing (one common reason for debt) but also because I needed something done.

Sooner or later, I knew I'd have to fix it "properly" but I figured I could do it later once things were working.

Compound interest

Technical debt, in itself, isn't entirely bad. As I mentioned, when you are fumbling through the code, not everything can be elegant and pretty. The better it is thought out, the less work it takes to maintain, but I believe most programs have to "settle" before they can be cleaned up.

The nasty part comes when I wrote code on top of the lousy code. Every time I build on it, I'm adding to the effort to clean it up. Do it once, it's just a little bit more. A year of heavy development on a lousy base... almost impossible to fix.

Biting the bullet

This week is cleaning up some of the worst of that debt. A simple thing, a text position, that is critical to almost every part of the system. I know it needed to be done and I have a much better idea of how to do it (the code is much simplier now), but still isn't fun.

And this week was the week to clean it up.

No regrets

I don't regret writing it in the first place. Sometimes, the software needs to ship because making it "right" will take too long. Other times, there isn't a good answer yet. The important part, more so with this 5-10 year project, is that I keep it mind and fix it before it becomes too integral to the system.

On the other hand, Select All works again. Page Up, Page Down, Right Word (but not Left Word), selection operations, Control Home (but not Control End) broke, but at least Select All works. :)

Yeah, I'll have that fixed by the 1st.

MfGames GtkExt TextEditor v0.2.0

2013-08-02T05:00:00Z

Well, it was a minor set of changes over the month, but the text editor needed quite a bit of work. In specific, the problems I had last month with accented characters blew up pretty badly over the month. The novella I was working on happened to have a character with an umlaut, which meant the program crashed every time I navigated through that characters name.

This ended up being a very interesting problem. I use Pango to both render the lines of text but also to handle navigating. So when the user uses the right arrow, I use Pango# to determine how many pixels to move over.

Unlike Gtk#, Pango# doesn't deal with character indexes from C#. It appears to give (and require) UTF-8 encoding. So, the third character in a string of "ééééé" (according to C#) is actually character index 6 according to Pango#. This took me a while to figure out, mainly because I would have never guessed UTF-8 encoding, but it seems to work.

Unicode

Reworked how cursor movement and caret rendering took into account with how Pango works with Unicode characters. +Changed
Better handling of trailing glyph edges while navigating to reduce the jumping of a single character while moving. +Changed

Releases

GitHub