'text' property for fields

Classic Servoy
1

Can we have one, plz?

I want to use the text property of an element (field) to set the data provider ‘street’ with a descriptive default value like ‘Street’ when a new address record is created.

I am currently using ‘toolTipText’ which works fine. Being able to use the text property would give us more flexibility by using a longer, more descriptive tool tip text and a brief label.

I haven’t thought about the implications but I would wouldn’t mind if you made this a default behavior of fields - to show the text property (in grey) as long as the fields data provider is ‘null’.

For now I would be happy with ‘text’ property for fields :).

2

I agree!

Having played around with a few of IDE / programming environments / GUI libraries I realize that Servoy’s database-centric design established a “Field is linked to a dataprovider” paradigm, having the “text property available only at design time”. I can’t see the reason why (from a users perspective)!

Actually this paradigm isn’t air-tight. We can link the field to a global variable! If so, why not use it on a form without actually being linked to a dataprovider? This is a bit like having a local variable displayed on a form (more on this later).

I’ve stumbled on this just a few days ago. But, being just a newbie, have been waiting to learn Servoy better. But since you mention this, I must say I agree completly with you Thertzler!

Another issue that I think relates to this is form variables.
Because of this I include the following thoughts.

Why not having form variables (instead of poluting global namespace)?

This way you could even get/set the text property from/to a form variable. I’m aware that we can use

globals.varX = 'example'

in a method without “declaring” the global in the dataproviders list (this is a good thing). But, naturally, the var will live on after the form is closed/destroyed.

It would make sense (for many situations) to have something like:

forms.['form name'].globals.['myVar']

or

forms.['form name'].vars.['myVar']

And the variable would be destroyed after form closing!

One recurrent situation these “variables scoped to a form” would be perfect at is when one is using a global variable to test whether or not the user can exit the current form (compulsive fileds have been filled per example).

After writting this I did a search on the forums (I know I should search first!) and found the same request in a few posts that are worth reading! And learned a little:

http://forum.servoy.com/viewtopic.php?t … baab70880c
http://forum.servoy.com/viewtopic.php?t … baab70880c
http://forum.servoy.com/viewtopic.php?t … ables+form

Still for now I think it makes sense to have locally scoped form vars. instead of assigning null or risking namespace pollution using the same (unlisted as a global provider) global var!

Best,
mjekl

3

thertzler:
Can we have one, plz?

Elements: changing 'text' property - Classic Servoy - Servoy Community

I want to use the text property of an element (field) to set the data provider ‘street’ with a descriptive default value like ‘Street’ when a new address record is created.

I am currently using ‘toolTipText’ which works fine. Being able to use the text property would give us more flexibility by using a longer, more descriptive tool tip text and a brief label.

I haven’t thought about the implications but I would wouldn’t mind if you made this a default behavior of fields - to show the text property (in grey) as long as the fields data provider is ‘null’.

For now I would be happy with ‘text’ property for fields :).

You can use masking for that! Look at this thread: http://forum.servoy.com/viewtopic.php?t … cc309f815e