Illogical component editor

Schematic
1

find my opinions summarized in this pic

1688×785 167 KB

2

For the question “Why not edit directly above instead?” the answer is very simple. Remaining controlls (check boxes, radio buttons, etc…) on the right have significant meaning during editing fields. The table on the left is only for showing entire fields.

IMO, this window layout is good enough.

3

Ok

and why did component name turn into a value ?
started of good as a component name as it should be.

4

Because it is unique…?
Every database need a ‘key’, an unique ‘key’. The symbol library is like a database.
Remember that KiCad did not show up yesterday. It evolves already pretty dozen years. On arose, some things were simplified by existed at all. There wasn’t an “army” of volunteers to write code. There wasn’t also a multitude of users, only the students of Mr. Jean-Pierre Charras.

Today KiCad has significant value in EDA world. So some things should be change to trample on the heels those with established position. But people doesn’t like revolutionary changes, so they must be introduced gradually. Eeschema and his library system is on the short list.
These documents (attachments) might be interesting for you: https://lists.launchpad.net/kicad-developers/msg23302.html

1 Like
5

true

understood

but it would not been any extra programming hours to stay with component name instead of value

also you open up the component properties tab/button but you dont get all the properties
there is a “T” button for another set of “text” properties
confusing for the newbie like me

maybe it has historical reasons and as you pointed out it dowsnt matter really once you figure it out.

but that could take some time

also i think that some more extra default fields could be standard just to point users in the right direction
manufacturer, “true value”, rating, tolerance
We have the gimmick field of datasheet, but not any other more normal/useful fields
Did take the time to put datasheet in , but could not put in true value ,?

some fields you could argue makes more sense if everybody have the same fields names for the basic things.

now people make parts that have the component name 10K
not very useful

the software itself can point into a direction where the libraries will get better quality if it becomes more obvious what fields you should use for what.

I think kicad will soon take-over as the #1 freeware tool
it is good enough , but some quirks that are not hard to fix would help

6

@nicholas
Your points are valid.
No point in defending a GUI that’s come to age, as is it’s underlying framework.
Just look at the v5 Roadmap and you’ll see that the developers see this as well:
http://ci.kicad.org/job/kicad-doxygen/ws/Documentation/doxygen/html/v5_road_map.html

It just won’t happen overnight or next week.
1-2 years is probably more on the money.
So look over the shoulders of people like @Andy_P and roll with it for the time being.
Or start to get involved :wink:

2 Likes
7

perfect

i will read up on the road-map soon

as always I am busy working in kicad, thats why i write here, when you work a lot with the tool some things bug you after a while,

thanks for your help and thanks to @keruseykaryu also

8

Everyone here knows exactly what you mean… but that’s probably true for any tool. :relaxed:

9

Yes

but i worked many years in cadence and mentor and it was less bugging
but even them with enormous pay-rolls would fail at some basic things

Kicad have some nice things the big guys do not have (apart from free)
Considering its free it is an amazing achievement

free software will cut a bigger market share as time goes on

its so good now that even if i complain i can work with it.

1 Like
10

You’ve seen @Andy_P post a link to his blog where he put info and stuff for the pro-way of dealing with this, right?

Just to make sure, I link it again as it’s very helpful:
ASP Digital Designs - Kicad Libraries & Scripts

1 Like
11

never seen it

thanks