[Cxtable-devel] Where are we at, once CVS is up?

[Williams, D. <DAV...@ca...>]

I guess I am wondering what things you were hoping to do once CVS was updated... 

I imagine the first step will be to add the "package cxtable.xxxx;" lines, and add the imports in the appropriate places, so that it will build again ;-)

Would you be able to do some of that, or would it be best if I went ahead and did that?

What are the basic commands for checking in?  (there goes my laziness again...I did not RTFM on CVS...so maybe I could start there...but it is just EASIER to ask people..)

Let me give you a concrete example of something, and you tell me if it would cause a problem..

In package corecomm, there are places where it references an xPanel (called reporter).  xPanel is in package gui. 

CAN (let's say its xRegistry...  when it adds a connection) "import cxtable.gui.xPanel;" and be compiled still when certain "GUI" elements use corecomm stuff?  Do you run into a chicken and egg scenario?

((I have grossly ignored learning about packages..but I agree that it is the best way to approach developing a project like this in the future...))

~Dave



David Scott Williams
Computer Associates
Marketing Representative-Sales Call Center
One Computer Associates Plaza 
Islandia, New York  11749
tel: +1 800-243-9462 ext. 73431
tel: +1 631-342-3431 (Direct)
fax: +1 631-342-5734
wi...@ca...