Hi Guys,
I actually did propose to change the names of the kicad tools few years
ago.
I personally think:
- all kicad tools should be renamed with 100% priority to users. Hence, for
example, the schematic editor should be called "schematic editor".
- rename kicad itself would also be a good idea
On Thu, Feb 02, 2017 at 05:59:00PM -0500, Chris Pavlina wrote:
> On Thu, Feb 02, 2017 at 11:54:09PM +0100, Kristoffer Ödmark wrote:
> > Why dont keep it dead simple, but still keeping the KiCAD brand?
> >
> > I suggest prefix every subprogram with kicad- and then use a either
> > extremely well kn
Well, the user response on the forum has been overwhelmingly in favor:
https://forum.kicad.info/t/non-devs-what-do-you-think-of-the-app-names/5147
That said, I'm in no hurry to do this - like I said, I'm just seeking
out opinions to know whether people agree with me or not. I'd like to
see it hap
Hi,
On 03.02.2017 13:22, Wayne Stambaugh wrote:
> We should probably put this on the KiCad website in the about section.
> I'm sure there are users who would like to know how the name KiCad came
> to be and now we know the rest of the story.
We could also ask for the mailing list archive to just
On 2/3/2017 7:14 AM, jp charras wrote:
> Le 02/02/2017 à 20:20, Pedro Martin a écrit :
>> There is still the secret of the meaning of the Ki of Kicad.
>>
>> Regards,
>> Pedro.
>>
>
> Well, Ki has no meaning.
> But Ki has a story.
>
> A long time ago I was looking for a name, a good name.
> A good
Le 02/02/2017 à 20:20, Pedro Martin a écrit :
> There is still the secret of the meaning of the Ki of Kicad.
>
> Regards,
> Pedro.
>
Well, Ki has no meaning.
But Ki has a story.
A long time ago I was looking for a name, a good name.
A good name is a short name, easy to pronounce by anybody, and
On Thu, Feb 02, 2017 at 11:54:09PM +0100, Kristoffer Ödmark wrote:
> Why dont keep it dead simple, but still keeping the KiCAD brand?
>
> I suggest prefix every subprogram with kicad- and then use a either
> extremely well known abbreviation (PCB) or a descriptive english word.
>
> Examples:
>
>
Why dont keep it dead simple, but still keeping the KiCAD brand?
I suggest prefix every subprogram with kicad- and then use a either
extremely well known abbreviation (PCB) or a descriptive english word.
Examples:
eeschema-> kicad-schematics
pcbnew -> kicad-layouts
3d-viewer -> kic
On Thu, Feb 02, 2017 at 09:55:59PM +0100, Clemens Koller wrote:
> Hi!
>
> On 2017-02-02 20:20, Pedro Martin wrote:
> > There is still the secret of the meaning of the Ki of Kicad.
>
> And what is the cv in cvpcb?
>
> bitmap2component seems also quite limited in case we are going to support svg
Hi!
On 2017-02-02 20:20, Pedro Martin wrote:
> There is still the secret of the meaning of the Ki of Kicad.
And what is the cv in cvpcb?
bitmap2component seems also quite limited in case we are going to support svg
import...
in, sure, an "Import..." menu option.
If we want project branded name
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,
+1 to changing the names. Every time I show kicad for the first time to
someone there is an odd silence when they find out the names. Then I try to
explain that those are "just names".
Please, any name you guys chose will be better than cvpcb and pcbnew. I
liked more Chris' suggestions.
Marcos
Sorry for the attachment.
I still have a 2004 copy in my computer ;-)
El 02/02/17 a las 19:58, Chris Pavlina escribió:
Why not keep the software originally exactly as JP wrote it in the
beginning?
___
Mailing list: https://launchpad.net/~kicad-deve
Can I just copy all this and claim I wrote it? It sounds good ;)
On Feb 2, 2017 2:11 PM, "Jon Evans" 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 fo
There is still the secret of the meaning of the Ki of Kicad.
Regards,
Pedro.
El 02/02/17 a las 19:35, Chris Pavlina escribió:
*scratches head* must have missed this...now I sure look like an ass for
submitting that suggestion as if nobody else had ;)
On Thu, Feb 02, 2017 at 07:33:01PM +0100,
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 produc
On Thu, Feb 2, 2017 at 12:58 PM, Chris Pavlina
wrote:
> I'm not getting these emails that JP is replying to that seem to be
> addressing me...
>
> On Thu, Feb 02, 2017 at 07:54:02PM +0100, jp charras wrote:
> > Le 02/02/2017 à 19:13, Pedro Martin a écrit :
> > > Hi Chris,
> > >
> > > Beginners so
I'm not getting these emails that JP is replying to that seem to be
addressing me...
On Thu, Feb 02, 2017 at 07:54:02PM +0100, jp charras wrote:
> Le 02/02/2017 à 19:13, Pedro Martin a écrit :
> > Hi Chris,
> >
> > Beginners solve this issue... reading the manual.
That's not the point. Silly qui
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
On 2/2/2017 1:33 PM, jp charras wrote:
> Le 02/02/2017 à 15:41, Pedro Martin a écrit :
>> Hi Chris,
>>
>> Maybe "Composant Vers pcb"? Component to pcb.
>
> Pedro, you are the winner!
> Merci, Pedro.
Know we all know. :) Thanks JP!
>
>>
>> Related to the other names, I don't mind.
>>
>> I vote
*scratches head* must have missed this...now I sure look like an ass for
submitting that suggestion as if nobody else had ;)
On Thu, Feb 02, 2017 at 07:33:01PM +0100, jp charras wrote:
> Le 02/02/2017 à 15:41, Pedro Martin a écrit :
> > Hi Chris,
> >
> > Maybe "Composant Vers pcb"? Component to
Le 02/02/2017 à 15:41, Pedro Martin a écrit :
> Hi Chris,
>
> Maybe "Composant Vers pcb"? Component to pcb.
Pedro, you are the winner!
Merci, Pedro.
>
> Related to the other names, I don't mind.
>
> I vote for Bitmap2Component as Import Image in libedit and modedit.
>
> Regards,
> Pedro.
>
On Thu, Feb 02, 2017 at 01:07:05PM -0500, Wayne Stambaugh wrote:
> On 2/2/2017 1:08 PM, Chris Pavlina wrote:
> > Keep in mind I am not suggesting changing the name of the whole package.
> > This is more like if Ford suggested changing Qxshift* to SelectShift[1].
> > It's a clearer name that tells w
Hi Chris,
Beginners solve this issue... reading the manual.
Why not keep the actual names only because JP named them this way?
Regards,
Pedro.
El 02/02/17 a las 18:46, Chris Pavlina escribió:
I think I am going to seek out some user views on this. As usual it
doesn't do us much good to specul
On Thu, Feb 02, 2017 at 01:07:05PM -0500, Wayne Stambaugh wrote:
> On 2/2/2017 1:08 PM, Chris Pavlina wrote:
> > Keep in mind I am not suggesting changing the name of the whole package.
> > This is more like if Ford suggested changing Qxshift* to SelectShift[1].
> > It's a clearer name that tells w
On 2/2/2017 1:08 PM, Chris Pavlina wrote:
> Keep in mind I am not suggesting changing the name of the whole package.
> This is more like if Ford suggested changing Qxshift* to SelectShift[1].
> It's a clearer name that tells what the thing does, and
> really...nobody's going to miss "Qxshift".
>
>
Keep in mind I am not suggesting changing the name of the whole package.
This is more like if Ford suggested changing Qxshift* to SelectShift[1].
It's a clearer name that tells what the thing does, and
really...nobody's going to miss "Qxshift".
[1]
https://owner.ford.com/how-tos/vehicle-features/
On 2/2/2017 1:03 PM, Andy Peters wrote:
>
>> On Feb 2, 2017, at 10:40 AM, Wayne Stambaugh wrote:
>>
>> I don't have a strong opinion one way or another but you should never
>> underestimate the power of branding. You can take the same car and
>> change the manufacturer and model names and the sa
> On Feb 2, 2017, at 10:40 AM, Wayne Stambaugh wrote:
>
> I don't have a strong opinion one way or another but you should never
> underestimate the power of branding. You can take the same car and
> change the manufacturer and model names and the same person who liked
> the car under one brand
Sounds like a good idea.
On 2/2/2017 12:46 PM, Chris Pavlina wrote:
> I think I am going to seek out some user views on this. As usual it
> doesn't do us much good to speculate about what non-developers want.
>
> I will say that so far two users have told me that the weird names
> confused them a
I think I am going to seek out some user views on this. As usual it
doesn't do us much good to speculate about what non-developers want.
I will say that so far two users have told me that the weird names
confused them as beginners, and only established developers have argued
in favor of keeping th
I don't have a strong opinion one way or another but you should never
underestimate the power of branding. You can take the same car and
change the manufacturer and model names and the same person who liked
the car under one brand name will hate it under another brand name. I
never understood thi
On Thu, Feb 02, 2017 at 11:20:46AM -0600, José Ignacio wrote:
> On Thu, Feb 2, 2017 at 7:56 AM, Chris Pavlina
> wrote:
>
> > I admit I'm getting self-indulgent here, this request is definitely a
> > bit "what Chris would do if made Dictator of KiCad", but... just testing
> > the waters here:
> >
On Thu, Feb 2, 2017 at 7:56 AM, Chris Pavlina
wrote:
> I admit I'm getting self-indulgent here, this request is definitely a
> bit "what Chris would do if made Dictator of KiCad", but... just testing
> the waters here:
>
> What do people think about, for either the 5.0 or 6.0 release, ditching
>
On Thursday 02 February 2017 16:28:27 Clemens Koller wrote:
>
> BTW: Assignment of a footprints seems to me completely odd at this level.
>
I do not agree. Assume a through-hole resistor which can be mounted
horizontally, vertically, on a single-sided board, on a double-sided board,
or a SMD-resi
017 15:28
To: kicad-developers@lists.launchpad.net
Subject: Re: [Kicad-developers] [RFC] Application naming
Hello, Chris!
Eeschema-> Schematic editor
Pcbnew -> Layout editor
Cvpcb -> move it to Library editor or manager
BTW: Assignment of a footprints seems to me completel
At my workplace, we use this workflow as well. Each real "part" is a
symbol as its base, with BOM info in the symbol properties, with a specific
footprint for each part. Out of the four EE's doing schematic/layout here,
we never open CvPCB.
--
Justin Partain
On Thu, Feb 2, 2017 at 10:28 AM, Cl
THANK YOU.
We argue about the bloody footprint workflow _constantly_, I can't
really say I appreciate another attempt to derail a thread by bringing
it back up.
On Thu, Feb 02, 2017 at 09:59:54AM -0600, Adam Wolf wrote:
> Hi folks!
>
> If it isn't too much of an imposition, can we move this disc
Yeah, but you don't need to if they're obvious. If the schematic editor
is called "schematic editor" and you tell a user to edit their
schematic, they'll find the schematic editor. :P
On Thu, Feb 02, 2017 at 04:58:10PM +0100, Nick Østergaard wrote:
> I myself quite like that the apps have unique n
Hi folks!
If it isn't too much of an imposition, can we move this discussion
about footprint and symbol philosophy that we seem to constantly have
going into its own thread, or maybe even off-list?
Thanks!
Adam Wolf
On Thu, Feb 2, 2017 at 9:56 AM, Justin Partain
wrote:
> At my workplace, we us
This is off topic.
Den 02/02/2017 16.56 skrev "Justin Partain" :
> At my workplace, we use this workflow as well. Each real "part" is a
> symbol as its base, with BOM info in the symbol properties, with a specific
> footprint for each part. Out of the four EE's doing schematic/layout here,
> we
I myself quite like that the apps have unique names and notngeneric names
like PCB editor, because it makes it easier when talking about a specific
name rather a description.
Den 02/02/2017 14.56 skrev "Chris Pavlina" :
> I admit I'm getting self-indulgent here, this request is definitely a
> bit
Hi Clemens,
This topic has been discussed many times, it is always controversial.
A part to buy, i.e. named "LTC6362CMS8" comes already with all the information
to be placed in the suitcase - it has exactly one type of footprint (here MSOP-8, JEDEC
MO-187-AA). I don't see any reason to assign
Hello, Chris!
Eeschema-> Schematic editor
Pcbnew -> Layout editor
Cvpcb -> move it to Library editor or manager
BTW: Assignment of a footprints seems to me completely odd at this level.
When I create a part it consist of a partname, schematic symbol, an assigned
footprint, a 3d
Hi Chris,
Maybe "Composant Vers pcb"? Component to pcb.
Related to the other names, I don't mind.
I vote for Bitmap2Component as Import Image in libedit and modeit.
Regards,
Pedro.
El 02/02/17 a las 14:56, Chris Pavlina escribió:
I admit I'm getting self-indulgent here, this request is def
45 matches
Mail list logo
