Zum Hauptinhalt gehen

HTML5 Viewer maturity from the user communities perspective?

Permanently deleted user

Guys, 

About to embark on SL to HTML5 (v2.3) prototype; hence keen to here what are the gotcha's that any of you have faced in this path?

We'll be working closely with Latitude on this but i just want to get a gauge of the maturity of the viewer for those users experienced first hand with the SL viewer and hav done the upgrade path.

Also keen to understand how your business has also recieved it vs the SL viewer?

Thanks

Brad

0

Kommentare

2 Kommentare

Datum Stimmen
  • Chris Dunlop

    Ive just done the same, and here are some things I had to watch out for:

    • Feature descriptions - hyperlinks - need to add target="_blank" to each one.
    • I had to reformat all feature descriptions to get rid of extra spaces etc.  I had to change all feature descriptions to use <div> for crlf.  Previously they were all <p> which SIlverlight interpreted as single line crlf.  (incidentally, I now only use Chrome to run Site Manager - IE11 is flaky for editing rich text) 
    • if you have any RunWorkflowByID hyperlinks in feature descriptions, make sure it's RunWorkflowById (Id, not ID) as HTML5 is much pickier about case.  If using the RunWorkflowWithArguments, make sure the workflowId variable is also cased properly.
    • data links - some didn't work.  I had to redefine the linking attribute so that the fully qualified field name was used.
    • HTML5 doesn't have right click menu capabilities out of the box, so I added it from the sample in the code gallery
    • Initial/Full extents didn't work correctly in HTML5, so I had to adjust them
    • I had to resize icons for the I Want To menu (32x32 down to 24x24) to make them fit better

    It took a lot longer to convert than I thought it would...

     

    Our Silverlight sites had several functions that are currently not available in HTML5:

    • No Reports option (where you pick the report and define the area graphically). 
    • Rich drawing tools (arrows, triangles etc)
    • Share Map/Export Map etc
    • Dynamic symbolization

    In spite of this, I ported our external sites over to HTML5 and made them live.  For our internal sites (with more advanced users), I'm holding off until 2.4.

    Good luck!

    Chris

     

     

     

    0
  • John Nerge

    Great list! If the reports option is important for you and you need to move to HTML5, you can replicate the behavior with a workflow that uses Get Display Capture Geometry, Query Task, and Run Report. I've even added a display form to choose the report I want to run with a combobox.

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Sie haben nicht gefunden, wonach Sie suchten?

Neuer Post