• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Framework Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Framework Question


  • Subject: Re: Framework Question
  • From: Ralph Scheuer <email@hidden>
  • Date: Wed, 29 Jun 2005 18:42:21 +0200

Hi,

Am 29.06.2005 um 15:48 schrieb Ute Hoffmann:


A. I need to use a partial Component residing in Framework B (no Bindings, but deeply knitted to the business logig in Framework B) in Framework A. The App both frameworks are used with sees both frameworks. I did try and it seems to work when i just use this partial Component in Framework A without a Reference to Framework B in Framework A. Is this a "safe" way to do this? Using partial Components from a framework which is referenced by the Application but not by the framework in which the component is actually used?

<insert the sound of an exploding head here>

Yes, that should be ok (if I understood correctly). In general, you should remember that you always have to include all frameworks that are used by the application directly or indirectly in the application project, that is:

Framework MyFoundation -- used by --> Framework MyComponents --> used by MyApplication

requires you to include MyFoundation and MyComponents in the Application project. You can then use MyComponent.framework components in the app, use MyFoundation classes in MyComponents, use MyFoundation classes in your app (the same goes for components...


B. Is it "proper" to cross reference Frameworks: Framework A has Framework B linked in and Framework B has Framework A linked in. I suppose I get into trouble that way, if I have to build from scratch and neither FW A is there nor FW B...

Yes, this will definitely result in a hen / egg problem that you don't really want to have. Try to avoid it and build a hierarchy instead. Thus, you can always stipulate where to start if you build everything from scratch - the day will come when you have to build from scratch. This is particularly nasty if you have changes in two interdependent frameworks where one change builds upon the other.


Framework B needs Framework A to build but Framework A does not need Framework B to build. Is this still true if I use a partial Component from FW B in FW A?

If you use a component from framework B in A, you will have to build B first, then A if you organize your framework in a hierarchical way (try to separate the levels, build one EOModel-containing EO framework, one with components, one with foundation extensions, etc. ) This might help you to know where to start and have a useful hierarchy.



I hope what I try to say does make some sense...

Apart from my exploding head: yes ;-)

Ralph
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Framework Question (From: Ute Hoffmann <email@hidden>)

  • Prev by Date: Re: Standalone Cocoa EOF Application Deployment
  • Next by Date: help for fetch with LIKE required
  • Previous by thread: Framework Question
  • Next by thread: WO 5.3 Deployment no longer platformed locked?
  • Index(es):
    • Date
    • Thread