I will be missing the meeting today. Stephen and I talked about this a bit at the UDL meeting today.
We seem to be a bit stuck. Stephen is having problems working with the existing "Fix Java Webstart" application. So that is going to take a while to get it working. The webstart based applying of the fix that we have talked about before and Stephen has brought up again, are not very easy. One task would be to make an example of this outside of our deployment system. Perhaps the hardest part is dealing with the permission problem. Normal users cannot access the file needed to be updated. That might require some native library code, or running a script that can show a gui requesting admin privileges. I would estimate this would take a week. I'll round up to 2 weeks for a programmer not familiar with webstart or working with the native side of things. Then the next tasks is integrating this into our deployment system. This will take more time probably requiring changes to the maven-jnlp building process, and to the sds jnlp modification code. We will be addressing some of these problems with the webstart proxy code, so if that is completed and working in our deployment system, integration with the deployment system will become easier. I estimate the parts of the webstart proxy work that help the deployment system integration to be completed around mid Jan. Scott Hiroki Terashima wrote: > Let's discuss this briefly during today's tels-tech meeting (e.g. what > kind of effort it will take, timeline, etc). Berkeley might be able > to contribute to this effort next year. > > Hiroki > > On Dec 19, 2007 7:04 AM, Scott Cytacki <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > This is part of the way to make it easier to apply the webstart fix. > There are things that makes it difficult to do some of the stuff > below. So if there is a developer who has time to work on it then I > will take the time to dig into it and discuss all the details. > > Sorry I'm being difficult on this, but we've discussed this before and > no work has been completed because people are too busy. I'm reluctant > to spend the time discussing it again until I know someone is > going to > actually do the work we discuss. > > Scott > > Stephen Bannasch wrote: > > Scott, > > > > Is there a reason this fix couldn't be folded in to the webstart > > deploy process rather than be a separate program Mac users have to > > run (and then run again whenever they update Java). > > > > We've talked about modifying the webstart deploy process to have a > > minimal initial set of jars downloaded and run first providing > useful > > information to the user about both what is happening and is about to > > happen. I'm going to call this set of jars and the functionality > they > > provide "Part1". > > > > Obviously this division into parts is part of the functionality you > > are working on for the webstart-jar-proxy server. > > > > What about adding the ability to check and even fix if needed the > > jar-differencing bug on a Mac as part of this same. Could we refuse > > to provide the Part1 jars in jar-difference forms to Macs? If so > then > > we know that even Mac's without the webstart fix would be able to > > download these jars. > > > > Perhaps if the computer is a Mac then we should provide just the jar > > for checking and fixing the webstart bug as a Part0 section in the > > jnlp. The idea is that this jar is always run first on a Mac before > > any other jars are loaded. Then the jars that might need to be > > updated in the real Part1 cold use jar-differencing. > > > > I assume that if the problem is found and fixed then the whole jnlp > > process might need to be started again -- if this can't be done > > easily for the user then I suppose the webstart-fixer could end with > > a dialog telling the user what had been fixed and ask them to close > > the dialog they are looking at and run the software again by > clicking > > on the webstart link in the html they had just been viewing > > originally. > > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
