| View previous topic :: View next topic |
| Author |
Message |
DC Kelley Site Admin

Joined: 24 Jun 2004 Posts: 1068 Location: Lost in LA
|
Posted: Thu Jul 22, 2004 9:06 am Post subject: Installing the Mini-Edit tool for the first time |
|
|
UPDATE Sept 28th 2005
Mini-Edit is now provided in two flavors.
You can get Classic Mini-Edit here, which has all the basic functions and is a mature release at:
http://www.itsware.net/MiniEdit/classic/ReadMe.htm
You can get the last Beta Release of Mini-Edit, which has recently released features you may want at:
http://www.itsware.net/MiniEdit/beta/ReadMe.htm
________________________________________
Installing the Mini-Edit tool for the first time involves making sure you have all the common DLL that are needed by the program. Much of this same information is available at: http://www.itsware.net/miniedit/Install.htm
Use the installer script located at
http://www.itsware.net/miniedit/Install_Current_Mini-Edit.msi
Simply runs the above script by downloading it then clicking on it. It will install the program in the normal way.
After running this script you will have an outdated copy of the tool installed (as well as all the support files), which you must then update.
Updating occurs by downloading the most current release on top of your old copy. Always update BOTH the application (Mini_Edit.exe) and the control file (MEDIT_Settings.mdb) if you wish to upgrade. Click the below link, follow the directions, than save the file (overwriting) your old files.
http://www.itsware.net/MiniEdit/classic/ReadMe.htm
Now you simply need to find a DB for the message set you wish to operate on. Most SDOs give these out if you ask. The TMDD one and some trivial example ones are present in the same directory as the above tools at: http://www.itsware.net/miniedit/ReadMe.htm |
|
| Back to top |
|
 |
 |
FHWA requests your thoughts on:
Building a Reference Implementation node
Read the request and thread, and get the survey form here
|
Consider how much easier YOUR life would be if there was place
on the web where you could go to see ITS work or to test your own
work.
Please participate in the survey.
|
|
|
|
|
DC Kelley Site Admin

Joined: 24 Jun 2004 Posts: 1068 Location: Lost in LA
|
Posted: Thu May 12, 2005 2:13 pm Post subject: Current status |
|
|
Updated May 2005
Just at the moment we are stuck in how we distribute this tool to non-SDO users. FHWA has agreed to continue the funding of the tool and IEEE has agree to take over the coordination and management aspects of thing (from the SAE), but the actual contracts to do all this has not yet be let. This also involves a bunch of improvements that the SDO collectively said they needed and which FHWA has agreed to fund. When all this is settled out (prob the end of May) the most current releases will be posted openly again. Until then, the slightly outdated one that the installer script places on your machine will work fine, but it lacks many of the new features people want. The DBs of the SDOs will work with either release. |
|
| Back to top |
|
 |
Site Admin Site Admin

Joined: 24 Jun 2004 Posts: 368 Location: Off at yet another ITS standards meeting
|
Posted: Thu Sep 29, 2005 10:57 am Post subject: |
|
|
Update Sept 28th 2005
We are now under contract again, now sponsored by IEEE for this work (we continue to perform other tasks for SAE such as the ATIS development but they have no involvement in the funding of the Mini-Edit project moving ahead). This set of improvements, the so called "critical feature list" that the SDOs developed should be completed by early 2006. We will be releasing beta versions to any user who wants the intermediate releases during the development time.
The best place to track the releases is at
http://www.itsware.net/MiniEdit/beta/ReadMe.htm
We are also including more automation between the tool and this site so that a number of new features will keep both standards developers and end deployments user in sync with changes to other peoples databases. This will include the limit ability to browse for database and schema's produced by other that you may need to obtain. Before anyone asks, no we are not building a formal registry at this time. The inability to establish common business relationships between the SDOs represents a major obstacle to that at present (in other words, don't shoot me I'm only the programmer). |
|
| Back to top |
|
 |
|