[Openroad-users] Included applications

[CAMF Delaunay]

Allan,

Maybe I have misunderstood something, but from my point of view this is a design point

Because OR included apps tree is a top-down hierarchy, why don't you go further in your split process 
and move application_a_objects & application_p_objects potentially-called-by-common_frames components
from application_a_objects & application_p_objects apps into common_frames app ?

application_a_objects & application_p_objects apps would only contain dedicated objects
while common_frames apps would contain low level components
as well as common application_a_objects & application_p_objects components
application_a_objects & application_p_objects apps should then be removeable from common_frames app

I have not opened OR for a (too) long time but hope this helps anyway
Regards
Christian

  ----- Original Message ----- 
  From: Allan Biggs 
  To: Openroad-Users 
  Sent: Friday, January 26, 2007 1:14 PM
  Subject: [Openroad-users] Included applications



  We are trying to split an application into its 2 component applications application_a and application_p and a common set of frames - hopefully this will reduce maintenance and implementation issues in the future. 

  What we have discovered is that to call a frame in  the common_frames app from application_a or application_p we have to include both application_a_objects and application_p_objects  in the common_frames application as well as in their parent applications.  [Frames in the common_frames app use objects also used by the main application] 

  application_a 
      (included apps) 
      common_frames 
      application_a_objects 

  application_p 
      (included apps) 
      common_frames 
      application_p_objects 



  common_frames 
      (included apps) 
      common_objects 
      application_a_objects 
      application_p_objects 


  This is fine for development but I perceive an issue when we come to create an image of application_a and application_p; reading the user guide the only way I can see of doing this is to link to the common application rather than include the common_frames.  At present we just include all applications in the combined image.   

  I wonder if I am misreading this -  we would prefer to have stand-alone applications application_a and application_p  with all applications included and to avoid dynamically linking to the common_frames app. 

  We are using OpenROAD 4.1/0403 on XP 

  We would appreciate any pointers. 

  Thanks Allan 

  for anyone old enough to remember this is a similar nightmare to linking tasks for RSX11M !! 

This communication is for use by the intended recipient and contains
information that may be Privileged, confidential or copyrighted under
applicable law. If you are not the intended recipient, you are hereby
formally notified that any use, copying or distribution of this e-mail,
in whole or in part, is strictly prohibited. Please notify the sender by
return e-mail and delete this e-mail from your system. Unless explicitly
and conspicuously designated as "E-Contract Intended", this e-mail does
not constitute a contract offer, a contract amendment, or an acceptance
of a contract offer. This e-mail does not constitute a consent to the
use of sender's contact information for direct marketing purposes or for
transfers of data to third parties.

Francais Deutsch Italiano  Espanol  Portugues  Japanese  Chinese  Korean

           http://www.DuPont.com/corp/email_disclaimer.html


------------------------------------------------------------------------------


  _______________________________________________
  Openroad-users mailing list  Openroad-users at peerlessit.com

  To unsubscribe please click on this link
  mailto:openroad-users-unsubscribe at peerlessit.com&subject=unsubscribe

  To subscribe please click on this link
  mailto:openroad-users-subscribe at peerlessit.com&subject=subscribe 

  __________ Information NOD32 1980 (20070115) __________

  Ce message a ete verifie par NOD32 Antivirus System.
  http://www.nod32.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://peerlessit.com/pipermail/openroad-users/attachments/20070129/ddd69306/attachment.html