Uploaded image for project: 'Fluid Infusion'
  1. Fluid Infusion
  2. FLUID-4884

Implement integrated and portable system for debugging and browsing framework activities operating on IoC trees



    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 3.0
    • Component/s: IoC System
    • Labels:


      The more sophisticated and powerful the IoC framework becomes, the harder it becomes to tell what it is doing. The value proposition behind an increasingly declarative idiom for expressing code clearly points to its tendency to facilitate the creation of an ecosystem of sophisticated browsing, debugging, and authoring tools, which we expect to have their power enhanced by removing the need for them to parse and interpret raw JavaScript code.

      However, we actually need to build such a system, and the more work we defer to the framework, the more urgent the need becomes. Some initial description of the work was done by offering it as a 2012 GSoC project, described here - http://wiki.fluidproject.org/display/fluid/Google+Summer+of+Code+2012+with+the+Fluid+Project - but unfortunately this project was not taken up.

      With our increased focus on authoring tools over the next few years with various projects (FLOE, Prosperity4all, etc.) we need to start formalising our ideas for design in this area and start work on the various primitives (e.g. browsers for configuration and other material expressed as JSON structures, dedicated graph widgets for visualising code structure) that are required and common across all these authoring scenarios. This JIRA and probably over time some dedicated wiki areas will be used as an area for collecting our design and implementation thoughts for this problem.


        1. Decapod-IoC.jpg
          1.54 MB
          Justin Obara



            Unassigned Unassigned
            antranig Antranig Basman
            0 Vote for this issue
            4 Start watching this issue