On Sonntag, 26. Oktober 2008, Peter TB Brett wrote:
> On Sunday 26 October 2008 07:57:06 Werner Hoch wrote:
> > Let's just see, what other users think about that. I'm pushing the
> > changes to the git repo.
>
> A few comments:
>
> 1. Sorry, Werner, the table takes up too much space relative to the
> library tree view in that configuration, making the component library
> pretty unusable on an 800-pixel-high screen (if you want to be able
> to see the schematic as well).
Have you tried to resize the attribute view? If you have 800 pixel high
for the dialog you can still see many items in the component library.
> 2. I notice that you're filtering the list on the
> option 'component-dialog-attributes', and that can take symbolic
> arguments. Just to make my life easier as I rework the config system:
> could you please make it take *only* a list of strings? Perhaps allow
> wildcards, so (component-dialog-attributes '("*")) would have the
> same effect as (component-dialog-attributes '(*)) currently does with
> your special-casing.
The configuration only accepts a list of strings, even if the list in
the special case has only one element '("*") or no element '().
Note that the list is also used to set the sort order of the attributes
in the component dialog.
> See:
> http://www.gtk.org/api/2.6/glib/glib-Glob-style-pattern-matching.html
>
> Doing it with globs also allows me to do "stockid-*" to show the
> stock numbers for all my favourite vendors!
Yup. Then the component-dialog-attributes setting could then look like
(component-dialog-attributes '("description" "device" "stockid-*"))
or
(component-dialog-attributes '("description" "device" "*"))
Where the "*" collects all remaining attributes.
> Alternatively, I'm considering adding PCRE to libgeda's deps after
> 2.6... *waits for massive outcry* ...so you could then go back to
> just specifying a string.
>
> (component-dialog-attributes "(attrib1|attrib1|stockid-.*)")
No. You're loosing the sorting feature of a attribute list.
> 3. Consider whether it would be good to distinguish between
> promotable and non-promotable attributes in some way.
Peter C suggested to set a different style for promotable attributes.
bold, different color, ...
Regards
Werner
_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
