The only step I know of is removing hard dependencies from NetUI code to
Controls classes. There might be more -- this is the only one I'm aware of.
Rich
Eddie O'Neil wrote:
Rich--
What are the steps that you think need to be taken toward modularity
that aren't currently done?
Eddie
Richard Feit wrote:
I think it would help Beehive adoption to be able to say, "the pieces
of beehive work really well together, but each can be used
independently." Spring does a great job at this -- it's consistent
across the framework, but it's very modular. Beehive is *almost* in
the same boat, with just a few hard dependencies (that I'm aware of),
and I think it would be great to take it the last few steps towards
modularity.
Thoughts?
Rich
- Re: dependencies between pieces of beehive Richard Feit
-