kicad-developers team mailing list archive

[Chris Pavlina <pavlina.chris@xxxxxxxxx>]

On Thu, Jun 16, 2016 at 09:50:21PM +0200, easyw wrote:
> >I mean features we _need_ in GAL
> sorry, I cannot imagine what _you_ consider a need...
> I just noticed that and other people did the same at the forum...

That's why I asked for an "official" list, I wasn't looking for opinions...

> 
> >As for a grid menu...why? You can still change the grid by hotkey or by the
> >menu in the toolbar.
> hotkeys are fine but the menu in the toolbar force you to stop routing to
> modify the grid
> 
> 
> 
> 
> On 16/06/2016 21.30, Chris Pavlina wrote:
> >I mean features we _need_ in GAL, not just things legacy has that GAL doesn't.
> >Some of those things don't need to be in legacy either. I don't see any need
> >for the Global Spread and Place menu in the future - the autorouter is garbage,
> >and we don't dump all the parts in a big pile anymore. What do you still need
> >out of it?
> >
> >As for a grid menu...why? You can still change the grid by hotkey or by the
> >menu in the toolbar. Though if we really want it I suppose I could add it...
> >
> >On Thu, Jun 16, 2016 at 09:26:59PM +0200, easyw wrote:
> >>there are two missing features I noticed:
> >>1) contextual 'Grid Select' menu to change Grid size while routing
> >>2) Global Spread and Place menu
> >>
> >>Maurice
> >>
> >>
> >>On 16/06/2016 03.30, Chris Pavlina wrote:
> >>>Other than a decently efficient fallback backend for systems that can't handle
> >>>OpenGL+GAL, do we have an official list of things we need to be implemented in
> >>>GAL before legacy can be taken out? I really want to keep working on the UI
> >>>cleanup, but having dual canvases is quite the roadblock to doing that
> >>>correctly. So far I've been handling the easy bits (legacy things that can be
> >>>taken out to achieve parity with GAL), but I'd like to contribute some time to
> >>>adding the missing bits to GAL.
> >>>