Changes between Initial Version and Version 2 of Ticket #40


Ignore:
Timestamp:
11/04/11 12:35:20 (13 years ago)
Author:
adube
Comment:

I've changed my mind with time. I think it's better to let the template (100% customized by user) to handle most the inclusions needed by widgets, including external libraries and such. The auto-including logic for printWidgetSource templates sometimes becomes a problem because the code is never compressed.

We could have something to handle including widget code for 'dev' purpose, but for the rest it should be controlled by the user.

I'm moving this to 'Future' until we think that is becoming an issue at some point.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #40

    • Property Component documentation → widgets
    • Property Milestone → Future
    • Property Priority major → minor
    • Property Type defect → enhancement

  • Ticket #40 – Description

    initial v2  
    33It would be nice if the widget docs made these requirements more explicit, or better yet if including the widget in your project it would automagically add any required template fragments into your template.
    44
     5For the resultextgrid, on the contrary, the code in core should definitively be moved from there at some point.
     6
    57This could be a doc or widget defect/enhancement.