kicad-developers team mailing list archive

[Jon Evans <jon@xxxxxxxxxxxxx>]

I guess ultimately this is up to Jeff since he's implementing it, but I
think this is going way above and beyond what any user should expect of an
application.  I have never used any software that tried this hard to handle
the "save as" feature without any chance of the user needing to take some
follow-up actions such as deleting old auto-generated files, etc.  I
question the value of creating this amount of complex UI around "save as".

On Mon, Nov 11, 2019 at 4:44 PM Eeli Kaikkonen <eeli.kaikkonen@xxxxxxxxx>
wrote:

> Here's a rough idea of what a confirmation dialog could do:
>
> [image: image.png]
>
> I think something like that would be flexible enough to help the user with
> most workflows and left the responsibility to the user while being simple
> and easy enough to use (although a bit more work to implement, of course).
>
> Eeli Kaikkonen
>
> ma 11. marrask. 2019 klo 23.20 Jeff Young (jeff@xxxxxxxxx) kirjoitti:
>
>> Limiting it to a dash is just because that’s all Kicad generates.  The
>> user could indeed use anything.
>>
>> So should we rename any file that starts with the old project name?  I
>> did have a version that did that, but it seemed too aggressive to me.
>>
>> On 11 Nov 2019, at 20:56, Eeli Kaikkonen <eeli.kaikkonen@xxxxxxxxx>
>> wrote:
>>
>>
>>
>> ma 11. marrask. 2019 klo 22.41 Jeff Young (jeff@xxxxxxxxx) kirjoitti:
>>
>>> Yes, the current algorithm renames files that either match the project
>>> name (with any extension), or start with the project name followed by a
>>> dash.
>>>
>>
>> Limiting the following character to dash seems arbitrary. Underscore is
>> used often, and why it should be limited at all?
>>
>> Here's one more possible solution. The current file dialog is kept, but
>> if any generated or unknown files which begin with the project name are
>> found, a new dialog asks if the user wants to rename and copy them or not
>> to copy them at all, or maybe copy them as is.
>>
>> On the other hand, what to do with other files which don't begin with the
>> project name? Should they be confirmed and copied (as is), too?
>>
>> What about the backup files?
>>
>> I can see two use cases: rename the project (replace the old one); and
>> copy the project to be a base for a new one. In the former case renaming
>> and keeping about everything could be desired. In the latter case all but
>> the basic project files would probably be ditched.
>>
>> In the case of renaming I'm also interested in knowing how it affects
>> version control, for example git, if the project is a repository. That must
>> be tested, I think.
>>
>> Eeli Kaikkonen
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>