Is there a UI toolkit for Java ME that I can use to generate UI elements on the fly, based on, for example, JSON or XML that I send to the device by way of a web service pull?
Multiple UI frameworks available for Java-me application. But i suggest LWUIT framework is good. LWUIT offers advanced UI capabilities and a clean API that is inspired by Swing. You can develop your own theme and animated screens by using LWUIT ResourceEdit. For more info see this LWUIT blog.
You can download latest LWUIT from this repository or you can use latest release of LWUIT version 1.4 available. LWUIT supports Blackberry, Android and Symbian OS.
For more info see this links for your reference,
Introduction of LWUIT
Building theme for LWUIT
For simple applications with a minimal footprint, try Thinlet JME. For more complicated GUIs, check out this list. Also consider going with HTML, mobile phone browser are getting better every day.
Note that if you want stuff like this to work in practice, you'd want a script engine also.
Related
Please suggest if there is any way to automate the testing of Javafx application using UFT 12.02 as UFT is unable to identify the objects in JavaFx application.
Thanks in advance.
After a quick Google search, you would find out that UFT has no direct support for JavaFX applications.
This link talks about it:
https://community.hpe.com/t5/Unified-Functional-Testing/QTP-not-recognizing-JavaFX-controls/td-p/5793877
A brief summary on the answers:
QTP does not have any separate add-in specifically for those controls,
QTP has only the standard Java add-in that would work if the mentioned
controls are Java standard controls and if they belongs to the
standard Java Swing classes or Java AWT clases, only standard no any
kind of customized nor third party control. Otherwise, the recognition
will be basic because QTP will not support the controls.
You can find more information about the technologies that support the
Java add-in in the next link at page 4:
HP QuickTest Professional 11.00 Product Availability Matrix
http://support.openview.hp.com/selfsolve/document/KM1210389
Actually we have an Enhancement Request to evaluate the prosiblitiy to
bring support to JavaFX objects:
Support for JavaFX 2.0.2.
https://support.openview.hp.com/selfsolve/document/FID/DOCUMENTUM_QCCR1J26625
For the moment as a workaround we recomend work with these kind of
controls as third-party controls.
How to work with unsupported or third-party controls
http://support.openview.hp.com/selfsolve/document/KM186906
I don't have further knowledge about it as I've never worked with JavaFX before, but I belive here you will find enough content to help you out
Please check out UFT 14.01, it is supported natively now.
UFT now supports testing applications built with JavaFX, natively using the Java Add-in.
Prior to 14.01, JavaFX was supported by Microsoft UI Automation for
purely JavaFX widgets.
You can find the documentation here: https://admhelp.microfocus.com/uft/en/latest/UFT_Help/Content/Landing_Pages/Whats_New_Landing_Page.htm#hp-minitoc-item-2
Xamarin
Write the model in C#
Write the views for each OS in their own native way
Xamarin promises that the new functionality in libraries is added the same day
Telerik Native script
Write in javascript and call native script's api that then calls the separate OS javascript apis?
Write the view in html5 and css which is re-usable for all OSs as they now all support html5 and css front ends?
Telerik simply states... and I paraphrase 'it does not have this problem'
If the above is so, how is Telerik any better than Xamarin as it states on its website:
"When using NativeScript the new additions to the native platform are
available immediately. This is not the case in neither Xamarin or
Appcelerator, where there are technical limitations and wrappers needs
to be created when new native platform features are added."
I am confused at how Telerik is being penned as being better than Xamarin when Xamarin comes with strong type language without using TypeScript's slightly loose thing going on. And also that Xamarin does in fact sit in exactly the same boat as Xamarin apart form the view part... which is actually supposed to be a benefit?
Question:
- What's the difference between them apart from the two I have denoted?
- Why would Telerik claim such a thing?
[Disclaimer: I work for Telerik.]
Telerik NativeScript and Xamarin are solving similar problems in different ways. Both frameworks are focused on enabling developers to create cross-platform mobile applications with native UI and shared, common code across all platforms.
For NativeScript, we're focused heavily on the web developer skill set. We want anyone that is comfortable today writing HTML/CSS/JavaScript to feel instantly at home creating native apps using NativeScript.
The only thing that is a little different is that views are defined in an XML-based markup. This markup is parsed by NativeScript and rendered as native UI on all target platforms. (NativeScript modules encapsulate the platform-specific renderings.)
The capability you highlight is also something unique to NativeScript's approach for exposing underlying native platform APIs. NativeScript effectively uses (build-time) reflection to make ANY native API available to the JavaScript proxy. That includes 3rd party native libraries. You do not depend on Telerik (or the open source community) to update NativeScript to take advantage of these new APIs. You simply execute a command and auto-discover the new APIs.
Of course, we don't expect a lot of people to write against the raw native APIs using JavaScript, so that's where modules again help encapsulate the different native APIs and expose a single, clean, cross-platform JavaScript API. Anyone can create NativeScript modules.
There's a great post that explains how all of this works in much more detail on the Telerik Developer Network (TDN):
http://developer.telerik.com/featured/nativescript-works/
NativeScript's public beta will be available this week, and v1 will ship in May.
UPDATE [Feb 2016]
Since this was originally posted, NativeScript has shipped and is now in v1.6. It is also now integrating heavily with Angular 2. You can track the project progress on GitHub: https://github.com/NativeScript/NativeScript
UPDATE [June 2016]
There are now performance metrics comparing NativeScript and Xamarin. Please find them here:
https://github.com/NativeScript/sample-iOS-Profiling/tree/performance-tests
Telerik is a UI component and it has some beautiful control for designing in xamarin forms,MVC. Net and etc, but xamarin forms is a technology that helps deveopers to make mobile application using c#
I need to add some multi-touch gestures to google earth plugin, and I want your opinion on witch way I can do that.
I work with a Dell XPS 18, running on Windows 8.1.
I found a way, using the RawInput API (here), but it's a very low level solution, so do you have another idea?
Thanks!
This is not an easy problem. The good/bad news is that you have found the correct API to use. The problem is that you can't simply "add multi-touch" to the plugin. The plugin runs in a web browser. The web browser doesn't have a concept of pinch-zoom or pan-tilt.
What you have to do is embed the plugin in your own custom program, and then intercept the raw inputs in that program. From there you will have to all the translations, and manipulate the GE camera appropriately (or, in some cases, just pass the events directly to the plugin.)
Again, this problem is not easy to solve.
A reasonable starting point (using WinForms / C#) is:
https://code.google.com/p/winforms-geplugin-control-library/
I would suggest trying to rewrite this library using WPF (maybe this already exists?) .NET 4.5 has gesture support built into WPF. (.NET 4.0 might have some stuff as well, not sure.)
I am developing (yet another) password manager add-on for Firefox. My add-on needs to:
Add two context menu items to each password field.
Open a dialog box or floating panel when the menu item is selected.
Access a specific method of a specific XPCOM component.
Fill the password field.
Include a preferences window.
Be compatible with Firefox 4.0.
Preferably, also:
Run on Firefox 3.5 and 3.6.
Some users don't update to the latest version.
Firefox 4.0 won't run on a PowerPC Mac.
Install without a restart on Firefox 4.0.
Allow for localization.
I have tried the Add-on SDK (formerly known as Jetpack), and it makes it very easy to start developing. However, I find that HTML cannot easily create "native looking" dialog boxes and that the SDK is rather heavyweight. (It takes many kilobytes to build a simple extension; that includes an XPCOM component!)
What are the advantages and disadvantages of using the Add-on SDK to develop my Firefox extension? Is it ready for "serious" extension development?
Advantages:
Jetpack API exposes high level APIs for most of the things you mentioned:
Add two context menu items
floating panel
API for password manager
Jetpack based add-ons are restart-less.
Jetpack based add-ons are future proof in a sense that high level APIs will remain unchanged
for the coming versions of FF.
You may be able to use some community developed modules for APIs that are not exposed by SDK.
If this is not the last extension you're planning to build there is a potential for code reuse,
by building third party modules as ones mentioned in 4 (see docs for details)
Support for mobile FF is coming in post 1.0 version of Addon-SDK which may mean that your
extension can be made compatible with mobile version of FF with minimal to zero effort.
Jetpack comes with build-in unit testing framework.
Has a better security model, which will ease add-on review process.
Jetpack support commonjs modules / packages that which means that some of the code can be borrowed
from other projects like nodejs for example.
Disadvantages:
Jetpack no longer supports FF<4.
Does not yet have support for localization.
Has no API for building preference panels, but can be developed as third party module and shared
with rest of the community.
Add-on will contain code with layers of abstractions, that will increase size of add-on (there is
ongoing work that will reduce xpi size by excluding files that are not used by add-on).
I want to customize my web page for Palm pre. Is the a way to use Mojo in web pages for palm pre? Can I for example use a Mojo picker or a scroll tag?
You can now use ENYO in your HTML on any platform.
Built from the ground-up for mobile first - Enyo powers webOS, and was
designed from the beginning to be fast and work great on mobile
devices Now available for desktop and cross-browser development - Enyo
2.0 now runs across mobile environments and desktop browsers including Chrome, Firefox, and Internet Explorer Highly customizable and
extensible - Enyo core can be expanded with modules, UI widgets, and
more Lightweight and fast - Enyo 2.0 core is about 13KB gzipped, and
built for fast application rendering and performance Simple,
self-contained, and easy to digest - Build increasingly complex
functionality starting with simple, reusable components Built to scale
- Enyo was created on the principles needed to build vast, complex mobile and web applications Open Source - Enyo is available under the
Apache License, Version 2.0.
No, Mojo is an SDK that is executed on the Palm device (e.g. Pre, Pixi). The browser will not interpret (or should not interpret) code that it finds written in webpages. This would be a HUGE security vulnerability.