Bug 627 - [Chameleon - PopUpStyle] New Shared Resource PopUpStyle
: [Chameleon - PopUpStyle] New Shared Resource PopUpStyle
Status: NEW
: Chameleon
Core
: 1.99
: PC Windows 2000
: P4 enhancement
: FUTURE
Assigned To:
:
: Need Product Discussion - 20041102
:
:
:
  Show dependency treegraph
 
Reported: 2004-08-24 20:50 by
Modified: 2004-11-02 15:23 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2004-08-24 20:50:52
[Chameleon - PopUpStyle] New Shared Resource PopUpStyle

PopupStyle Shared Resource - There should be a new shared resource defined like
the Textbutton shared resource that allows all popup attributes do be defined
within a shared resource. 

Suggested changes for this to happen:

1) This will require creating a new attribute that for the attribute for
PopUpStyleResource to call the name of a specific PopUpStyle shared resource.

2) Since there is already a PopupStyleResource for the textbutton shared
resource. It is recommended that this attribute be changed to
PopupButtonResource, or PopupButtonStyleResource.

In my oppinon this is a bug since, so it is difficult to determine weather this
should be an enhancement or a development feature requiremed for 1.99. Darren
and Paul should talk this one over.
------- Comment #1 From 2004-10-12 22:21:28 -------
Chris, I think what you are looking for is to replace the widget attributes that
define the style of popups (like whether to inlude scrollbars, status bar etc)
in a SharedResource and then point to the shared resource using a new attribute.

This could be useful but I think in general it would be better to define good
default values for these and make them non-mandatory (I think popupwidth and
popupheight are mandatory but probably shouldn't be).

As a side note, popup styles (either as attributes or in a shared resource)
should define the ability to decide which 'spinner' to use in any given popup. 
Currently, the same spinner is used everywhere which is sometimes inappropriate.

Since the capability to perform most of this exists, I'm changing to an
enhancement.  Since it is not required for 1.99, I'm targetting as FUTURE.