I am not sure what you could do. Most of the user interaction is done on web side and the actual interaction with bitshares wallet is minimal.
Here is a list of commnads. You could make the wallet go to the transaction of the payment in your shopping cart. Either that or lock the wallet?
I'm trying to see if there is any functionality to put in the bts login plugin that makes a lot of sense.
Perhaps if a user is a delegate and then putting the 'vote for me' link in their profile but that sort of stuff requires a lot more effort. However if you couple it with the membergroups on registration you have a system where delegates could have their own membergroup and likely work off that.. So 3 tiers = unreg/reg/delegates. For delegates we could pull out special fields etc.
anyway.. thinking outloud but if anyone has any ideas on functionality tell me now why i am still actively working on this project because ramp-up time/learning curve is what always kicks you in the balls. It is more likely I will do it now then later if someone has a good idea that isn't difficult.
- Go to profile
xts:profile-name
- Add new contact with name
xts:name:XTSaccountkey
- Request Payment
xts:name/transfer/[amount/amount/][memo/memo text/][from/sender name/][asset/asset name] (registered accounts)
xts:name:XTSaccountkey/transfer/[amount/amount/][memo/memo text/][from/sender name/][asset/asset name] (unregistered accounts) (Not Yet Implemented)
The ordering of the amount, memo, from and asset fields is unimportant.
- Vote for delegate
xts:delegate-name/{approve|disapprove}
- Go to block
xts:Block/num/block-number
xts:Block/block-id
- Go to transaction
xts:Trx/transaction-id
Note that transaction-id above may be a prefix, as long as at least 8 characters are present
- Login to website
xts:Login/server-one-time-public-key/signature-of-one-time-public-key-with-account-key/www.server.com:port/path/to/login.php
For more information on the BitShares XT Login protocol, see here.