[icf-dev] custom properties for widgets in the repository

Posted by LegacyUser on 18-Feb-2003 05:01

Hi,

we are developing a visual basic renderer for the dynamics repository data.

the visual basic frontend calls appserver routines to get the actual

repository data when rendering containers or viewers. so far - so good.

to gain the biggest possible help from the dynamics tools we tried to stay

as close to progress widget definitions as possible but that is not possible

in every case, as we would limit the possibilities of the visual basic user

interface and some of our custom controls.

the dynamics tools/progress ade helps us a lot with datafields in viewers as

I am able (the dcu helpled here) to set up a datafield_site_1511 class

containing our custom properties extending the default dynamics datafield

class.

for simple controls (progress widgets) I need to be able define my own

properties as well. I tried to extend the DynButton class with a

DynButton_SITE_1511 class and added that to the icfprogress.cst file as

followed:

*BUTTON_SITE_1511 &Default IT focus Button

DESCRIPTION IT Focus Default Button

INHERIT &ICF Standard Button IT Focus

NAME buButton

The appbuilder seems to ignore this entry in the .cst-file (I have verified

that the correct .cst file gets useds) - I cannot find the button on the

appbuilder palette. I expect that the dynamic viewer editor of the

appbuilder treats class children of DynButton objects like DynButton

objects. This behaviour is allready there/intended for the general editing

possibilties of classchildren of the DynView or DynBrowse object type. The

same should be possible with all the dynamic widget classes.

I tested this with a posse_main download from 02/17/2003.

Before logging an issue I'd like to know if I made a mistake or if the

required feature is not intended by Dynamics development in general.

Regards,

Mike

mike fechner it consulting

Breite Str. 116

50667 Köln

Germany

Tel.: +49 (0) 221 / 27 609-40

Fax.: +49 (0) 221 / 27 609-41

Mobil: +49 (0) 160 / 700 82 29

mike.fechner@fechner.de

www.fechner.de

To unsubscribe, e-mail: dev-unsubscribe@icf.possenet.org

For additional commands, e-mail: dev-help@icf.possenet.org

All Replies

Posted by LegacyUser on 18-Feb-2003 09:39

Hi Mike,

The current appBuilder palette is currently designed to work with static

widgets only. It is currently not possible to specify dynamic widget

objects for palette items.

If you want your button to be available in the appBuilder palette, you need

to modify the .cst file as with any palette item and add the desired

attributes or trigger code for that button. If you want it as the default,

you need to specify the &Default name. You could add the following:

*BUTTON &Default

DESCRIPTION IT Focus Default Button

INHERIT &ICF Standard Button

NAME buButton

(list of attributes here}

Having said that, we are in the process of modifying the AppBuilder to store

the .cst information in the repository.

(See Issuezilla 4493 http://www.possenet.org/issues/show_bug.cgi?id=2493 for

attached spec.)

Once this is implemented, you will be able to specify extended widgets.

Don

~~~~~~~~~~~~~~~~~~~~~~~~~~~

Don Bulua

Progress Software Corp.

Montreal, Quebec

email: dbulua@sympatico.ca

tel:(514) 685-0412

fax:(514) 685-0361

~~~~~~~~~~~~~~~~~~~~~~~~~~~

-Original Message-

From: Mike Fechner

Sent: Tuesday, February 18, 2003 6:01 AM

To: dev@icf.possenet.org

Subject: custom properties for widgets in the repository

Hi,

we are developing a visual basic renderer for the dynamics repository data.

the visual basic frontend calls appserver routines to get the actual

repository data when rendering containers or viewers. so far - so good.

to gain the biggest possible help from the dynamics tools we tried to stay

as close to progress widget definitions as possible but that is not possible

in every case, as we would limit the possibilities of the visual basic user

interface and some of our custom controls.

the dynamics tools/progress ade helps us a lot with datafields in viewers as

I am able (the dcu helpled here) to set up a datafield_site_1511 class

containing our custom properties extending the default dynamics datafield

class.

for simple controls (progress widgets) I need to be able define my own

properties as well. I tried to extend the DynButton class with a

DynButton_SITE_1511 class and added that to the icfprogress.cst file as

followed:

*BUTTON_SITE_1511 &Default IT focus Button

DESCRIPTION IT Focus Default Button

INHERIT &ICF Standard Button IT Focus

NAME buButton

The appbuilder seems to ignore this entry in the .cst-file (I have verified

that the correct .cst file gets useds) - I cannot find the button on the

appbuilder palette. I expect that the dynamic viewer editor of the

appbuilder treats class children of DynButton objects like DynButton

objects. This behaviour is allready there/intended for the general editing

possibilties of classchildren of the DynView or DynBrowse object type. The

same should be possible with all the dynamic widget classes.

I tested this with a posse_main download from 02/17/2003.

Before logging an issue I'd like to know if I made a mistake or if the

required feature is not intended by Dynamics development in general.

Regards,

Mike

mike fechner it consulting

Breite Str. 116

50667 Köln

Germany

Tel.: +49 (0) 221 / 27 609-40

Fax.: +49 (0) 221 / 27 609-41

Mobil: +49 (0) 160 / 700 82 29

mike.fechner@fechner.de

www.fechner.de

To unsubscribe, e-mail: dev-unsubscribe@icf.possenet.org

For additional commands, e-mail: dev-help@icf.possenet.org

To unsubscribe, e-mail: dev-unsubscribe@icf.possenet.org

For additional commands, e-mail: dev-help@icf.possenet.org

Posted by LegacyUser on 18-Feb-2003 13:35

Hi Don,

the current behaviour of the appbuilder and the appbuilder palette is

"dynamic enough" for what I was requesting. Buttons in dynamic viewers are

allready stored as "DynButton" objects in the repository. In addition to

that I only need the ability to select if the button is stored as a

DynButton object or a DynButton_SITE_1511 object. I was expecting that to be

done via the .cst (or extended classes in the object type maintenance).

I need to be able to store additional attributes and ui events to the button

objects without having to modify the DynButton class itself (what is not

suggested for deployment and upgrading purposes).

Can you estimate when enhancement described in the mentioned issue will be

available?

Thanks,

Mike

-Ursprüngliche Nachricht-

Von: Donald Bulua

Gesendet: Dienstag, 18. Februar 2003 16:40

An: dev@icf.possenet.org

Betreff: RE: custom properties for widgets in the repository

Hi Mike,

The current appBuilder palette is currently designed to work with static

widgets only. It is currently not possible to specify dynamic widget

objects for palette items.

If you want your button to be available in the appBuilder palette, you need

to modify the .cst file as with any palette item and add the desired

attributes or trigger code for that button. If you want it as the default,

you need to specify the &Default name. You could add the following:

*BUTTON &Default

DESCRIPTION IT Focus Default Button

INHERIT &ICF Standard Button

NAME buButton

(list of attributes here}

Having said that, we are in the process of modifying the AppBuilder to store

the .cst information in the repository.

(See Issuezilla 4493 http://www.possenet.org/issues/show_bug.cgi?id=2493 for

attached spec.)

Once this is implemented, you will be able to specify extended widgets.

Don

~~~~~~~~~~~~~~~~~~~~~~~~~~~

Don Bulua

Progress Software Corp.

Montreal, Quebec

email: dbulua@sympatico.ca

tel:(514) 685-0412

fax:(514) 685-0361

~~~~~~~~~~~~~~~~~~~~~~~~~~~

-Original Message-

From: Mike Fechner

Sent: Tuesday, February 18, 2003 6:01 AM

To: dev@icf.possenet.org

Subject: custom properties for widgets in the repository

Hi,

we are developing a visual basic renderer for the dynamics repository data.

the visual basic frontend calls appserver routines to get the actual

repository data when rendering containers or viewers. so far - so good.

to gain the biggest possible help from the dynamics tools we tried to stay

as close to progress widget definitions as possible but that is not possible

in every case, as we would limit the possibilities of the visual basic user

interface and some of our custom controls.

the dynamics tools/progress ade helps us a lot with datafields in viewers as

I am able (the dcu helpled here) to set up a datafield_site_1511 class

containing our custom properties extending the default dynamics datafield

class.

for simple controls (progress widgets) I need to be able define my own

properties as well. I tried to extend the DynButton class with a

DynButton_SITE_1511 class and added that to the icfprogress.cst file as

followed:

*BUTTON_SITE_1511 &Default IT focus Button

DESCRIPTION IT Focus Default Button

INHERIT &ICF Standard Button IT Focus

NAME buButton

The appbuilder seems to ignore this entry in the .cst-file (I have verified

that the correct .cst file gets useds) - I cannot find the button on the

appbuilder palette. I expect that the dynamic viewer editor of the

appbuilder treats class children of DynButton objects like DynButton

objects. This behaviour is allready there/intended for the general editing

possibilties of classchildren of the DynView or DynBrowse object type. The

same should be possible with all the dynamic widget classes.

I tested this with a posse_main download from 02/17/2003.

Before logging an issue I'd like to know if I made a mistake or if the

required feature is not intended by Dynamics development in general.

Regards,

Mike

mike fechner it consulting

Breite Str. 116

50667 Köln

Germany

Tel.: +49 (0) 221 / 27 609-40

Fax.: +49 (0) 221 / 27 609-41

Mobil: +49 (0) 160 / 700 82 29

mike.fechner@fechner.de

www.fechner.de

To unsubscribe, e-mail: dev-unsubscribe@icf.possenet.org

For additional commands, e-mail: dev-help@icf.possenet.org

To unsubscribe, e-mail: dev-unsubscribe@icf.possenet.org

For additional commands, e-mail: dev-help@icf.possenet.org

To unsubscribe, e-mail: dev-unsubscribe@icf.possenet.org

For additional commands, e-mail: dev-help@icf.possenet.org

This thread is closed