The office will be closed on the 25th and 26th December and then again on the 1st January. The days in between will be covered by a reduced number of staff (yes – I am taking a holiday) so please be sure to use support@
Martyn's blog for the Revelation Software community, sharing ideas, news, views and more. NOTE - Views and opinions expressed in this blog are personal and do not necessarily represent those of Revelation Software.
Wednesday, 24 December 2008
Seasons Greetings
The office will be closed on the 25th and 26th December and then again on the 1st January. The days in between will be covered by a reduced number of staff (yes – I am taking a holiday) so please be sure to use support@
OI9.0 Controlling the Development Tools
The ‘Controlling Development Tools’ white paper is designed to get people thinking about their options when it comes to deploying an application to end users from version 9.0 onwards. Whilst it does not explore all of the options available to OpenInsight developers, it does cover some of the easier, non-code driven options. The paper can be downloaded by clicking the link above.
Wednesday, 17 December 2008
OI - Did you know?
The document can be downloaded by clicking here.
Version 9.0 and the blog
- A paper to help reduce the size of your application’s footprint
- A paper that brings together all of the 7.x, 8.x and 9.0 readme files
- An updated paper on locking down the new Network User deployment license
- An examples application, written entirely in 9.0 under Vista
- An unofficial paper to help configure OECGI2 and use WebOI on a Vista machine running IIS7 (currently needing some testers)
I’m then also hoping to go on to take a look at the Bravo Dashboard, individual cell control in the Edit Table along with other Edit Table enhancements, the brand new System Editor and OIPI.net – including enabling users to enter data into a .pdf document before printing it.
What else would you like covered?
OpenInsight 9.0 is the most exciting release yet and, along with Revelation's White Papers, Quick Start Guides and Tutorials, I hope to help all OpenInsight developers take advantage of the new features provided in OpenInsight version 9.0.
Watch this space… and please don’t forget to use the labels in the blog to bring similar categorised topics together, for example OI9.0, Vista, etc.
Tuesday, 16 December 2008
OI - Did you know?
FUNCTION CTO_MSG(PARAMS)
This routine opens up an OpenInsight MSG window on your ARev32 or CTO form.
For example:
call CTO_MSG("Hello World")
FUNCTION CTO_POPUP(DEFN,POPUPNAME)
This routine displays an OpenInsight PopUp window on your ARev32 or CTO form.
For example:
call CTO_POPUP("","CUSTOMER")
SUBROUTINE CTO_GUI_SUBROUTINE(SNAME,PARAM1,...PARAM20)
This routine calls any OpenInsight subroutine that requires running within an event context.
For Example:
call CTO_GUI_SUBROUTINE('START.WINDOW','ORMAIN32') will call Report Builder.
call CTO_GUI_SUBROUTINE("RUN_REPORT","","LIST 10 VOC F1 F2 F3") will run an Rlist statement.
Thursday, 11 December 2008
Very useful SENL from Sprezzatura
I would urge all OpenInsight developers, anyone running a legacy ARev system and Revelation users needing a strong disaster recovery solution to take a look at this latest edition and register to receive future editions.
Tuesday, 9 December 2008
OpenInsight 9.0 EMEA price list is now available.
The line-up also includes brand new Enterprise packages reflecting the needs of our larger clients. These licenses now have Universal Drivers and or the Universal Driver Heavy bundled, along with WebOI and multi-user ODBC driver licenses.
The Single User Runtime is still available as a marketing tool and package & pricing options for version 8.0.7 and earlier remain largely unchanged at the present time.
The 9.0 price list will not be published to the revsoft.co.uk web site, but it is available on request. Simply drop me a line and I’ll send you the list in .pdf format. I will also call you to make sure that you understand everything.
As always though, I would urge you to call me and discuss any quote or end-user requirements so that we can ensure that all of the options are considered and the right pricing goes on your quotation.
Bitten by Vista big time - Grrrrrrr
As many of you will now know, I have been writing a new examples application to coincide with the OpenInsight version 9.0 release. This application has been completely written using my Vista Home Premium machine.
Now, not being overly technical, I usually opt for defaults when installing software – it usually helps when I get myself into a mess as the support guys know where to find things. Anyway, choosing default options on this occasion has left me with something of a headache – mainly because I had planned to give my application to WORKS subscribers and most of you will have wisely stayed with Windows XP.
The issue is that Vista has a lovely new font called Segoe and I understand that Microsoft have set this as the default font for Vista. In turn, my OpenInsight installation picked this up as the chosen default font when creating a new application. I only noticed this when I dropped the application onto a colleague’s XP machine to show them how nice it looked. Needless to say, it looked awful as the XP default font on that machine was wider than Segoe and caused the text on my buttons and labels run off the controls.
Not to worry I thought. Sprezzatura have a friend in Microsoft and I’ll check that it is OK for me to include the Segoe font with my application – problem solved. But Oh no – It is covered under license and you can not freely distribute it. So my options are:
- License the font for each user.
- Get the user to upgrade to Vista, buy one of the Windows Live packages or Office 2007 (all of which I understand have the new font (but do your own homework before buying)).
- Change the font on every window and resize the controls as applicable.
- Only support Vista with my application.
Needless to say, as my application is primarily for demo purposes on my machine, I’ll be choosing option 4 for the moment.
BUT be warned. If you are planning a move to Vista, make sure that you use a common font such as Arial when designing and building your applications.
My advice – stick with XP Pro for the moment!!!
Monday, 8 December 2008
OI - Did you know?
For example, my oinsight.ini file contains the entries noted below. The first entry defining which buttons I want to show and in what order – very useful for your choice of System Editor. The following lines are used to define two buttons, one for ARev32 and the other for S/List.
SideBarToolList=2,1,3,15,5,8,16,12,13,11,14
SideBarCustom_Name=AREV32,S/List
SideBarCustom_Text=AREV32 Interface,
**S\ListDesignerSideBarCustom_Img=c:\RevSoft\Bmps\arev32big).bmp,
**C:\Revsoft\MDP\Images\zz.gif
SideBarCustom_Cmd=OIWINEXE**AREV32_STANDALONE_FORM,
**OIWINEXE**SLIST_EXECUTIVE
NOTE: The two astrixes (**) signify lines that are broken in the posting but should be one long line in the Oinsight.ini file. They should be removed when entring these lines into your oinsight.ini file.
Friday, 5 December 2008
OpenInsight and .net
I have recently been working on a brand new examples application that will also help to manage my photograph collection (more on that coming soon). Mike Ruane recently called me to share a really kewl feature that they have built for one of their client’s application – it’s now partly in my examples application.
Win Win Solution’s client manages a cemetery somewhere in the USA. Employing a large number of people whose first language is not English was causing some communication issues when needing to maintain a specific grave. Their OpenInsight based application now maintains an image of the grave in the database. However, that’s not the clever part. The digital camera has a GPS add-on, which captures the GPS position of the grave, well really the GPS position of the camera when the picture is taken. This is then used in the application to map exactly where the grave can be found – yes the cemetery’s are huge – and the employee has an image of the memorial or grave stone to confirm that they have the right one.
My examples application does not go quite that far, but Mike has let me have the .net wrapper which exposes the .jpg file header information and displays it in an edit table in my app. Please drop me an email if you wish to explore this further.
With this example, OIPI.net and other .net technologies being written for OI, support for exploiting the .net framework and third party components is looking really good.
Does anyone out there have any OpenInsight interacting with .net success stories to share? Click on comments below to add them to this thread.
Thursday, 4 December 2008
OI - Did you know?
Anyway, I stumbled on a nice little work around to this issue, the product of accidentally setting the auto resize properties of a label, instead of an edit table – well it was late ;-). It is also useful if you can't control the resizing of your windows, (for instance MDI children) but you do not want the form to sized smaller than the controls on the form and mess up your well designed and balanced forms.
This neat trick is achieved by dropping a label onto the form, removing the text and setting the background colour – or simply making it invisible. You then check (tick) the autosize height and width properties for the control.
The form will allow the user to make the window smaller, but only by the size of the label. Once the label reaches 0:0, it will not resize any smaller and stops the whole window from being made smaller. I have my windows open up at the size I designed them to be (usually the optimal size) and then have a 1:1 sized label so that it gives the user the impression that the window can only be sized bigger and not smaller.
This simple method, still leaves the user with the ability to make the window as large as they want, but you can usually handle those aesthetics through making other controls auto resizable and setting their anchor properties.
Tuesday, 2 December 2008
Global OIL Reserves Dry Up
Back in 2004, Revelation released ‘OpenInsight for Linux’. Initially supporting RedHat and Debian distributions, this was extended to support other emerging Linux distributions such as SUSE. However, for lots of reasons take-up of OIL was slow and following news earlier this year that some major Linux players were shelving plans to distribute a traditional desktop Linux product into the consumer PC market, OIL has finally been withdrawn (1st December 2008) from the Revelation product line.
Linux is still very much around though and continues to be an option for servers. For this reason, Revelation continue to support OpenInsight for Windows installed on many Linux servers. OpenInsight developers can simply take their Windows compiled applications and install them on Linux servers with Windows desktops, connecting them using a SAMBA share and the Universal Driver.
Friday, 28 November 2008
One of my most frustrating questions
I was reading a very interesting article in Computing recently that finally touches on one of the questions that frustrates me more than any other during my working day.
With key clients operating in financial markets and in the public sector, many with respected market leading solutions, I am sometimes asked to assist with the question “Why is your application not written in Microsoft or Oracle?”
In most cases, we have satisfied the users that the solution ticks all of the business case boxes, it fits within the available budget, and the sponsor, decision maker and evaluator are all happy and signed up to the purchase. It then goes to IT with the request to identify a suitable central server to host the application for final enterprise wide testing. At this point IT get involved and out comes the question and another round of justification begins!!!
This becomes even more frustrating when you know that OpenInsight applications usually require fewer resources than many RDBMS based systems, they don’t normally impact on other software on the server and they can play quite happily with most backup and failover systems.
So why does this question keep coming up?
In truth, we all know the answers – ‘Perceived’ cheap widely available RDBMS resources, staff wanting to stay in their comfort zones, the opportunity to stay buzz word compliant, etc. – all regardless of the impact on the business.
I’ll leave you to review the full article and draw your own conclusions, but it is nice to know that finally, people are beginning to question why IT staff are still trying to dictate what technology should be used, rather than purchasing the best solution for the business requirement and user productivity - regardless of what it is written in!
Click here for the full article entitled ‘How careerism can warp IT procurement’.
Thursday, 27 November 2008
OI - Did you know?
Wednesday, 26 November 2008
OI - Did you know?
Latest OpenInsight 9.0 beta released
Labelled ‘Beta 6’, the new version 9.0 moves into the final phases of the beta cycle with an anticipated commercial release over the next couple of weeks or so once the last couple of bugs are ironed out. All new bug reports and suggestions (reported through the bug tracker and suggestion tracker in the WORKS area) will be added to the 9.0.1 features list which is now being compiled.
Tuesday, 25 November 2008
OI - Did you know?
Recent RUG and OI4U2 days in Chiswick!
The RUG particularly generating a lot of excitement amongst the developers that made the trip down to London earlier this month.
Please click here for a review of the two days and to see what all the excitement was all about – as a teaser, I’ll give you one number ‘9’.
Monday, 24 November 2008
OI - Did you know?
Welcome to Martyn's RevSoft UK blog
I would urge you to subscribe to the news feed that has been made available to this blog. I do not intend to post every day, nor do I plan to post on a periodic or regular basis - I'll post as and when there is something to say and leave the news feed to notify you of the posting, with out you having to keep a eye on the blog itself.
I hope that you find this new approach useful. With the ability to add comments and participate in polls, I hope that this will become a two way share of information.
Martyn.