From: Jeff Squyres; Wednesday, June 16, 2004 6:11 AM > >On Tue, 15 Jun 2004, Lombard, David N wrote: > [deletia] > >> Having done that, what about the opd GUI? This required an ugly hack to >> make the "exclusive" checkbox use the new "--nomaster" option. It's >> ugly 'cause the GUI is a little knotty, and the initial probe of the >> master ODP site must either time-out or be cancelled before the >> repositories can then be added and the "exclusive" checkbox checked. > >I'm not familiar with the code logic of the GUI, but perhaps it would be >possible to pre-load this checkbox by having the GUI do a quick ping of >the master site -- or, better yet, ask OPD to do a "quick" ping (something >that would potentially only take a few seconds to time out, not 30 or 60) >to see if it can connect to the default master. > >Or perhaps OPD should do this by itself, and therefore the logic of the >GUI wouldn't need to change. > >And perhaps it's also time to be a bit smarter about finding the default >master for OPD. Perhaps it would be good to have back-end file-based >defaults, so that OPD will [by default] use the same master that you used >last time. And so on. > >This might make the OPD experience a little nicer. > When I first started, the timeout took quite a while. Now (after the patches) the timeout is very short. I hope I didn't break something :-/
But, assuming no breakage, the current timeout is quite acceptable. A dialog indicating it was unable to contact the master repository would be a Good Thing (TM). >> So, I can now query an arbitrary repository w/o Internet access, but >> alas, the "Download Selected Packages" button caused an immediate >> termination of the downloader. >> >> This was due to an improper oscar_package.xml file; apparently >> OpderDownloadPackage.pm wasn't doing sufficient data checking and again >> the need to check the master OPD repository. > >I guess we had always assumed correct XML. Do we need to provide support >for non-correct XML? Yesterday, the answer was first "YES", then once I figured out an XML problem, "um, it's OK". Preventing death (missing XML fields) is highly desireable; a message on bad data (size, cksum) preventing the download would be another Good Thing. [deletia] >> So, the attached patch allows opd and the opd GUI to function in a more >> useful manner, where organizations can set up their own web-based >> servers without need for an Internet connection. The attached patch >> does *not* make the GUI more robust -- it still fails in the face of >> incorrect XML. > >I'd say to go ahead and commit the opd patch. Can't comment on the GUI >patch. Yeah, I'd like some comment on the GUI patch, as I'm not sure it is the best fix -- you know, it works v. it's correct. Also, the OPD GUI has no memory. So, you need to set the repository info every time you enter the GUI -- a Bad Thing(TM) ameliorated by the expectation that a "real user" doesn't go in and out of the GUI... -- David N. Lombard My comments represent my opinions, not those of Intel Corporation. ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
