Skip to main content

[REORG] Project separation ready

4 replies [Last post]
Anonymous

I have finally managed to separate the projects and add some common
reporting targets.

Currently I have tested all in NetBeans, and the build works ok, except
for the JNDC markup stuff, that is missing the TabularDataModel stuff.

I'll continue polishing it and adding Eclipse support(also straight Ant
of course), some documentation and demos for each package.

Please take a look around and let me know what you think.

--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
rbair
Offline
Joined: 2003-07-08

Whoa! You commented out the ProgressManager from the AbstractDataSource! I assume this was done to reduce probably the only dependancy of the binding framework on the Application class (or App as I guess it was renamed?).

The whole progress API I added a couple of months ago without much fanfare, I don't know if you are familiar with how it all works? This link (http://www.javadesktop.org/forums/thread.jspa?forumID=53&threadID=4585&m...) provides the justification.

What it all boils down to is that the DataStoreConnection needs to be able to tell the ProgressManager that it has a new Progressable for it to keep track of. I'm not sure how to remove this dependancy from the data API

Richard

Nicola Ken Barozzi

jdnc-interest@javadesktop.org wrote:
> Whoa! You commented out the ProgressManager from the
> AbstractDataSource! I assume this was done to reduce probably the only
> dependancy of the binding framework on the Application class (or App as
> I guess it was renamed?).

Yes, this was the reason.

I found it amusing that actually the packages where linked one another
usually only in a couple of points.

> The whole progress API I added a couple of months ago without much
> fanfare, I don't know if you are familiar with how it all works? This
> link
> (http://www.javadesktop.org/forums/thread.jspa?forumID=53&threadID=4585&m...)
> provides the justification.
>
> What it all boils down to is that the DataStoreConnection needs to be
> able to tell the ProgressManager that it has a new Progressable for it
> to keep track of. I'm not sure how to remove this dependancy from the
> data API

This is a very important point... even more, as it boils down to this:
how should the Application interact with other packages?

For example, I'm also forced to have swingx stuff depend on the app
package just because the JXEditor has some undo-redo actions. For the
rest, there is no dependency.

The only way I can think of right now is that the Application itself
sees if the components are ProgressTrackable and supplies them with a
ProgressManager, which should be in the Progressable package. Oh, and
ProgressManager becomes an interface and the Application has
ProgressManagerImpl.

Or, if we want for some reason to keep the static accessor to the
Application services, we can make a separate AppApi project that keeps
only the service interfaces. Not nice IMHO.

--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

rbair
Offline
Joined: 2003-07-08

When I pulled the project open in NetBeans (awesome, so glad I didn't have to create the project files myself), I got several "Resolve Refeference Problems". They were all simple, except for the one about "Java_HotSpot_TM__Client_VM_1.4.2_05-b04". Is there a more common name that we could use for the VM? I'm not an expert at NetBeans (yet...), but I'm a little concerned that I can't use my Java 5 vm with the project set up the way it is. Of course I could change the project, but that's not cool :)

Richard

Nicola Ken Barozzi

jdnc-interest@javadesktop.org wrote:
> When I pulled the project open in NetBeans (awesome, so glad I didn't
> have to create the project files myself), I got several "Resolve
> Refeference Problems". They were all simple, except for the one about
> "Java_HotSpot_TM__Client_VM_1.4.2_05-b04". Is there a more common name
> that we could use for the VM? I'm not an expert at NetBeans (yet...),
> but I'm a little concerned that I can't use my Java 5 vm with the
> project set up the way it is. Of course I could change the project, but
> that's not cool :)

Yeah, it sucks mightly... the fact is that my 1.4VM exposes itself with
that name, and to prevent me from using 1.5 stuff, I put that in.

Not sure how to fix this though, will check.

--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net