CSCI321 - Project Diary

Thursday, August 3

Generic Portal Page Design

Well, last post I said I wrote down some idea's on the portal design and some functionally...

What I have next is what I see each page needs to contain:


{Script Header/Key/vrl/DTD}
{Top Nav Definition}
{Login Script/Code and check}
{Interaction Code/ Requests/ Left Nav "features"}
{Display - Map}
{Interactive/interaction Code}
{End/Footer}


Now, here are some more notes on a couple of them...

{Display Map}
  • createMap
  • addControls
  • setCentre(Based on unit(s) location)
  • displayCurrentLocation as Marker
    • UUID -> Use a Nickname,
    • lat/long (georeferencing -> Address - assumes land based),
    • Current Speed,
    • Current Direction,
    • Reading Type,
    • Time reading Taken, and
    • Time reading received.
  • Different Markers for different states
    • Speed Ranges,
    • Reading Type, and
    • Age of Reading.
{Interactive/interaction Code}
  • onclickMarker
    • Display some of the above info in Tab's
  • History Display
    • Date range/Number of points
      • Display as markers, OR
      • Display as line
  • Geofencing
    • Click, define radius,
    • Inside or Outside alert,
    • Set/Save to DB,
    • Define alert method,
      • Marker/icon colour,
      • popup,
      • email, and
      • SMS.
  • Speed Alerts
    • Define speed (Max/Min)
    • Set/Save to DB
    • Define alert method
      • Marker/icon colour,
      • popup,
      • email, and
      • SMS.
Roman and I need to define the API which we are going to use to interact within the portal, while we need to let Andrew know what functions he needs to create, and what trigger are needed.

Shawn

0 Comments:

Post a Comment

<< Home