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.
- 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
- 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
Updates to website for info on remotely connecting to cave:
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
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
- added a subsection to the Map Editor for Adding a New editor and for Renaming an Editor
- Added text to be a little more clear when referring to the file menu (in the add map section as well as the add projection section)
- replaced the old gif for adding a tab with a new one that reflects the current menu options
- added a new gif for renaming map tabs
Added all the images that were supposed to go in with the previous commit for updates to the d2d perspective page
- in the "Hold-Right-Click Resource Name for Menu" subsection, removed the parenthesis text right-clicking to toggle visibility since this is incorrect. The correct usage is left-clicking to toggle visibility and that appears correctly in a previous subsection.
- After the gif in that same section, added text explaining this menu also has the option for unloading the selected dataset, which might be useful
- In the Display Menu section, moved the order of Sampling Loaded Resources to come before the Two Panel Display subsection
- in the 2-panel section removed the original text in parentheses talking about loading data since I explain in more detail now.
- Added a "Note" about how the cursor does the same in both panels in the 2 panel display
- added a screenshot for this functionality
- added a text explaining data loads to both panels by default but there is an option to load to a specific panel
- added a screenshot for the option to load to a specific panel
- added text pointing out the the ability to pick one panel to load to
- added screenshot of the panel with the L in bottom left
- added new subsection with text and screenshot for unloading data using the Display Menu
-added a note stating that users should use the exact links and specific versions we specify in our instructions, and that deviations from this may caus problems
docs/index.md:
-changed the python-awips link from the readthedoc site to our python-awips page in the user manual
-added a note after python-awips "(a python package)"
-added a section after "Download and Install EDEX", titled "Working with Python-AWIPS" which links to our python-awips section of the user manual
install/install-cave.md:
-updated the windows direct install system requirements to include "python3.7" for the miniconda install specification
-added the "python3.7" specification to step one of the install
-added a screenshot of the miniconda install showing the checked boxes for path and default python options
-added the full path for the jdk install under step 2, bullet 2
-updated the environment variables screenshot to have 181 which is what we're distributing
python/overview.md
-changed the title from Python API to Python-AWIPS
-Removed "DAF" from the description and reworded it slightly
-made the link to our documentation the entire last sentence instead of the word "here", and made the whole sentence bold
mkdocs.yml
-changed the name of the python outline link from "Python API" to "Python-AWIPS" and moved it up to under the EDEX User Manual
