- the alttext for images still didn't seem to appear in a google search, so added a little more actual text describing the errors encountered, with hopes that google will find this page
- updated the common problems page to have descriptive alt descriptions for the images about the windows ipv6 startup error, this should hopefully lead to more google hits when searching for the description
- common problems page:
- renamed the caveData section to be more clear
- install cave page:
- added a link to the blog posts with our awips release notes
Slight clarification for setting the environment variables for the windows direct install.
Added a bullet point specifying these needed to be created using the "New..." buttons on the Environment Window.
- updated images to remove version number from them
- updated caveMacUserInstall.png to have a border and look a bit more consitent
- added note and image about running CAVE the first time prompts for permission because it was downloaded from the internet
- have the instructions for awips-python.pkg come first, so the user doesn't just install cave and then skip this step
- updated with images for the pkg installer, and removed old screenshots, since now it's signed and notarized, those warnings don't appear
-Removed steps that are now done either in the awips_install.sh or edex bash script
-Updated information that needs to go in /etc/hosts
-Added step to start LDM
-Added new section to specify the registry.xml LDM file and how you can increase the queue size
-Added a lot more RGB products all with images
-Updated the GLM area
-Added new section for DMW
-Added new section for vertical temp/moisture profiles
-Specified which sectors had derived products
-Updated all images
- changed the requirements to specify C++ Build Tools 2015, but not the "Update 3" or version number, since that's different with these new instructions
- fixed a typo of 20215 to 2015
- added a comment about uninstalling software first before redoing necessary installation steps to fix the incorrect jep install for the windows direct installation
- replaced all '> Note' notes with either '!!! note' or '!!! warning' as appropropriate, for more consitency on our website
- updated steps 4 and 5 of the download and installation instructions for the direct windows download to include the new steps to use the new build tools installer to install the proper C++ build tools packages and then run the pip installs
- added screenshots for clarity
- added a new subsection in the common problems page titled "Products Not Loading Properly in Windows" and added some description, and a screenshot of the behavior when jep isn't installed properly
- added a link back to our installation instructions telling them to redo steps 4 and 5
- changed all '>' style notes to the '!!!' style
- moved the "run as root" message to the top of the page and removed it from each subsection
- added 'sudo vi /etc/yum.repos.d/awips2.repo' command in the second section, for clarity
- updated three images: gitImport2 - changed the path, runApplication % debugApplication - extended the view so you can see the project in the project explorer
-added notes about running as root when applicable
-added a note to check for libGLU package (because this was an issue I encountered when creating a ADE VM from scratch)
-alphabetized our git clone list and added the goesr repo
-added note about switching branches if desired, before importing into eclipse
-updated the command for running eclipse (no longer has '.sh' on executable)
-Reformated section 5 to have subsections/subheaders
-made paths more specific in section 5 so there is no confusion on where settings are to be found
-added screenshots for importing git repos and cleaning workspace
-reformated section 6 to have subsections/headers
-added screenshots for clarity
install-cave.md:
- add a requirement to the top of the General Requirements section stating "local machine"
- add a note after that saying ssh tunneling and x11 forwarding are not supported, with a link to our new section in the Common Problems page about remote access options
common-problems.md:
- add a new subsection called "Remotely Connecting to CAVE"
- say that x11 fowarding and ssh tunneling are not supported and we highly recommend running CAVE locally
- add some comments about nomachine and realVNC as well as ultraVNC
- add a note saying these software packages will most likely require configuration or installation on the remote machine to be done by an administrator
- added some text in the beginning describing how/where to find the VB
- added an image highlighting the menus
- moved some text into it's own subsection for the Visual Overview
