Next generation exposure control

In another thread I made a comment how the controls and interfaces on today's DSLRs are still firmly rooted in the analog age. On this occasion I wanted to start a discussion about how exposure controls should ideally work on a modern computerised DSLR.
Let's summarize the current state, we have P/Av/Tv/M to choose from, one or two wheels that control time or aperture depending on the mode we are in, then there's ISO which can be set manually by using the menu or extra buttons or, with restrictions, automatically, and exposure compensation, which also doesn't always work (e.g. doesn't affect auto ISO in M).
Obviously ISO, the third parameter besides time and aperture that controls the exposure, is still a second-rate citizen, otherwise we would have 8 insteaed of 4 major shooting modes, ISO auto/manual * time auto/manual * aperture auto/manual.
So how about three switches or buttons to toggle each individually from auto to manual?
Or how about three wheels, that each control one of these three parameters and toggle auto/manual with a click?
That way in full manual I have full control over all three; if all three are in manual, there's no exposure compensation; as soon as I switch one of the three to automatic, it becomes free to control exposure compensation!
And if two are in automatic and one in manual then one of the wheels whose parameter is on auto can be used for exposure compensation, and the other to control the bias of the automatic because in this scenario the automatic has two values under its control, so there are many combinations that are valid, and I'd like to tell the automatic whether to prefer large apertures or higher ISOs, for example.

RichLavigne wrote:
well thought out
Thanks. Just noticed that I forgot to include freely configurable limits for all the parameters that are chosen automatically, preferably focal-length and IS dependent...

Similar Messages

Does Firefox support java applets if the "Next generation plugin" is disabled via the Java plugin control panel.

I'm still trying to get a definitive answer to this question.
My applet is not "Next Generation compliant". When we run our applet in Internet Explorer it runs fine as long as we disable the "Next Generation Plugin" via the Java plugin control panel. However our applet does not run in Firefox if the "next generation applet" is disabled.
Is it a requirement that if I want to run an applet in Firefox 3.6.x or higher that the "next generation plugin" be enabled via the Java plugin control panel.

Current Firefox versions (3.6 and later) can only run Java applets via the Next Generation plugin.
*http://java.com/en/download/help/new_plugin.xml

Next-generation plug-in 1.6 : ClassNotFoundException and not caching JARs

Hi,
Since the introduction of the next-generation plug-in in Java 1.6.0_10, the applet I have used and developed for many years don't load anymore.
The situation is this : the Jars of this applet are embedded in a Lotus Notes database as Java resources, in order to be used in a particular form in my application. Note that this application is accessed via a Web browser through a Domino server and that this application requires a user authentication. If I try to open the form containing the applet while using a plug-in 1.6.0_10 or newer, with default parameters (cache and next-generation plug-in activated), here is the exceptions I get (here with plug-in 1.6.0_20) :
load : class mycompany/tools/Planner not found.
java.lang.ClassNotFoundException: mycompany.tools.Planner
     at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source)
     at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source)
     at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: open HTTP connection failed:http://www.mycompany.com:80/test/database.nsf/46277DA0EF2790B0C12574040052D714/$FILE/mycompany/tools/Planner.class
     at sun.plugin2.applet.Applet2ClassLoader.getBytes(Unknown Source)
     at sun.plugin2.applet.Applet2ClassLoader.access$000(Unknown Source)
     at sun.plugin2.applet.Applet2ClassLoader$1.run(Unknown Source)
     at java.security.AccessController.doPrivileged(Native Method)
     ... 7 more
Exception : java.lang.ClassNotFoundException: mycompany.tools.PlannerBy reading a lot forums I found that a lot (really a lot) of people were experiencing the exact same issue, regardless of the type of server they used to host their applet. And unfortunately, only few answers were relevant to help me understand why I got this error...
By looking deeper in the documentation, I have found this [Applet Developer's guide|http://download.oracle.com/javase/6/docs/technotes/guides/jweb/applet/applet_dev_guide.html]. Here, it is written that one of the enhancement of the next-generation plug-in is that : "+... The JVM running the applet is isolated from the web browser at the operating system level. If something should go wrong while running the applet, or if an uncooperative applet refuses to shut down, the new Java Plug-in detects and handles the error condition gracefully; the Web browser is unaffected+".
I am not quite sure of what it really means, but I have started to think that my problem could be that, by running in a separate process than the one of the Web browser, loading the Jars will require an authentication on my server. To verify this hypothesis, I have changed the codebase of my applet, so the Jars are downloaded from another server where no user authentication is required. The good news is that my applet can now find the Jars and run as expected. The bad news is that none of the Jars are placed in the cache, which means that the Jars have to be downloaded each time I start a new session to work with my applet.
I have also tried to disable the "Use the next-generation plug-in" option in the Java control panel. In this case, everything is fine, too, and even the Jars are stored in the cache. The interesting thing is that afterwards, by enabling the "Use the next-generation plug-in" option again, the applet will load and run like a charm... because the Jars are in the cache and the class loader can find them! (I suspect that this case has been experienced by several people, answering on forum posts that they cannot reproduce the issue.)
Anyway, even if there is some workarounds to ensure it is possible to work with the latest versions of the plug-in, having to change the default options is not always easy or possible, depending of the environment. This applet that I am talking about is used by a lot of our customers and all have their internal policies and requirements regarding the Java configuration. If for some of them it will be possible to use a workaround, for others it will not. And this is a major problem to me.
As I said, a lot of people have experienced this issue. I hope that someone having a better understanding on how this next-generation plug-in works, will have a solution, or at least, will be able to explain what is wrong in this approach and if my suggestion regarding an authentication issue for the class loader make sense.
Any help will be greatly appreciated.
Philippe

Hi,
I was wrong in my approach.
My applet was implemented using the "<object>" tag and it seems that it was not the best way to address compatibility issues across all versions of the plug-in and all browsers.
So, I have finally found what I was looking for in this "[Java Rich Internet Applications Development and Deployment|http://download.oracle.com/javase/6/docs/technotes/guides/jweb/index.html]" guide. In this guide, it is recommended to use the "[Deployment Toolkit|http://download.oracle.com/javase/6/docs/technotes/guides/jweb/deployment_advice.html#deplToolkit]", based on a Javascript library containing everything needed to deploy your application as an applet or a Java Web Start application.
My application, deployed as an applet, now works like a charm.
I hope pointing on this Deployment Toolkit will also help others...
Philippe

Detecting if next generation plug-in is activated

Hi,
I am wondering if there is a way to programatically detect if the next generation plug-in check box is selected for the JRE/Control Panel (1.6_11).
We are having trouble with our software when this is enabled (the default) and want to notify the user to turn it off. I am assuming that this value is stored in the registry or some properties file but I can't seem to find it.
Thanks!
-Rob

The Deployment Toolkit portion of this document
file:///C:/Program%20Files/Java/docs/technotes/guides/jweb/deployment_advice.html#deplToolkit
has a link to deployJava.js which contains a function that will tell you if the new plugin is active.

Java options: "Enable the next-generation Java Plug-in"

On windows, this option is sometimes "grayed out" and you cannot disable it.
This option is available since java 6 u 10, and is accessible via windows control panel, or alternatively via javacpl.exe.
Which are the cases where the option is grayed out?
I've made the assumption that it is grayed out on windows 7, or on windows 7 64, but there are cases of windows 7 64 where the option isn't grayed out.
It seem neither connected with Internet Explorer version, since it works or not with either IE 8 or IE 9.
Edited by: Agostino on 18-gen-2012 2.58

Current Firefox versions (3.6 and later) can only run Java applets via the Next Generation plugin.
*http://java.com/en/download/help/new_plugin.xml

The next-generation Java Plug-in

I really need to disable the next-generation Java Plug-in on the Advanced tab of the Java control Panel, but it is grayed out. I have admin rights. I tried to uninstall/install Java, but that did not work. Any suggestions? Thank you

Hello jpalan!
Last case, you can make a PKGBUILD for on older version on your local pc, according to a working PKGBUILD.

Next-Generation Java 7 Plugin Performance on Windows 7 and IE 8

Applet performance has historically been a black eye, to say the least, for Java Applets. Slow load times over today's networks are simply not tolerated by today's network standards. I'm currently supporting an Applet that is forced to move to the Java 7 Platform. As such, we are particularly sensitive to anything new that may further hinder applet performance. To that end, I've been doing quite a bit of benchmarking lately of Applet load times using various configurations with the Java 7 Plugin on Windows 7 using IE 8.
To capture Java Applet load times, I've simply been marking the start time in Javascript from the HTML onLoad() event, and then calling out to a similar Javascript function to mark the end time from the bottom of the init() method in the Java Applet. I subtract the two times to get a general idea of how long it takes to load the applet.
The best load times, so far, (when loading the JARs from the web server) occur when caching is employed (e.g., cache_option, cache_archive, cache_version). What I've noticed though, is that when everything else is the same, the performance is degraded by at least half when I check the 'Enable the next-generation Java Plug-in' in the Plugin Control Panel. Applet load times slow down by at least half when this option is enabled. When loading JAR files from the web server, with caching in effect, the applet load time performance is comparable to loading JAR files from the file system only when the next-generation plugin is not enabled. I assume this is because of the associated overhead of spinning-up this external JVM process, but I'm not certain.
Does anyone know if this is a correct assumption? And if I'm correct, are there ways to speed up the loading of an applet when caching is used with the next-generation plugin? Is this another cold-start vs. warm-start issue for the JVM?
My goal is to have applet load times for JARs loaded from the web server, using the next-generation plugin, as fast as when the JARs could be loaded from the local file system (which apparently is no longer possible using the next-generation plugin, sadly).
Thanks!

Thanks Igor.
Web Browser: IE 8.0.76
Java Plugin: 7u3 (1.7.0_03-b05)
OS: Windows 7 Enterprise (32-bit)
Server: Websphere 7
Java Applet is in O&M phase and been around a while. Rich Internet Application with file system access requirements. Currently compiled with JDK 1.5. 10 JAR files total, 6 of which are third-party JARs. 4 JARs are custom and are signed.
JAR1.jar -> 11077 bytes
JAR2.jar -> 14207 bytes
JAR3.jar -> 5093 bytes
JAR4.jar -> 22233 bytes
JAR5.jar -> 18722 bytes
JAR6.jar -> 17578 bytes
JAR7.jar -> 722237 bytes
JAR8.jar -> 90688 bytes
JAR9.jar -> 17521 bytes
JAR10.jar -> 50686 bytes
JSP Page is used to render the following HTML tags for loading the applet:
<object classid="clsid:${UID}" name="preview" width="100%" height="300" id="poc">
<PARAM name="java_code" value="com.loadfast.Applet.class"/>
<param name="codebase" value="/www/applet"/>
<PARAM name="cache_option" value="Plugin"/>
<PARAM NAME="cache_archive" VALUE="
JAR1.jar,
                    JAR2.jar,
                    JAR3.jar,
                    JAR4.jar,
                    JAR5.jar,
                    JAR6.jar,
                    JAR7.jar,
                    JAR8.jar,
                    JAR9.jar,
                    JAR10.jar
"/>
<PARAM NAME="cache_version" VALUE="
                    1.0.0.11,
                    1.0.0.11,
                    1.0.0.11,
                    1.0.0.11,
                    1.0.0.11,
                    1.0.0.11,
                    1.0.0.11,
                    1.0.0.11,
                    1.0.0.11,
                    1.0.0.11"/>
<PARAM name="type" value="application/x-java-applet"/>
</object>
Here's a brief synopsis of my test methodology:
Assuming caching is the fastest performance I'm going to get by putting JARs on web server, goal was to determine if browser plugin and next-gen plugin will offer the same performance in terms of time to load the Applet.
To test, I unchecked the 'Enable Next-Gen' plugin option in the Java Plugin. I updated the cache_version values for all JARs. I 'touched' all JAR files in the WAR (I use cygwin) and redeployed the WAR. I have a cli script that launches IE and points it at my applet. When the applet loads, a Javascript Alert box displays showing the number of milliseconds it took to load the applet. I document the time, quit the browser, and re-execute my script. I do this 10 times for each test scenario and take the average.
The two basic test scenarios are using the Browser Plugin (not next-gen) and using the Next-Gen Plugin. That is the only variable I change between test scenarios. Here is the raw data I collected for each test scenario:
Not Using Next-Gen Plugin (milliseconds):
run1 run2 run3 run4 run5 run6 run7 run8 run9 run10
1761 474 535 495 500 505 502 267 693 513
Avg: 625ms
Using Next-Generation Plugin (milliseconds):
run1 run2 run3 run4 run5 run6 run7 run8 run9 run10
5382 1529 983 1545 1622 1575 1544 1544 1545 1529
Avg: 1880ms
The time it takes to load for each first run indicates caching is happening as subsequent runs are faster. I verified that the JVM is not making http requests for cached JAR files by proxying these requests with Tcpmon just to confirm this was the case.
I'm basically just looking for a logical explanation to account for the significant time difference that occurs from this Plugin configuration change. It seems to make logical sense to me that this can be explained by JVM Process start up time, but I'm looking for corroboration on that or another explanation.
Thanks for any advice, help, etc. I'll start looking into JNLP and JAR index as well.

U2018The next generation of SAP B1 add-onsu2019 - The power of mobility.

AbacusConsulting has come out with the next generation of SAP Business One add-ons. The SAP Business One Mobilizer!
Now the conventional boundaries have been broken down and limitless possibilities are within grasp with the introduction of the SBO Mobilizer. Dwelling on futuristic technology, the SBO Mobilizer allows you to have access to your SAP B1 database and its key functions around the clock, from anywhere in the world.
Extremely reliable, robust and secure, the SBO Mobilizer enables sales teams, distribution teams, management, field force employees, etc to post and view sales orders, delivery orders, invoices, returns and payments from remote locations, enabling them to make instant and well calculated decisions without any delay. It provides greater control over the whole operation process and securely centralizes data within minutes.
Working on both offline and online modes, the SBO Mobilizer not only saves time and money but itu2019s highly flexible design also enables limitless On-The-Fly form designing. A few clicks and new forms are ready to be published.
Language not being a barrier anymore, the product can be custom developed for any language intended and keeping a futuristic approach, the product is not limited to SAP but can be custom developed for any ERP system.
And the possibilities donu2019t end there. AbacusConsultingu2019s product will let you set your possibilities yourself. Itu2019s all in your hand. Amplifying the power of SAP B1 several folds, it is a product that I recommend you have a look at.
If you wish to discuss the possibilities in further detail, drop me an email at arqum.tashfeen@abacus-global. com or call me directly at +92 322 7171078.
Best Regards,
Arqum Tashfeen
Edited by: arqum.tashfeen on May 9, 2011 1:54 PM
Edited by: arqum.tashfeen on May 9, 2011 1:56 PM

Sorry,
I figured that out. I would rather inherit from <b>B1Menu</b>
    public class B1BrowserAdd: B1Menu {
        public B1BrowserAdd() {
            this.MenuUID = "1282";
        [B1Listener(BoEventTypes.et_MENU_CLICK, true)]
        public virtual bool OnBeforeMenuClick(MenuEvent pVal) {
            Console.WriteLine("1282 Menu Pressed");
            return true;

Java 8, next-generation java plug-in?

hey all,
i'm looking for the "enable the next-generation java plug-in" option in java 8 update 40, but can't find it in the advanced tab of the java control panel.
has it been removed?
thanks!

anyone?

Next Generation 7.1 GIGAWORKS

We have seen the new generation sound cards: x-fi. The GIGAWORKS S750's have been around for a while now. When will we see the next generation? Or where might I be able read news about this?

I believe that Creative's policy is similar to Microsoft's, they refuse to comment on anything and everything.
I have personally been looking at buying a set of the s750's but with all the problems I've seen in the forums I've decided to wait for the next revision... so far I've been waiting 2+ months.
Honestly speaking it would be nice if Creative did tell us if they ever are considering releasing a new flagship set, but the probably won't.
Thing's I'd like to see in the new 7.1 system are: 100 watt per channel and a 10" 300w sub (combined power 1000w), and a Dolby DTS and PRII decoder built in, and the controler for the speakers to have a LCD display like the Logitech flagship range, as well as a more powerful remote.
[Edit] and a ability to buy a extended warranty, for up to like 5-10 years [/Edit]
Message Edited by pro-logic on 09-04-2006 05:46 PM

Next-Generation Plug-In settings in the Enterprise

I work in a company of 1000+ desktops and various user groups running various core systems. For background, we've been standardized on IE 6 for years, and we're trying to move to IE 8.
I'm looking into an issue with one of our core systems. It's a 3rd party solution that relies on an applet that fails when the latest JRE is downloaded and the "Enable the next-generation Java Plug-in" is checked (which it is by default).
I've been searching the web, and I know most of the work-arounds, including how to run ssvagent.exe -high -jpisetup -old from the JRE install folder. I'm almost ready to pass this information on to our desktop admins, but I have a few questions I know they are going to ask. I would deeply appreciate any help in answering these questions:
What is the possible impact of disabling the next-generation Java Plug-in on other applets from other 3rd party vendors? Are we likely to run into some applets/plug-ins that fail when this option is disabled?
The vendor of the app that's failing isn't being very helpful. Is there any info we can give them on how to recompile the applet so that it works under the default setting?
What are other large enterprises doing to manage this?
Thanks in advance for any answers. Until we have this resolved, we're unable to upgrade users to the current JRE.

I tried the java_version param. It prompted me with a warning informing me that the app would run an earlier version of Java. I clicked run, and continued having the same issue. I captured this from the console:
Java Plug-in 1.6.0_20
Using JRE version 1.5.0_15-b04 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\kswans1.AMERICREDIT
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
o: trigger logging
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
x: clear classloader cache
0-5: set trace level to <n>
java.lang.NoClassDefFoundError: sun/awt/DesktopBrowse
     at sun.plugin2.applet.Applet2Environment.initialize(Unknown Source)
     at sun.plugin2.main.client.PluginMain.handleMessageSetJVMID(Unknown Source)
     at sun.plugin2.main.client.PluginMain.mainLoop(Unknown Source)
     at sun.plugin2.main.client.PluginMain.run(Unknown Source)
     at sun.plugin2.main.client.PluginMain.main(Unknown Source)
security: property package.access value sun.
security: property package.access new value sun.,com.sun.javaws
security: property package.access value sun.,com.sun.javaws
security: property package.access new value sun.,com.sun.javaws,com.sun.deploy
security: property package.access value sun.,com.sun.javaws,com.sun.deploy
security: property package.access new value sun.,com.sun.javaws,com.sun.deploy,com.sun.jnlp
security: property package.definition value null
security: property package.definition new value com.sun.javaws
security: property package.definition value com.sun.javaws
security: property package.definition new value com.sun.javaws,com.sun.deploy
security: property package.definition value com.sun.javaws,com.sun.deploy
security: property package.definition new value com.sun.javaws,com.sun.deploy,com.sun.jnlp
security: property package.access value sun.,com.sun.javaws,com.sun.deploy,com.sun.jnlp
security: property package.access new value sun.,com.sun.javaws,com.sun.deploy,com.sun.jnlp,org.mozilla.jss
security: property package.definition value com.sun.javaws,com.sun.deploy,com.sun.jnlp
security: property package.definition new value com.sun.javaws,com.sun.deploy,com.sun.jnlp,org.mozilla.jss
basic: setDeployURLClassPathCallbacks: no enhanced access
basic: Added progress listener: sun.plugin.util.GrayBoxPainter$GrayBoxProgressListener@153f67e
network: Cache entry found [url: http://drvmwebbnt02.americredit.com:9081/MyProvenir/MyProvenirZip.class, version: null] prevalidated=false/0
network: Connecting http://drvmwebbnt02.americredit.com:9081/MyProvenir/MyProvenirZip.class with proxy=DIRECT
network: Connecting http://drvmwebbnt02.americredit.com:9081/MyProvenir/MyProvenirZip.class with cookie "JSESSIONID=84C38F94C7BABF9B3318856D87B9736D; __utma=1.1067525869.1271360926.1278605523.1278684887.12; __utmz=1.1271360926.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)"
network: ResponseCode for http://drvmwebbnt02.americredit.com:9081/MyProvenir/MyProvenirZip.class : 304
network: Encoding for http://drvmwebbnt02.americredit.com:9081/MyProvenir/MyProvenirZip.class : null
network: Disconnect connection to http://drvmwebbnt02.americredit.com:9081/MyProvenir/MyProvenirZip.class
network: Cache entry not found [url: http://drvmwebbnt02.americredit.com:9081/MyProvenir/, version: null]
basic: Applet loaded.
basic: Applet resized and added to parent container
basic: PERF: AppletExecutionRunnable - applet.init() BEGIN ; jvmLaunch dt 374612 us, pluginInit dt 666096 us, TotalTime: 1040708 us
basic: Applet initialized
basic: Removed progress listener: sun.plugin.util.GrayBoxPainter$GrayBoxProgressListener@153f67e
basic: Applet made visible
basic: Starting applet
basic: completed perf rollup
basic: Applet started
basic: Told clients applet is started

IPod Shuffle 4th Generation's control buttons not working.

My iPod Shuffle 4th Generation's control buttons are not working. Sometimes it works after formatting it stopped again.. Please give a solution ASAP...

Hello.. When I switch on the iPod Green light appears. after 10 - 15 secs 3 times orange light blinks... After that I wont be able to increase / decrease the volume nor change the song. If I need to change the song, I should switch off n switch it on back. Actually I washed the iPod. It was in my jeans pocket.. Put in the washing maching without knowing that iPod was in the pocket. Charge also not staying long...
**Warranty is there for the iPod. Unfortunately it has two dents, so its not eligible for the replacement..

Ssvagent.exe does not always disable next-generation Plug-In

Around half the time running the "ssvagent.exe -high -jpisetup -old" in a vbs after the jre-6u22-windows-i586.exe process stops running
the next generation Plug-In option is not disabled.
I have verified that it does not run until after the Java installtion is complete.
Running "ssvagent.exe -high -jpisetup -old" manually right after installing Java will always disable next generation Plug-In.
Any ideas why it won't always run properly from a script?
Edited by: EthanD on Sep 20, 2012 10:21 AM

Hi,
I was wrong in my approach.
My applet was implemented using the "<object>" tag and it seems that it was not the best way to address compatibility issues across all versions of the plug-in and all browsers.
So, I have finally found what I was looking for in this "[Java Rich Internet Applications Development and Deployment|http://download.oracle.com/javase/6/docs/technotes/guides/jweb/index.html]" guide. In this guide, it is recommended to use the "[Deployment Toolkit|http://download.oracle.com/javase/6/docs/technotes/guides/jweb/deployment_advice.html#deplToolkit]", based on a Javascript library containing everything needed to deploy your application as an applet or a Java Web Start application.
My application, deployed as an applet, now works like a charm.
I hope pointing on this Deployment Toolkit will also help others...
Philippe

Next Generation Jet Database?

My company is already looking into the future beyond Exchange 2013 and we are interested in what storage engine\solution will be in place for the next generation of Exchange. Some believe the Jet database needs to be seriously updated or another storage
solution such as SQL be used. Does anyone know for sure and what the timing might be?
ML Anderson, Sr Exchange Engineer

Andy is 100% correct, project Kodiak was the SQL initiative several years ago ( I think about the Exchange 2007 time frame if memory serves) and one of the major issues that came up was that SQL couldn't handle the rapid and sometimes massive change rate
of folders etc so it was ditched because it could not keep up with JET
Jet (ESE) is still the most performant option available and as Andy says 2013 was a major and I mean MAJOR upgrade across the board with DB structure, resiliency and other features to make it more bullet proof if you will. Also as Andy states
anyone in the absolute know of any impending change couldn't say without violating their agreement with MS
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Next Generation in Monitor or PDA screens...

OK, so I'm sitting here on my iMac, and reading this, and reading that, we do a lot more reading then we used too, and we read more on electronic screens, then plain old school paper and print. SO the financial pundents hammer apple constantly for not bringing the truly next great WOW FACTOR, to the masses. I tend to think, Apple itself is having identifying the next wow factor in itself, there in case, the problem.   Heck, I have been struggling with, "What would be really great, next" kind of thought, ??????? but sitting here at my MAC it slapped me square in the face.   I know the technical developers have been into this kind of technology for quite some time over the past years, and, considering the vacuum in the NEXT GREAT THING category, and not just Trumped up progressions of ALREADY GREAT THINGS, Apple needs to WOW the world once again. And here is what Apple has to do......
We are going to be reading on our screens for generations into the future, The Print can not appear "under the glass" The print must appear "on the surface" Presently, Static on the screens attacks dust, which causes the eye to focus shift, dust to text, dust to text, text to dust. When the eye goes finite and precise, it can detect these minute differences and shift. When you choose just to focus on the text, you still know the dust is still there.   (Yeah, just clean your screen is not going to cut it anymore, and the foolish company will loose if they do not seize this need the consumers will demand.) So, the NEXT great thing is Print, Text, and Color, on the surface of the screen, and one other thing will need to be coupled with this, actually two, sorry.   Back lighting this new screen will have to be thought of as the way it was, Backlighting will only be needed in low light and night conditions, Daylight operation will have its light source external, from the sun, from interior lighting.   Again, if backlighting is not thrown out with the bath water, then we will have back lighting available to us in low light conditions.
Apple started from Steve Jobs love of the finite and beautiful, Calligraphy.
Those who perfect the next generation screens on their products right now, will carry the day and alligence of the most consumers.
S.M. ~you need me~

Hi,
I was wrong in my approach.
My applet was implemented using the "<object>" tag and it seems that it was not the best way to address compatibility issues across all versions of the plug-in and all browsers.
So, I have finally found what I was looking for in this "[Java Rich Internet Applications Development and Deployment|http://download.oracle.com/javase/6/docs/technotes/guides/jweb/index.html]" guide. In this guide, it is recommended to use the "[Deployment Toolkit|http://download.oracle.com/javase/6/docs/technotes/guides/jweb/deployment_advice.html#deplToolkit]", based on a Javascript library containing everything needed to deploy your application as an applet or a Java Web Start application.
My application, deployed as an applet, now works like a charm.
I hope pointing on this Deployment Toolkit will also help others...
Philippe

Next generation exposure control

Similar Messages

Maybe you are looking for