CEDET

>>> Joakim Verona <joakim@...> seems to think that:
>Hello,
>
>I'm experimenting with the cogre-uml support.
>
>Saving of an autogenerated graph doesnt work, so I made a diff to
>enable it.
>
>Saving and loading of an uml graph works a bit with this diff but
>there are problems.
>
>A saved and restored graph looses its ability to link with the
>original source.
>
>The diff tries to take care of this, by useing the semantic overlay
>link/unlink functions. This doesnt work however. At least the
>overlays arent saved like #<overlay ...> in the file so it works to
>restore the file somewhat with this diff.
>
>Am I using the link/unlink stuff the wrong way?

You have the right idea.  Semanticdb uses the same calls as you are
using.

The problem with the -link- functions is that they assume that the
tags are to be linked to the current buffer.  A bit of an oversight
in the API it appears.

The code needed to fix it involves using semanticdb-find calls to
search out tags with those names in the project.  The tags in the
saved UML nodes would then be completely replaced with the found ones.
At the time I wrote that code, there was no good way to do this which
is why I didn't.  I hadn't thought of just re-linking them.

It seems to me that the semantic API needs a way to also save the
originating file name.  I'll have to think up a way to allow tags to
be saved/restored by external applications.

Eric

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org

"Eric M. Ludlam" <eric@...> writes:

>>>> Joakim Verona <joakim@...> seems to think that:
> The problem with the -link- functions is that they assume that the
> tags are to be linked to the current buffer.  A bit of an oversight in
> the API it appears.

hmm oki, that probably explains it...

> The code needed to fix it involves using semanticdb-find calls to
> search out tags with those names in the project.  The tags in the
> saved UML nodes would then be completely replaced with the found ones.
> At the time I wrote that code, there was no good way to do this which
> is why I didn't.  I hadn't thought of just re-linking them.

the good thing with that aproach would be that the graph would
assimilate changes in for instance method declarations in the original
source, no? The code could also be used to make a working "refresh"
function I guess, that re-creates the uml graph from changed sources.

> It seems to me that the semantic API needs a way to also save the
> originating file name.  I'll have to think up a way to allow tags to
> be saved/restored by external applications.

A further benefit of that is that it would ease round-trip editing I
guess. For instance, It might be convenient to use the graph to prototype a
number of classes. Each node could have manually entered tags,
including filenames. Then sources could be generated to files, from
the graph. And then sources could be changed and the graph refreshed
and so on...

> Eric
>
> -- 
>           Eric Ludlam: zappo@..., eric@...
>    Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
> Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org

>>> Joakim Verona <joakim@...> seems to think that:
>"Eric M. Ludlam" <eric@...> writes:
>
>>>>> Joakim Verona <joakim@...> seems to think that:
>> The problem with the -link- functions is that they assume that the
>> tags are to be linked to the current buffer.  A bit of an oversight in
>> the API it appears.
>
>hmm oki, that probably explains it...
>
>> The code needed to fix it involves using semanticdb-find calls to
>> search out tags with those names in the project.  The tags in the
>> saved UML nodes would then be completely replaced with the found ones.
>> At the time I wrote that code, there was no good way to do this which
>> is why I didn't.  I hadn't thought of just re-linking them.
>
>the good thing with that aproach would be that the graph would
>assimilate changes in for instance method declarations in the original
>source, no? The code could also be used to make a working "refresh"
>function I guess, that re-creates the uml graph from changed sources.

Yup.  A useful feature indeed.

>> It seems to me that the semantic API needs a way to also save the
>> originating file name.  I'll have to think up a way to allow tags to
>> be saved/restored by external applications.
>
>A further benefit of that is that it would ease round-trip editing I
>guess. For instance, It might be convenient to use the graph to prototype a
>number of classes. Each node could have manually entered tags,
>including filenames. Then sources could be generated to files, from
>the graph. And then sources could be changed and the graph refreshed
>and so on...

And that is one of my end goals.  All that's left to write is the code
generation framework, a tag refresher, and the appropriate user
interface elements to allow improved graph editing... preferably
in-line.

Eric 

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org