Integrate a generic "setup" command into ubiquity.
Example:
setup mycommand {username} {password}
This would associate the {username} and {password} to the command 'mycommand' and store the data in Application.prefs
This would be a great way to unify how we store credentials in ubiquity. if a command requires a username and password, just run the setup command and then call those variables from your command whenever you need them.
right now i'm manually doing this. I'm creating a simple mynotes application and have to include a mynotes-setup to store the appropriate data in prefs. it would be nice if i could just skip that step and have it built in.
setup mycommand {username} {password}
This would associate the {username} and {password} to the command 'mycommand' and store the data in Application.prefs
This would be a great way to unify how we store credentials in ubiquity. if a command requires a username and password, just run the setup command and then call those variables from your command whenever you need them.
right now i'm manually doing this. I'm creating a simple mynotes application and have to include a mynotes-setup to store the appropriate data in prefs. it would be nice if i could just skip that step and have it built in.
5
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
-
Inappropriate?A great idea, especially when combined w/ user-defined aliases for commands.
How about somehow allow Ubiquity to access cookies for this information? If authentication information is needed and not available, the command would send you to the login page of the associated site. Would this introduce security problems?
I’m excited
Loading Profile...




