Book a Demo

Author Topic: Project Hyperlinks  (Read 6836 times)

Uffe

  • EA Practitioner
  • ***
  • Posts: 1859
  • Karma: +133/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Project Hyperlinks
« on: January 04, 2012, 08:29:27 pm »
Hey guys,


Well maybe I'm a complete idiot, but:

In medium-to-large EA deployments I usually recommend my clients to set up links between related projects, and typically to establish one central project whose sole purpose is to link to all the others (kind of like a home page).

The way we do this is by creating Hyperlinks to files which are .EAP shortcuts (which in turn are simply text files containing an EAConnectString).
The problem with these is that they only work if you have access to the file (server) where they are located, which in larger installations is not always the case even if you have access to the database holding the project. Think WANs, think intranets, think external consultants, you know the tune.

Now you can also create an EA Command Hyperlink which holds a FileOpen command - but that only pops up the Open dialog, it doesn't allow you to specify an EAConnectString.

That, simply put, is what I would like: the ability to create EAConnectString hyperlinks.
They should ideally be proper model elements rather than just diagram objects, like linked documents, but I'll take them as Hyperlinks if that's all I can get.  ;)

Or am I in fact an idiot and is there already a simple, one-click procedure to achieve this without going through an external file?

Cheers,


/Uffe
My theories are always correct, just apply them to the right reality.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Project Hyperlinks
« Reply #1 on: January 04, 2012, 10:18:52 pm »
Let me try to repeat your thought in other words: you want a model element representing a different repository.

q.

Uffe

  • EA Practitioner
  • ***
  • Posts: 1859
  • Karma: +133/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Re: Project Hyperlinks
« Reply #2 on: January 04, 2012, 11:18:22 pm »
Well yes, I suppose that would be a less rambling, wordy, nitty-gritty, lavish, profligate and redundant way of putting it.  ;D
My theories are always correct, just apply them to the right reality.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Project Hyperlinks
« Reply #3 on: January 05, 2012, 02:31:32 am »
Right. But your background is important.

I would use objects for this purpose. Like elements they have a files section where you can place the link to the repository. What would be neat is a way to perform a scriptable action on dbl-click. Thus the file could be opened automatically. There is an EA_OnOutputItemDoubleClicked which probably could be used for such a purpose (IIRC I already did something similar in the past).

q.

Uffe

  • EA Practitioner
  • ***
  • Posts: 1859
  • Karma: +133/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Re: Project Hyperlinks
« Reply #4 on: January 05, 2012, 03:21:55 am »
Provided it's a file, yes. But it needs to work for DB repositories too, so it'd have to be a breakdown of the EAConnectString, either as parameters in a hyperlink, like the ones you set for a Search hyperlink, or as a model element with tagged values or some hidden magic.
I'm thinking an Artifact with a «project» stereotype and a tiny EA logo in the top right corner.

The double-click script group could be useful on its own, although it would probably have to be restricted to elements and indicated visually -- could be pretty dangerous otherwise.

/Uffe
My theories are always correct, just apply them to the right reality.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Project Hyperlinks
« Reply #5 on: January 05, 2012, 06:35:13 am »
The problem I see here is that this EA artefact (which btw. could be created via shape script) contains information which is site specific like your external shortcuts. The problem persist - it just looks different. From my point of view the shortcut/dbl-click variant is sufficient.

And it will help you earn your next Rolex...

q.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Project Hyperlinks
« Reply #6 on: January 05, 2012, 10:19:38 am »
Quote
[size=18]...[/size]
I'm thinking an Artifact with a «project» stereotype and a tiny EA logo in the top right corner.
[size=18]...[/size]
/Uffe
No, use a «repository» stereotype.  We can start to end the project/project dichotomy where it sometimes means a repository and other times means a root within a repository.  (Unless you meant the ability to link to a project root in another repository - which I don't think you did)

Otherwise, gets my vote...

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Uffe

  • EA Practitioner
  • ***
  • Posts: 1859
  • Karma: +133/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Re: Project Hyperlinks
« Reply #7 on: January 05, 2012, 06:37:04 pm »
No, yes, the repository is what I want to link to, and a stereotype thus named would be absolutely fine.

And somewhat OT, but I don't actually find the project / repository thing much of an issue, because they're both EA-internal concepts; model now, model is a biggie: sometimes it's a project, sometimes a root node, and sometimes a package with something in it.
If we could get that cleared up, I would sleep a lot better at night. Also, peace would reign and sea levels would drop.
My theories are always correct, just apply them to the right reality.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Project Hyperlinks
« Reply #8 on: January 05, 2012, 09:37:16 pm »
Taking your OT issue: if all roots and views were just packages and it was left to the user to just stereotype them, everything would be fine. The current concept is a heritage which is not of any real worth. Or can anyone explain why I can't move packages to root or view level? And why I can't tag roots?

q.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Project Hyperlinks
« Reply #9 on: January 05, 2012, 11:47:15 pm »
Off topic:
The reason why you can't do what you want with regards to the root packages is the fact that these objects don't have an EA.Element.
Dealing with this in automation can also be a big PITA.
Had to fix a bug this morning which was caused by this anomality.

On Topic:
There's the EA Protocol Handler that might be of use. (you know the one click existing solution you were talking about)

Geert

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Project Hyperlinks
« Reply #10 on: January 06, 2012, 02:11:23 am »
Hmm. 2 bug entries. Latest dated 2009...

q.