-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Config's Standard Params and Advanced Params pages #3270
Comments
I agree. |
I stopped using this screen because I never knew up front, if the parameter I wanted was "Advanced" or "Standard", and it just made it harder to find having to know this first. |
1.The whole idea of categorizing Advanced and Standard parameters is coming from the parameter metadata, defined in the source code by the @user field. keeping only the full param tree means that we no longer need that type of distinction ? Basic and Advanced param screens created to use and 'enforce' boundaries, set in the parameter metadata, do we really want to get rid of it ? |
yes...Full Param List does that value check also ....Std vs Advanced tagging has been inconsistent and really is meaningless since the what is advanced to one user would be std to another... back when there were much fewer params, std vs advanced MAY have steered noobs away from messing with params they did not understand or ,more likely, not covered in the wiki...not effective now |
OK. I think the most non disruptive way is to redo the layouts
|
@Hwurzburg and I think that it would be good to remove the Standrad Params and Advanced Params pages. I suspect very few people find the format easier to use than the Full Parameter List because:
The text was updated successfully, but these errors were encountered: