Size May Not Be Significant

not yet complete

Have you ever heard anyone brag about how large their Omnis libraries are? If so, did you ever stop to think about what that may mean about those libraries? Here are a few things to consider.

Anyone can make a large Omnis library. It doesn't take much to fluff one out. A lot of graphics placed on windows and reports, lots of comments, unneeded variations of formats (especially search and report formats), using Omnis Notation for everything (instead of more concise commands when a choice can be made), storing background data within the library itself (using the library as a datafile), and just plain bad code can cause the size of a library to mushroom. None of this is necessarily anything to be proud of. It all depends on how the techniques are used and whether they enhance the functionality, efficiency and conciseness of the finished application.

The real thing to brag about is how much work the library does. If two libraries do exactly the same things (in terms of data manipulation), but one of them is significantly smaller, the smaller one should get the kudos! Efficiency is the key -- not size. Let's examine each of these points to see how we can make more concise libraries and dispell the "bigger is better" myth.

Graphics are nice enhancements to an application when used in moderation. They can be used to make the visual presentation more appealing and approachable. They can make windows and reports more meaningful and easier to read and understand.

comments

format variations

notation

data in library file

bad code