Author Topic: Hide or Cloak Projects or On demand loading  (Read 3531 times)

Roger A. Shepherd

  • EA User
  • **
  • Posts: 35
  • Karma: +0/-0
    • View Profile
Hide or Cloak Projects or On demand loading
« on: October 26, 2006, 08:50:24 am »
For those of us that push the limits of EA and truely use EA for Enterprise work, it would be VERY helpful if there were some way to hide/cloak projects so that we don't have to see items which we don't need to.  

There is also a related concept of on-demand loading of information.  It is taking longer and longer to open the central repository and having the ability to load packages and elements as their needed would be helpful.

peter.zrnko

  • EA User
  • **
  • Posts: 253
  • Karma: +0/-0
    • View Profile
Re: Hide or Cloak Projects or On demand loading
« Reply #1 on: October 26, 2006, 10:25:42 am »
Quote
it would be VERY helpful if there were some way to hide/cloak projects so that we don't have to see items which we don't need to.  


Try "Open Project" from menu. Select a project you want to remove and press "Remove from selection list".
Peter

Roger A. Shepherd

  • EA User
  • **
  • Posts: 35
  • Karma: +0/-0
    • View Profile
Re: Hide or Cloak Projects or On demand loading
« Reply #2 on: October 31, 2006, 10:58:09 am »
Thanks, but I guess I needed to clarify.  Within one central repository, we have MANY root projects in the project Browser that represents many of our systems.  Often times we find it desirable to hide the systems we're not actively working with.  And ideally, each user can have muliple profiles to allow them to work with whatever system(s) they're working with at the time; for me it changes weekly and sometimes daily so that I'd like to switch between which sets of root projects are hidden.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8085
  • Karma: +118/-20
    • View Profile
Re: Hide or Cloak Projects or On demand loading
« Reply #3 on: October 31, 2006, 12:59:32 pm »
There's no way currently do do what you're wanting.  But you could achieve similar results by having each user have a local repository (eg. eap file) and using controlled packages.

Then you can import a controlled package when you want to work with it, and remove it from your model when you don't want to see it.