Uploaded image for project: 'XWiki Platform'
  1. XWiki Platform
  2. XWIKI-2568

Continue implementing the new Rendering Architecture

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.5
    • Fix Version/s: 1.6 M1
    • Component/s: {Unused} Rendering 2.0
    • Labels:
      None
    • Similar issues:

      Description

      what's left:

      • Link parsers + -link rendering (XWikiSyntaxRenderer)-
      • Caches
        • Add suppor for caching macro block generation
        • Add caching of "static" blocks
      • More syntax support
      • -Finish implementing the xhtml, velocity macros (parameters support)-
      • Implement all missing macros (all the radeox macros we had)
      • Modify document link saving (no need for rendering, just parsing)
      • -Make preview work-
      • Find a way to move all old rendering code to a separate package so that it can be easily removed later and so that we have some clean code left (if possible)
      • Make the XHTML parser fully work (lots of issues, see http://code.google.com/p/wikimodel/issues/)
      • -Make Inline mode work-
      • --Modify the Document Information panel in edit mode so that it lists all doc that are included with the new rendering {include}

        macro.--

      • Question: how do we support automatic inline editing?
      • Decide on syntax elements
        • -escaping blocks of text- ({ { { } } } - need to be implemented in wikimodel)
        • -double curly braces for macros?- (yes)
        • images in links?
        • -Tables in wiki syntax?- (no, only macro)
        • quotation character and quotation blocks
      • Check for view rights in the include macro
      • Groovy refactoring and new grooy module/components
      • Add translation support in include macro
      • -Add api to convert parameters in values (boolean, integers etc.)-
      • -Modify macro api to be able to know where the processed macro is located in the XDOM-
      • -Add id Block (and it's corresponding macro that add the block in the dom) which generate anchor in HTML for example to be used has target in the links-
      • TOC macro:
        • -generate list tree from sections-
        • -support "numbered" parameter-
        • -support "scope" parameter-
        • add internal link targeting sections (temporary solution already committed waiting for LinkBlock to support children blocks as label)

      ... and a lot more I'm sure (this list should be edited as we progress)

      See http://dev.xwiki.org/xwiki/bin/view/Design/NewRenderingArchitecture for Architecture details

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                vmassol Vincent Massol
                Reporter:
                vmassol Vincent Massol
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Date of First Response: