kicad-developers team mailing list archive

["phinitnan_c" <crackerizer@...>]

Manveru,

Thank you for cleaning up my wiki page. I'm quite new to wiki and will update it soon.

It seems that there has been a lot of on going in this matter. The first priority to me now is, how library/module directory are organized. Is there any conclusion on how the directories are organized? Will we still use the old style (Many components per file)? According to khiraly proposal, I thinkthe one component per file style has more advantages, especially for an open source project where the developers live in different places. By using directory structure, the components can be categorized in the tree-style manner. Below is my proposed structure:

library
|
|- category1 (transistor, opamp, etc.)
| |- manufacturer1
| | |- component1
| | |- component2
| |- standard component1
| |- etc.
|- category2

module
|- category1 (pdip, soic, etc.)
| |- package1
| |- package3d1
| |- package2
| |- package3d2
|- category2

--- In kicad-devel@xxxxxxxxxxxxxxx, "phinitnan_c" <crackerizer@...> wrote:
>
> Dear Manveru and all kicad developers,
> 
> I've started a wiki page for this matter at 
> 
> http://kicad.sourceforge.net/wiki/index.php/User:Crackerizer
> 
> Please feel free to edit any part of the page. I also would like to invite all developers to share your idea.
> 
> Thank you.
> 
> --- In kicad-devel@xxxxxxxxxxxxxxx, Manveru <manveru@> wrote:
> >
> > 2009/11/2 Dick Hollenbeck <dick@>
> > 
> > >
> > >
> > > [...]
> > > I would start there. Only then does finalizing a design make most
> > > sense. Otherwise it will end up being a wish list that gets forgotten
> > > in 30 days.
> > >
> > > I don't think we want to make this email list into a "wishlist graveyard".
> > >
> > 
> > 
> > Could we collect these ideas on Wiki?
> > 
> > -- 
> > Manveru
> > jabber: manveru@
> > gg: 1624001
> > http://www.manveru.pl
> >
>