Splitting Model and UI in packages dependency problems

Hello:

    I'm working on a project, in which i want to organize the classes and
loose methods of the "core" functionality into a package (or more than one),
and the UI stuff in another (presenters, views, etc).
    So far, this worked well, but now i have more "core" classes and more UI
classes, i have dependency problems i cant resolve.

    As I can see, it's impossible to solve it having two separate packages,
so i should put all in one. But perhaps there is some trick or technique to
attack this kind of problems.

    Best regards,

--
Esteban A. Maringolo

Esteban A. Maringolo wrote:

>     I'm working on a project, in which i want to organize the classes and
> loose methods of the "core" functionality into a package (or more than
> one), and the UI stuff in another (presenters, views, etc).
>     So far, this worked well, but now i have more "core" classes and more
[...]
>     As I can see, it's impossible to solve it having two separate
> packages

This /should/ be possible.  In fact it should be easy to arrange.  Can you say
more about the problem you have, and what makes it difficult to solve; and
perhaps give an example ?

    -- chris