Option to hide data table scriptsHide Scripts that are saved to the data table
blum.b.1
Re: Option to hide data table scripts - Status changed to: Open for VotingRe: Option to hide data table scripts<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />Can you provide a description of what Github does? I created an account but couldn't see what you might be talking about.
A screenshot would be good too.
Thanks!
Re: Option to hide data table scriptsMichael, I like both your suggestions.
For me it would be ideal if it would be similar to what Github is doing.
Re: Option to hide data table scriptsThis is a fascinating idea.
Let me make a couple suggestions to get our minds moving. I'd be interested in whether any of these fit your use case, Bea, and whether any of these are implementable at JMP.
Idea 1: enable some sort of versioning of scripts. I could select the final version of the script, but then have some sort of tabbed option in the Edit Script panel to let me see prior versions (and potentially run them from there). The versioning could potentially even highlight differences between versions of the scripts. That's going to take some amount of work but you've already taken a step with the revisions in JMP 13 that automatically name scripts... One could potentially allow a person to type a new script name in, or select an existing one to be prompted with a check-in dialog of "overwrite this script" "append a number to the name" or "archive the previous script as an old version" ?
Idea 2: allow scripts to be grouped (just like we have Group Columns, we could have Group Scripts). A user could put their best script at the top but then keep a hierarchy of old scripts as well. This idea might be more flexible as it could allow a variety of other use cases, and I imagine it would be easier to implement.
Re: Option to hide data table scriptsI am seeing this in the context of reproducible research. By saving the scripts that led to a final model that’s being published it’s mostly reproducible which steps were taken to get there. But those intermediate (modelling) steps are not needed to be revisited on a regular basis once you are done. Therefore, with finalizing the effort, I would only like to see the scripts that are really relevant for the client.
That’s my background and motivation.
Re: Option to hide data table scriptsblum.b.1 ,
This seems to violate a number of core principles for us. Especially around how you'd ever get to the scripts to run them if they were hidden. Can you provide some more background and information about the use case here?
