jaefruit.blogg.se - Adding inputs to blocs app inventor

ADDING INPUTS TO BLOCS APP INVENTOR HOW TO
ADDING INPUTS TO BLOCS APP INVENTOR INSTALL
ADDING INPUTS TO BLOCS APP INVENTOR CODE
ADDING INPUTS TO BLOCS APP INVENTOR PASSWORD

Additionally we’ll need to indicate the function associated to each GET request, i.e. This can be done for example starting from the TinyWebDB file and including into it the classes from SendMail. The combination of both services consists of merging the contents of the respective main.py files. We’ll just explain the small adaptations required for these two purposes since the services are fully explained in the above mentioned posts. The service deployed in this tutorial serves two purposes: unify both services (TinyWebDB and SendMail) and introduce security.

ADDING INPUTS TO BLOCS APP INVENTOR CODE

Alternatively, since both user interface and code blocks are very simple, you may consider developing the client side from scratch. The part that concerns us is just the mail sending window (see below). You’ll realise there’s some functionality that is not explained in this tutorial because this is actually a more general application (which is explained in the Login template post). with the AppEngine console)ĭownload these sources and upload them into App Inventor.

Deploy again the application as in the first step (i.e.

Edit the main.py and replace the contents of the variables EmailFrom and AuthKey as explained below.

Download the files app.yaml and main.py and replace the files with the same name located in the folder where you downloaded the TinyWebDB.

Create and deploy the TinyWebDB service as explained in the tutorial Creating a Custom TinyWebDB Service.

ADDING INPUTS TO BLOCS APP INVENTOR INSTALL

Installation Mail sender service (App Engine)Īssuming we really intend to provide a shared service for both the TinyWebDB and mail sending, I recommend following these steps to install the solution: For an explanation of the steps involved you may be interesed in this post: Python 2.7 migration demystified.īy the way when explaining the Web DB service we’ll also mention a useful trick to ease DB editing which you may not be aware of since the TinyWebDB describes an alternative way of doing it. This is probably more relevant for the TinyWebDB than for the mail sending itself. the ability to restrict its utilization to privileged users.

ADDING INPUTS TO BLOCS APP INVENTOR HOW TO

How to deal with security issues for the service, i.e.

Since we’ll usually have an application service to provide de DB capabilities, it would be a pity to use a different one for sending mails (remember Google AppEngine’s limitation to 10 free services).

How to set up the mail sending service together with the TinyWebDB service.

However this post adds some practical details that were necessary to integrate the solution in my app, and which I think will be common to most apps: What are we going to buildĪctually the solution is not original but rather provided in a project by ShivalWolf (see next chapter for more details).

Therefore we’ll show an alternative way to send mails without user interaction.

ADDING INPUTS TO BLOCS APP INVENTOR PASSWORD

For example, I recently created a Login Template where it was unsuitable to show the mail prior to sending it because it contains a secret password and hence only the email receiver should be able to read it. Unluckily using the device mail client is not adequate when the mail needs to be sent without the user noticing it, or at least with minimal interaction (maybe just a notification). It’s based on the startActivity component and is extremely simple to implement as explained in the App Inventor reference documentation. App Inventor provides an easy mechanism to send mails using the client installed in the device.