Changeset 22684 in main


Ignore:
Timestamp:
03/11/21 19:56:17 (5 weeks ago)
Author:
GarthBraithwaite_STG
Message:

nm epht - Brett's css tweaks. Updated ss props to new content and published content paths.

Location:
adopters/nm-epht/trunk/src/main/webapps/nmepht-view
Files:
5 edited

Legend:

Unmodified
Added
Removed
  • adopters/nm-epht/trunk/src/main/webapps/nmepht-view/WEB-INF/config/SiteSpecific.properties

    r20916 r22684  
    11#------------------------------------------------------------------------------
    2 # Site Specific Property Overrides for the NM EPHT IBIS-PH View app/system. 
    3 # These values are applied to the Spring context configuration bean definitions. 
    4 # The form is: beanID.propertyName = value
     2# Site Specific String Property Overrides for the IBIS-PH View app/system. 
     3# These values are Spring context configuration "string" bean definitions i.e.
     4# only string type bean values can be specified here.  See the ss.xml to override
     5# actual bean definitions.  The form is: beanID.propertyName = value
     6#
     7# IMPORTANT: For these values to be used, this string property override must be
     8# referenced.  This is typically specified via the siteSpecificPropertyOverrides
     9# bean which is a default core implementation that is typically contained in the
     10# config/srping/SiteSpecific.xml file.  There is typically a more specific
     11# property override file specified that is used for local development properties
     12# to be specified.  This property file is typically in the user's home directory
     13# (see the siteSpecificPropertyOverrides bean for a complete list of files refd).
     14#
     15# The use of this file is OPTIONAL.  These values can be specified in the ss.xml
     16# file as well but require more work as a complete, whole new bean with the same
     17# name will need to be defined.  This file is useful for poking string values into
     18# existing bean definitions or when specifying different values to be used while
     19# keeping the same war file deployable to multiple environments without mods.
     20#
     21# PATH CONVENTION:
     22# Paths shall have a trailing "/".  Sub paths should never have a leading "/"
     23# but will always have the trailing "/".  Base paths can have a leading "/" as
     24# this represents the root of the file system.
    525#------------------------------------------------------------------------------
    626
    7 #queryIBISQRequestPath.string =http://10.135.2.255/cgi-bin/hi_iq_func22.exe
    8 #queryIBISQRequestPath.string =https://ibistest.health.state.nm.us/ibisph-view/query/proxy/1.xml
     27#--- IBISQ/QueryApplication URL address.  For local, non sas development the
     28#       addresses can reference a proxy to the deployed IBIS View system which has
     29#       to be configured for the proxy request and is setup for the backend server
     30#       (the address to SAS Intrnet, or the actual address of the webserver/IBIS-Q
     31#       SAS CGI application).
     32#
     33#       Proxy request made to a view app that makes the actual ibisq request.
     34#
     35#       HTTPS NOTE: things like https://kyibis.mc.uky.edu/ehl/query/proxy can choke
     36#       because cert is not verified!
     37#
     38# Linux Example:        http://hlcbsas/cgi-bin/hi_iq_func
     39# Windows Example:      http://localhost/cgi-bin/hi_iq_func.exe
     40# Proxy Example:        http://ibis.mt.gov/query/proxy/temp.xml
    941queryIBISQRequestPath.string =http://10.135.2.255/cgi-bin/hi_iq_func3.exe
    1042
     43
     44#--- Content Paths.  Adopters should be splitting their content from the
     45#       ibisph-view webapp.  This allows the ibis webapp to be seperate from the
     46#       content which allows the content to be managed without having to touch the
     47#       deployed webapp.
     48#
     49#       There are two types of content published XML and static content.  Published
     50#       XML is the ibis-admin app's data that is published to XML files (org units,
     51#       topics, measures, published indicators etc.).  Static content include images,
     52#       json, pdfs, HTML_CONTENT XML files, query module XML files, SELECTION XML
     53#       files and any content that is maintained by hand.  Published and static files
     54#       can exist in different places although most adopters will likely keep them
     55#       together.  The exception is if the static content is on a different server
     56#       so that it is more easily managed while the published data is on a server
     57#       that has the ibis data admin app.
     58#
     59#commonContentBasePath.string =../../ibisph-content/
     60#commonContentBasePath.string =file:/d:/tomcat7/webapps/ibisph-content/
     61#commonContentBasePath.string =http://localhost/ibisph-content/
     62# THIS VALUE NEEDS TO BE THE URL TO THE PRODUCTION CONTENT SERVER
     63# FOR LOCAL DEV THE FOLLOWING VALUE SHOULD BE PLACED IN A USER PROPERTIES FILE AND HAVE A PATH LIKE:
     64commonContentBasePath.string =../nmepht-content/
     65
     66communityRequestPathPrefixToRemove.string =/dataportal/community/
    1167queryModuleSelectionModelMap.pathPrefixToRemove =/dataportal/query/selection
    1268
    13 #commonContentBasePath.string     =../nmepht-content/
    14 #IBISPHViewContentBasePath.string =../nmibis-content/
    15 commonContentBasePath.string =http://10.135.2.255/test/nmepht-content/
    16 IBISPHViewContentBasePath.string =http://10.135.2.255/test/nmibis-content/
    1769
    18 communityRequestPathPrefixToRemove.string =/community/
     70#--- Example of published XML on different server. 
     71#       The core code defaults to the published XML path being the same as the
     72#       content's XML path which in both cases is the base path with an "xml/" suffix.
     73#       If the published XML is in a different location then both paths should be
     74#       specified.
    1975
     76# THIS VALUE SHOULD BE THE PRODUCTION NM IBIS VIEW APP.
     77#commonPublishedXMLBasePath.string =https://ibis.health.state.nm.us/nmibis-view/view/xml/
     78# FOR LOCAL DEV THE LOCAL USER FILE SHOULD CONTAIN VALUE TO POINT TO TEST  or LEAVE IT POINTING TO PROD!
     79commonPublishedXMLBasePath.string =https://ibistest.health.state.nm.us/nmibis-view/view/xml/
     80
     81
     82#--- Explicit base server with app context request URL prefix.  This value is
     83#       the base of all view webapp page link requests.  If the value is blank then
     84#       the app creates a default value that is the first HTTP request's URL for
     85#       protocol, server name and context path.  For most situations this is default
     86#       value is preferred (fine being left blank so that the working actual request
     87#       URL is used).  However, in some deployments behind a proxy or if nervous
     88#       about the first working request not being correct (i.e. mixed HTTP HTTPS
     89#       deployments) then this value can be specified.  See notes in the
     90#       commonWebAppBasePathModelMap
     91#        (common.xml).  Default value: "".  Below is an example:
    2092#commonWebAppBaseRequestPath.string =https://nmtracking.org/
    21 commonWebAppBaseRequestPath.string=
     93
     94#--- For development users IF the above is set, place a local, user property
     95#    override file in the  [user]/ibisph-view.properties file with an entry of:
     96commonWebAppBaseRequestPath.string =
     97
    2298
    2399#--- self registered user email overrides
     100#    BELOW ARE PLACEHOLDERS that adopters using MyData should specify.
    24101userEmailVerificationService.mailMessageFrom =admin@nmtracking.org
    25102userEmailVerificationService.mailSubject     =NM EPHT - Self Registed MySelections Account Verification
     
    28105
    29106#----------------------------------- END OF FILE -----------------------------
    30 
  • adopters/nm-epht/trunk/src/main/webapps/nmepht-view/WEB-INF/config/spring/SiteSpecific.xml

    r22659 r22684  
    2424
    2525        <import resource="view.xml"/>
    26 
    27         <import resource="IBISPHViewContentPath.xml"/>
    2826
    2927
  • adopters/nm-epht/trunk/src/main/webapps/nmepht-view/css/_SiteSpecific-Topic.css

    r22605 r22684  
    1818
    1919        color: white;
    20         background: rgba(18, 81, 94, 0.3);
     20        background: rgba(18, 81, 94, 0.7);
    2121        text-align: center;
    2222        width: 100%;
     
    3333}
    3434
     35
     36.Topic #content
     37{
     38        padding: 30px 0;
     39}
     40
     41.Topic #content .NavigationPathSocialMedia
     42{
     43    margin:     0 20px;
     44}
     45
     46.Topic #content > header
     47{
     48    margin:     20px;
     49}
    3550
    3651.Topic #content > section,
     
    4358}
    4459
    45 
    4660.Topic #content header + section h2
    4761{
    48     margin-top:         1em;
    49 }
    50 
     62    margin-top:         15px;
     63        margin-bottom:  10px;
     64}
    5165
    5266/*
     
    7892.Topic #content > .SubSectionsContainer::after
    7993{
     94        margin-top: 50px;
    8095        background-image: linear-gradient(180deg, rgba(220,220,220, 20%) 1%, rgba(0, 0, 0, 0%) 100%);
    8196}
     
    104119{
    105120        position: relative;
    106         margin-bottom: 0.5em;
     121        margin-bottom: 20px;
    107122}
    108123.Topic #content section section h3::after
  • adopters/nm-epht/trunk/src/main/webapps/nmepht-view/css/_SiteSpecific-general.css

    r22571 r22684  
    3131{
    3232/*      padding:                        5px 0 3px 0; */
     33        margin-bottom:          10px;
    3334        font-size:                      1.5rem;
    3435}
    3536h3
    3637{
    37         margin-top:                     0.5em;
     38        margin-top:                     10px;
     39        margin-bottom:          10px;
    3840        font-size:                      1.1rem;
    3941        font-weight:            bold;
  • adopters/nm-epht/trunk/src/main/webapps/nmepht-view/css/_SiteSpecific-layout_navigation.css

    r22673 r22684  
    1212}
    1313
    14 
    1514#header
    1615{
     
    2827
    2928
    30 
    3129#searchAndLoginContainer
    3230{
     
    5351        margin:                         0 1em;
    5452}
     53
    5554
    5655#siteSearch
     
    107106
    108107
    109 #xxxxxxxxxxxxsiteNavigation
    110 {
    111         margin-top: 25px;
    112 }
    113108#siteNavigationMenu.HorizontalMenu
    114109{
Note: See TracChangeset for help on using the changeset viewer.