On Feb 4, 2005, at 21:12, Maxwell, Adam R wrote:
> On Feb 4, 2005, at 07:12, Christiaan Hofman wrote:
>> Sorry to start this discussion again, but I was finally getting back
>> to the issue of the autogenerated local-url. I keep breaking my head
>> over the way to implement it. Let me recapture the way I remember the
>> Autogenerate when:
>> 1) newly added files (drop or choose from editor or doc), after:
>> - pref option to autogenerate is set
>> - && required fields are set
>> - && local-url field has not been edited by the user
>> 2) when we choose "Generate Local-Url(s)" from some menu (in Main
>> Menu or Editor Action popup).
> Sounds right.
>> Now there can be several possibilities for (non)exisiting files:
>> Old location: Generated location: Move/Generate?:
>> yes no yes
>> no no yes(generate)?
>> yes yes no, warn?
>> no yes no, warn?
> I'm afraid I don't get the "no" at old location options. Other than
> that, this is what I recall.
I am thinking of a situation where the local-url field is set, but the
linked file is somehow not there (either lost or never there). I guess
this should not happen when dropping or choosing a file, but it can
happen when some AutoFile menu item is chosen.
>> - do we autogenerate a local-url even if there was no linked file?
>> - do we want to generate a warning when a file already exists on the
>> generated location also for AutoFile? (presently we are silent on
>> Now my main problem is finding out wether the Local-Url field has
>> been edited. We concluded that we did not want autogeneration in this
>> case. Setting an ivar like needsToBeFiled is not persistent, so do we
>> only autogenerate (when we can) in the session where we add the file
>> by dropping/choosing a file, and not in a later session?
> Another option would be to make this dependent on using a .bdsk file,
> in which case the needsToBeFiled ivar could be archived. This would
> also allow archiving the file as an alias ref, which would be helpful
> as well. In lieu of those changes, yes; I'd only allow automatically
> setting it for the case you describe.
>> As a last remark, do we want to keep the current way of
>> autogeneration by moving-without-renaming? We can have an extra
>> option (though it might be confusing to add that in the pref UI), or
>> what I was thinking of is to add two new format specifiers:
>> %l filename without extension
>> %L filename with extension
>> so that the current implementation is equivalent to format="%L" (with
>> the improved "%l%n0.pdf" that adds a unique number).
> Yeah, that sounds reasonable. Better to add a format specifier than
> maintain similarly large and buggy blocks of code :).
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> Bibdesk-develop mailing list