← Back to team overview

kicad-developers team mailing list archive

Re: [RFC] Application naming

 

Just going to chip in and say that I agree here, having had students working with kicad, Its really not obvious what application to use for what. The cvpcb is unpronouncable in any regard and even harder to remember. One of the most common questions actually.

- Kristoffer

On 2017-02-02 20:28, Chris Pavlina wrote:
Can I just copy all this and claim I wrote it? It sounds good ;)

On Feb 2, 2017 2:11 PM, "Jon Evans" <jon@xxxxxxxxxxxxx
<mailto:jon@xxxxxxxxxxxxx>> wrote:

    As a mostly user and occasional code hacker, here are my thoughts:

    The EDA tool industry is trending towards more integration, as many
    of the commercial products were originally formed from separate
    applications (often from separate companies originally).  I have
    used a number of commercial products and they are all this way.
    Having separate applications with separate lineage makes for
    less-than-optimal usability and workflow, and so all the vendors are
    trying to move towards integration -- either by putting everything
    in a single binary, or more often, keeping multiple binaries, but
    branding them together, making sure the UIs look consistent, and
    having lots of integration between them so it doesn't feel like a
    struggle to go between the different binaries for different parts of
    the EDA workflow.

    So, I'm in favor of rebranding the KiCad applications, because I
    think it's in line with the work you all are doing to improve the
    user workflow and improve the integration between the schematic,
    layout, and library workflows.  I also think it would be good to
    include the name change in a "marketing message" to the user
    community about a focus on the whole EDA workflow, not separate
    applications in silos.  Even if you technically can run the
    schematic editor separate from the PCB layout tool, if you have the
    *mindset* that they are all pieces of the same puzzle and need to
    fit together, it can influence the philosophy of the project.

    But, as JP mentioned, this would be a big deal in terms of
    documentation and resources on the web.  I would suggest that the
    problems can be overcome, but only if the communications and timing
    of the change is handled well.

    -Jon

    On Thu, Feb 2, 2017 at 1:54 PM, jp charras <jp.charras@xxxxxxxxxx
    <mailto:jp.charras@xxxxxxxxxx>> wrote:

        Le 02/02/2017 à 19:13, Pedro Martin a écrit :
        > Hi Chris,
        >
        > Beginners solve this issue... reading the manual.
        >
        > Why not keep the actual names only because JP named them this way?
        >
        > Regards,
        > Pedro.
        >

        Thanks Pedro.
        But the major issue which must be taken in account it not that.

        Changing names has serious results:
        * Documentation and all the translations has to be modified.
        Opinion was asked to devs, to users, but not to doc
        writers/translators,and this is really not fair.
        * Links on Internet cannot be modified, and there are a lot of
        hits regarding kicad:
        I really agree Cvpcb is not a good name, but just try "Cvpcb" on
        Google .

        Before changing these names you have to  *seriously* think to
        the results.
        (Think about that not only twice, but 3 times about that)

        --
        Jean-Pierre CHARRAS

        _______________________________________________
        Mailing list: https://launchpad.net/~kicad-developers
        <https://launchpad.net/~kicad-developers>
        Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
        <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
        Unsubscribe : https://launchpad.net/~kicad-developers
        <https://launchpad.net/~kicad-developers>
        More help   : https://help.launchpad.net/ListHelp
        <https://help.launchpad.net/ListHelp>



    _______________________________________________
    Mailing list: https://launchpad.net/~kicad-developers
    <https://launchpad.net/~kicad-developers>
    Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
    <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
    Unsubscribe : https://launchpad.net/~kicad-developers
    <https://launchpad.net/~kicad-developers>
    More help   : https://help.launchpad.net/ListHelp
    <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



References