X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Fri, 13 Jan 2017 17:46:52 +0100 (CET)
X-X-Sender:	igor2 AT igor2priv
To:	"Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
X-Debug:	to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From:	gedau AT igor2 DOT repo DOT hu
Subject:	Re: [geda-user] made with gEDA
In-Reply-To:	<CAJXU7q9SPFrVee5CjdVjvWsyCetrVEb56Y1ocZfy-9_CWLnUhQ@mail.gmail.com>
Message-ID:	<alpine.DEB.2.00.1701131727100.7286@igor2priv>
References:	<39216e8d-00d4-29c9-56e6-8ae22fe81833 AT neurotica DOT com> <CAJXU7q-qtfNiqe-VuYK+k81PR7cTN2XaJWtxXk3uPzjjm5+TgQ AT mail DOT gmail DOT com> <ac6764d4-3c77-baf6-5df8-d3f46c4660c9 AT neurotica DOT com> <CAJXU7q9SPFrVee5CjdVjvWsyCetrVEb56Y1ocZfy-9_CWLnUhQ AT mail DOT gmail DOT com>
User-Agent:	Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version:	1.0
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1416453144-1484326012=:7286
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE



On Fri, 13 Jan 2017, Peter Clifton (petercjclifton AT googlemail DOT com) [via ged=
a-user AT delorie DOT com] wrote:

>
>
>On 13 Jan 2017 3:19 p.m., "Dave McGuire (mcguire AT neurotica DOT com) [via
>geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote:
>
>      > I need to come up with a strategy for upstreaming that..
>      basically, what
>      > I did on my branch isn't super compatible with the newer PCB
>      versions.
>      > It extended the hacky way PCB uses extra layers in an
>      arbitrary order
>      > after the defined ones as silk layers (by adding two optional
>      mask
>      > layers after the silk ones).
>
>=C2=A0 It would be great to get that upstreamed, and maybe even into
>pcb-rnd.
>=C2=A0It looks like there's a huge amount of very good development
>happening
>on that project.=C2=A0 As soon as there's transparency support, I'll be on
>that like white on rice. :)
>
>
>Transparency support where, pcb-rnd?
>
>Not sure when that might happen.. one of Igor's original stated reasons fo=
r
>forking was to rip out the (optional) upstream support for opengl which I
>added.


True. A lot has changed since: pcb-rnd is much more modular than mainline,=
=20
so having an opengl option would not be a compile-time decision. So back=20
then, before I had the multi-HID support, I disabled opengl, but now that=
=20
it would be just yet-another HID that the user can select runtime, it=20
doesn't get in my way any more.

So now that the infra is strong enough for it, the reason we don't=20
have opengl support is simply that noone wants to do it. See=20
http://repo.hu/projects/pcb-rnd/devlog/20160921_gl.html for more details;=
=20
meanwhile I started to work on point 1. for other reasons.

As of the alternatives, long term I want to have an SDL based hid. SDL has=
=20
support for 2d hardware acceleration. I'm not convinced that it would be=20
slower than opengl. (Note: I don't plan to do 3d in the SDL HID).


Regards,

Igor2

--0-1416453144-1484326012=:7286--

- Raw text -