I have a basic understanding of Java , like basics nothing special, so I was wondering if someone would be kind enough to help me with an example for how the following should look
When the app is opened it takes you to a scene with a background photo and a basic selection box prompting the user to make a selection out of a list of different choices, then which ever choice is picked will load a new scene with the corresponding image or images for that choice. Any and all input is appreciated
Related
I want to be able to set up a series of menu's, at the end of selections it then links to an image, like a jpg or pdf perhaps.
Let me put it in a context. Maybe as a playbook viewer (American Football). I start with 'Offence' and 'Defence' as my options, which ever I choose takes me to a list of formations, then to 'Pass' or 'Run' then a list of plays. When I select a play if shows an image of the play.
Another might be job descriptions. I select the level 'manager', 'assistant' etc, then the section and then it shows a job description as an image or I guess text.
I think there are probably quite a few uses for this. I know I could set this up with basically web pages stored locally on my phone, but it would be kinda cool to have some smooth swooshing animations and such.
I'm wondering if it should initially be a desktop application so you can link up the menu's and images and it then compiles an apk for you?
Is this possible?
More generically...
What you're describing is a hierarchical database.
You need a tree manager app - where all your 'menu items' and subordinates are simply nodes and leaves of the tree.
A generic app would allow nodes/leaves to be 'textual', iconified, or pictures.
I haven't done any searches... but given that iconified list views, and cursored SQL queries are part of the standard package.... I'd think this would be relatively straightforward to both develop (app to add nodes/subnodes, builf the tree, enter/import the content) ship (app to serialize the database config+data, as a psuedo-app) and deploy (load a serialized db, execute it)
I'm a noob at android & at Java - but I might take a crack at something if I ever find time (my job & family don't leave a lot of time for anything else)
Found this and figure someone might be interested.
Taken from the Post:
looking for an Android application developer to pick up where another developer left off work on a drill-down Application/Travel Guide. It is a fairly simple application, displays tables, content and images in about 130 separate views. (The only animations are moving between views and scrolling through content.) Project is based on an existing iPhone application.
http://newyork.craigslist.org/mnh/cpg/2013929163.html
I could use some help with an app I'm working on. I need to know how to control the views and work with which things are in focus. I also want it to work even while in the background so using a handler or something else is knowledge I could use help with. I've been sifting through the javadoc and multiple other forums and am pretty much stuck. Anyone with decent knowledge that would be willing to help me out should message me. Thanks in advance.
First I would move this to the Android dev forum
Android uses Intents to display and run processes. Activities are Intents (views)that you can actually see on the screen and Services are Intents that can be run in the background.
Starting on the Android dev site is really the best place to find the answers to the problems.
That and using the Android examples that come with the SDK. Good luck and I hope you were talking about Android! XD
I was talking about android so here's what i'm trying to do. I want to take in trackball movements and pretty much make it so they don't affect my program or others. I'm not sure how to make it so that requestFocus() will take whatever view is currently on the screen, capture it, and pretty much revert right back to it if the trackball is used. I've tried a lot of different things, but I have been stuck on this forever. Anyone know how to accomplish this because for the most part I think that the trackball is not documented all that well. Any suggestions would be great!
I would look at the http://developer.android.com/guide/topics/ui/ui-events.html , onTrackballEvent(MotionEvent) . You should be able to override that in your service, and just process the motion however you want and not call super.onTrackballEvent();
The problem is that although onTrackBall does captures events, it does not capture all of them. In the docs it says that the method will handle all events not already handled by a view. So I guess my question overall is how do you do just that? Take in every trackball movement no matter what view is reading it? Whether it be another app or anything else. How would I capture the remaining movements?
So after a bit more research here's what I've come up with for what I need to do. Either access the event queue or make it so any time the trackball is used, whether on the homescreen or something else, my application will be able to take these events and manipulate then as i need to. So anyone willing to help with this? I figure I need to make a thread, but how do I get it to read in other applications readings? Is this even possible?
Hi,
A year ago I developed an app as part of a group project at uni. Due to the limitations set by the project rules the app isn't properly designed for Android. The app is a tour guide, in 2 parts. The guide itself is an XML file which has all the content on it. The other part is the player, which is an Android app. The player parses the XML and forms Java Classes to store the data and then play it. The content is saved in the form of Slides in a Slideshow (part of the requirements of the project, not our choice). So for instance 1 slide will be the main menu, then clicking a button will take you to another slide which will be a sub menu and so on.
Now a year later I've come to update this app, originally I was just intending to change the AbsoluteLayouts we used to Relative/Linear/List/whatever works best for that particular slide and also to put the layouts into XML rather keep them in the Java. However I was wondering what would be the best Android practice for an app such as this?
The advantage of using XML for the guide is that say if we had a guide to a different city we could just upload that new XML to a server (the player can download remotely) and then download it to get a new tour guide. However would it be best for me to strip away all of this and start afresh, with Android in mind? I.E. by removing the need to parse an XML file at the start and just have a new app for each city.
I've been thinking about a complete overhaul as changing AbsoluteLayout will be a pain. At the moment each component is given X and Y coordinates in the main XML file, so changing that to relative commands, changing the parser to read that will be hard. Also it's best practice to store the layouts in R.layout but it would be hard to convert the layout from the main Tour Guide XML to a layout XML... if that makes sense :/
If I were to remove the main XML, how would I handle each menu or content page? Would they be given their own activity?
Sorry for the long post, I just want to be clear on what the best way to update this app would be and am just learning how to properly design Android apps. I really appreciate any advice and for taking the time to read this post!
If I've put this in the wrong forum then let me know and I'll move it
Sent from my GT-I9100 using XDA App
check out
http://www.appcelerator.com/
i created my first app using it
and its on the market with around 2k downloads
it has its issues and bugs but it was my first real coding experience.
its worth checking out
and its free
Good afternoon everyone! I have been looking for a forum to hit up that isn't stack-overflow for android developing and a friend pointed me here. Currently my experience with android is very minimal, I am working on a simple (simple is read, "Dear god what did I get myself into") project for school with no background in this sort of platform. I program in PHP and C# primarily and thought that this project would be a fun way to immerse myself in Android.
The application I am writing is a sort of life style app to gather daily eating habits from the user in an attempt to make you feel bad about your terrible eating choices and get you to eat better. If anyone is familiar with Good Eats I am basing the app around Alton Brown's 4 list diet.
Here is where the issues have started:
I constantly feel like I am coding myself into a corner and have started over a number of times, there seem to be many ways of gathering this information from the user but non of which seem very cut and dry with database interactions.
What I am looking for is a way to gather the day and list choices from a user (for the lists I was using dialog check boxes spawned from buttons but this doesn't seem to be the best way to do it as I cannot figure out how to store the checked off boxes within the dialog).
So my noob question is, are there any tutorials dealing with basic data gathering and storage?
Thanks for your time and look forward to hanging out on these forums more regularly.
ZachM86 said:
So my noob question is, are there any tutorials dealing with basic data gathering and storage?
Click to expand...
Click to collapse
Try this link -- developer.android.com/training/basics/data-storage/index.html
ZachM86 said:
Here is where the issues have started:
I constantly feel like I am coding myself into a corner and have started over a number of times, there seem to be many ways of gathering this information from the user but non of which seem very cut and dry with database interactions.
What I am looking for is a way to gather the day and list choices from a user (for the lists I was using dialog check boxes spawned from buttons but this doesn't seem to be the best way to do it as I cannot figure out how to store the checked off boxes within the dialog).
Click to expand...
Click to collapse
this may help:
create variables for each checkbox that can be checked
in your dialog interface onClick if (isChecked) { variable = 'which';}
then enter it into your database when submitted. Then when you query just correlate the variable to the corresponding string name
this may help as well (go down to the multi/single choice list)
http://developer.android.com/guide/topics/ui/dialogs.html