Hi Everyone, I hope that you are all well, staying safe during these Covid-19 days and that the various government measures around the world are not impacting on you, your families and your businesses too much.
Looking back at the blog, I cannot believe how long it has been since I posted anything here. That is not a sign of how busy, or not busy, I have been and I have been keeping very busy over the nine months or so.
Personally, I have been working from home throughout the lockdown period in the UK and nothing much really changed, other than my daughter taking over my office and regular workplace. Thankfully, I can work pretty much anywhere. I hope that you have been as fortunate in your workplace, although I know that some of you have struggled to settle into working from home and you are glad to be getting back t osome level of normality.
On the work side, I was really busy at the beginning of lockdown. This was mostly helping people with setting up remote workers as countless numbers of end users were moved from office to home working. I am pleased to say that pretty much everyone relocated their OpenInsight end users to remote working, regardless of whether this involved an eay O4W move or a slightly more involved OI desktop move.
The process also had one interesting benefit. It flagged up a number of systems that were not necessarily configured for optimal performance and stability and my support colleagues worked with those clients to help them to get the best from their remote access solutions.
Following this floury of suport activity, which also resulted in a number of new licenses, my client side activity settled back to normal levels for the duration of the lockdown and July and August are seasonally slow.
For me, this was the perfect time for RevUS to begin putting the finishing touches to the next OpenInsight release. I was given access to the 10.0.8 alpha and then beta releases and I set to building myself a brand new application. This would be written for the desktop and entirely in version 10.0.8. The development has gone well and, once completed, I hope to make it availble to all of our WORKS subscribers.
“… this is THE release when I think that OpenInsight and other Multivalue developers should begin to explore OpenInsight and how it can be used to modernise and benefit their application development.“
This project has enabed me to get more and more into application development with OpenInsight 10.0.8 and to learn more and more along the way. I will write more about the application itself nearer to when it is released, but it features commuter modules heavily (whereas the EXAMPLES application in OpenInsight is largely script based), some nice pretty) screens and I hope that it will feature a complex report with charts and more. The is an area that I am working on with my support colleagues at the moment.
I have been amazed at what a junior developer can build using OI10 and this is never moreso that now with the new version. The process of application development using the new version is becoming quicker and more enjoyable with each release. In addition, in my opinion, this is THE release when I think that OpenInsight and other Multivalue developers should begin to explore OpenInsight and how it can be used to modernise and benefit their application development.
Personally, I would have liked for this to be version 10.1, yes I really do think that it is good enough. But, I fully respect Revelation’s decision to hold this as another point release and especially as more and more Revelation developers are currently making the move to version 10 and more developers are reporting on their experiences of running their older applications through the conversion.
Will the next release be that ground breaking 10.1, we will have to wait and see, but I certainly hope that it will.
So, if you are an OpenInsight WORKS subscriber, you can now download both the 10.0.8 upgrade and full install files from the private WORKS area. If you are not yet on WORKS, or your subscription has since expired, you can still get your hands on the usual 30 day evaluation which has just been updated to 10.0.8.
For those of you that sinply want an update on the main changes, I have copied those below for your reading pleasure.
So, I’ll leave this long posting for now and I’ll be back very soon (I hope) with details of my new OI 10.0.8 written demo app.
OpenIsight 10.0.8 Release Notes
Major Changes in the OpenInsight 10.0.8 Release
OpenInsight now provides an option to change the precision of mathematical operations. This can be set by calling the setEPMode stored procedure, passing in 1 to enable and 0 to disable the functionality. By default, the extended precision math will maintain 32 digits of precision, but this can be modified by calling the setEPModePrecision stored procedure, passing in the number of digits of precision desired. Both the enabling of extended precision, and the default number of digits, can also be defined in the application properties. The following operators/functions are affected: +, +=, -, -=, *, /, ==, =, !=, <>, >, <, >=,<=, mod(), int(), abs(), atan(), cos(), exp(), ln(), pwr(), sin(), sqrt(), tan()
OpenInsight’s RLIST functionality and performance have also been improved starting with the 10.0.7 release. A new version of RLIST (RLISTX), which optionally replaces and extends RLIST, is available to enable these enhancements. RLISTX merges the features of RLIST, SELECT_INTO, OLIST/RUN_REPORT, and RTI_XBAND. One obvious change is the ability to pass in multiple select statements to RLIST in a single call, @FM delimited. Using the Record Editor, or the Configuration Record option from the OI Console, you must create a CFG_RTI_RLIST record in SYSENV, with RLISTX in field 1. If this record doesn’t exist, or has anything other than RLISTX in field 1, then normal RLIST behavior (“RLIST 9”) and functionality will remain. (Note that the CFG_RTI_RLIST information is cached by your system; after changing this value, you should exit and re-enter OpenInsight).
The MultiValue BFS (MVBFS) connections for QM, D3 and U2 have been enhanced to submit multiple select lists to the “back end” host for bulk processing whenever possible. This enhancement can result in significant performance improvements when using an MVBFS connection. Note that these changes work in conjunction with the RLISTX changes discussed above; you must enable RLISTX and install a “plugin” stored procedure on the host system to access these changes. There is now a button on the MVBFS connection designer which will install this plugin (a program named RTI_MVBFS_SERVER_PLUGIN_U2, RTI_MVBFS_SERVER_PLUGIN_D3, or RTI_MVBFS_SERVER_PLUGIN_QM).
Starting with OpenInsight 10.0.4, “child” processes launched from OpenInsight can be configured so that they do not consume
additional license seats. In particular, CTO, AREV64, BRW, and O4W calls (using the engine server’s built-in web server)
made from a copy of OpenInsight will not count against the licensed count of users.
For example, a single user copy of OpenInsight can now run the IDE, a CTO session, and generate a BRW report at the same time.
Note that this enhancement requires both OpenInsight 10.0.4 (or above), and the Universal Driver 5.2 (or above).
OpenInsight 10.0.8 will work with the Universal Driver 5.1, but it will not exhibit these license enhancements until it is
“paired” with a UD 5.2.
To take advantage of this license enhancement for O4W and engine server tasks, users/developers must update their eserver.cfg file (either directly or through the Settings dialogs). In particular, any passwords that are currently explicitly embedded in the eserver.cfg can be replaced with an asterisk (“*”); this indicates that the specific connection should use the enhanced licensing. This also has the additional advantage of no longer requiring manual updates to the eserver.cfg file when passwords are changed for the applications or users defined in the connection string. (As an additional enhancement, the username can also be replaced with “*” if you wish to use the ‘default user’ created for an application).
For example, if your eserver.cfg previously contained the following lines:
They can now be replaced with the following lines: