You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have had this idea some time ago, I have tried fixing some rough edges, but there is still something to work out.
My idea would be to deploy a google script (as a web app) which the iser could use to configure GCEN.
This is a rough draft of the concept:
a web page with a form field (text, list, check box...) for each setting
the user fills in the settings, receiving immediate feedback about malformed/invalid input
the user submits the settings
a more thorough check is performed on the input
if everything is alright the user is presented with the code correctly configured which can be copied and deployed as usual
This would mean:
users would be helped in the configuration of the script (and issues about misconfigurations should happen less often)
we would need to maintain this second script as well (although it should be easier as users would not access it directly and its logic would be simpler)
we could split the monolythic code.gs into smaller, more manageable files
The text was updated successfully, but these errors were encountered:
Although I haven't looked at the requirements, I suspect it would then be possible to use the web-app to generate and optionally auto-deploy the GCEN code (or modify it if already-deployed). It could include some handling like "are you sure you want to overwrite the existing deployment" if auto-deploy sounds like an invitation to disaster. Of course that would make the web-app noticeably more complex, but as a pay-off it would mean when people open a support-request-issue due to having problems copy-paste-deploying GCEN manually, the first question as response can be "have you tried it using auto-deploy from the web-app". Whenever this works, we could then say "therefore the problem is in the manual steps you are taking" (meaning, either just stick with auto-deploy or re-read the documentation more thoroughly if you want to manually deploy).
I have had this idea some time ago, I have tried fixing some rough edges, but there is still something to work out.
My idea would be to deploy a google script (as a web app) which the iser could use to configure GCEN.
This is a rough draft of the concept:
This would mean:
code.gs
into smaller, more manageable filesThe text was updated successfully, but these errors were encountered: