kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #15207
Re: Library Editor naming consistency
On 10/14/2014 4:54 PM, Mark Roszko wrote:
>> The manual uses component throughout and indeed Component name in the UI
>> Component properties dialog. All the screenshots show Component too.
>> If eeschema has changed these, they should be changed back
>
> An manual should never define the software, it should explain the
> software. Or else we'll never have new features or evolutions in
> feature sets.
> As it stands right now, the pcbnew manual is now out of date because
> modules have been completely renamed to footprints in the last few
> days.
>
> I wish the manuals were plain text based, I would be more than happy
> to update documentation as I change things. I do it all the time with
> the Linux kernel patches I upstream where its a requirement ;)
There is actually work on that taking place this right now. Hopefully
we will have a list of viable alternatives in the not too distant future
and an overview of the advantages and disadvantages of each format so we
can make a informed decision. I'm leaning towards one of the markdown
formats myself. However, before any decision is make, I will solicit
the input of the development team.
>
> Schematic Library Editor does seem like the most neutral(i.e. it
> doesn't pick parts, component or symbol to call it) that the thread
> seems to be leaning to.
>
Follow ups
References