I have to design a mobile application as my mini project. I cannot find the documentation of javax.microedition in my java folder. I tried searching it online, but all the websites have vague information. I need proper details of this package. Where can I find it?
tried searching it online, but all the websites have vague information
Did you try different search engines? I always switch to alternative engine when I feel that one I usually prefer doesn't do the trick.
Don't know if your case but to me results of search for "javax.microedition package" were totally different depending on engine. While one engine ("good") gave me a needed link at the top of the very first page, another had it buried at 7th page ("bad", really bad).
Anyway, there's pretty detailed and accurate answer at SDN Mobility Reference FAQ - J2ME Package Listing:
Question
What package names are defined in the J2ME environment?
Answer
The J2ME environment introduces a number of Java packages. These are almost exclusively placed into the package javax.microedition. The few exceptions are technologies that could be used in one or more other editions of the Java platform as well. For example, because you might use Bluetooth technology in either J2ME or J2SE, the Java APIs for Bluetooth specification (JSR 82) uses the package names javax.bluetooth and javax.obex.
The table shows the package names specified by the J2ME JSRs, as defined by the Java Community Process (JCP). It includes...
...continue reading at above link if you're interested in more details
Related
I know you can extend Adobe Premiere Pro with some simple JavaScript. The problem with that link (which I got to through the official Adobe website), is that all of sample code links are outdated (they point to the wrong location of the file, to lines that aren't correct anymore).
The second paragraph instructs you to install a bunch of things, none of which seem like things you "install", and they mention ExtendScript, which I don't understand whether is already installed with my Premiere or not (it's not available on Creative Cloud, and also the links I found on Adobe's website for it are, again, dead). I keep searching online and finding dead links to tutorials that no longer exist. Really, dead links everywhere.
I'm an experienced developer with good JS background, I just want know what I need, some simple examples of basic usage to get me started and maybe working links to some cheat-sheet I can use when I'm looking for available functions.
Extendscript is the name of the old API for automating Premiere and other Adobe apps. It's built-in and can basically do anything that you can do with the GUI, and it's javascript-based.
There is an IDE for Extendscript, the Extendscript Toolkit (ESTK) which has a debugger and allows you to inspect data etc. It's perplexingly hard to find on the Adobe website; I found it by a duckduckgo search here, I installed it through the creative cloud desktop manager, though I'm not sure how you do that with the current version.
As far as documentation goes, you're right, it's dead link city. There is a Javascript Tools Guide included with the Extendscript Toolkit, on windows it's in C:\Program Files (x86)\Adobe\Adobe ExtendScript Toolkit CC\SDK\. That covers creating UI elements, but doesn't explain Premiere's object model. AFAIK there is no official documentation for this, you have to use the ESTK data browser to look for yourself.
The CEP extensions are a new development and allow for easier integration with the host. I think you already have all the documentation there is for it. I'd advise that you pester Adobe to make it easier for developers like yourself to create tools for their users.
Here is for anyone else who gets here from a Google search: You can also go to this link to download the ESTK: https://helpx.adobe.com/download-install/kb/creative-cloud-apps-download.html
Yesterday a customer asked me whether there is some kind of javadoc library available for all the extlib control objects, like we have it for the standard Xpage related controls:
http://public.dhe.ibm.com/software/dw/lotus/Domino-Designer/JavaDocs/DesignerAPIs/index.html
All I could say was "have a look at XpagesExt.nsf and see how they did it...". Which is quite a lame answer, I feel. So I spent half this morning googling but couldn't find anything. Anyone having a link for me?
Thanks,
Lothar
I've added it to the OpenNTF XPages Knowledge Base, in the General space, but also cross-linked from the Extension Library space. You can find the XML definitions for components and complex types as well as the JavaDoc for Extension Library. I will endeavour to keep it up to date as releases come out (it's not onerous, so should not be an issue).
I will take forward an action for the next OpenNTF board meeting to see if we can host Javadocs for this online on the OpenNTF site somewhere (as well as other OpenNTF projects). It looks like there's not a way to host them within Confluence (the product used for the Knowledge Base), but that should not be a barrier. We may also be able to add Extension Library into the build process to automate the generation and publishing.
We are planning to develop an application that can work with any ECM systems. SO we planned to use CMIS.
As our application is in Java, I came across openCMIS. It seemed all useful.
But now I need to know, which all repositories are tested/supported with openCMIS?
OpenCmis will be really helpful for many ecm systems but it is not a one common answer for all of them.
For example, for IBM CM or Filenet there is IBM CMIS which comes bundled with Content Navigator. Please note this is also lacking some basic functionalities and i developed that just recently. (on the latest version)
I would recommend to build the java application using the most relevant CMIS apis you need and for the closest specific ECM product.If you want to build it in a way which works on all ECM platforms then the coding needs to be in different way.
like - identify which ecm system is being called by your java program
and then load the classes or functions for that specific system.
Hope the above helps :)
This page lists CMIS servers:
http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services
OpenCMIS is one the mostly used CMIS libraries, and I would say it is the most-tested CMIS library you can find.
I have not seen any "official supported list", but OpenCMIS at least works for Alfresco, IBM FileNet, NemakiWare, and most CMIS servers I have tried. A notable exception seems to be IBM Connections, because of a IBM Connections bug.
What would be the best practice to share busines logic c# code between MonoTouch and Mono For Android projects?
Edited:
Initially, my question was about the physical file sharing:
What do you propose to use: network file sharing or some code
version control (git, svn)? In my case I am using two workstations -
Mac (MonoDevelop with MonoTouch) and PC (Visual Studio with
MonoDroid).
What about Solution/Project folder structure? In
"Blog Post: Xamarin Mobile World Congress 2012 Unofficial
Conference App Released!" example structure is quite confusing:
several solutions in one folder and then different platform projects in one
subfolder with different folder and project names. It can not be accomplished nativly
with IDE. Are they editing content of solution files and folder names manualy
outside of IDE environment?
And for projects of common code what kind of profile (template) to
use? Monotouch has several: Empty Project, MonoTouch Library
Project and MonoTouch Binding Projects? In Android i supose -
Android class library?
This is a very general question, but here are a few resources that may help you get started:
Video: Cross-platform Mobile Development
Blog Post: Shared Libraries For Windows Phone 7, MonoDroid and Beyond
Book: Mobile Development with C#
Blog Post: Xamarin Mobile World Congress 2012 Unofficial Conference App Released!
Edit (to answer your new questions)
The idea behind linking files across projects is that there is only one actual copy of the file, rather than having to manage multiple copies and keep them in sync yourself. The file will actually exist in just one project and be linked into the others, but when the projects are compiled it treats the file as if it were actually there.
I can't speak to exactly how they created their folder structure, but I know there have been many cases where I would manually edit project or solution files to get the folder structure I want, because there was no way to get what I wanted through the IDE alone. This really boils down to personal preference on how you want your folders to be structured.
In the end, what you need is a class library project for every platform you want to target. When going with the linked file approach, it's totally up to you where you put the physical files. One approach I use often is to actually create a standard .NET 4.0 class library, put the files in there, and then link them into my Mono for Android and MonoTouch class libraries. If all you care about is targeting iOS and Android, that may be more trouble than it's worth, and you can just let the files live in one project and link them into the other.
Disclaimer: I've got a particular Mvvm methodology that I use for sharing code across multi-platform projects...
Despite this, I genuinely don't believe in "one size fits all" frameworks - I think you need to be careful to pick an approach that best suits your project, your developers and your organisation.
With that said, some of the tools you can use within the Mono development approach are:
using Portable Class Libraries to share exactly the same code between platforms
using platform specific Class Libraries to share code between platforms, linking these using the Project Linker tool from Microsoft
using #define code within your class libraries to provide platform specific implementations of the projects (I personally try to avoid this approach, but it does often provide the quickest route to market)
using DI/IoC techniques to provide components for those occasions when platform specific implementations really are required.
using a assembly linking to provide IoC - e.g. this is what the Xamarin MobileAPI does
using server-based logic for genuine shared functionality - e.g. using REST or SOAP-XML services to implement logic
sharing tests (e.g. NUnit) between platforms to assure the quality of your logic
using shared code techniques - MVC (MonoCross) or MVVM (MonoMobile.Views or MvvmCross) for UI "controller" logic; MonoTouch.Dialog and MonoDroid.Dialog for "View-level" abstractions; CrossGraphics for UI "drawing"; SQLite.Net for database; etc.
I'm finding the MonoTouch, MonoDroid and the Microsoft tools provide real and signigicant benefits in developing cross platform code - but you do have to work and think to achieve this.
Hello dearest community
I just given a task to develop a mobile application for chinese mobile phone, Nexian NX-G920. At first, I think it can just run the J2ME application. But it didn't, it only support MRP application. Having read about it here : MRP, I think my best case is, if any, convert my *.JAR application into *.MRP. Is there any tool that can do it?
My Plan B is, to develop using specific MRP SDK. But that is just to costly, in term of effort to be use.
As far as I know there are only Java to C translators or Java bytecode to assembly translators like those listed in this question.
These include JCGO, Toba, gcj and llvm. However a Java to C translator or similar is only part of the solution because it would only help you if you were translating classes that didn't interact with Java libraries that are not part of the MRP platform. This is because MRP platform won't have the libraries you link to and will have different GUI and hardware API calls than J2ME.
The only SDK for MRP is the OpenSDK which you have already mentioned.
I think I've found one solution, but I have to use my C languages, not the plain J2ME as first I thought it will. Here is the SDK, Open SDK by Sky Mobi.
Haven't try it though, but I think this is one solution that fit the problem.
Sky-Mobi SDK is saved this archive on Wayback Machine
The Sky-Mobi is saved this page of site in the Internet Archive