The Source for Java Technology Collaboration
Webmaster Alert: Posting to Jive Forums is currently not working. Estimated time for fix is unknown.

Home » java.net Forums » Mobile & Embedded » OCAP-RI Users

Thread: Doubt regarding multiple workbenches in OCAP trunk

Welcome, Guest Help
Login Login
Guest Settings Guest Settings
This question is not answered. Helpful answers available: 2. Correct answers available: 1.

Reply to this Thread Reply to this Thread Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 1 - Last Post: Nov 24, 2009 9:13 AM by: mmillard Threads: [ Previous | Next ]
mark13

Posts: 6
Doubt regarding multiple workbenches in OCAP trunk
Posted: Nov 23, 2009 8:37 PM
 
  Click to reply to this thread Reply

When I went through the directories I have seen multiple workbenches. After reading some posts I concluded that, Vidiom's Workbench is kind of obsolete and tru2way workbench is in use. Is that correct?

If it is so, why there are some directories for Vidiom stuff. Is tru2way workbench using some of the Vidiom's components?

Also, can we use tru2way workbench to alter/provide implementations within the specification or is it just used for developing applications?

If we cannot modify the implementations using workbench, how to do that?

Thanks in advance...................

mmillard

Posts: 16
Re: Doubt regarding multiple workbenches in OCAP trunk
Posted: Nov 24, 2009 9:13 AM   in response to: mark13
 
  Click to reply to this thread Reply

You are correct to assume that the Vidiom VISION Workbench code in this project is obsolete and no longer being supported. The CableLabs SDK can be found in the main trunk under https://ocap-ri.dev.java.net/svn/ocap-ri/trunk/SDK.

The <tru2way> Workbench is based upon the TVT Framework from TvWorks. Some code has been leveraged from VISION Workbench to implement OCAP Project workflow features.

The <tru2way> Workbench is mainly used for developing OCAP applications. The workbench uses the RI Emulator for simulating the applications using the RI OCAP Stack. You can think of the emulator as a port of the RI OCAP Stack to Windows.

If you want to alter the RI OCAP Stack implementation, you need to work in the https://ocap-ri.dev.java.net/svn/ocap-ri/trunk/ri tree. The ODLSrc directory contains the RI OCAP Stack implementation and the RI_Platform directory contains the underlying platform support for the Windows port.




 XML java.net RSS