I wanted to ask is there any professional name for one page / screen / view in GUI design / development. Let's say I have one "screen" and on this "screen" there is a button that moves user to another screen. Is there any name for those screens? And by the way - do they both live in memory in the same time? I've seen different approaches to this so it makes me confused.(There is a router in react, there are stackviews in Qt and ios/android native apis. ) Should I keep all the screens in memory when the program stars or keep deleting them and rendering again?
Related
Im writing an application for workers in our factory and one of requirements is that they should be able to take images using camera integrated in PDA with WM6.5.
The main difficulty is, that thay MUST NEVER EVER be able to enter windows, Start button, desktop etc. They are allowed ONLY to see my fullscreen application.
I succesfully deactivated BlueTooth + red, green and volume buttons (if you are interested, im pasting links here)
http://forum.xda-developers.com/showthread.php?t=546737
http://msdn.microsoft.com/en-us/library/bb431750.aspx
http://social.msdn.microsoft.com/forums/en-US/vssmartdevicesvbcs/thread/a4f9f41d-47a8-4080-8613-2c2ddcf4c012/
And now I have to implement the camera function. But as CameraCaptureDialog opens a new dialog and shows start button, task bar and allows user to open list of applications, I must not use it.
I must create my own dialog that will show the Live Preview in a panel or in an imageBox and photo will be taken using a button.
I searched the whole internet and found only DirectShow.NETCF (but people do not recommend it) and CameraCaptureDialog.
Can I somehow redirect the CameraCaptureDialog to my dialog? Or can I access camera directly via .NET framework? Or can I modify the CameraCaptureDialog not to show Start button, menu etc?
Looks like you have a bit of a challenge. I agree that Directshow is a questionable solution, but it may be your only option. I did get http://alexmogurenko.com/blog/directshownetcf/ to work, but only on low resolutions.
A better option might be to find a device that does not show the menu bar/start button. AFAIK, the HTC HD2 has a very clean Cameracapturedialog..
Good luck.
I am developing a chat application in blackberry.
I have made a main screen which acts like the home screen of the application. Whenever application is started this screen appears first.
There are like 5 screens (1 Main screen and 4 other screens).
My problem is..I want to update this 1 main screen when something happens on other 4 screens. Like For example, if I'm using the voice recording screen of my application. I have to add an icon to my main screen of the application indicating I have recorded a voice message after I have finished up.
I am not able to get the logic for doing this. Since I want to update a screen's UI which is already on stack, from a screen which is at the top of the stack.
And also, I want to keep those things at the main screen of the application whenever I start my application(just like history of the activities).
please help.
Read this article:
http://berrytutorials.blogspot.com/2009/12/blackberry-threads-dynamically-update.html
It shows how to update UI from different thread using Observer Design pattern. But you can use same technique to update screen from different screens.
Take a look at MVC design pattern.
Implement screens as Views which get notified when data model changed.
I have recently started on a project developing a window mobile/ce buisiness application. I have a ui design that uses a wizard to capture input data. To get the wizard started we open a windows form and maximize it. The form has one panel on it that is set to the size of the form. We pass a reference to the panel into the wizard controller as a container for the wizard user controls (each wizard step is a user control and the user control's size is set to that of the panel and thus the windows form. When viewed in a windows mobile emulator this works great the user control takes up the entire screen and the controls on the wizard step control are all visible on the screen with no vertical or horizontal scroll bars visible. When we load this onto one of the potential handheld devices the windows form doesn't fit exactly onto the screen as I would expect. There are both horizontal and vertical scroll bars and the controls aren't all visible. Does anyone have any hints and tips on getting around this problem? Is it possible to maximize a windows form in such a way that it exactly fills the screen on any mobile or ce device?
You need to check the screen resolution of your emulator and of your handheld device.
I suspect you are working on different screen resolutions.
If it's the case, then set the screen res for your emulator to match the screen res of your device. If for some reason this is not possible, just create your form to match the screen res of the device and try to fit all your UI in that limited space.
If you need to support many screen resolutions, you have 2 approaches:
1. Develop for the lowest res. This might look a bit ugly for higher res devices
2. Use anchors and control docking when defining your form layout.
I've learnt Cocoa + Objective C primarily for iPhone development, and I need to utilize this skill set to build a very basic kiosk application for OS X in a couple of days. The application is basically as follows :
The setup has two touch screen monitors, the app must be running full screen mode. The monitor on the right acts as a detail view to a list of options on the left. There are 3 options on the monitor on the left. Picking one will play a movie on the right, Picking two will take you to a quiz, Picking 3 will pull up a Webview.
The user may not use any other operations on the PC. (I've started reading about OS X application development and realized Cocoa provides a kiosk mode for these types of apps)
My questions briefly are
Firstly, any help on how to get my app running in a kiosk mode is much appreciated! I'm under a bit of a time crunch (2 days to get all this done, talk about life in startups!), so completely static content is fine, I'm slightly worried about how OS X will handle full screen mode if an app has been written in a smaller window size. (Scaling etc.)
Next, assuming there are two windows, one on each screen, how do I deal with focus? If the user suddenly gets bored with content on the right and touches the window on the left, the first touch will probably act to focus the window and the second will act as a click on the button. I'd like to avoid this scenario!)
What are the navigation paradigms in OS X ? I'm guessing it's not as simple as [navigationController pushViewController]? In short, how do I display a new view over an existing view?
Thanks,
Teja
Firstly, any help on how to get my app running in a kiosk mode is much appreciated!
http://developer.apple.com/library/mac/#technotes/KioskMode/
Next, assuming there are two windows, one on each screen, how do I deal with focus? If the user suddenly gets bored with content on the right and touches the window on the left, the first touch will probably act to focus the window and the second will act as a click on the button. I'd like to avoid this scenario!)
Click-through is the default. If you have any custom views, respond to acceptsFirstMouse: with YES to support click-through in them.
What are the navigation paradigms in OS X ?
Typically either window-based or source-list-based. Your application is atypical.
I'm guessing it's not as simple as [navigationController pushViewController]?
It's simpler and more complex at the same time. There is no stack to manage; you can have multiple windows up at the same time. It gets more complex when you want everything in one window (as in your kiosk-mode app), in which case you end up using tab views (with or without tabs) to enable the user to switch from one view to another.
In short, how do I display a new view over an existing view?
You don't. Layering one view over another in the same superview is barely supported at all in AppKit, and almost always wrong.
In a normal application, you should make multiple windows. In an app like yours, you'll need to use tab views. View controllers may help you here, although NSViewControllers are very different from UIViewControllers (as I mentioned, no view stack); they're more similar to NSWindowControllers.
I have to port a GUI that is currently running on a pc, to a wince device. I have already compiled the code on a win CE platform, the problem is now with the size of the screen of the device which is smaller than some of the dialog boxes of the GUI. I could resize some them in resource view of visual studio 2005. I am unable to proceed further as a lot of screens have bitmaps mapped to them and i cannot just resize the dialog boxes without changing the corresponding bitmaps.
What is the best way to proceed- my last resort would be to disable the bitmaps and redraw them at a later stage.
is there some method of automatically mapping the size of the screen to all the dialog boxes so that they would automatically resize (alongwith the assocaiated buttons etc)
Honestly I think my advise would be to stop and think about the differences between the two contexts before event considering how you would scale the interfaces.
PCs and phones have completely different interaction paradigms and simply scaling from a PC to a phone is very unlikely to work. Even if you could, it's likely to produce an unsatisfactory user experience.
I would expect that the best way to proceed is to sit down and draft up a new UI for the phones. Then bring you back ground code across from the PC and code up the interface part to work with the new UI. If you code is designed according to MVC principles then you are just looking at recoding the controllers and redesigning the views.