Groups > Palm OS > Palm Java forum > RE: Java Conduits




RE: Java Conduits

RE: Java Conduits
Wed, 30 Apr 2008 22:55:30 -070
I was emailed questions in regards to this. This lazy posting of my developer's
guide was a bit long-winded and not exactly clear on certain things since it was
written with the assumption you had access to my ant scripts and source code.
   
  Here are a few important quick points you might miss when using MIDP For
PalmOS and trying to write a Java conduit for it:
   
  - Use CDK403. The newer version does not support JSync13.
   
  - Use Java Conduit Manager (www.javaconduitmanager.org) to register the Java
conduit by a GUI or by the command-line (useful for installation since the CDK
wants you to write your own in C/C++ and does not provide a command-line
interface).
   
  - Compile the midlet setting the source and target to Java v1.2 for MIDP For
PalmOS.
   
  - Compile the conduit setting the source and target to Java v1.3 for JSync
since it uses JRE1.3.
   
  - The conduit should reference the RMS store by "<rms store
name>-<palm id>". The midlet should reference the RMS store by
"<rms store name>". MIDP for PalmOS automatically adds the palm
id to the datastore name.
   
  - JSync13 tutorial is a must read.
  
Matthew Johnson <mjohnson@ihmc.us> wrote:
        v\:* {behavior:url(#default#VML);}  o\:* {behavior:url(#default#VML);} 
w\:* {behavior:url(#default#VML);}  .shape {behavior:url(#default#VML);}       
st1\:*{behavior:url(#default#ieooui) }                Thanks.
   
  I had downloaded CDK 6.0.1 which (as you say) does not contain JSync support.
   
  Matt
   
      
---------------------------------
  
  From: %%email.bounce%% [mailto:%%email.bounce%%] On Behalf Of Keith Gardner
Sent: Tuesday, January 01, 2008 10:50 PM
To: Palm Java Forum
Subject: Re: Java Conduits

   
    I used the following technology....

     

     

  Directory Structure     

    ant - Contains command-line scripts to build the application. Modify the xml
files according to directory structure and needs. Modify the bat files according
to directory structure and needs. See http://ant.apache.org/ for more
information.

     

    build – Temporary directory for building and compiling source files.

     

    dev – Archive of versioned development tools for convenience.

     

    dist – Output directory of release files.

     

    docs – All development and other documentation produced. 

     

    lib – Additional development tools which are linked by ant.

     

    resource – Resources used by client application (images, icons). 

     

    src – Java source code of client application. 

     

    src-conduit – Java 1.3 specific source code for the Java conduit.

     

    src-installer – All installation files to be distributed

     

     Resources     

    This section describes the software resources used to develop the
application.

     

  Client Development     

    The client source files are located in the src directory. The following
software was used to develop the client:

     

    J2SE SDK 1.6U3 – Used to build client class files in the src directory.
Installer located in the dev directory. See http://java.sun.com/ for more
information.

     

    J2ME WTK 2.5.2 – Used to build the J2ME class files in the src directory.
Installer located in the dev directory. See
http://java.sun.com/products/sjwtoolkit/index.html for more information.

     

    Apache Ant 1.7 – Used as a command-line compiler with xml files and
environment batch files located in the ant directory. The installation file is
available in the dev directory. See http://ant.apache.org/ for more
information.

     

    Antenna 1.0.0 – Used as a Java source code preprocessor. File is located in
the lib directory. Later versions are unsupported. See
http://antenna.sourceforge.net/ for more information.

     

    MIDP for PalmOS 1 – Used as a J2ME MIDP1 virtual machine for Palm 3.5 and
newer devices. It is located in the lib/midp4palm.jvm directory. For more
information, see
http://handheld.softpedia.com/get/System-Utilities/MIDP-for-PalmOS-8767.shtml.

     

    Palm Emulator – Used for testing PalmOS v3.5+ devices. Installer, skins, and
ROMs located in the dev directory. See http://www.access-company.com/developers/
for more information.

     

    Palm Simulator – Used for testing PalmOS v5.x+ devices. See
http://www.access-company.com/developers/ for more information.

     

  Conduit Development     

    The conduit src files are located in the src-conduit directory. The
following software was used to develop the conduit:

     

    J2SE SDK 1.6U3 – Used to build client class files in the src directory.
Installer located in the dev directory. See http://java.sun.com/ for more
information.

     

    Palm CDK 4.0.3 – Used to build the Java-based conduit (JSync conduit). Note
that a newer version is available, which is missing the JSync conduit. An
installation file is available in the dev directory. JSync 1.3, part of Palm CDK
4.0.3, is also available in the lib/jsync13 directory. See
http://www.access-company.com/developers/ for more information.

     

  Installation Development     

    The following software was used to develop the installer:

     

    Java Conduit Manager (JCM) 0.4 – Used to register/deregister conduit with
HotSync at installation. It is located in the
src-installer/Setup/palm-desktop/jcm directory. For more information, see
http://www.javaconduitmanager.org/.

     

    JSync 1.3 Installer – Used to run the Java conduit from the HotSync manager.
It is  located in the src-installer/Setup/palm-desktop directory. It is part of
Palm CDK 4.0.3.

     

    J2RE 1.6U3 – Used to run JCM. It is located in the
src-installer/Setup/palm-desktop directory. See http://java.sun.com/ for more
information.

     

    Inno Setup 5.2.2 – Used to build installation scripts for the desktop
application (conduit) and clients. For more information, see
http://www.jrsoftware.org/isdl.php.

     

    Adobe Acrobat Reader 8.1.1 – Used to read User’s Guide. Setup file is
located in the dev directory. See http://www.adobe.com/ for more information.

     

    pdf995 8.3 – Used to create PDF files. Setup files are located in the dev
directory. See http://www.pdf995.com/download.html for more information.

     

  Other Common Tools     

    Microsoft Excel – Used for the reports.

     

    Microsoft Word – Used for documentation.

     

    TextEditor/IDE – Used to produce source files, xml files, command-line
scripts, etc. Eclipse and other text editors/IDEs are available for free.
Specifically, a licensed copy of Helios Software’s TextPad was used.

     

    Image Editor – Used to create images and icons. The GIMP is available for
free. Specifically, a licensed copy of JASC’s Paint Shop Pro was used.

     

    

Matthew Johnson <mjohnson@ihmc.us> wrote:

    I am just getting started and am trying to get Java conduits working. I
downloaded the CDK but this seems to only be for C/C++. I found what looks like
a nice tutorial at: 
http://www.access-company.com/developers/documents/docs/conduits/win403/JSyncCom
panionTOC.html

What I can't find is the jar that contains the required classes. Is JSync not
part of the CDK? Any help is appreciated.

MJ
-- 
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
   
    
    
---------------------------------
  
  Never miss a thing. Make Yahoo your homepage. 

-- 

For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/



--   For information on using the ACCESS Developer Forums, or to unsubscribe,
please see http://www.access-company.com/developers/forums/


       
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.
Post Reply
about | contact