My app contains two Frames in one window (FirstFrame & SecondFrame).
When I try to navigate in FirstFrameViewModel with navigationService.navigateTo(AnotherView) AnotherView fills the entire window instead of filling only FirstFrame.
How I can resolve my problem?
Related
I have implemented custom tabs in my app and I have bottom navigation bar. When I click on any item in the bottom bar the fragment opens. Inside the fragment the custom tabs have to open. Custom tabs have to be open in a view not as a separate window.
Custom Tabs is not a View, but an entire Activity that is hosted in the browser process and handled as part of the application tasks stack. So, it can't be part of another Activity's view hierarchy and can only be used as a standalone Activity.
The Android WebView is a an Android View and can be used inside an Activity. But,
generally, content opened inside the WebView should be designed with the component in mind, as it doesn't support every API available to modern web apps (eg: push notifications).
I user LayoutPanel in the GWT view and each time i press the TextBox the Keyboard appears and squeezes the view.
on android this happens and on ios it doesnt.
i want to keep the height in proportions to the view original height...
thanks
You have two options:
A. On resize event in this view, check if user agent is Android. If it is, force the size not to change.
B. Create a different view for Android devices, and then use GWT's deferred binding to substitute your view class if user agent is Android:
https://developers.google.com/web-toolkit/doc/latest/DevGuideCodingBasicsDeferred#replacement
This is a another good post:
http://code.google.com/p/google-web-toolkit/wiki/ConditionalProperties
I'm a newbie in UI Automation using instruments and I have the following question:
- the application starts and I get the mainWindow screen (which contains SignIn and Register buttons)
- I've managed to write the JavaScript code in order to tap one of the two buttons.
-> after tapping one of the buttons, another screen is displayed. let's say the Sign In screen which contains two fields: username and password.
In this case, how can I tell Instruments that this is another screen and this contains another elements that should be retrieved in order to fill the fields and tap the Sign In button ?
I only know to retrieve the mainWindow. I don't know how to write the code for a next screen
Did you try to capture what you do with the small record button in the Javascript editor window? That way you can find out how Instruments can call the elements you use.
See also this thread:
UI Automation - how to capture - record using javascript editor
I am very new to iOS development. I am going to start a new project which is mostly related to to the database. Can you suggest what should I start from Window or view based app?
A view-based app only have one view, and includes a nib. However, window based app don't include a nib or a view, it's for add your own view.
I would chose view-based
1.There is no such difference in both
In View Based app you will get a default view controller in window.
In Window Based app you will not get anything by default already added in window, you have to add your own view.
They're used for different things. Neither is better than the other.
If you're a total rookie, I'd go with View based. It comes wired up with more stuff for you by default, and lets you work on your app's functionality rather than the details of getting stuff on the screen. It also limits you in ways that Window based doesn't, but for your level that's probably a good thing.
Anyway you have to make ViewController if you make project using window based.
Make your project using window based and View based. and compare both. So you can find what is different.
and iOS can have many view on only one window.
I'm creating an app and I need some help with design.
Launch Screen - I want to show 6-8 "category" buttons with labels loaded from an array ("normal" buttons from interface builder - not tab bar buttons or menu bar buttons).
Table Screen - When one of the category buttons is pushed on the launch screen, I want to show a table view with all of the items in that category.
Detail Screen - When one of the items on the table screen is selected, go to a new screen with details for the item. There will be an action button on this screen which will remove the item from the list if pressed.
My questions are as follows:
1) I don't want to show navigation buttons on the first screen. Can I still use a Navigation-Based application and hide the navigation controls on the first screen, or would it be better (easier) to create a view-based application and put a navigation controller "inside" one of the views? I'm totally open to any basic design approach suggestions you may have.
2) I've figured out how to create a sqlite3 file, add it to the project, query it, and generate the table view from the results, but I'm not sure about how to store the sqlite file in a way that will persist on the device when the user upgrades the app later. Any pointers on that?
Thanks for any help/links/documentation you can point me to. I've watched a million tutorials but none of the ones I've seen really address basic app design.
Now for Q1, both ways work fine but if you have buttons from the first screen, having a uinavigationcontroller might make it slightly easier if you plan to have back buttons on the screens after the first screen.
For Q2, to make the database persist when the user updates their app at some stage, simply keep the original database and include a new database (with a different name) with additional content, then modify your original database and import any additional content to it.
You can also do variations of that also, ie import content from old database to new database and etc. But the key is to keep the database file names different, ie add database_v1.sqlite, database_v2.sqlite and etc.
BTW don't forget to clean up any databases you won't use in future.