Rev Editor

Want to edit something? We can help! 
Contributors
Tags



February 6, 2010

Need more detail in card snaps? ZOOM!

Watch me zoom a card snapshot out to full size with a click, double-click or a keystroke:

(download)

Click to zoom:

Keystrokes that zoom:

Click to unzoom:

Keystrokes that unzoom:

All tRev components have been updated for zoom as well as the Quickstart and Shortcut documents for OS X and Vista/7.

ALERT: As of the update made today after this post, double-clicking the area outside the snap will no longer zoom and unzoom. Instead double-clicking the area directly outside the snap (but with the surrounding snap pane) will now edit the script of the card snap's stack. Also, double-clicking any non-control area inside the snap will open the script of the card.

You should click below to...

Loading mentions Retweet
Filed under  //   snaps   trev   upd   update   vid   video   zoom  
Posted by Jerry Daniels 

Comments [2]

February 6, 2010

Some Plugins for tRev

Captures your code and puts it in an email with name of object as subject:

Click here to download:
Email My Code.rev (7 KB)

Captures your list of handlers and puts it in an email with name of object as subject:

Click here to download:
Email Handler List.rev (7 KB)

Captures your list of stacks and puts it in an email:

Click here to download:
Email Stacks List.rev (7 KB)

Captures your list of cards and puts it in an email with name of its stack as subject:

Click here to download:
Email Cards List.rev (8 KB)

Captures your list of controls and puts it in an email with name of stack and card as subject:

Click here to download:
Email Controls List.rev (8 KB)

Captures your code statistics and puts them in an email with name of object as subject:

Click here to download:
Email Code Stats.rev (7 KB)

To add any one of these to your plugins, choose Plugin Manager from tRev's Plugins menu:

You should click below to...

 

Loading mentions Retweet
Filed under  //   plugins   trev   trev plugins   trev plugins free  
Posted by Jerry Daniels 

Comments [0]

February 6, 2010

General practice as regards comments, reports, etc.

Friends and colleagues

The following general practices are just common sense, and I would ask that everyone to do their best to adhere to them in commenting and reporting, etc. I will try to do the same. Some times we all get a little too playful and sometimes the play becomes rough or thoughtless.
  • I recommend people email me with requests, bugs, etc. because the need for interaction is fairly high. Comments to our site don't lend themselves to that.
  • Please choose descriptive subjects for your emails that are devoid of venting and unwarranted conclusions or alarms. I scan these for real emergencies.
  • It is not practical or best practice to implement every request for a new feature. Without a lot of careful thought, adding features can kill the product.
  • I often delete comments from the blog that are not timely. A bug that's been fixed or a request that's been met doesn't need to stay. This reduces site clutter.
  • Abusive commenting will result in a request from me to refrain from commenting. $50 is not a ticket to harass me or anyone else. Life's too short.
I do like to hear from people. I'm always interested in what folks want our product to do for them. However, the practice of pestering, insulting, threatening or guilt-tripping as a ploys to get attention or get features doesn't really work with me or anyone else. Those who have tried me, know this already.

I'm from Texas where I'm no better than anyone else, but no one else is any better than me.

Thanks for listening,

Jerry Daniels

You should click below to...

Loading mentions Retweet
Filed under  //   commenting   emailing   requests  
Posted by Jerry Daniels 

Comments [0]

February 3, 2010

Stack corruption with Rev engine circa 4.0-dp-4

During the period near the time the 4.0-dp-4 engine was sent to testers, there was a bug in the engine that would break a stack during save if the stack made use of custom properties with multidimension array values. If the stack used such values, it would save and open in 4.0-dp-4 but would fail to open in engines after that such as 4.0-gm-1 and 4.5-dp-1. 

This bug has been resolved but since there might be developers still using the old test engine, this is a word of warning: move to another engine and test if you can open your stacks. If you can't then, try removing the said custom properties and saving it again, then on the newer engine, you can create the property again. 

Many thanks to happy tRev user Andre Garzia for this note!

Loading mentions Retweet
Filed under  //   alert   engine   rev   tRev   warning  
Posted by Jerry Daniels 

Comments [0]

February 2, 2010

Download Build 201 of tRev Application

There is a brand new build (201) of the tRev application that you will want to download.

The links for each OS are on the right side of the main page of our site.

The following enhancements have been made to tRev and its components:
  • Non-admin users can now use tRev without having to alter read/write Rev folder permissions.
  • Sockets are being managed even more carefully to avoid conflict and to improve performance.
  • Communication between Rev and tRev is now tighter and more stable.
  • tRev no longer erroneously reports you are not connected to the internet.
  • Errors indicating missing broker files and other components have been drastically reduced.
You will need to restart tRev after downloading it, launching it and updating its components. If you forget to do this right away, you may have to force an install by holding down option/alt when you relaunch.

NOTE: In order to do all the clean up listed above, I had to temporarily sacrifice the multiple instances of tRev running simultaneously feature. With 201 you can only run one instance of tRev at a time on a machine.

You should click below to...

Loading mentions Retweet
Filed under  //   tRev   upd   update  
Posted by Jerry Daniels 

Comments [0]

January 27, 2010

Greater tRev-to-Rev interoperability and more!

Watch as I run through the new tRev features and enhancements noted below:

(download)

You should click here to see the Basic tRev API in PDF format hosted on my iWork shared documents site.

You may have noticed a new link in the upper right of the editor window in the video above. The Latest Post link appears when there is only one open tab. It uses the Twitter API to filter my Tweets for ones relevant to tRev users. The mechanism for updating this link operates completely asynchronously, so it will not interfere with our normal programming (pun intended).

You should click below to...

Loading mentions Retweet
Filed under  //   feature friday   interoperability   revolution   tRev   video  
Posted by Jerry Daniels 

Comments [8]

January 26, 2010

Write your own plugins for tRev!

Watch me add a couple plugins to tRev:

(download)

Start your plugin engines! Your tRev components have been updated and are ready for you!

ALSO: The tRev Quickstart docs have been updated with information on Plugins and the Plugin Manager.

You should click below to...

Loading mentions Retweet
Filed under  //   plugins   tRev   video  
Posted by Jerry Daniels 

Comments [4]

January 21, 2010

Jerry's email address

Contact me at this email address:

jerry@reveditor.com

This email address has been retired:

jerry@daniels-mara.com

Best,

Jerry Daniels

Loading mentions Retweet
Filed under  //   address   email   jerry  
Posted by Jerry Daniels 

Comments [1]

January 20, 2010

Tired of opening the same stacks over and over?

(download)

You really CAN avoid the painful, repetitive use of the Rev menu in opening your stacks! Just click a link in tRev's Scratch Pad and the stack is automatically stored in memory so you can work on its code. You don't even have to have it showing in Rev to do so. Big plus: less clutter; less mind-numbing tasks!

That's right! In addition to having fast access to a handler on which you were laboring, the tRev Scratch Pad also functions a work space. In the video above, you just saw tRev use its Scratch Pad and Object Browser to perform a virtual hat trick as a (1) handler navigator, (2) stack loader and (3) stack viewer.

Again, to see that stack you have in memory, open the tRev Object Browser, select the stack name (or any object in it) and click the Go To column button or just type g. BAM! Your stack is now editable in Rev and you can work on it's properties or whatever.

This little hat trick not only saves me OODLES of time, but it also keeps me from going postal (on a rampage with a rifle).

For those interested in the etymology of the phrase hat trick:

You should click below to...

Loading mentions Retweet
Filed under  //   hat trick   scratch pad   tRev   video   work space  
Posted by Jerry Daniels 

Comments [0]

January 20, 2010

Reporting bugs, making suggestions

If you developed tRev, looked in your email in-box and saw this subject line, what you think?

I don't get that many bug reports, I'm happy to say, but about 40% of them are sensational and downright un-helpful. Like this one.

In this case, tRev did not stop working. But how was I to know? I had to read the entire email to discover that one feature in tRev did not perform as expected. 

I respond quickly to all reports, so there is absolutely no need to sensationalize a bug report to get my attention. 
Say what the problem actually is—not how badly you feel about it. tRev doesn't do something you want it to do, so the whole program doesn't work? No. Say what it is that isn't working and tell me how I can replicate the problem.

If I can replicate it, I can fix it. If there is a work-around, I will advise you of it while I fix the problem.

Sometimes I get tRev not working subject lines, and it's a request for a new feature. When you want a feature, Tell me what—in a larger sense—you're trying to do. From requests like that, our best, new features have come.

If you're frustrated or unhappy, take a deep breath. Chillax. I'm not trying to make your life miserable. Because I'm enthusiastic about my product doesn't mean I'm indifferent to bugs or suggestions. Please don't assume a bunch of stuff, and then write tRev doesn't work.

That doesn't work for me. And therefore, it won't work for you.

You should click below to...

Loading mentions Retweet
Filed under  //   bugs   reporting   suggestions   tRev  
Posted by Jerry Daniels 

Comments [0]