I had always in mind, that there was a function:
controller.visible = false
But there is’nt!
Is there an other way to do this? (not by security!)
I did’nt need it. Now I do!
Can it be done?
what should that do?
set the visibility to false on all components?
So you just have an empty (gray) screen??
Why would you do that?
A lot of us (developers) make, for example, there own security.
Just to make it simple for the end-user
So when you have a function to disable (like the acces-feature under security!) a form, that would very handy.
You can use now: controller.enabled = true, but this functions only ‘greys-out’ the form.
mabye you must call it: controller.acces
so that you can’t go to the form, and when the form is used in a tabpanel, that it is tottaly blank or make the specific tab not-clickable.
But not only for security reasons, also I can think a lot of other situations.
Why don’t you just make the form not accessible for the users (mening: do not show it in the forms list) and disable whatever button you use to open it)?
Paul
Yes, I know what you mean.
but in some of my situtations, this is not possible.
Some of my buttons have multiple functions.
Anyone else, how can see the benefits of this feature?
I agree! would be very useful!
Thanks,
Stef
I must explain better, or else I don’t see this is comming on the wishlist.
What I really want, is a function: controller.acces = false
( The same function as the acces in the current security)
What I can do than, is do that by scripting.
One part, I use my own security. If this function is possible I can do in a start-script:
forms.form1.controller.acces = false
forms.form2.controller.acces = false
etc..
I than don’t have to worry in other scripts, that goes to this form.
The user get’s the message: Acces to this form denied.
I would really see this on the wishlist!
Hey, this is a cool idea. Instead of setting this in the security system setting the same flag via scripting.
Cool!
why would you controll the acces yourself to a specific form?
Why not disabled all the things that lead to that form?
So the button that would open that form is not visible?
If this would be recommended, why do you have this function in the security?
I have several buttons on different forms, which leads to specific forms. Now I have to write a bunch of methods that must prevent or check or disable the buttons from executing.
If I could set (at startup) forms.form1.controller.acces = false
I don’t have to worry about anything anymore.
Every way that leads to this form, is prevented. Even when form1 is used in a tabpanel!
Do you agree, that this would be much less complex? and much more flexible?
i still find it ugly.
if you need to hide it from the user and you are already doing it in javascript. Why not disabled/set not visible the buttons (at startup) just as you do now with that line you mention.
OK maybe instead of
forms.form1.controller.acces = false
you have
forms.form2.element.button.visble = false
forms.form33.element.button.visble = false
in you startup script..
but it is much cleaner..
I don’t agree with you, Johan
why is it ugly?
You dont’even see an empty screen!
and I think I am not the only one. There are 2 guys with me!
Tell me than, why is the function possible/build in the security?
security is another level!
and is still think that even with security . you should disabled the buttons that point to that formpanel. Not the formpanel itself..
if you use scripting then you should do it the right way and disable the entries to that form. (Even if you use the build in security!!)
For now it is not on the planning that you can change security settings through scripting.
don’t make people that uses youre solutions wiser then they are (they shouldn’t know that there is another form…)
As requested elswhere on the forum, I would also like to see the features you have under security in the method editor. Next to the arguments allready mentioned in this tread, I also saw many people (just like me) like to set up their own security. My reason for this is that I want to make solutions that can be configured by the users. Therefor I create forms where the user or specific users can tweak the application.
It would be very nice if I could also let a super user modify all the securitysettings that Servoy security offers, through a selfmade form, so I do not have to give the users access to the develloper…
Paul
but that kind of support is already in it.
Just add or remove a user from group(s) you specify…
so make a few groups.. add the users you want to them And if one logs in and something changes just modify the user to a group (or remove him from a group)
I know that! And am using it. What I’m talkign about is the ability to specify per profile, if a field/button/element is enabled/disabled, can be focused/is seen at all etc.
Basically, all the functions available under Security I would like to see in the Method Editor
Paul
Just ran across this thread while looking for something else. It looks like the topic’s pretty much dead, but I want to throw in my two cents (.002, when adjusted for the exchange rate among the other posters in the thread ).
I’m not sure I follow the reasoning either way in this discussion, but I do agree that it’s preferable to set up a UI screen so that a user admin can edit security, without having to call me.
The only thing missing for FULL control of the security layer from the UI screen is the ability to set access for the different groups. From a method, the user can create a group, create users, add users to the group, etc., but if they add a group, they can’t edit the privileges of that group.
I’m trying to control user acess through dynamic menus, which I think will work as Johan is describing, but actually disabling access to a form would add just that much more security. Also, I’d particularly like to be able to enable/disable table tracking for a group.
For what it’s worth…