kicad-developers team mailing list archive

[Cheng Sheng <jeru.sheng@xxxxxxxxx>]

I myself prefer storing all files specific to the project within the
project directory, including datasheets, components, adjusted footprints
and scripts. This way makes things easier when I copy the project around.
After all, I don't mind disk space waste on a few duplicated datasheets;
they don't take much space.

If the direction of move by the patch makes some other workflow styles
harder to optimize in the future, please let me know. I don't mind
alternative proposals that can fulfill more workflow types. What I wrote is
just a "shortest-path" I can see based on my own workflow.

Regards,
Cheng

On 28 May 2017 at 20:53, Ingo Kletti <ikletti@xxxxxxxxxxxxxxxx> wrote:

> Am 28.05.2017 um 18:47 schrieb Sergey A. Borshch:
>
>> On 28.05.2017 14:35, Cheng Sheng wrote:
>>
>>> So I made a patch to resolve the path before it is passed to
>>> "wxLaunchDefaultBrowser()". If it looks like a URL or is an absolute
>>> path, doesn't do anything; but if it is a relative path, append
>>> "${KIPRJMOD}" to it.
>>>
>> Are you storing all datasheets in every project? I think it's better to
>> keep one copy per library, so path must be relative to library location.
>>
>
> Don't know about the OP, but from past experience it is wise to store the
> datasheet for the different components tpgether with the project files.
> That way you always have the specs available that your design is based on.
>
> So a relative path makes sense depending on the use case and workflow.
>
> Regards,
>
> Ingo
>
>
> _______________________________________________
> 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
>