[Chameleon-dev] [Bug 957] New: Popup widgets: implement POPUPPAGE
attribute
bugzilla-daemon at maptools.org
bugzilla-daemon at maptools.org
Fri Feb 11 08:25:15 EST 2005
http://www.maptools.org/bugzilla/show_bug.cgi?id=957
Summary: Popup widgets: implement POPUPPAGE attribute
Product: Chameleon
Version: 2.0
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: enhancement
Priority: P2
Component: Core
AssignedTo: chameleon-dev at lists.maptools.org
ReportedBy: bartvde at xs4all.nl
CC: thijs.brentjens at geodan.nl
We could do that as part of the Popup.php code so that all popups
inherit the capability ... this would add a new attribute to every
widget that supports popups, something like 'POPUPPAGE' and you would
provide a URL to that page ...
Paul
bartvde at xs4all.nl wrote:
> Hi list,
>
> we are struggling with what is the best option to maintain a separate look
> and feel for the standard Chameleon widgets.
>
> E.g. for the ExpressionBuilder widget (and for many other widgets too), we
> have changed the HTML look and feel quite extensively (also the workflow
> in the GUI), which has resulted in a custom version of
> ExpressionBuilder.phtml. Ideally you would want to manage this whole
> system with css, but I doubt this is a possibility right now.
>
> I can see a few options for maintaining this kind of system:
> -creating a copy of the standard widget and renaming it, but this is not a
> very well maintainable option.
> -is it possible to create your own widget, which inherits from the
> Chameleon widget, and then only change the phtml file used in the widget?
>
> What I would like to see personally maybe as an option, would be to have
> an attribute on every Chameleon widget, with which you can override the
> phtml file used.
>
> Any thoughts on this subject?
>
> Best regards,
> Bart
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the Chameleon-dev
mailing list