RAD for Linux: A Review of Omnis Studio
Manufacturer: Omnis Software, Inc.
Price: $149 US
Reviewer: Nicholas Wells
The gcc compiler we all rely on when developing programs for Linux is a standard recognized throughout the entire UNIX world. It's fast, it's straightforward, and it compiles standard C (or C++ for the g++ compiler). But anyone who has written a large makefile knows it isn't a complete development environment by itself. With the advent of some serious tools like Code Fusion and Source Navigator from Cygnus, developing large projects with multiple programmers is getting easier all the time.
Rather than use these tools, however, many professional software developers rely on Rapid Application Development (RAD) products to design, prototype and code applications. Many of these applications revolve around database access; many are created by an organization for internal use or by consultants for vertical markets. These might be billing or database access systems, customer support systems, or pieces that integrate existing web services so all employees can access data using a browser. The issues facing these internal developers are different from those that face someone creating a “boxed product” or a standard open-source project for eventual public consumption. Three examples of these issues include very tight deadlines, a need to integrate with existing IT infrastructure, and a need to run on multiple platforms running in an organization.
The process for completing an internal project might look something like this:
Plan the project, including creating a schedule for development.
Create a demo (if things are moving slowly) or a prototype (if they're moving rapidly).
Develop the actual program.
Test it within the department where it will be used.
Deploy the program, and begin the revision phases as needed.
Java is the proposed solution to many of these internal development projects. It's a cross-platform language, it works with the Web, and everyone seems to accept it as a good idea. But Java is not always the answer, as developers on many abandoned projects can attest. Microsoft Visual Basic is also widely used for these internal projects.
The problem with so many of these internal projects is that after a lot of work has been put into the planning step, the prototype and development take so long and cost so much that the whole project may become unworkable (or at a minimum, go way over budget). Part of the problem lies in converting a plan into a prototype, or a prototype into a working program. Other problems often revolve around a lack of appropriate tools or talent, or the need to create the program so that it runs on multiple platforms (or the Web—which brings a separate set of challenges). RAD tools are the solution many developers look to. These developer tools combine a graphical interface, database access and additional tools to help code, debug and deploy an end-user-oriented application.
While a few high-end tools have been available on Linux for a while—some for $10,000 or more per developer—those needing RAD tools normally didn't consider Linux. (One promising tool, Borland's Kylix, is still in beta testing.)
A recent entrant in the field of Linux software development is Omnis Studio from Omnis Software (http://www.omnis-software.com/). Though this company and product have been around for over twenty years, they began shipping a Linux product just last year. Fortunately, the maturity of their products and the depth of the feature set have carried over very well to the Linux port. Omnis Studio takes a Java-like approach to software development that creates a single cross-platform program in a very powerful graphical development environment.
Omnis uses a run-time engine to both develop and execute programs. If “editing” is enabled in your license, you can create new programs; otherwise, you can run only existing programs. Amazingly, this engine (without the libraries your program may require) is only about 1MB. Both the small size and the execution speed of Omnis Studio applications are surprisingly good, given that this is an interpreted environment. Engines that let you create and execute Omnis Studio programs are available on Linux, Windows and Macintosh. To show the flexibility of the technology behind this product, consider that you can develop a program on Linux, make changes to the same program file on a Windows system (running a developer license of Studio), then run the newly altered program on a Macintosh. You can think of the “program” as a script that can be run or edited on any of the platforms. Figure 1 shows the architecture of the product.
Longtime users of both Omnis and other tools (Java or Visual Basic) have told me that Studio requires about 20% of the development time of Visual Basic because of the automation Studio includes. Some of these automation features are things like auto-typed variables which are tokenized throughout the project, and single-file projects that collect all relevant information in one place.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Stunnel Security for Oracle
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- SourceClear Open
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide