Posts by DecSoft

Hello!

Thanks for sharing Andreas! :)

Hello Andreas,

Many thanks for inaugurate this forum's section sir! Thanks for sharing!

Hello to all!

Here in this forum's section you can place and can find developed App Builder's Javascript plugins shared to the program's community. If you want to create new App Builder's Javascript plugins this tutorial is available. Also you can use the forum's attachment manager to zip your plugin's files and upload it.

Please, try to following these little rules in order to post in this forum's section:

1º Be descriptive with the thread's title. Your plugin name must appear, and a little words to describe it. Just like in "My Cute Plugin - A cute plugin to do these and these other things".

2º Describe your plugin in more deep inside the new post. Comment about the plugin, their dependencies (if any), if you provide some example, if the plugin includes a contextual help, etc.

3º Don't use this forum to ask about plugins or whatever other thing. For that feel free to use the App Builder general forum's section. Here only plugins must be published.

That's all!

Hope you found this forum's section useful!

Thanks for comming!

Hello Ade,

If I am not wrong the installer is configured to use the system language by default or the english language if the first one is not available. The installer currently support english and spanish, the same languages than the App Builder GUI has availables. The installer "remember" the language you use in an installation, and then, when the program is installed again (after an update, for example) the installer take the latest used language. That's the behaviour I can see here.

Hello Samuel,

Well. The problem is apparently the way in which App Builder retrieves the CSS properties. They use the "ComputedStyle" way, and, for some reason (and in some browsers) they appear to don't return the expected value for "shorthand" properties like "background".

Probably this is like that because such kind of properties can contains more than one value... then the behind function can't return a computed value at all. This doesn't happend with "background-color", since they are a property that have just one value, which can be computed and then returned without problems.

I can't found information about this right now, but my bid is for this Samuel, since they have some logic, do you?

Hello Samuel,

Ok. Apparently "background" is not deprecated, so, for some reason that I can't understand, major browsers complains about when retrieve such property. Since we can use another CSS property for the same thing... and they works... probably we no need to go ahead, IMHO.

Hello Samuel,

Please, don't worry at all! "background" is and old CSS property that probably is now deprecated. But may I am wrong: I just try with "background-color" and find it working. On the other hand, when something works in one browser, but not in others... probably we must to follow the "others"... :)

Hello Samuel,

Try to use "background-color" instead of "background".

Hello Ade,

I noticed something although it is not an issue but just an observation, if check (from app builder icon) for updates and download the setup file then app build close and update will began (this happen on fly) then the installation setup file language will spanish but if I click the setup file downloaded on my desktop then the setup file installation language will be English.

What happend if you do it the same again? After the installation finish (in english) then try to start the installation again... what language is then used?

Hello Andreas,

Welcome to the forum and thanks very much for sharing this! :)

Hello Samuel,

Yes; I am very happy with the WebExtensions concept, but remember! They are a relative new concept, so currently we can only try (or I try) with Chrome and Opera. Firefox 50 (nightly build) is also ready, but with some rare behaviour. Microsoft Edge promises to their users a way to convert WebExtensions into their own extensions... I think they must do, since WebExtensions are ready to stay in all other modern browsers... unfortunatelly maybe Internet Explorer is out of this field, but I am not sure about Internet Explorer 11 in the near future: may can finally support it.

So in order to clarify some points:

1º Our applications can run as WebExtensions "as is", but of course we can't use WebExtensions' stuff outside the browser, better said, until our app are installed as a WebExtension. What this means? Well. We can create applications that simply works as WebExtensions, like the Calculator example, which don't use at all any WebExtensions specific stuff. And we can create applications like the WebExtension sample, which in fact have non sense out of the WebExtensions world.

2º The "manifest" file is what we need to use in order to install the WebExtension to debug it. We must navigate to "chrome://extensions", for example, in Google Chrome. Then we choose the "Install unpacked WebExtensions" and just indicate where the manifest file is placed. In order to upload a WebExtension to a browser's store, we need to Zip our application as well the manifest: and we can do it from App Builder and the Zip app tool. Look at the Tools menu. When we are ready can navigate to the browsers store webpage (for example the Google Chrome Store), enters in our account and upload the Zip file. And that's all!

Hope this information can be useful to you Samuel, but please, don't hesitate to post here any further question. :)

Hello tin,

If the "Focus" / "Blur" events trick works, that is, if we can change the input type as expected for the softkeyboard, then may we need to take care about the "Change" event. Maybe, when we enter in the "Focus" event, can set certain "flag variable" to "True", and then, in the "Blur" event, set that variable to "False".

Why to do this? The idea (I don't know if they can work, but we can try it before try any other possible approach) is to format the number in the "Change" event ONLY if the input doesn't have the focus. In the "Change" event we can look for the "flag variable", and, only apply the format if such variable is "False", that is, the input has no the focus.

Hope you can understand what I means tin.

Hello tin,

Please, can you describe what is your expected behaviour and what you get in Android?

You're welcome! ;)

Hello Tin,

Please, update your AB copy:

2016.140 (07/09/2016)

* Add the TextAlign CSS property in all Inputs (Text, Number, Phone, etc.) and for the three CSS style tabs: Normal, Hover and Focus. By now the changes are only visibles in runtime or after change the Input value.