Uploaded image for project: '{RETIRED} Curriki'
  1. {RETIRED} Curriki
  2. CURRIKI-3258

Asset conversion changes Wiki syntax into HTML in the output and seems to have added some garbage.

    XMLWordPrintable

Details

    Description

      It appears the content conversion not only copies the content of the text asset class into the asset content direct, it seems that the conversion turns the wiki syntax into generated HTML. Please inspect the following resource and compare between Beta and Nest:

      http://next.dev.curriki.org/xwiki/bin/view/Coll_jmarks/CurrikulumBuilderOverview e.g. http://beta.curriki.org/xwiki/bin/edit/Coll_jmarks/CurrikulumBuilderOverview?editor=object

      compared to

      http://beta.curriki.org/xwiki/bin/view/Coll_jmarks/CurrikulumBuilderOverview e.g. http://next.dev.curriki.org/xwiki/bin/edit/Coll_jmarks/CurrikulumBuilderOverview?editor=wiki

      Before conversion the content is the following text:

      1.1 Overview of the Currikulum Builder Application
      
      The Curriculum Builder is a javascript application designed to make it easy and fast to create and edit a hierarchical collection of assets. It is intended to be used "Full screen" and be WYSIWYG (What you see it what you get). 
      
       When you edit a collection in the Curriki Currikulum Builder you have a Table of
      {image:CB TOC.PNG|303|172| |floatright}Contents on the left to navigate between the different elements and levels in the collection. You also have some mode tabs on the top to view the metadata for the collection being edited and the assets inside, for viewing the comments for assets, and to view the history to compare or revert to prior versions.  The Curriculum Builder has "Specific Displays" for editing different types of assets. The asset types the currikulum builder current understands are: 
      * {style:type=div}Wiki text blocks like this one{style}
      * {style:type=div}HTML blocks that can contain most styles of HTML content{style}
      * {style:type=div}Image files of web displayable format (GIF, PNG, JPEG, etc.) {style}
      * {style:type=div}MP3 Audio files{style}
      * {style:type=div}Zip file archives- including the ability to access individual files in an archive{style}
      * {style:type=div}(Coming soon) Video upload and capture with streaming playback. {style}
      
       This collection will demonstrate each of these types of assets and the special display and edit capabilities for each. 
      
        
      {table}
      Content Type|Features|Limitations
       Text block|{style:type=span|color=#ff0000}~~__styled__~~{style} Text, Images, formatting, attachments and links|Complex tables
       HTML|Anything you can do in HTML, including Style sheets, Javascript (With limitations for cross site scripting) etc.|Browser issues in HTML and JS support
       Image|Size, captions|Only browser displayable formats (PNG, GIF, JPEG, etc.) No TIFF or SVG support for display.
       Flash/SWF|Plays in interface or in its own window|Almost no limitations for pure SWF files. Client needs plug-in
       Audio|Supports playback in site for MP3 files|No embedded player for other formats (OGG, Windows Media, AAC etc.) 
       Video|Upload and embedded playback (Or download) of almost any video format and CODEC, much like YouTube.|Some practical file size limitations (200MB+ is problematic) 
       ZIP Archives|Upload SCORM archives, or any file archive. Access individual files or launch archive in its own window using a start file.|Some practical file size limitations (200MB+ is problematic). Some archives can contain files with bad encoding
      {table}
      

      The following in the content conversion on Next we see:

      <h3 class="heading-1-1" id="HOverviewoftheCurrikulumBuilderApplication"><span>Overview of the Currikulum Builder Application</span></h3><p/>
      The Curriculum Builder is a javascript application designed to make it easy and fast to create and edit a hierarchical collection of assets. It is intended to be used "Full screen" and be WYSIWYG (What you see it what you get). <p/>
       When you edit a collection in the Curriki Currikulum Builder you have a Table of
      <div class="imgfloatright"><img src="/xwiki/bin/download/Coll_jmarks/CurrikulumBuilderOverview/CB%20TOC.PNG?height=303&amp;width=172" height="303" width="172" alt="CB TOC.PNG" title="CB TOC.PNG"/></div>Contents on the left to navigate between the different elements and levels in the collection. You also have some mode tabs on the top to view the metadata for the collection being edited and the assets inside, for viewing the comments for assets, and to view the history to compare or revert to prior versions.  The Curriculum Builder has "Specific Displays" for editing different types of assets. The asset types the currikulum builder current understands are: 
      <ul class="star">
      <li><div style="" >Wiki text blocks like this one</div></li>
      <li><div style="" >HTML blocks that can contain most styles of HTML content</div></li>
      <li><div style="" >Image files of web displayable format (GIF, PNG, JPEG, etc.) </div></li>
      <li><div style="" >MP3 Audio files</div></li>
      <li><div style="" >Zip file archives&#45; including the ability to access individual files in an archive</div></li>
      <li><div style="" >(Coming soon) Video upload and capture with streaming playback. </div></li>
      </ul> This collection will demonstrate each of these types of assets and the special display and edit capabilities for each. <p/>
        
      <table class="wiki-table" cellpadding="0" cellspacing="0" border="0"><tr><th>Content Type</th><th>Features</th><th>Limitations</th></tr><tr class="table-odd"><td> Text block</td><td><span style="color:#ff0000; " ><em><em class="underline">styled</em></em></span> Text, Images, formatting, attachments and links</td><td>Complex tables</td></tr><tr class="table-even"><td> HTML</td><td>Anything you can do in HTML, including Style sheets, Javascript (With limitations for cross site scripting) etc.</td><td>Browser issues in HTML and JS support</td></tr><tr class="table-odd"><td> Image</td><td>Size, captions</td><td>Only browser displayable formats (PNG, GIF, JPEG, etc.) No TIFF or SVG support for display.</td></tr><tr class="table-even"><td> Flash/SWF</td><td>Plays in interface or in its own window</td><td>Almost no limitations for pure SWF files. Client needs plug&#45;in</td></tr><tr class="table-odd"><td> Audio</td><td>Supports playback in site for MP3 files</td><td>No embedded player for other formats (OGG, Windows Media, AAC etc.)</td></tr><tr class="table-even"><td> Video</td><td>Upload and embedded playback (Or download) of almost any video format and CODEC, much like YouTube.</td><td>Some practical file size limitations (200MB+ is problematic)</td></tr><tr class="table-odd"><td> ZIP Archives</td><td>Upload SCORM archives, or any file archive. Access individual files or launch archive in its own window using a start file.</td><td>Some practical file size limitations (200MB+ is problematic). Some archives can contain files with bad encoding</td></tr></table>
      

      Clearly the two are different.

      Attachments

        Activity

          People

            jmarks Joshua Marks
            jmarks Joshua Marks
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: