several questions about your commits from branches/attachments.
Ivan Glushkov
gli.work at gmail.com
Thu Aug 9 22:45:51 PDT 2007
> > 2. act.py:
> > elif r == mi_new:
> > ti = DITrack.UI.TextInput("File to attach (blank to
> > abort)")
> >
> > while 1:
> > fname = ti.run()
> >
> > ...
> > issue.add_attachment(fname)
> >
> >
> > It is possible to define a key for attachment in _Attachments:add(),
> > but it's not allowed to determine it here.
>
> Why do you think it would be usable? I can imagine only one use case
> where a user wants to attach a file under different name than it is on
> the disk. I think in this case there is a simple workaround of renaming
> the file into desired name beforehand.
>
> Adding a possibility to attach a file under a different "short name"
> seems like unnecessary complexity to me (at least at this point).
ok, i agree. This is indeed useless feature.
> > 3. May be we should use some agreement about attachments naming? For
> > example to link to the second attachment of the 5'th issue: "i#5.f2"?
> > Or something similar?
>
> Yeah, we might... But there is a problem of "unusual" file names here
> (spaces, commas, etc). So it's not that straightforward. I suggest
> getting users' feedback after the 0.6 release to decide how we want to
> handle that.
i meant here to address to them by number, not name. So i#5.f2 - is
the second file attached to issue #5.
Ivan.
More information about the Dev
mailing list