Re: gEDA-user: git for gedasymbols.org ?
Kai-Martin: How about git for gedasymbols.org? (I'd volunteer to modify the instructions to reflect the change) Yes please, and I'd volunteer to do the conversion. And while we are at it, why not drop the symbols and footprints from the programdistribution and just point the programs to gedasymbols.org or a local copy, there could even be a File-git-pull entry. Regards, /Karl Hammar --- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: git for gedasymbols.org ?
On Thu, Feb 3, 2011 at 11:45 AM, Colin D Bennett co...@gibibit.com wrote: On Thu, 3 Feb 2011 13:51:33 +0100 (CET) k...@aspodata.se (Karl Hammar) wrote: Kai-Martin: How about git for gedasymbols.org? (I'd volunteer to modify the instructions to reflect the change) Yes please, and I'd volunteer to do the conversion. I have to say it would be much more pleasant to use git than CVS. And while we are at it, why not drop the symbols and footprints from the programdistribution and just point the programs to gedasymbols.org or a local copy, there could even be a File-git-pull entry. I'm not sure I support this. I prefer the gEDA distribution to have a core stable set of symbols/footprints that doesn't change unexpectedly. It would be nice to have easy access to a larger set of symbols/footprints, but I think it's important to have a separation between widely-accepted and tested entities versus some new symbol (or especially footprint, where precision is often even more critical) that may have been used only by one person. The biggest usability improvement for me in terms of finding new symbols/footprints would be if the gedasymbols.org web interface had a more organized way of browsing and searching items. All users' footprints should be available under a category-based hierarchy. Some examples of how the hierarchy might be organized: - Switches - Tactile pushbuttons - Switches - Toggle switches - Integrated circuits - DIP - Connectors - Single row pins - Connectors - D-subminiature - LEDs - Surface mount Tagging is better than hierarchy. Regards, Mark markrages@gmail -- Mark Rages, Engineer Midwest Telecine LLC markra...@midwesttelecine.com ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: git for gedasymbols.org ?
I have to agree with Mark. Maintaining a hierarchical organization would be a laborious and thankless job for one poor schmuck. But a tagging scheme puts most of the burden on individual contributors. I think it could actually work. On Thu, Feb 3, 2011 at 11:00 AM, Mark Rages markra...@gmail.com wrote: On Thu, Feb 3, 2011 at 11:45 AM, Colin D Bennett co...@gibibit.com wrote: On Thu, 3 Feb 2011 13:51:33 +0100 (CET) k...@aspodata.se (Karl Hammar) wrote: Kai-Martin: How about git for gedasymbols.org? (I'd volunteer to modify the instructions to reflect the change) Yes please, and I'd volunteer to do the conversion. I have to say it would be much more pleasant to use git than CVS. And while we are at it, why not drop the symbols and footprints from the programdistribution and just point the programs to gedasymbols.org or a local copy, there could even be a File-git-pull entry. I'm not sure I support this. I prefer the gEDA distribution to have a core stable set of symbols/footprints that doesn't change unexpectedly. It would be nice to have easy access to a larger set of symbols/footprints, but I think it's important to have a separation between widely-accepted and tested entities versus some new symbol (or especially footprint, where precision is often even more critical) that may have been used only by one person. The biggest usability improvement for me in terms of finding new symbols/footprints would be if the gedasymbols.org web interface had a more organized way of browsing and searching items. All users' footprints should be available under a category-based hierarchy. Some examples of how the hierarchy might be organized: - Switches - Tactile pushbuttons - Switches - Toggle switches - Integrated circuits - DIP - Connectors - Single row pins - Connectors - D-subminiature - LEDs - Surface mount Tagging is better than hierarchy. Regards, Mark markrages@gmail -- Mark Rages, Engineer Midwest Telecine LLC markra...@midwesttelecine.com ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: git for gedasymbols.org ?
On Thu, 3 Feb 2011 11:32:22 -0700 asom...@gmail.com wrote: I have to agree with Mark. Maintaining a hierarchical organization would be a laborious and thankless job for one poor schmuck. But a tagging scheme puts most of the burden on individual contributors. I think it could actually work. I would imagine that each contributor would have to assign one or more categories to each footprint. How much is it to ask that someone click Pushbutton Switch or LED in a list of categories. Some things might belong to more than one category, and that is where tags make it easier in some ways. If there were a standard set of tags (switch, momentary-switch, toggle-switch, led, smt, through-hole, header, etc.) then a hierarchical browser could be implemented for footprints having appropriate tags. (By mapping certain tags to certain points in the category list/tree.) Tags are more general than categories, but in my experience it is quite difficult to productively browse a database that uses free-form tags. If there were well-thought-out, strictly standardized tags that each contributor applied consistently, then it might work well. Regards, Colin ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
