[Jsmooth-cvs] jsmooth/docs jsmooth-doc.xml,1.23,1.24
Status: Beta
Brought to you by:
reyes
Menu
▾
▴
[Jsmooth-cvs] jsmooth/docs jsmooth-doc.xml,1.23,1.24
|
From: Rodrigo R. <re...@us...> - 2007-05-27 14:52:02
|
Update of /cvsroot/jsmooth/jsmooth/docs In directory sc8-pr-cvs6.sourceforge.net:/tmp/cvs-serv11297/docs Modified Files: jsmooth-doc.xml Log Message: update with splash window example, and some other minor change Index: jsmooth-doc.xml =================================================================== RCS file: /cvsroot/jsmooth/jsmooth/docs/jsmooth-doc.xml,v retrieving revision 1.23 retrieving revision 1.24 diff -C2 -d -r1.23 -r1.24 *** jsmooth-doc.xml 19 May 2007 14:59:24 -0000 1.23 --- jsmooth-doc.xml 27 May 2007 14:51:54 -0000 1.24 *************** *** 1089,1103 **** JNI option, and add the <function>jsmooth.Native</function> calls in your java code. You need to build your project using the ! <function>jnismooth.jar</function> library, but don't need to ! package it with your application, as it is embedded (as well as the ! native functions implementation) in the wrappers. ! </para> ! <para>Before using any JNI feature from the <function>jsmooth.Native</function>, you must check that the native methods are correctly bound to their native implementation by using the <function>jsmooth.Native.isAvailable()</function> method. If this method returns false, you cannot use any of the ! native method.</para> <sect2><title>Examples</title> --- 1089,1106 ---- JNI option, and add the <function>jsmooth.Native</function> calls in your java code. You need to build your project using the ! <function>jnismooth.jar</function> library, and include if possible ! the jar in your application, to avoid a ClassNotFoundException that ! could be raised. Using the library is always safe if you first ! check that you can use it with the ! <function>isAvailable()</function> method.</para> ! <warning> ! <para>Before using any JNI feature from the <function>jsmooth.Native</function>, you must check that the native methods are correctly bound to their native implementation by using the <function>jsmooth.Native.isAvailable()</function> method. If this method returns false, you cannot use any of the ! native method (an exception shall be raised in this case)</para> ! </warning> <sect2><title>Examples</title> *************** *** 1213,1216 **** --- 1216,1265 ---- </sect3> + <sect3><title>Interacting with the splash window</title> + <para> + When the splash window is enabled, the JSmooth wrapper displays an image + at startup, until your application opens its first own window. + </para> + + <para>If your application takes some time loading its resources, it + may be convenient to use the JSmooth progress bar feature of the + splash window to provide an indication of completion to the user. + + <programlisting> + + jsmooth.SplashWindow spw = null; + + // + // First, we need to check if the JNI bridge is available... + if (jsmooth.Native.isAvailable()) + { + // + // If the splash window exists, this method returns a + // SplashWindow object that we can use. If there is no + // splash window displayed, this method returns null + spw = jsmooth.Native.getSplashWindow(); + } + + // + // Let's say there are 50 resources to load... + for (int i=0; i<=50; i+=1) + { + loadResource(i); + + // + // Update the progress bar, if it exists + if (spw != null) + spw.setProgress(i, 50); + } + + </programlisting> + </para> + + <para> + It is safe to assume that the splash window may not be available, for + any reason. For instance if your application is not launched with + JSmooth... </para> + + </sect3> *************** *** 1251,1284 **** </question> <answer> - <para> - - Whenever possible, the wrappers delete the file on - exit. Note however that this is not always possible. For - example, an instance of a JVM created using the JVM DLL does - not unload cleanly. This behaviour (not to call it a bug) is - documented by Sun, and there is no known work-around for it. - - </para> <para> ! ! Both Windowed and Console wrapper always prefer the JVM ! instanciation methods that allow them to delete the temp jar ! after the application exits. Note that embedding a jar in ! the exe is not required, it is always a safe choice to just ! leave it on the filesystem near the executable, either in ! the same directory, or in a sibling or parent directory. ! ! </para> ! ! <para> ! ! Note also that deleting the files in the windows TEMP ! directory is not required for Windows applications, and most ! application just leave them, letting the operating system ! manage it. The standard behaviour of MS Windows is to ! propose the user to delete the temporary files when the ! disks are running low on available space. ! </para> --- 1300,1315 ---- </question> <answer> <para> ! Whenever possible, the wrappers delete the file when the ! application exits. Note however that this is not always ! possible, as some versions of Sun's DLL do not return ! properly. In any case, all the temporary files used by ! JSmooth, including the extracted jar, are flagged to windows ! as "Delete On Reboot". Therefore, even if the wrapper does ! not get a chance to delete a temporary files, it is anyway ! always deleted automatically by windows during the next ! booting sequence, preventing the files to proliferate on the ! end-user's disk. </para> *************** *** 1300,1304 **** No. While the jsmooth wrappers may use a jar to bootstrap ! the java application, you can reference other jar files in a jsmooth project. Those jar files will be accessible to your executable binary, provided the path specified is --- 1331,1335 ---- No. While the jsmooth wrappers may use a jar to bootstrap ! the java application, you can refer other jar files in a jsmooth project. Those jar files will be accessible to your executable binary, provided the path specified is *************** *** 1405,1412 **** Wrapper-specific options can also be passed in order to ! override the defaults parameters set up at wrapper ! creation. Those options start with ! <function>-Jskel_</function> (names are case-sensitive as ! well). <itemizedlist> --- 1436,1442 ---- Wrapper-specific options can also be passed in order to ! override the default parameters set up at wrapper ! creation time. Those options start with ! <function>-Jskel_</function> (names are also case-sensitive). <itemizedlist> *************** *** 1451,1457 **** I have a filetype associated to my program. However, when I ! launch a document, my application can't find its resources, because the current directory is the directory of the ! document. How do I fix that ? </para> --- 1481,1488 ---- I have a filetype associated to my program. However, when I ! open a document, my application can't find its resources, because the current directory is the directory of the ! document, not the directory of the executable. How do I fix ! that ? </para> *************** *** 1460,1468 **** <para> ! You can force the wrappers to always force the current ! directory of your application to be the executable's instead ! of the document's by enabling the "Sets the executable ! folder as current directory of the application" option ! (located in the executable settings panel). </para> --- 1491,1499 ---- <para> ! You can force the wrappers to modify the current working ! directory at startup. In this case, you just need to enable ! the "Sets the executable folder as current directory of the ! application" option (located in the executable settings ! panel). </para> *************** *** 1470,1475 **** <para> This works correctly because Windows always provides the ! document as an absolute path argument of the application. ! </para> </answer> --- 1501,1506 ---- <para> This works correctly because Windows always provides the ! document location as an absolute path to the default ! application. </para> </answer> *************** *** 1511,1518 **** arguments (only the first argument of the command line is taken into account). If the "autostart" option is ! enabled, the service will be automatically when Windows ! is started. ! </para> ! </listitem> <listitem> --- 1542,1547 ---- arguments (only the first argument of the command line is taken into account). If the "autostart" option is ! enabled, the service will be automatically started by ! Windows. </para> </listitem> <listitem> *************** *** 1582,1586 **** <para> ! The first thing to do, is to run the wrapper with the additional argument <function>-JskelDebug=1</function> (the option is case-sensitive). This will start the wrapper in --- 1611,1615 ---- <para> ! The very first thing to do, is to run the wrapper with the additional argument <function>-JskelDebug=1</function> (the option is case-sensitive). This will start the wrapper in |