Fwd: [ditrack commit] r1126 - src/trunk/DITrack/Command

[Oleg Sharov]

2007/1/23, Vlad Skvortsov <vss at 73rus.com>:
>
> Oleg Sharov wrote:
>
> [skipped]
> >
> > Author: oleg
> > Date: 2007-01-21 03:53:35 -0800 (Sun, 21 Jan 2007)
> > New Revision: 1126
>
> [skipped]
>
> > -                "Invalid entity name '%s'" % opts.fixed[1],
> > +                "Invalid entity identifier: '%s'" % opts.fixed[1],
> >                  fatal=True)
> >
> > Vlad, I tolk with you about IDENTIFIERS and NAMES (see doc/design.txt)
> > I think we must change the notion NAMES, it similar with IDENTIFIERS,
> > but using for local entities.
>
> ...and the reason why we need to do this is ... ?


Different messages such as "Invalid issue name" and "Invalid issue
identifier" will confused an end user

>
> > Now, we have ambiguous using these notions, please
> > review error message in DITrack/Command/commit.py
>
> What's the exact problem with that?


from DITrack/Command/commit.py
if x in string.digits:
     "Non-local issue id '%s', ignored\n" % id

from design.txt
"...local entities are assigned character ids, which we refer to as
NAMES..."
but we give the ambiguous message with "local issue" and "id"

from DITrack/Command/commit.py
"Invalid entity name '%s', ignored\n" % id

we write "entiry name", but if an user call alphanumeric combination we will
write "Non-local issue ID"

I think, we can named local/firm entities anyhow for ourselves.
But an end user must see the homogeneous appellation "identifier" or "id"


-- 
Oleg G. Sharov
o.sharov at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ditrack.org/pipermail/dev/attachments/20070126/bb93e4bd/attachment.html