Descripción del proyecto
The task is to make a script for GreaseMonkey for FireFox (FF only) that will make it easier for me to work with the site .
The problem is not conventionally simple.
is an electronic wallet. I need to add a couple of crooks that will make it easier for me to work with the site in a way that makes it easier for the owner of several wallets. You need to simplify the “entry” and transfers between your wallets. Not much work, but a lot of detail.
What needs to be done:
Facilitate the authorization process.
At the moment, the authorization there is as follows:
You need to enter the MANUAL (with a copypast there is difficulty) phone number (attached figure 1), then press "in" and then the second step is suggested: you need to enter the password, then again press "in" and then the entrance is performed. With such a complex procedure and rigid validation that does not allow you to enter a login normally (through a copypast) and at the same time it is also impossible to save logins and passwords with standard browser tools, in general, the authorization process takes a lot of time. When you have multiple wallets, it’s a total ass.
What do you need to do? In the attached figure 2, the desired concept is visible. Instead of the authorization form, drop down the list. After selecting the desired option (wallet), without clicking on any buttons, authorization should immediately occur WITHOUT the need to enter a password. So the script has to do everything itself. In the drop-down list, wallets are described so that they can be easily identified. But when you choose a wallet in the list, the script itself does everything, substitutes the phone, enters the password and enters. Obviously, the script should contain in the code: description (for the drop-down list), login and password.
I have the skills to copypast js and edit html and css myself. So I don’t need to take care of beauty, I’ll decorate it myself. Actually, I should be able to easily add new “wallets” to the script code for a drop-down list, that is, the list of wallets with data (description for a drop-down list, login and password) should be described in one place and not scattered throughout the script.
For testing and work, if the contractor is not from Ukraine, I will provide access to several of my empty wallets. At the very first entrance to the wallet (at registration), the site requires the entry of SMS password. Further in the wallet, you can already assign a password to enter in the settings, so that you can enter by your password, and not by SMS. The script created by default should assume that the wallets described in it already have passwords installed previously.
Under the drop-down list (or among the list options) there should be a button when you click on which the script returns the usual authorization form (in case you need to log in from a wallet that is not yet described in the drop-down list).
A little hack of deauthorization.
When clicking on the exit button, the script must delete all cookies monexy.ua and after successful deletion reload the page, in order to 100% guaranteed to remove cookies that were placed at the previous entrance under another wallet.
Facilitating transfers between your wallets
Take a look at figure 3. Here is the form you need to fill out to make a transfer to another MoneXy wallet. Here everything now in fact needs to be entered manually and although the manix has a template function, nevertheless, in each wallet these templates need to be created anew, and you can facilitate all this. Instead of the recipient’s wallet number input field, you can show the same (or similar) drop-down list (which is essentially shown when logging in) so that I can choose from my own wallets to transfer. We obviously need to remove the wallet we're authorized to use from the list. Again, it is quite obvious that under the drop-down list (or among the drop-down list options) there should be a button whose task is to return the standard field for entering the wallet number (in case you need to enter a new wallet number that is not yet described in the list).
In the comment field, a random stone from the list of random stones scored in the script should be automatically substituted. Add a couple so I can build and add mine.
After entering the translation data, we click on the “further” button and before us there is a stupid step that requires unnecessary action. The essence of the step is visible in figure 4. We need to make this step skip, that is, we need to make sure that after pressing the button further (the tick was put itself and the button was pressed itself) and we immediately have what is visible in figure 5.
Something like that.
The problem is not conventionally simple.
is an electronic wallet. I need to add a couple of crooks that will make it easier for me to work with the site in a way that makes it easier for the owner of several wallets. You need to simplify the “entry” and transfers between your wallets. Not much work, but a lot of detail.
What needs to be done:
Facilitate the authorization process.
At the moment, the authorization there is as follows:
You need to enter the MANUAL (with a copypast there is difficulty) phone number (attached figure 1), then press "in" and then the second step is suggested: you need to enter the password, then again press "in" and then the entrance is performed. With such a complex procedure and rigid validation that does not allow you to enter a login normally (through a copypast) and at the same time it is also impossible to save logins and passwords with standard browser tools, in general, the authorization process takes a lot of time. When you have multiple wallets, it’s a total ass.
What do you need to do? In the attached figure 2, the desired concept is visible. Instead of the authorization form, drop down the list. After selecting the desired option (wallet), without clicking on any buttons, authorization should immediately occur WITHOUT the need to enter a password. So the script has to do everything itself. In the drop-down list, wallets are described so that they can be easily identified. But when you choose a wallet in the list, the script itself does everything, substitutes the phone, enters the password and enters. Obviously, the script should contain in the code: description (for the drop-down list), login and password.
I have the skills to copypast js and edit html and css myself. So I don’t need to take care of beauty, I’ll decorate it myself. Actually, I should be able to easily add new “wallets” to the script code for a drop-down list, that is, the list of wallets with data (description for a drop-down list, login and password) should be described in one place and not scattered throughout the script.
For testing and work, if the contractor is not from Ukraine, I will provide access to several of my empty wallets. At the very first entrance to the wallet (at registration), the site requires the entry of SMS password. Further in the wallet, you can already assign a password to enter in the settings, so that you can enter by your password, and not by SMS. The script created by default should assume that the wallets described in it already have passwords installed previously.
Under the drop-down list (or among the list options) there should be a button when you click on which the script returns the usual authorization form (in case you need to log in from a wallet that is not yet described in the drop-down list).
A little hack of deauthorization.
When clicking on the exit button, the script must delete all cookies monexy.ua and after successful deletion reload the page, in order to 100% guaranteed to remove cookies that were placed at the previous entrance under another wallet.
Facilitating transfers between your wallets
Take a look at figure 3. Here is the form you need to fill out to make a transfer to another MoneXy wallet. Here everything now in fact needs to be entered manually and although the manix has a template function, nevertheless, in each wallet these templates need to be created anew, and you can facilitate all this. Instead of the recipient’s wallet number input field, you can show the same (or similar) drop-down list (which is essentially shown when logging in) so that I can choose from my own wallets to transfer. We obviously need to remove the wallet we're authorized to use from the list. Again, it is quite obvious that under the drop-down list (or among the drop-down list options) there should be a button whose task is to return the standard field for entering the wallet number (in case you need to enter a new wallet number that is not yet described in the list).
In the comment field, a random stone from the list of random stones scored in the script should be automatically substituted. Add a couple so I can build and add mine.
After entering the translation data, we click on the “further” button and before us there is a stupid step that requires unnecessary action. The essence of the step is visible in figure 4. We need to make this step skip, that is, we need to make sure that after pressing the button further (the tick was put itself and the button was pressed itself) and we immediately have what is visible in figure 5.
Something like that.
Desarrollo de sitios web Dinero electrónico
