|
|
|
|
|
 The Studio version of PlanBoard is a complete redesign that takes full advantage of all that Studio has to offer. We used powerful object-oriented design patterns to implement features that make PlanBoard application development easier than ever.
To create a fully functional window, you only need to subclass a single object called the PlanBoard delegate. This 'delegate object' contains custom methods and attributes that can be overridden at will. Each section of the PlanBoard window is a subwindow that can easily be subclassed. You can open as many PlanBoard instances as you like.
From a user's perspective, PlanBoard for Studio feels very natural. Where certain behavior (such as vertical scrolling and redrawing) had to be 'faked' in Omnis Classic, Omnis Studio has a more complete feature set that we are able to use to its full extent. Planning slots now become selected when single-clicked. They also have tool tips so they can easily be selected even in the larger time scales. Resource rows automatically adjust their height to accommodate multiple planning slots. The legend is a palette window that automatically disappears when another window comes to top. PlanBoard refreshes without closing its window, even when switching color schemes or when adding or removing resources. The demo library even allows users to switch languages on the fly.
PlanBoard was built on top of the foundation layer of MasterStudio, Master Object AB's amazingly powerful application framework.
|
|
Information on this page:
|
Other Links:
|
|
Navigation
-
Selectable rights for creating/moving/resizing/deleting
-
Create new slots by dragging them from Legend
-
Live scrolling during drag & drop
-
Right-mouse click to access slot properties
-
Duplicate slots by right-mouse dragging
-
Group slots to always move them together
-
Move the cursor to an edge, and time will scroll automatically
-
Intuitive keyboard shortcuts
-
Dynamic context menus on every slot and subwindow to which you can easily add your own commands
-
Fully resizeable (no screen size limit)
-
Zoom in and out by clicking in timeline or by keypress
-
Selectable grid per scale, snap to grid
Data model
-
Entirely database-independent
-
Independent of field names and table/schema/query/file class names
-
Unlimited number of resources (for best performance, you should only display a screenfull at a time)
-
Unlimited number of slots
-
Display text can come from an existing database field or it can be calculated from your database fields
-
U.S. English, U.K. English, German, Dutch, and Italian strings built-in, other languages can easily be added. Optionally, you can use strings from your string tables or database
|
|
Interface
-
Scale-switching: 15 Minutes, 2 Hours, 8 Hours, Day, 3 Days, 5 Days, Week, Month, 6 Weeks, 3 Months, 6 Months, Year
-
ISO week number display
-
Blue, Graphite, Green, Metal and Red color schemes
-
On-the-fly color scheme and background switching
-
Application-driven color legend
-
User-configurable resource width
-
Flexible button bar (you can change it at will)
-
Open multiple PlanBoard instances simultaneously
-
Show multiple panes within one window
-
Adjustable planning slot overlap
-
High-resolution printing of any scale
-
Cascaded printing mode or "WYSIWYG"
Omnis-specifics
-
Classes come in separate, well-organized libraries
-
Demo library includes full source code of sample implementation
-
Classes can be copied to your existing library
-
Only uses standard external components supplied with Studio
-
Source code for all windows included
-
Modeless window, will also work in modal app
-
StudioTIPS naming conventions for local and parameter variables
System Requirements
-
Supported on Windows and Mac OS versions of Omnis Studio 4.1 - 4.3.1 (Non-Unicode. PlanBoard version 4.0 will support Omnis Studio 5.0/Unicode. Support for Omnis Studio 3.x and 4.0 ended on January 1, 2008).
-
For best performance, libraries should be installed on a local hard drive. See the MasterStudio FAQ for more information.
|
|
|
Navigation
-
Navigation arrow buttons remain visible all the time
-
Continuous scrolling only fetches from the database after half a window has been scrolled
-
Single-click selects a planning slot
-
Delete (or Command-Backspace) deletes a slot
-
Selection handles reflect applicable rights for the current slot
-
Separate drag handle to move a slot to another resource without changing start and ending time
-
Cursor changes automatically into the appropriate resize cursor when mouse is over the edge of a planning slot
-
The Legend is a palette window that automatically disappears when another window comes to the front
-
Easily add your own interactive objects and fields to a PlanBoard window
-
Buttonbar can easily be changed or removed by developer
-
Scale-specific time grid (snap to grid)
-
Clickable Legend items
Data model
-
Works with your schema, query or file class field definitions
-
Dynamically add, remove and redraw resource lines
-
All fields (including booleans for privileges) can now be mapped to your database fields, or you can still use global fields that are mapped to a public file class
|
|
Interface
-
Tooltips for planning slots and legend
-
Legend indicates whether slot may be created by dragging
-
New non-obtrusive Metal color scheme option
-
Uses adjustable field styles for fonts
-
On-the-fly language switching
-
New improved drag & drop cursors
-
Smoother redraws
Omnis-specifics
-
Easier and more powerful API through delegation and subclassing
-
Each PlanBoard instance runs in a separate task resulting in better separation from your own code
-
Easily add your own objects to a PlanBoard window
Not implemented in Studio version 3.0
-
Option to show "current time" marker (SET_MARKER)
-
User-resizable resource height (now automatic depending on the number of overlapping slots per resource)
-
User-resizable conflict height (SET_CONFLICTHEIGHT now automatic)
-
"Resource types": The popup list is no longer standard, but you can still add one yourself
|
|
|
PlanBoard for Omnis Studio comes with US English, UK English, German, Dutch and Italian strings. Because all strings are stored in a separate object class, creating other translations is extremely easy. If you wish, you can adopt the object class to read strings from your existing string tables or from your database. PlanBoard automatically adjusts to local time guidelines, such as the use of AM/PM and month/day order. For manual entry of start/end date a PlanBoard window uses your application's #FDT setting.
|
|
Please contact us and tell us about your application and the expected number of users. We will send you an attractive proposal and you will receive an invoice after you order. The software, Developer Manual, registration codes and license agreement will be sent to the e-mail address you specify. We offer a 30-Day Money Back Guarantee on the PlanBoard developer pack. Please read the License Agreement before ordering.
|
|
After acquiring PlanBoard we have invested into modernizing the product, improving the Developer Manual and sample library, creating a new look&feel in version 2, and developing the Studio version. To allow us to further expand and invest in the product we charge a yearly 15% maintenance fee that includes updates and E-Mail support. In addition, we offer phone support and we provide assistance in developing Omnis applications.
|
|
|
|
