Actuate Programming Journal

Report design from a guy who thinks he knows what he’s doing; you decide . . . .

Archive for the ‘Requests’ Category

The Differences Between Actuate 6, 7, 8, and 9

with 9 comments

Inconsequential.

Hopefully from that one word you can tell I am more likely to focus on opinions than facts.

In general the changes that Actuate makes to its reporting suite have influenced the server application more than the development IDE. This shouldn’t come as a surprise because there really isn’t all that much new under the sun regarding how to build reports. The server bells and whistles are what sell the product to the folks that pay for Actuate–that’s not normally a crowd full of developers looking for slicker programming environments. I’ve been far enough removed from the server side of things in these past years that I will only say that somewhere in there they added support for clustering (probably from 6 to 7).

The IDE on the other hand has had a few noteworthy, but barely braggable updates.

6 became the benchmark in my mind for IDE stability. Before that eRDPro was prone to hiccups that trashed ROD files and required restarting the app and sometime rebooting your computer. I think this is when we got the Dynamic Text Controls. Grouping and Sorting got a fancy new widget in this version or 7. I don’t use or recommend it’s use so I don’t recall.

7 added that crosstab widget that I avoid but I hear others like well enough. I think they deprecated AcGraph in favor of AcChart and the new–thank God–graph/chart widget.

8 was the biggest leap since I’ve been around. eRDPro went from in-house interface to Eclipse based. Though I wouldn’t call it a full on embrace of Eclipse since there is still some functionality I would have expected to see but don’t: code highlighting and completion being the most obvious.

9 is an extension of 8 but with the funky little do-dad for doing conditional formatting. It’s handy, but not as robust as I would have liked for my coding.

Things I’d like to see:

  • code highlighting
  • code completion
  • file manager interface
  • better server access (more clarity)
  • ability to open more than two instances of eRDPro

I am sure there are other IDE standards that I am not thinking of at the moment. I suspect I am too ingrained in the product as is to think to far outside the current feature set.

As for the question that spawned this post, there are really no difference in the ROD file types except that you can’t run newer versions in the older IDE/Server. Backward compatible, yes; forward, no. I have no evidence, experience, training, or interest in finding out why that is, but I suspect it’s nothing more complex than “file version <= IDE version?”.

A remainder not to quote me on any of the above ‘facts’. This is totally out of my brain. If you require a technical comparison of the feature sets between versions, please check Actuate’s documentation regard such.

Written by Douglas

20080220 at 11:57 am

Posted in Actuate, Requests

Tagged with , , ,

Viewing Actuate Files

with 11 comments

This is inspired by my trawling of the referring ‘search terms’ part of my stats program for this site.

Unless you are a developer, attempting to view an Actuate file is probably a waste of effort.  What you want to focus on rather is the output on the web.  Here is a run down from first to last…

RODs are design files that are only openable using Actuate’s IDE.  ROLs, libraries, are the same deal.

The IDE produces a BAS file from the ROD when compiling.  It’s not clear to me if this is a requirement of the compile or a bonus for developers.  In either case its a text file easily viewable in anything that displays text.  You cannot compile this file, but you can painfully reconstitute a ROD using it.

ROXs are generated by compiling a ROD and are placed on the server for execution.  They are not viewable.

ROIs are the result of the execution of a ROX (and some other less important files).  In the old days we viewed these files directly in the web browser with a plug-in for te browser.  These days Actuate has some bit of code ont he server that translates these into DHTML.

So, if you are a user, you are most likely going to view these on the web.  Depending on your acess you will have options to download as text, PDF, or spreadsheet.

If you are a developer, it’s a weird search to be doing.  Stop it!

Written by Douglas

20070124 at 12:43 pm

Posted in Actuate, Requests

Tagged with ,

Request for OSS( ) Material

with one comment

I have been seeing quite a few searches that end up here from “obtainselectstatement” or “obtain select statement”.

And I have been meaning to write soemthing up soon about that, but if any of you have a specific focus or topic, feel free to share in the comments.

Written by Douglas

20061020 at 12:25 pm