| |
|
| 1. |
Add Layer(s) button is added to Layer Manager form. |
| |
|
| 2. |
Add Layer(s) form can auto-record the used directories list. |
| |
|
| 3. |
Debug mode is switchable. In Non-Debug mode, Mobile Engine will not return exceptions actively. |
| 4. |
All objects support to import and export XML files. Through exporting properties of objects to XML files, the interoperability |
| |
with other SueprGeo 3 series products can be reached. For example, the project developed by Mobile Engine will be |
| |
compatible to SuperGIS Desktop, SuperPad, and SuperWebGIS through such built-in exporting function. |
| 5. |
Besides Label function being supported in SuperGIS Mobile Engine Beta 1, the Label function for Line layer is added in |
| |
Beta 2. |
| |
|
| 6. |
In SuperGIS Mobile Engine Beta 1, general symbols and unique symbols are supported already. Now in Beta 2, graduated |
| |
symbols are also added. In the future, more symbol styles will be available, including classified symbol, bar chart and pie chart. |
| |
|
| 7. |
Properties page form is built in objects, and display interface is available in Traditional Chinese and English. |
| |
|
| 8. |
SGToolBarButtonGroup class is added so that the toolbar group can be rapidly produced. Most GIS software installed in a |
| |
smart device works most of the functions by toolbar buttons, while the screen size of a smart device is not big enough to |
| |
cover all buttons. Plus, the project developed by .NET Compact Framework supports one toolbar control only, so various |
| |
toolbar buttons must be integrated and displayed as a list. In SuperGIS Mobile Engine, an object termed as a |
| |
SGToolBarButtonGroup is designed as a solution to enable developers to rapidly integrate multiple toolbar buttons into a group. |
| |
|
| 9. |
Smart devices with resolution in 640*480 or higher are supported. Although the current smart devices on market mostly |
| |
support resolution in 320*240, the adoption of high resolution panel to smart devices must be a future trend. Also, the |
| |
rendering quality will be improved. At present, resolution in 640*480 and 800*480 can be seen in market gradually, so |
| |
SuperGIS Mobile Engine takes the lead in supporting rendering with high resolution. |
| 10. |
The new toolbar buttons: |
| |
| A. |
OpenMapFileButton: |
The toolbar button can input map profile. It supports *.swg files currently and will support *.spm |
| |
|
files in the future to improve the compatibility to other SupreGeo products. |
| B. |
SaveMapFileButton: |
The toolbar button can export map profile. It supports *.swg and *.slr files and will support *.spm |
| |
|
file in the future to improve the compatibility to other SuperGeo products. |
| C. |
GPSStatusButton: |
Displays GPS status. |
| |
|
 |
| D. |
CameraButton: |
The toolbar button provides camera function. After photograph is taken, GPS information will be |
| |
|
written to the image file for photo navigation use. |
| |
|
 |
| E. |
CreatePhotoLayer: |
The toolbar button can produce photo layer and record coordinate information and image file |
| |
|
path to attribute table at once. With the hyperlink function button, users can open the related |
| |
|
photo files when querying a feature. |
| |
|
 |
| F. |
HyperlinkButton: |
The toolbar button offers hyperlink function. |
| G. |
MeasureButton: |
The toolbar button provides multiple measure functions, including polyline, freehand, rectangle, |
| |
|
radial and ellipse measures. |
| |
 |
| H. |
PanToGPSButton: |
The toolbar button provides panning map function. In the application of GPS integrated map, |
| |
|
besides the function of labeling GPS coordinates and trail on the map, directly panning map |
| |
|
to GPS position, which is pretty common in navigation application, is also a necessary |
| |
|
function. So, Mobile Engine is fixed to directly integrate such function and is able to specify the |
| |
|
map scale after panning |
| I. |
GPSNavigationButton: |
The toolbar button can display GPS navigation. |
| J. |
SelectFeatureButton: |
The toolbar button supports various ways to query feature attributes through selecting features |
| |
|
by point, polygon, ellipse or freehand. |
| |
|
 |
|