[Chameleon-dev] [Bug 133] New: [Chameleon]CWCJSAPI Widget or SharedResource?

[bugzilla-daemon@www.maptools.org]

http://www.maptools.org/bugzilla/show_bug.cgi?id=133

           Summary: [Chameleon]CWCJSAPI Widget or SharedResource?
           Product: Chameleon
           Version: 1.1
          Platform: PC
        OS/Version: Windows 2000
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Widget
        AssignedTo: chameleon-dev@lists.maptools.org
        ReportedBy: thorne@dmsolutions.ca


Can we really say in our documents that the CWCJSAPI is actually a widget?

I perssonnelly feel that this feature (extension) to Chameleon cannot be
described as a widget as it is in the Widget Docs. 

When reading the CWC2JavascriptAPI.html document it suggests that it is a major
enhancement and extension to the Core of Chameleon. The difference is that this
CWCJSAPI can be turned on or off by adding the <CWC2 TYPE="SharedResource"
NAME="CWCJSAPI"/> & <CWC2 Type="CWCJSAPI" DEBUG="False"/> to a template. Even
the tags themselves do not seem to make sense to me, from a users point of view. 

Here is what I suggest, that no longer should the CWCJSAPI be defined as a
WIDGET but rather a "Shared Resource" for all potential Widgets. This will mean
that we can remove the Widget tag and place the DEBUG parameter within the
Shared Resources. He is what it may look like:

<CWC2 TYPE="SharedResource" NAME="CWCJSAPI">
   DEBUG="[True|False"]
</CWC2>

These changes should be reflected in the documentation. But first There should
be a Shared Resources Doc or Section.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.