Re: [Gerbv-devel] user feedback

[Dan M. <da...@mc...>]

yeah, I didn't say they were easy...  I may see if I can tackle some of 
the layer translation though.  Certainly for a drill file it shouldn't 
be too bad.  I guess I'll see though.

Julian wrote:


> Dan,
>     Your list looks good.  Other than the accelerator key changes, most 
> of the others will take some time, sadly....
> 
>     BTW, thanks for your hard work releasing 2.2  And also, thanks for 
> keeping the build documentation readme's up to date...most mortals 
> wouldn't take the time to do that, but it's definitely useful. :)
> 
>     I only have one v2.2 gripe to mention...the benchmark function 
> should probably have been removed as it is now.  The GUI hangs for 2 
> minutes with 100% CPU usage...I would guess 95% of users would think the 
> program just crashed and try to end the process.  If we think it's 
> important for the end user to have this functionality, we need to let 
> the user know what's about to happen via a dialog or start a new thread 
> for the task.
> 
> Cheers--
> 
> On Tue, 2009-01-27 at 18:40 -0500, Dan McMahill wrote:
>> Here are some things which would, I believe, enhance the utility of gerbv.
>>
>>
>> - when something is selected and we ask to show the object properties, 
>> it says the aperture code or tool number but then you have to analyze 
>> the layer and look up what that means.  An automatic lookup would be 
>> most useful.  Also, a hotkey would be great. I'd suggest 'q' for query. 
>>    So for example, you select a round pad, hit 'q' and you right away get
>>
>>
>> 0.032"  in addition to the log that says it was flashed, D48, CIRCLE.
>>
>>
>> - hotkeys (a hot topic over on geda-user right now..) are not displayed 
>> in the menus.  Makes it harder to learn them as you progress from 
>> beginner (drive via menus) to advanced user (drive from hotkeys).  z/Z/f 
>> for example.
>>
>> - hotkeys are different if the Messages tab versus the Layers tab is on 
>> top.  z/Z/f for example dont' work if the Messages tab is selected.
>>
>>
>> - multi segment ruler.  By this I mean click once to start, click 
>> several times to add nodes on your measurement and along the way you get 
>> a total dx, dy, and length along the path.
>>
>> - missing ability to pan/zoom while using the measuremment tool.  Makes 
>> it hard to zoom in for an accurate start point and then zoom out/pan to 
>> the destination.
>>
>> - missing ability to translate a layer.  Useful for those times that a 
>> less than friendly tool translates a fab drawing for you.
>>
>> - gravity for the ruler would be useful.  By this I mean you could get 
>> close to an edge or a centerline and the measurement tool would snap to 
>> that point.  Also the ability to select between only allowing 
>> horizontal/vertical or horizontal/vertical/diagonal or unconstrained 
>> angles for the measurement tool would be helpful.  You may want to be 
>> able to cycle through these modes while putting down nodes in a 
>> multi-segment measurement.  You may also want to be able to enable 
>> gravity on each of the following features: "edge", "centerline", 
>> "endpoint" (the center of a flashed circle or square would be the 
>> endpoint).  I'm picturing a dialog with checkboxes where you pick which 
>> features have gravity.  I'm also thinking maybe you wouldn't see gravity 
>> kick in until you got within some number of pixels of the feature.
>>
>>
>> - Ability to do a blinking xor.  Here I'm thinking you turn on a 
>> soldermask relief layer and a silk screen layer and it starts blinking 
>> where there are overlaps.  Blinking can be nice as your eyes can pick 
>> out almost any blinking even if tiny where a solid color is harder to spot.
>>
>> Despite the length of this list, gerbv has been working pretty darn well 
>> and it is really cool to see how far it has come over the years.
>>
>> -Dan
>>
>>
>>