Robert Widhopf-Fenk <[EMAIL PROTECTED]> writes:
> On Friday, May 21, 2004 at 11:07:44, Masatake YAMATO wrote:
>> > I cannot find a location where it is actually used.
>> >
>> > IMHO the "partner" functionality might be even removed as
>> > bookmarks are more powerful/user-friendly.
>> >
>> > Robert.
>>
>> I'm sorry but to tell the truth, I have not tried bookmark yet. My
>> xtla development process is still depends on partner functionality.
>> `tla-partner-popup-menu' written by me is for future use.
You should ;-)
> Well, I will not remove it, but you know the discussion
> about fighting features? IMHO we should provide just one
> way/interface to the same functionality. This decreases the
> code that must be maintained, might be more stable and new
> users have a clear way where to go in order to do XY.
I had a discussion about that with Aaron Bentley, author of aba. (in
Cc of this message)
The bookmark feature is nice. But:
* This is an Emacs-only feature.
* The bookmark contents is managed on a per-user basis. It's nice, but
we should also provide a way to manage this on a per-project basis.
The typical scenario is:
- A new developer joins the team
- He gets the list of archives+version from the project itself
- He can add his own
- On his side, he may want to use a superset/subset of the set of
versions suggested by the archive.
=> We would like to set up a convention for several (all ?) tla
front-ends:
* The file {arch}/=partner-versions should be a list of newline
separated version names. It is added in the archive.
* The file {arch}/++my-partner-versions is also a list of newline
separated version names, but is not added in the archive.
* The front-end should use {arch}/++my-partner-versions as a list of
partners, if the file exists, and if not, use
{arch}/=partner-versions.
That's for the general convention. For the particular case of xtla's
bookmarks, I think we can keep the bookmark-missing feature as it is,
and provide a function to initialise the list of partners from those
files.
So,
1) Aaron, did I summarize the situation well? Anything to add?
(Please, Cc the xtla ML in your reply)
2) Xtla's developers, what do you think about that?
--
Matthieu
