Except for the Locale code I infused into Trace, it should be very simple to
make a fat and slim distrubution. I purposely set up DIFactory and the
pre-existing DatabaseInformation class for this, so that
1.) different children of DIAbstractTableProducer can be selected at either
compile or con
Thanks Campbell,
1) I am not concerned at all about commenting 1.6.1 and 1.4.x, otherwise
what's the point of doing all the work to get 1.7.0 out. As for the next
release, we need a two-version (fat and slim) distribution because of the
very large size of your much improved metadata. (To put thi
Thanks Ulrich,
You can upload a context diff to the patch tracker and it will certainly be
incorporated into the code to cater for small device screen sizes.
As Campbell said, we do welcome new developers and if you are interested to
contribute and be involved you are most welcome to join. There
Ulrich:
It sounds like you are really starting to get active with the code. I, for
one am really happy to see this. As I have stated many times in various
threads, we really need more active developer-role project members. So,
while I am not in a position to enroll you as a project member mys
1.)
Ok. Thanks for the clarifications. I'm still 100% clear though, because I
forgot to ask some questions:
When we add in my MetaData stuff, much of the current javadoc for JDBC will
cease to be valid. So, should I be docing based on the next release
including the MetaData patches, or should
Hi,
I suggest two small changes for DatabaseManager and
ConnectionDialog.
1. If the DatabaseManger and the ConnectionDialog are started on a
device with a small screen (as on my PDA Psion) i. e. with a screen
width less or equal than 640, the corresponding frames are set to
location (0,0) with t
Re JDBC documentation, we must indicate which methods we support and which
limitations there are. JDK source comments assume the method is supported
whereas ours throw a NOT_IMPLEMENTED exception. Also there is the question
of support for JDBC2 from JDK 1.1.X which I have addressed to some extent,
Fred:
I think the JDBC documentation is already done in a way: If we simply do
not include *any* javadoc comments for the JDBC interface methods, then if
the latest JDK src is on the javadoc classpath at javadocs build time, then
the comments are simply copied over from there, with an indication
