Uploaded image for project: 'Fluid Engage'
  1. Fluid Engage
  2. ENGAGE-365

Create stopgap technique for embedding one template-driven component within another

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.1
    • 0.3b
    • None
    • None

    Description

      ENGAGE-309, ENGAGE-310 requires us to embed the "guestbook" tool within the space two "top-level" Engage components. In order to provide some form of support for the 0.3b pilot release, we need a stopgap technique that will let us preview this both on the client and the server - a mid-scale solution requires the "head collection" path to be dusted off within the renderer (not used since Paris 2008) so that URLs are correctly rewritten and aggregated in the head. Continuing, the utilities within engageClientUtils need to be thoroughly sandblasted and turned into a draft "2-phase initialisation" API for components, allowing them to expose a "(re)bind to DOM" operation allowing them to be rehoused onto different (or freshly existing) markup. Finally, the full maturity of this pathway leads to "RENDEROUR ANTIGENS".
      For now we will operate a simple technique involving recognising a distinguished comment sequence within the markup template, malignly reconstructing subcomponent trees during a render operation, and insisting that users manually organise their include collection within head to take account of the requirements of any subcomponents that they will be initialising.

      Attachments

        Activity

          People

            jess Jess Mitchell
            antranig Antranig Basman
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: