Thank you for downloading this release of Focus. The Focus application is useful for examining, editing, and correcting SEDRIS Transmittal Format (STF) files (also called SEDRIS transmittals). This release has been tested on Linux and Windows NT/2000/XP and is compatible with SEDRIS 4.1.1.
This release implements the following capabilities:
- Open multiple transmittals simultaneously.
- Create multiple views of a transmittal.
- View and edit the objects in a transmittal.
- Find a specific object in a transmittal by its DRM class or ID.
- Navigate from object to object in an object tree hierarchy.
- Create bookmarks on transmittal objects.
- Copy and paste objects within and across transmittals.
- Create objects in a transmittal.
- Delete objects from a transmittal.
- Run an application on a transmittal from the main window.
- Locate an object in post-processing of syntax or rules checker via GUI.
- Configure GUI and transmittal traversal preferences.
- Add and Remove relationships between objects in a transmittal.
- Search the transmital for specific criteria using XML OMEs.
Return to: Top
The following list provides a summary of the improvements/fixes in the 4.1.1.1 release:
- Migrated Focus to SEDRIS 4.1.x compatibility.
- When created or edited, <Axis> instances now list for selection only the EDCS_Attribute_Codes and EDCS_Unit_Codes that are consistent with their data type requirements. (This does not cause any loss of data for existing <Axis> instances with invalid fields.)
- When created or edited, <Table Property Description> instances and <Variable> instances now list for selection only the EDCS_Unit_Codes that are consistent with their data type requirements. (This does not cause any loss of data for existing objects with invalid fields.)
- Eliminated a limitation on the maximum size of an array field that could be displayed.
The following list provides a summary of the improvements/fixes in the 4.0.1.2 release:
- Added the necessary fixes so that Focus can now correctly view and edit ITR transmittals.
- Fixed the problem that was introduced in version 4.0.1.1 that caused new components not to show up in the viewer right away.
- Fixed numerous small bugs.
The following list provides a summary of the improvements/fixes in the 4.0.1.1 release:
- Fixed a bug that caused Focus to crash when searching for objects of a specific type. Problem was caused by a static global fixed size string that was being overrun when the path to a specific object was long, or deep in the transmittal, causing the overwriting of other variables.
- Fixed a bug that caused an "out of heap memory" exception when trying to search a transmittal using the OME interface and the resulting matching set was large.
- Fixed a caching problem with the storage and retrieval of mathcing objects from the OME search.
- Re-worked the OME search interface for flexibility and ease of use.
- Added a progress bar that displays the time elapsed for OME searches that take a lot of time.
- Added a way to stop an OME search and return all matches up to that point. Works well when the search seems like it's returning more objects than you expected your OME to return.
- Separated the object set window from the match information window.
- Added an option to open an object set from the Search Menu.
- Added a button in the object set viewer to change the stf that the matching objects apply to.
- Added additional information to the object set format such as the originating transmittal name, the OME name, and the OME file name.
- Added a button to the object set viewer to view the object set information.
- Added an option to save the object set as an XML object set (re-usable in Focus), or a list of plain object IDs.
- Fixed a bug in the Recent Files list.
- Fixed the background color of the MDI to a solid medium grey color.
- Added an enhancement that remembers the previous size and location of the Main window each time you open and close Focus. The initial size is still fullscreen the first time that you run Focus.
- Added options to object set window to allow for changing the number of objects to show at one time, and also a way for users to go to a specific index in the matching set.
- Added buttons for navigating through the matching objects.
- Upgraded the OME File viewer to a simple editor.
- Added Model Viewer as a pre-installed application.
- Multiple documentation fixes and enhancements.
The following list provides a summary of the improvements/fixes in the 4.0.0.1 release:
- Re-vamped the browse buttons on the Toolbar to make them more intuitive as far as behavior/icon/text names. New browse buttons on the Toolbar are Aggregate/Component, Previous/Next Sibling, and Step Up/Down in the view tree.
- Add a color chooser in for the RGB, HSV, and CMY Colour classes.
- Added new OME matching functionality with window that provides links to objects in object tree.
- Fix the Toolbar LayoutManager so that the icons are not arranged 2 x 2, but 1 x 1, when the toolbar is moved to the sides.
- Changed the version from v0.6 to 4.0.0.1.
- Fixed the Toolbar icons so that we can add a few new ones for future tasks. Involved creating all new simpler icons in the 24 x 24 and 16 x 16 sizes only without the anti-aliasing and shadowing. Fixed the System Preferences regarding the new icon sizes.
- SRM_VOS_Code was missing the first code called UNDEFINED so it was added.
- Made the toolbar icon text size smaeller so that it won't extend the icons outside of the application's viewable range by default.
- Added a Status Bar to the bottom of the Edit Area and changed a few of the 'message' type pop-ups to update the status bar instead of showing the pop-up message.
- Error file extension was always expected to be '.txt'. Fixed to allow any extension.
- Added Window Selector to the MenuBar for internal frame windows.
- TM Augmented 3D icon text was overwriting class type text so it was removed from all the location icon texts because it was redundant and was overlaying the actual class name text.
The following list provides a summary of the improvements/fixes in the 0.6c release:
- Fixed bug in array for credit_count in <Description> does not save to transmittal.
- fixed bug in VOS_Code type where it had a blank in comboBox at end.
- EDCS Info Window initial size was too tall. Resized to max initial size of 600.
- Fixed problem with EAV and Comination Field. The real_values and integer/count_values were grouped and had a different number of input items causing an exception when reading from the API.
- fixed problem with the history and String types in the EAVs.
- fixed problem with the Interval types layout, they're not filling the whole space as required.
- fixed problem with the history and the Interval types in the EAVs.
- Added ability to add one-way or two-way associations. Problem came up while trying to manually duplicate a tree in one transmittal into another transmittal and we couldn't replicate the one-way association to the <Geometry Model> from the <GMI>.
- Fixed layout of Real_Value in EAV - layout was not being set correctly.
- Combination Field regarding Property_Code and Element_Type. Made an adjustment to the update method in the Combination Field class to check the EAC's type to make sure that it's an Enum type before updating the EAVs.
- Fixed location icons in the browser. Also truncated 'Surface' to 'Surf.' for icon tags because 'Surface' is too long and it's overlapping the class type name.
- Added 'Save' question before running applications.
- Updated/fixed the User's Guide to match the current GUI. Required updating screen captures and in many cases the text. Re-worked the structure of the file to accomodate all aspects of capabilities without becoming too redundant.
The following list provides a summary of the improvements/fixes in the 0.6b release:
- Replaced the EDCS field 'definition' buttons with 'dictionary entry' buttons. This allows the user to make more informed decisions as to what they should select in regards to SE_Single_Values and EDCS_Attribute_Values.
- Added 'Close' button to File Menu to allow closing of all views of a selected transmittal.
- Fixed bug in 'Recent Files' behavior. Moved 'Recent Files' list into sub-menu of 'File' menu.
- Changed 'Help' files to use the default HTML browser instead of the basic HTML viewer Focus was providing.
- Added in an extra text field to the 'Find' dialog to allow users to copy and paste an entire object ID. Redesigned the 'Find' dialog for less confusion. Fixed bug in 'Find' dialog when selecting a type in the list that didn't exist in the transmittal.
- Added in new WindowListeners to the 'Edit' and 'Array Edit' windows to handle the window closing events from the 'x' button in the top right hand corner of the window.
- Fixed mismatched menu key commands and mnemonics for menu items.
- Made menus and the toolbar context sensitive.
- Fixed big in add and remove relationship dialogs in regards to read-only mode.
- Fixed several small bugs related to the 'System Preferences'.
- Fixed bug that wouldn't let user edit the SE_SRF_Info fields angular_units and linear_units.
- Added in wait cusor for objects with long load times, such as those using the EDCS.
- Added title text '(Read Only)' to internal frame title when applicable.
- Fixed bug in GUI when a transmittal view was deleted and another selected the toolbar would disappear.
- Fixed bug regarding the number of unfreed object references when trying to delete and object/tree.
- Fixed bug in 'Delete Object' that was orphaning rather than removing objects from the transmittal.
- Added validation to paste object/tree to make sure that the paste is valid before actually trying to paste (report to user).
- Fixed bug that returned a blank message to user when entering an orphaned object ID into the 'Find' dialog.
- Fixed GUI repaint artifact that happened to the menu bar when the toolbar was not repainted.
- Added 'Save' to the 'File' menu. This change allows the user to save the most recent changes without having to close down the transmittal, and in some cases Focus, and then re-open it to run an application on those recent changes.
- Added 'Save As' to the 'File' menu that allows the user to rename the currently selected transmittal.
The following list provides a summary of the improvements/fixes in the 0.6a release:
- Multiple Document Interface (MDI) to replace the tabbed pane and allow users to view transmittals side by side.
- Add and remove relationship options added.
- Fixed problem with dealing with link objects and their relationships.
- Fixed SE_Locale enumerants so that country and language are actually shown with the codes.
- Fixed bugs when editing arrays.
- Fixed the new/create object to only show valid classes that can be added below a parent class.
- Limitations on editing certain objects has been removed. Classes that pertain to <Data Table>s were previously blocked from editing so that the user could not invalidate the <Data Table>. Now all objects can be edited. A warning pop-up is now displayed if the object to be edited may affect the validity of a <Data Table>.
- Migration to SEDRIS 4.0.x
- Many minor misc. bugs fixed.
Return to: Top
The following list provides a summary of the major improvements planned for future releases:
- Add optimization to opening of ITR transmittals.
- Data Table Signature Selector only shows a maximum of 4 <Table Property Description>s. Need to fix it to show all.
- Add a way for the user to add all the required components to a single object in a single step.
- Make the "New Component" selection drop-down a multi-selection box.
- Add in capability to retrieve the transmittal's GIUD.
- Add in capability to allow user to run Defrag and also retrieve valuable data about the fragmentation and unused bytes in a transmittal.
- Upgrade Data Table Editor to handle SE_Intervals.
- Upgrade OME searches to report labels and their values.
- Switch OME to use the C++ OME from the SEDRIS C++ SDK.
- Switch all Focus JNI code to use the SEDRIS C++ API instead of the C API.
- Bugs reported with the previous versions not already addressed such as:
- Data Table Editor seems to hang after re-opening it a few times.
Return to: Top
The following provides a summary of the currently known defects and limitations:
- Find by ID and URN doesn't work when traversing ITR transmittals. This includes the OME searching object buttons and the error reporting object buttons.
- No current support for SE_Interval_Type in Data Table Editor.
- No current support for SE_String in Data Table Editor.
- No direct provision for expanding or eliminating data from <Data Table>s.
- No provision for importing or exporting data to and from <Data Table> or <Image> objects.
- When editing an object linked through an association, the result will not be reflected on the preview pane of that object although the new attribute values are stored in STF. Workaround: select another object and then re-select the original object to force preview pane refresh.
- When editing an object through an ITR link, the result will not be shown on the preview pane of the same object opened explicitly.
- There is a limitation on selecting enumeration type values in the EDCS_Attribute_Value type when the class that it resides in is a <Property Characteristic> or <State Data>.
In the case of the <Property Characteristic>, it is only a problem when the aggregate <Table Property Description> has an EAC of type enumeration and the user tries to select 'Enumeration' for the EDCS_Attribute_Value in the <Property Characteristic>, otherwise the EDCS_Attribute_Value behaves normally.
In the case of the <State Data>, it has a requirement based on the 'state_tag' field of the <State Related Features> or <State Related Geometry> object that the <State Data> is being used as a link object for. The EDCS_Attribute_Value has the same problem in this case when it comes to selecting the 'Enumeration' type for the <State Data>.
Both need to query another object to get their EACs, then query the EDCS to get the applicable EECs.Return to: Top
Hardware
- Recommended minimum CPU speed for Intel based machines is 650 MHz.
- Recommended minimum RAM for all supported platforms is 128 MB.
- Minimum disk space required is 30 MB.
Software
- Requires a JRE (Java Runtime Environment), version 1.4.2 or later, installed and set-up prior to its use. You can download the JRE from Sun. Follow the download and installation instructions on their site.
- Operating System
- Linux Red Hat 9
- Microsoft Windows 2K/XP
Return to: Top
To install, extract the contents of the compressed file:
- Unix
Use the "tar" and "gzip" commands to extract the application:
using the appropriate filename for "focus_file.tgz".gunzip -c focus_file.tar.gz | tar xf -If you have the latest GNU tar installed, you can use the following command instead:
tar xzf focus_file.tgz
- Win32
Use WinZip or other decompression utility to extract the application.
To run Focus, open a terminal or command prompt then change directories into the newly created Focus directory. Type "run_focus" to start the application. If using Windows Explorer, navigate to the newly extracted Focus directory and double-click on "run_focus.bat" to start the application. The Focus splash screen will dislpay followed by the Focus application main window. The splash screen will disappear shortly after the application starts or when clicked. Note: Focus requires a JRE (Java Runtime Environment), version 1.4.2 or later, installed and set-up prior to its use. You can download the JRE from Sun. Follow the download and installation instructions on their site.
Return to: Top
See Users' Guide.
Return to: Top
This section describes the following environment variable that are available for users to configure the SEDRIS runtime environment. The default values should be sufficient for most users:
- SE_API_MEMORY_MODEL
This variable allows the user to specify, at a high level, the amount of memory to use. Its allowed values are SMALL, MEDIUM, and LARGE. The default setting is SMALL. Each of these three choices will set the default values to the subordinate memory model environment variables SE_RAIF_MAX_OBJECT_CACHE_SIZE and SE_STF_BLOCK_CACHE_SIZE
- SEDRIS_RESOLVER_PATH
This variable specifies the path(s) where the SEDRIS resolution (*.rsl) files reside. There can be more than one resolution file in the paths provided. The default path is where the running application resides.
Please refer to the SEDRIS documentation for more detailed information about these particular variables.
Return to: Top
Questions, comments, and bug reports should be sent to help@sedris.org.
If you are an associate, please send email to se-coders@sedris.org.
Return to: Top
These links require Internet access.
Return to: Top
Copyright © 2007 SEDRIS