Due to the lack of updates recently (caused by a lack of development), I thought I'd give a little teaser of the improvements that the next major update for STE has over what you are currently using (most likely the 3.50 release).

Regular progress updates: A progress bar at the bottom of the application is used for every lengthy task, giving you an idea of how long it will take.

Automatically download updates without visiting the website, using the all-new launcher.

And there is more to come, as many of those are under-the-hood updates that make the UI improvements possible.

I'm not quite ready to release a video showcasing the changes, despite some of the features being easier to demonstrate that way. However, I will give you a screenshot of the editor view. In this case, the Wikidot Community site has been opened for editing:

Also, I previously mentioned on Twitter that STE would not be integrated with the "Colombo" project when the next major update is released. I am currently in the process of revising that decision, and looking at ways to integrate the two. So integration at launch is a possibility.

I had to look up the definition of "Second System Syndrome". I have heard the term before, but was not completely sure of the meaning. Wikipedia has this to say:

In computing, the second-system effect or sometimes the second-system syndrome refers to the tendency, when following on from a relatively small, elegant, and successful system, to design the successor as an elephantine, feature-laden monstrosity.

James: Point taken :)

I can't bring myself to release an unfinished product, but I can lower the definition of what 'finished' means, and I'll do that.

When working on my own projects I constantly found myself compiling a copy of STE 4 just so that I could use it, despite it seriously lacking some of the more basic 3.50 features. So it's definitely useful at this point, but I still want to add a couple more things before release.

08 Sep 2012 16:10. Edited 0 times. (Edit, Permalink)
I suppose I was looking for "Version 2 Syndrome", but the internet doesn't seem to have a term for it.

Wikipedia's definition is a little harsh and not really what I'm trying to convey either … This blog is where I got the term from, and is much more elegant in it's explanation:

It usually happens when someone, feeling that the current system is not good enough, believes that it is would be easier to abandon the current code base and give it a fresh start
…
The result of this pursuit is that it [takes] years before [the developers have] a new [software] with the expected functionality