You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(1) |
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2003 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: Gerald B. <lux...@ya...> - 2003-12-13 17:37:17
|
Hi, The Saturn Times announced the nominations for the "Web Start Project of the Year 2003" award today. The line-up includes: * NetX * OpenJNLP * Xito BootStrap * JDistro/Wharf * Web Application Launcher (WAL) * Web Start Services Pack * Apollo * Rachel * Lopica Web Start Tools * Vamp Ant Task Suite Cast your vote today and help NetX make the winner. You can find the pollstation online @ http://lopica.sourceforge.net/times/2003/12/poll_what_is_your_web_start_project_of_the_year_2003.html - Gerald PS: I've collected all links to the Web Start projects in a Web Start News Wire story for easy reference. See http://article.gmane.org/gmane.comp.java.jnlp.announce/56 for details. ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca |
From: Gerald B. <lux...@ya...> - 2003-04-24 20:58:55
|
Sorry, I forget the links to the lopica-announce mailing list. Here we go: * Subscribe/Unsubscribe: http://lists.sourceforge.net/lists/listinfo/lopica-announce * Archive: http://sourceforge.net/mailarchive/forum.php?forum=lopica-announce - Gerald ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca |
From: Gerald B. <lux...@ya...> - 2003-04-24 20:51:04
|
Hi Deane, Hi Jon A., I invite you to also send your OCD and NetX announcements or any other Web Start news (say about apps, toolkits, articles and more) to the lopica-announce mailing list also known as the Java Web Start News Wire. The goal is to turn the lopica-announce mailing list into an independent Web Start news source that helps to promote all things Web Start. For a start I will profile new Web Start launchers, apps and more in the Saturn Times - a web site dedicated to Web Start news from around the globe - online @ http://www.vamphq.com/times/ I also will add interesting Web Start links to the Unofficial Web Start FAQ or to the Web Start Link-opida online @ http://lopica.sourceforge.net I am sure others will also pick up your news and announcements and will help to expand the Web Start universe. - Gerald -------------------------------------- Gerald Bauer Lopica "Web Start Encyclopedia" Editor http://lopica.sourceforge.net -------------------------------------- ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca |
From: Dino <ocd...@ya...> - 2002-04-17 21:13:51
|
Hi David, Thanks for your interest in our Project(s). To answer your question, Netx grew out of the OCD Project. The OCD Project attempts to create a complete computing environment for net based Java Applications. Netx is a Fully compliant JNLP client that was masterfully written by Jon Maxwell for the OCD Project. However Netx can run and be useful by itself without OCD. OCD requires Netx but Netx does not require the OCD Services. Hope this answers your question. Can I ask why you wanted to know? Thanks, Deane Richan ----- Original Message ----- From: "Williams, David" <DAV...@ca...> To: <ocd...@li...> Sent: Wednesday, April 17, 2002 1:51 PM Subject: [Ocd-developers] How intertwined... > Is netx w/ OCD..? > > > > David Scott Williams > Computer Associates > Marketing Representative-Sales Call Center > One Computer Associates Plaza > Islandia, New York 11749 > tel: +1 800-243-9462 ext. 73431 > tel: +1 631-342-3431 (Direct) > fax: +1 631-342-5734 > wi...@ca... > > > _______________________________________________ > ocd-developers mailing list > ocd...@li... > https://lists.sourceforge.net/lists/listinfo/ocd-developers _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Williams, D. <DAV...@ca...> - 2002-04-17 20:52:01
|
Is netx w/ OCD..? David Scott Williams Computer Associates Marketing Representative-Sales Call Center One Computer Associates Plaza Islandia, New York 11749 tel: +1 800-243-9462 ext. 73431 tel: +1 631-342-3431 (Direct) fax: +1 631-342-5734 wi...@ca... |
From: Jon A. M. (JAM) <jma...@co...> - 2002-01-02 19:54:40
|
Ted, My apologies for not writing back after a day or so like I had said -- the holidays caught up with me. ;-) Anyway, Deane Richan is still on break I think but I'm sure he'll want to discuss your comments and ideas about OCD in depth, and see about you helping out if that's what you want to do. I believe that you mentioned OSGi, that you had written an implementation of it, and suggested that OCD adopt some of its ideas. I looked up the OSGi spec and it seems to be similar to what Deane was doing with the OCD services concept. One thing I like about the OSGi is that the 'bundles' register the components that they contain with the system. I think this would be a better way that how it is currently done in OCD. On the other hand, the way that the OSGi spec puts information in the bundle jars seems pretty weak. From what I could tell, it adds certain entries in the manifest to hold all of the data about the bundle, what other bundles are needed, what packages to export, etc. From just glancing at it, a lot of the information mirrors that in a JNLP file -- parameters, versions, other resources, native code libraries, and so on. The main difference seems to be using BNF instead of XML to format the data. You also mentioned that you tried to implement a services framework on top of Web Start, but that Web Start was not able to add resources to already-running code. One of the next things to add to the JNLP code in OCD is the ability to link a JNLP file to another already loaded file. Currently we have a hack that allows the different OCD services to be loaded separately into the same classloader/namespace. This should make the JNLP code able to support a services framework. If one was to implement an OSGi framework as part of OCD, my suggestion would be to essentially map the OSGi bundles to JNLP files and we can extend the XML file format (or the JNLP client classes) for whatever information OSGi has that cannot be stored already as JNLP. It's quite a bit more complicated to support more than one type of execution environment in Java, as you know, because there are only one of the security manager and policy. The two systems run together and make a mess IMHO, so the options are either that mess, make an 'ubersystem' to allow both to co-exist, or make one conform the other. As far as NetBeans and Eclipse are concerned, I haven't used them enough to really comment on how they create an environment by plugging in separate code. I think that these show that this kind of environment can be used to great effect when there is an overall direction (ie, making a full-featured IDE). However, NetBeans at least is also very slow and bloated, likely due to just this combining of different pieces. I think it is good to keep that in mind that making an environment based on small pieces that hook together is very powerful but may not actually fit the user's needs. As a rough analogy, a lot of perl was essentially hard-coded into the language to directly call C routines and whatnot. As a result it was very fast and efficient. On the other hand, shell scripts do basically the same thing but are much slower and less efficient (and no more powerful since perl can call external commands). And people picked perl hands down. Anyway you should discuss your ideas with Deane Richan, because he is the one that did the services and GUI framework part of OCD. I'll probably be helping out with those parts to some degree, but making the JNLP client part more compatible with Web Start is a high priority. P.S. Deane - I disabled the forums as Ted suggested and made the ocd-developers list accessible to the public. I've included Ted's post below if you haven't seen it yet. Jam Ted Stockwell wrote: > Hi all, > > I think the OCD project is very timely. I think that this kind > of project is very much in need right now. Though most > developers don't seem to think that Java has much of a future > on the client, I have convinced myself that a correctly > architected Java client can bring functionality to the desktop > that no other enviroment can touch. > > I thought I'd drop you a note about my own efforts in this > area and see if there is some common ground between your > efforts and mine. I would like to participate if I can. > > For the better part of a year I have been working in my spare > time to create an application development and deployment > framework with many of the same goals that you have set for > OCD. Specifically: automatic updates, pluggable services API, > GUI framework for easily creating applications. I consider > NetBeans (http://www.netbeans.org) and Eclipse > (http://www.eclipse.org ) to be fine examples of the kind of > applications that I want to create (except that I want to > create generic business application, not IDEs). These > applications can automatically update themselves, have plugin > frameworks, and each has its own GUI framework that makes it > easier to develop UIs for the application domain. > > After creating applications with Java Web Start and NetBeans I > finally settled on Eclipse (http://www.eclipse.org). > > Here's why... > > ...I found it too difficult to implement a basic service API > on top Java Web Start. My idea of the perfect service/plugin > API is something along the lines of OSGi > (http://www.osgi.org). At one point I released an > implementation of the OSGi 1.0 specification > (http://servicetango.sourceforge.net). Since JWS controlled > the runtime environment so tightly I could not figure out how > to extend an already deployed application. > > ...Anyway, after banging my head on JWS for a while I then > discovered NetBeans. NetBeans has its own proprietary update > mechanism a plugin API and a GUI framework. Unfortunately I > found NetBeans extremely difficult to change into a generic > business application framework. The basic plugin and GUI > frameworks are not very modular and I found it extremely > difficult to change NetBeans into something that I could use > to develop generic business applications. > > ...then I found Eclipse several months ago. I think that > Eclipse is about as nearly perfect all-around framework for > all kinds of development as you'll find right now (maybe OCD > could be better!). It has its own update mechanism, a very > clean plugin mechanism, and a very fine GUI framework that > make it easy for plugins to add new views, menus, and toolbars > to an application. The biggest problem with Eclipse is that > its GUI framework was not built using AWT or Swing, it uses a > widget libray called SWT. No problem for me though, I've > ported the Eclipse GUI framework to Swing and I use Eclipse's > update and runtime plugins as they are. > > Anyway, in the meantime I'll be hanging out here and taking a > closer look at OCD. > > best regards, > ted stockwell |
From: Jon A. M. (JAM) <cod...@ea...> - 2001-11-28 05:05:17
|
Deane, I checked in the new classloader stuff, and removed the extensions.properties files. I accidentally got the desktop to work again, but there may be url -> xml issues. The new classloader is JNLPClassLoader. It's fairly clean, but I would like to get rid of the getExtensionName and getExtensionHREF methods. I think this would improve the DCF codes too, since they could just get the JNLPFile and use that instead of getting each part seperately. Or the ExtensionName should at least be unnecessary since it loads from a URL directly instead of looking it up in a table. You mentioned that this might be bad because the files might move, but it may be better because the local system could now read 'documents' that were created on other systems that 'knew about' more extensions than the local one, if a network location for the extension was used there. Anyway, it seems to work. It uses a really simple cache instead of hooking into cachemgr (I didnt' know if cachmgr was thread safe and there were enough potential problems to worry about!). I propose a new cache policy, where instead of checking for and downloading new versions immediately, apps are run with the old version in cache and then the new version is downloaded while it is running, and used when the apps is launched at a later time. This should dramatically increase startup time... check out http://www.gentleware.com/download/Poseidon4umlJWS.jnlp for an example (have to turn off security to get it to work); it's got ~25 jars that used to be checked for being up-to-date each time it was run, initial startup going from ~22 seconds (depending on trans-Atlantic congestion) from the cache to ~1 second. Check out CacheUtil in jnlp dir for where hooks into the cache would go. Also I removed the IExtensionLoader interface to the classloader... if code is hard-wired to the jnlp classloader it won't matter if it is using an interface or class. Jam |
From: Dino <ocd...@ya...> - 2001-11-21 21:01:04
|
The code should all be working now. the problems I was having was = related to my Name changes not any ClassLoader problems. All new files should be placed under the new src tree rather then the = org tree. Now if we change the name of the project it will only impact = the package names nothing else. Dino ----- Original Message -----=20 From: Dino=20 To: ocd...@li...=20 Sent: Tuesday, November 20, 2001 5:40 PM Subject: [Ocd-developers] New Source Code Tree Hey, I moved the source code tree from the org directory to a directory = called src. I removed the ant directory and placed the build.xml in the = root of the module. Now to build just go to the ocd module directory of your sandbox and = type "ant all" I have also renamed all of the files and removed the OC and IOC from = the names as a prefix. I use DC as the prefix for DCF code. Every Thing should compile but I am having a few runtime errors I = thought might be related to the new ClassLoader stuff. I will look into = it when I get a chance. Dino |
From: Dino <ocd...@ya...> - 2001-11-21 01:33:10
|
Hey, I moved the source code tree from the org directory to a directory = called src. I removed the ant directory and placed the build.xml in the = root of the module. Now to build just go to the ocd module directory of your sandbox and = type "ant all" I have also renamed all of the files and removed the OC and IOC from the = names as a prefix. I use DC as the prefix for DCF code. Every Thing should compile but I am having a few runtime errors I = thought might be related to the new ClassLoader stuff. I will look into = it when I get a chance. Dino |
From: Deane R. <dr...@do...> - 2001-10-30 22:32:35
|