I have found the trackball so hard to maneuver to the most simple locations in any kind of compose window -- to go from beginning of a line to end of line, top of composed text to end of text block... I would really like for it to move much faster in those situations.
Also in scrolling up/down a web-page for simply reading.
At the same time. I find it way too hair-trigger and uncontrollable when trying to locate the link you want to click, or the field you want to edit on a form or any page.
Is this all Android-controlled, or does HTC hardware and its Sense UI add controllable refinement and adjustments?
Thank you.
(Bonus question which I will search for by myself: Are the hard buttons remappable to other functions. If so, is it possible to multi-function a hard-key by having it do one thing with a very light touch, and another with a press & hold ? )
These issues, as well as my Q re capacitive vs resistive screen are all about discomfort from Repetitive Stress having to place fingers and finger tips is positions completely different from using Windows Mobile devices. I am sure there much be advantages I am missing. I really look forward to those.
well, is it possible to implement bouncy scrolling in x10, the one with the spring effect at the end of the document? I guess Apple has a patent for it, heck it has patent for everything!
I did some searching and got that we can have this effect in the homescreen (through adw launcher), but i am talking about every scrollable menu list.
Incase you don't get what i am talking about, the effect is in devices like iPhone, Samsung Captivate, etc. When a menu list reaches its end, the scroll does not stop, rather there is an spring like effect which allows the list to go little up or down, depending upon the direction of the scroll.
Cheers!
For the home screen and app drawer this is definitely availible through adw and possibly launcher pro. However in order to have an effect in menus like system preferences and such would I require a modification to the rom I believe. I could be wrong
was thinking the same thing. i suppose its not easy as like opening build.prop and putting a line that says " windowsmgr.scroll_cool_bouncy_effect = yes ", is it? haha.
But someone should have some idea on how to do it..
does anyone know about custom menu loaders?
anyone....?
I'm designing an App with several layers of menus (on the screen, not from the menu button) which lead to several content pages each, so in total I'll be looking at probably 6 screens of Menu and about 30 content screens (just a picture, text and some buttons).
Should this be just 1 activity for the entire application and with each menu and content page loading a different layout xml? If so how do I do change the layout?
Or should each menu screen and content screen be its own activity as well as having it's own layout xml?
Thanks very much for any help.
I usually use dialog box for simple user infos and I prefer activities to do something more complicated, but it's my opinion. I prefer activities because are simplier than using different dialog boxes or anything else, and so my code doesn't become an incredible mess
I don't think it would work to have dialog boxes to display buttons, like I need for my menus or content pages.
If I did only use 1 activity for it, what's the best way to redraw the layout from a different xml when you click a button? Just have the onClickListener call setContentView(R.layout.new_layout)?
PrometheanFire said:
If I did only use 1 activity for it, what's the best way to redraw the layout from a different xml when you click a button? Just have the onClickListener call setContentView(R.layout.new_layout)?
Click to expand...
Click to collapse
Ok, I understand your needs. Unfortunately I didn't use a new layout in the same activity after a button click, it should be tested.
For my game, I have on the same screen different buttons, textviews, and imageviews that appears and disappears, even after a button click. I putted all of them in the same layout xml (one above the other, what a mess!) and I set the different visibility suitably the buttons clicks (the OnClickListener). It works for me because I have 7-8 items to manage, but maybe not so smart for a lot of different items.
In general, Google recommends using different activities, I remember reading about it in the Dev Guide somewhere.
Although maybe your case is different.
The default recommendation of Google is to use activities. But it does depend on your usage - if everything you are doing is related to the same "activity" (for want of a better word), it may make good sense to keep everything in the same class.
You should also think about what behavior you would like the app to have. Do you want the user to be able to use the "BACK" button to step backwards in your menus? If so, it may make sense to implement this as multiple activities (which will give you this behavior for free), rather than implementing it manually.
I think I'm leaning towards activities as from all I've read it does seem to be best programming practice, it just seems a bit of a waste for me to have 1 activity just displaying a menu! However yes, it would be much easier to use activities then just have user press BACK to navigate backwards.
Also with having 1 activity just switching layout it would mean a massive onClick() 'switch' with at least 30 'cases'! I had thought about implementing my own Back button on the screen but that would be a pain to code.
Thanks for the replies, think I'll go with separate activities and see if it works ok, like I said my main concern was that it's a waste of an activity to have it do something so basic!
Maybe ViewFlipper will be useful?
ViewFlipper just seems to add an animation to changing the layout, no? I'm wondering whether I should just change the layout per screen or to start a new activity per screen.
I've worked it out and I've got 27 Menus, each of these is a ListActivity and 62 Content Pages (each of these is an activity calling a RelativeLayout and some onClick Listeners).
In total this is 89 activities, is this too many for one application? I like the idea of having a different activity per page as that means the user can just press the Back button on their phone to go back up the menus rather than coding in one myself. I've got it working with all the menus but only 1 content page and it's ok, but I can imagine that if I add the remaining 62 contents it may get bogged down?
But yeah, is this too many activities for one app? It is likely at a given time the user probably won't use more than 10 of them.
trying to have a single Activity and then have it able to handle every layout you throw at it and its coorosponding functionality will be a nightmare. use multiple Activities. it will also make using the back button alot easier.
http://developer.android.com/guide/practices/design/seamlessness.html#multiple-activities
Thanks, shouldn't take me too long to create all the content (with copy paste and find/replace) so will see how it works like that.
i am trying to do something silmiar to apps like swipepad, taskxp, and taskie where the user swipes
or touches an area of the phone screen like the edges and the program functions even if its activity is not shown.
I have no idea where to start since i dont even know whats its called
Any help would be much appreciated!
Is it possible in Android to have partially scrolling homescreens? In other words, can you have a homescreen set up so that instead of going page-by-page, you can scroll half a page at a time, or dynamically (i.e., a full swipe = a full screen, half swipe = half screen).
I've done a bit of searching on this, and haven't been able to find anything. I was wondering if anyone has looked into this before.