Communicating Tree Browser on Eclipse

Hi, I want an Eclipse plug-in. This plug-in has 3 views. 1) Tree browser view 2) Chat view 3) Editor view I have (1) and (2) executing as applets, now I want it as Eclipse plug-in (specifically, Eclipse 3.0 and Eclipse 3.1) Tree browse view ================ This the tree browser view reads from an tree-xml file and display the contents as a tree. When you click on a node in the tree, that node has a reference to a content-xml file. The editor view will display the content of that content-xml file. I have the tree browse as a swing applet. Now I want it ported to Eclipse. There should be a lot of reuse here. You should use the same code to read the tree-xml file as I have in my current applet. This view must operate very much like the eclipse navigator, except that the tree is based on the tree-xml file. Chat view ========= This is a view that allows you to do chatting. It allows to eclipse instance running on two separate machines to connect to each other and start chatting. Chatting refers to text chatting. Two person can talk to each other. I have this functionality running as an applet. Now I want it ported to Eclipse. There should be a lot of reuse here. You should use the same communication mechanism as I have in my current chat applet. Editor View =========== This view displays the content of the content-xml file. This view has two tabs to display the content-xml file. The first tab displays the content-xml file as HTML after applying an XSL onto the XML. The second tab displays 2 key attributes of the content-xml very much like an input screen. There is no need to implement any "save" of the content-xml file. There is currently no implementation of the editor view as an applet. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform This project will be created in Eclipse. It should contain the existing applets and reuse as much of what is available in the applet. The applets and this eclipse plug-in should be in the same Eclipse project to ensure that the applets will continue to work when the Eclipse plug-in is completed. This project should run on both JDK 1.4 and JDK 1.5. The plug-in should run on both Eclipse 3.0 and Eclipse 3.1.