I am searching a way to programmatically create buttons in a vertical scroll alignment layout in MIT App Inventor but unable to find proper tutorial or documents not available. Could someone highlight if it's possible.
Thanks.
To create components dynamically is not possible in the core system of MIT App Inventor, but there is an extension you can use, which is able to do it, see here Dynamic Components Extension (for all App Inventor components) by Yusuf Cihan
See the App Inventor Extensions document about how to use an App Inventor Extension.
For the extensions directory see here.
Related
I wish to make a mobile app that will take a picture of a student’s answer sheet with OMR check boxes filled in.
And I want to then read the results of the answer sheet (which check boxes are marked) on the app. (offline, not using a web service, or api)
I'm using xamarin croos platrom application. (Androis and IOS)
how can i do this? Or, is there a tool for this solution?
Thanks.
I added the component TinyDB1 to Screen1.
Then I went to Screen2 and tried to add the same database as a component, but it's not there in the palette (left hand side screen). It's also not recognized in the call block I added
I would like a common TinyDB as a way to transfer data between screens ...
In the designer of Screen2 you first have to drag a TinyDB component from the storage drawer into the working area, see also the TinyDB tutorial by Stephen.
A very good way to learn App Inventor is to read the free Inventor's Manual here in the AI2 free online eBook http://www.appinventor.org/book2 ... the links are at the bottom of the Web page. The book 'teaches' users how to program with AI2 blocks.
There is a free programming course here http://www.appinventor.org/content/CourseInABox/Intro and the aia files for the projects in the book are here: http://www.appinventor.org/bookFiles
How to do a lot of basic things with App Inventor are described here: http://www.appinventor.org/content/howDoYou/eventHandling .
Also do the tutorials http://appinventor.mit.edu/explore/ai2/tutorials.html to learn the basics of App Inventor, then try something and follow the Top 5 Tips: How to learn App Inventor
I'm building an app, and I was curious if there's a way to open the app when you're on the website through the iOS Safari extension. So, if I'm on a post I'd tap the app icon in the share sheet and I'd pass that to the app to load the post in the app.
I know the Bing app can translate the current website and inject directly into the DOM, so I was wondering what custom logic you can implement.
There's really no way to open the app from this kind of extension. Extensions can't access [UIApplication sharedApplication], so they can't call openURL:. There's an openURL:completionHandler: method on NSExtensionContext, but it only works in "today" extensions. Share extensions can display a fully custom UI and can save data that's available to their containing app, but they can't actually open that app.
I am developing share extension for my app. In my share extension info.plist , i added NSExtensionActivationSupportsImageWithMaxCount activation rule.So i expected my app share extension will present in any image share from any apps.But my issue is my app share extension also presenting in apple's Open-In options menu view.Is there any way to stop presenting my app in Open-In menu?
Note: My app has supports Custom URI schemes for different type documents.
Is there any tutorial available for creating Universal UI which can run on iPad as well as iPhone on different resolution. I tried looking in the official documentation, but couldn't find anything about UI files.
I notice you've tagged this question with Marmalade, so I'm assuming you are talking about how to write a Universal app in Marmalade? If so then creating a Universal UI is pretty much up to you to implement in the best way you see fit.
By default all Marmalade apps are Universal apps, though you can limit to iPad only with the MKB setting iphone-ipad-only.
Marmalade does come with the iwui module that allows you to lay out user interfaces with buttons and text boxes etc. but ultimately unless you have a very simple UI you'll need to either provide different UI layouts for each screen resolution/orientation you wish to support, or do some fancy laying out in code.
Apple wisely chose to persuade developers into creating separate UIs for iPhone and iPad since the one-layout-fits-all approach generally looks bad at any screen size.