NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Bill, Thanks for your reply. >I don't understand what 'registered with RendererControl' means? What method are you invoking to register? Here 'registered' means fetching a RendererControl from Host. I used localRendCtl = (RendererControl )localDisplay.getControl(RendererControl.class); to fetch RendererControl from Host. It worked well. This was not one of my questions. Sorry about the confusion. >VisAD has built-in support collaboration between remote Displays, as described at: http://icecube.wisc.edu/~dglo/visad-collab/index.html >The IDV supports remote collaboration using VisAD but >without VisAD's built-in support. Perhaps someone from >Unidata can describe how that works. >Note there are complex synchronization problems with >remote collaboration, so if you can use the built-in >support or copy the IDV approach, it will make life >easier. Yes, I've gone through all the tutorials suggested above and invoked most of the mothods in my application. I mainly use the visad built-in collaboration support so far. Based on RendererControl, all graphics widgets associated with Controls and ScalarMaps worked very well. I found that when a DataReference has been removed in Host, Clients didn't response. After investagation on VisAD, it seems that REFERENCE_REMOVED event was not sent to clients. So I made some changes to VisAD system to make this part work. Although I knew this may bring some trouble later on, but I have no better choice at this moment. To those self-developed graphics widgets (e.g. ComboBox, Button etc.) which neither belongs to Controls nor ScalarMap. I still have no idea how to make them collaborative. I will follow your suggestion to see if IDV's approach can be invoked in my application. Thank you very much. Mike -----Original Message----- From: owner-visad@xxxxxxxxxxxxxxxx [mailto:owner-visad@xxxxxxxxxxxxxxxx] On Behalf Of Bill Hibbard Sent: 28 January 2006 19:38 To: Mike Wang Cc: visad@xxxxxxxxxxxxxxxx Subject: Re: collaborative GUI Hi Mike, > I'm developing a 3D visualization system based on VisAD. > I now encountered a problem, hope somebody on the list can give me > help. > > In server side, I developed a set of Swing and AWT GUI components to > manage visad display properties. They are working well on both > standalone and server mode. All GUI componemt registered with > RendererControl can be manipulated in either server or client side. I don't understand what 'registered with RendererControl' means? What method are you invoking to register? > The problems are: > 1. How can I make GUI components which not registered with Display's > RendererControl or ScalarMaps collaborative? 2. How to broadcast a > message between collaborators (e.g. send a String from Server to > Client and vice versa)? VisAD has built-in support collaboration between remote Displays, as described at: http://icecube.wisc.edu/~dglo/visad-collab/index.html The IDV supports remote collaboration using VisAD but without VisAD's built-in support. Perhaps someone from Unidata can describe how that works. Note there are complex synchronization problems with remote collaboration, so if you can use the built-in support or copy the IDV approach, it will make life easier. Good luck, Bill p.s., happy new year everyone
visad
archives: