Don’t have a full picture yet on all the possibilities / problems that you would have to deal with, but what about Security settings on attached modules?
Scenario:
I have build a module that I want to put out there in the market commercially. So, I do not like it if the developer that buys it can see exactly how it works. Meaing: i do not want him to see the content of my methods. Instead, I would like to give him the option to call (certain) methods and with the move sample button let him insert a description of how to use the method. Also, some of the forms in my module should not be called directly, but only through, for example, buttons on other forms of my module (because, if called directly, the workflow breaks)
This would entail, as far as I can see:
Ability to create sample code for methods
Specifiy which methods of a module are visible in Developer
specify per method of a module if the code can be viewed in Developer
specify which forms of a module are visible in Developer
To the other developers: Is this a relavant scenario?
to Servoy: would this be possible?
pbakker:
Scenario:
I have build a module that I want to put out there in the market commercially. So, I do not like it if the developer that buys it can see exactly how it works. Meaing: i do not want him to see the content of my methods.
If you password protect the module, the methods cannot be opened (content cannot be viewed)
pbakker:
This would entail, as far as I can see:
Ability to create sample code for methods
Specifiy which methods of a module are visible in Developer
specify per method of a module if the code can be viewed in Developer
specify which forms of a module are visible in Developer
Currently not possible, will likely not make it into Servoy 2.2, to overcome this make a dev. manual how to use your module
pbakker:
To the other developers: Is this a relavant scenario?
I think the scenario sounds very realistic and the features described are quite useful. But for me, there is more interesting stuff that could be done before
One of the points I thought abour before is this
Ability to create sample code for methods
This is also useful if you are inside your own solution. How about something like
either a text field where you can enter simple text (like “parameter_A, [Parameter_B]”…) that is then placed between the brackets when you choose “move code” on a method
or maybe even easier a line of comment like ```
// callParameters: parameter_A, [Parameter_B]
I’m intrested in this too, it would be very nice when writing commercial modules.
Maybe there could be something like: the first row of ```
// comments
The example code maybe could wait a little longer...
I think, we need also options for things like “method is not visible but executable”. In this case, you can only see the method-name (+ parameters) but not the code etc.
pbakker:
Scenario:
I have build a module that I want to put out there in the market commercially. So, I do not like it if the developer that buys it can see exactly how it works. Meaing: i do not want him to see the content of my methods.
If you password protect the module, the methods cannot be opened (content cannot be viewed)
Sorry about that Jan, but I experience the exact opposite this night. Using version 2.2 I exported protected modules and non protected main solution. I could easily read methods from modules when logged into solution…
As a matter of fact, modules were not previously protected by password on this installation (test server at customer place) could this have an impact?
We support fully your scenario Paul, we think that commercial modules can be very important in the future.
I’ve exported a module with protection (the module contains other modules), delete all modules in rep., created a new solution, imported the protected module and added the imported module to the new solution.
In the new solution you can see the method contents from the protected modules :-(.