Rev Editor

Should I switch to tRev?

The tRev Way

There is a defining philosophy built into every tool that you use. tRev is no exception. It’s a new editing environment for folks who use Revolution to develop software. As its name suggests, tRev tends to be rather terse—but in a most helpful way.

If you like clean, simple tools that stay out of the way by eliminating administrative debris and emphasizing what’s important, you will love tRev.

Here are three things to consider in using tRev:

Some tools are very demanding. They need constant adjustment and attention in order to perform. They have lots of preferences and ask you to invest in learning something complex so that your life will somehow become easier and more simple. This is not one of those tools. It’s very simple and straight-forward.
If you are coming from another development environment, this one will not be like the one you just left. The Revolution language and fixed object structure make many of the daily chores you once performed obsolete.
tRev has been built for Revolution developers to help them do the things Revolution developers do, not the things Visual Basic or C# developers do. Writing Revolution code is somewhat like writing good prose. It’s not like building a circuit board.

My comments here are not directed only to developers who are new to Revolution. I’m also speaking to Revolution developers who are willing to let go of some old tools and habits—and embrace something new, simple and exciting: tRev.

There are a couple things Revolution developers should know going in:

If you are accustomed to the setting in the Rev IDE that forces you to use explicit variables, you will find there is no such setting in tRev. You can declare variables, but, there is no setting that will force you to do so.
If you cannot live without a modal debugger, you may not be happy with tRev's modeless Decoder. Our users like Decoder because it’s very simple and never interferes with itself or Revolution. Because of it, you’ll find Rev IDE just keeps running.

Lastly, if you are accustomed to companies behaving like government agencies, you’ll find us a bit different. There are just two of us, and we don’t pretend we’re a big company. We speak to you directly as a colleague and an adult. I'm also a software auteur whose products have innovation and personality. Not everyone likes that.

Mary Jane (my wife and partner) and I have some very specific goals in mind as we develop tools, programs, training and documentation for this market:

We are not looking to make everyone somewhat happy with our work. We want to make 1,000 people downright delighted with it.

We hope you’re one of them!

Best,