Here is how I would state our requirements for the Tulka modifications. We are looking at using the Tulka WB. It is located at [url removed, login to view]~benes/tulka/ When the client is started, it is passed to the server, port, etc directly. It then pops up a login box to request the username/password. We want to be able to pass it the username/password in the same way it accepts the server and port information. We also don't want it to display the login box at all. You can find the login box code in tulka/whiteboard/[url removed, login to view] if you download the source code from the website listed above. To summarize, the desired behavior upon clicking a link is for the whiteboard to launch and upon launch, to be passed the server, port, media, username and password. Upon completion, we will require the modified source code as well as a new .jar file for the client.
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).
Windows, linux browsers IE, Firefox