I used DateField in a Form. When I try to select a date it opens up calendar functionality provided by cellphone.
As you know the UI features in j2me are not that great. I looked at third party libraries to design fancy UI. So far I have not found any api which makes DateField fancy. Is anybody aware of any API which supports DateField?
Using the phone's native control for this is exactly what j2me is supposed to do.
The system has clear advantages when changing the phone language, especially when the alphabet isn't in basic ASCII characters.
If you want to control exactly the way the calendar looks, you'll need to draw it yourself in a Canvas and deal with user input, screen size and localization issues yourself.
In general, you might want to look into the LWUIT library for an intermediary solution between fixed native controls and direct screen access.
Related
Looking at the sample scenes, it seems like the MRTK uses a pointer system instead of actually giving you virtual hands that can be manipulated by pressing buttons or triggers on the controllers, and allowing you to grab objects.
Is there a built-in way to use hands?
There is currently not a set of virtual hands build into MRTK for VR, however it would be possible to rig up a custom visual for a controller that looks like hands, and animate the hands based on things like which buttons / triggers are pressed on the controllers.
Oculus provide hand models which are rigged in their SDK, which you can appropriate for use in the MRTK as shown in the video below.
https://www.youtube.com/watch?v=F3e2lwqVPyc&list=PLCK8aOPy3e4JhG06GRdlJkmNXoITEewxV&index=4
You'd just need to do a little more work to get the hand rigging hooked up to the MRTK hands.
I am working on windows 10 mobile app. If I design an UI for 5' device, it doesn't look good on 5.2' device. Also on emulators of different screen size show messed up UI. Is there any work around this? Or do I have to design it for every screen size?
Usually, please avoid to have fixed Width/Height for your controls. With a Grid layout, you can set columns/rows and place your controls inside each cells. This is a first level to adapt properly your interface. In addition, UWP provides AdaptiveTriggers if you want to adapt the layout based on the screen resolution (cf. https://channel9.msdn.com/Series/A-Developers-Guide-to-Windows-10/07) for additional information. Last but not least, please check Design&UI documention on https://developer.microsoft.com/en-us/windows/design.
The trick is with UWP that you can design for every screensize at once. It's just a responsive design you use (either HTML/CSS or XAML). But you have to use the right controls and settings.
Some guidance on how to design for various sizes can be found at the MSDN design page.
To create a dynamic layout with XAML, see this article. There are various panel-types you can use to do the layout (see this article). But if you really want to build a responsive UI (or change it dramatically in various sizes) RelativePanel is your friend.
we are making one mobile application in j2me java symbian. we want to display marathi font in our mobile application.we tried searching on various forums but was unable to get a solution related to language support. if not marathi please tried to provide solution trying any language rather than english. how to display marathi font in application and how to use unicode in marathi in j2me.. we need an expert advice on this...
The way that I have usually seen or implemented similar things done in the past is to create your own font texture and handle all the character drawing yourself. Basically, if the font you want isn't provided for the handset you are targetting, you have to handle all text drawing yourself.
I use the .net propertyGrid a lot to edit objects.
The MonoTouch.Dialog allows much of the same functionality for iOS. But it needs a way to simply allow double's to be displayed and edited. Float uses a trackbar - which can be useful sometimes, but not for entering data like a price, etc. Am I missing something?
very quick one, I was always wondering, do internet browsers use for rendering OS API functions to create buttons, render mages and so, or do they render it all on their own?
I first thoght that it uses system api, but there are some effects like when screen fades into grey and you see only small window in the middle, you know, thet effect used on many picture albums online, which I dont really how to achive using for example only Win32 calls.
EDIT: To be more exact, I know that final drawing on screen will always use system API, but you can send prerendered image as you want to it. Thanks.
Web browsers use their own rendering engines rather than OS API. Using OS API to render buttons totally depends on the design decision of a particular rendering engine. However, to run on various operating systems these engines prefer their own rendering to offer same look-n-feel across platforms.
Gecko, for Firefox
Trident, for Internet Explorer
Presto, for Opera
KHTML, for Konqueror
WebKit, for Apple's Safari and Google's Chrome web browsers.
Ref: http://en.wikipedia.org/wiki/Web_browser_engine
Do browser rendering engines useOs api for creating buttons, writing text, creating boxes, etc., or do they render all of this on their own using OS API just for actually show the rendered image on the screen?
I implemented something of a browser rendering engine (see e.g. Table of Supported Elements and Supported Properties for a list of the HTML elements and CSS properties that it supports).
I use system APIs (.NET Framework APIs, which are thin wrappers around underlying O/S GDI APIs) to:
Measure words (strings of text)
Paint words
Draw lines and boxes
Fill rectangles with solid color
These are the kind of API functionality that's implemented by the Windows GDI.
There are also some system (O/S or .NET) APIs that I use, to draw buttons and combo boxes (see Rewrite standard controls like edit, combo, etc?).
Becouse, the whole rendering of text, graphics and so seems pretty hard to write completely yourself
Yes, implementing CSS and everything does take a while. You've seen how long it took the browser developer teams to implement: several calendar years, many person-years.