X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Message-ID:	<5735ACC6.30105@iee.org>
Date:	Fri, 13 May 2016 11:30:30 +0100
From:	"M. J. Everitt (m DOT j DOT everitt AT iee DOT org) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version:	1.0
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Re: gschem annoyances
References:	<154a7fb8d8c-2a04-17506 AT webprd-a31 DOT mail DOT aol DOT com> <20160513081037 DOT GA23474 AT visitor2 DOT iram DOT es>
In-Reply-To:	<20160513081037.GA23474@visitor2.iram.es>
X-Enigmail-Version:	1.6
OpenPGP:	id=93C22371
X-Provags-ID:	V03:K0:AyI15RNoP9AzFfiKv7dJatqoV/hxQkbc75UfGAH2AD44tBDAL3h
	LE+d0injxSWXRHc4lMMfeZDBw2y0fxkI4iZfjwj5kg3UhGsQmwivlrliZn3h/2cUthZNKGT
	n0hftZgrUZ8mwujfDiEy9NNz+IB6eADYyXK0N5WAKk5da5GoIUghTfdzz7kXXYP5E4udf1M
	XZfDXetfRSMvHZo+Yz2mQ==
X-UI-Out-Filterresults:	notjunk:1;V01:K0:+eDZN0Yu4e8=:ESOfwPsWweFDtNmgla/na0
	WwhuhVOMM2cevh3a9zbc2olNTlYHcxHhqGed8qNdTKiUx/Bh/Zjj+mY0pMrKkDAV7umklvhkF
	OBLMj2YhNxexIGgYcfLBZKHAFt87bke11JRIDjlVAcxywWtbm9ze1bts6YAd6xrvjgSmkVsaJ
	3XDlPMsyt+eWX8RPuDQIRVIQAJfCDpQSEhnxrdIJV/tWQyz980H4b0Cye6KS3HwzSKFoD/Fc9
	9KYKpZJW2oEQ53SOYJ8sjk7u/Ao/oS7I7YEAPL7HwbU05K5MR7L5UV4jymm8b5MVdZ8RLW2YV
	jVNjwFgQRoGv0vHfCZw4HSdpeiOID6/k/7vylJtjq7FZypgNnjJcgwUuVXFt9vCBGbt6aoxlf
	YjwUWDVlZyzUrgpIC1UXVx2MO4yQNa2/R60UKiuEwoXCxss8W5xQaqSL6FgM+ME+STgQTH2g9
	lO20lY+IrK6iy3PEj/dx6Va6SiXeIcMQBe3J/YdAdUTv70qiGaUfMPX3GjUZ39PsppKWkhUTv
	KLROVlDaj1S+IWy1Bf7zQxfju5evj3a2TVyQ4cJ/ZCEr8midp+Qnp76qIzTCAzkhiOyXahIxR
	9o2USDxtn3A+SLWvyX99Q4qlgjqi7yRTYpFeJPyMsz4kfF7k0as3EWvlaRMeEsDYuVIbjKG6w
	ZS2nbgR8lqkqd/1CWDaGxYaov3IgxskfHzI6JinvFaO/ks0QHZySuz9PgB94m4Cjjtrk=
Reply-To:	geda-user AT delorie DOT com

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--26CR8soWKkDTKQQIA3L4W5jaO8VXkhS9s
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 13/05/16 09:10, Gabriel Paubert (paubert AT iram DOT es) [via
geda-user AT delorie DOT com] wrote:
> On Thu, May 12, 2016 at 10:39:21PM -0400, Paul Tan (pt75234 AT aol DOT com) [v=
ia geda-user AT delorie DOT com] wrote:
>> On Thu, 12 May 2016, 09:50:00 +0100, Peter Clifton wrote:
>>> I think the point is correct.... More developers are needed to port g=
schem
>>> to GTK3. I might guess that GTK2 has another 5-10 years of being read=
ily
>>> available though... so I'm not swayed heavily by the argument that we=

>>> imminently need to do it. (Just start thinking about it perhaps).
This is an applaudable aim, but with the current level of input, will
take some considerable time to achieve, and by that point, the next
graphics library will also have become obsolete. So you're always going
to be behind the curve ...
>>
>> On Thu, 12 May 2016, 10:00:43 -0600, John Doty wrote:
>>> A clean ground-up redesign of gschem, using the same file format, but=

>>> with a modern UI, would be welcome. Encumbering the old, quirky, but
>>> productive UI with new features is not.
>> Sounds like a good case to port gEDA to QT5 (instead of GTK3.0).
>> Limited spare time accumulated during 5-10 years may be good=20
>> enough to tempt someone to take up the challenge, including
>> me.
> Well, QT is not usable from C. So you have to rewrite in another langua=
ge,=20
> C++ or some interpreted language, or something that runs in a browser
> now that the OS is the web browser for most people (ducks for cover).
Yeahno, whilst geda-web2.0 may seem like a fun idea .. I can't see a lot
of ChromeOS users being bothered by not having a port of gEDA to use on
their chromebooks! I think it would be time better spent on shoring up
the excellent work people are doing on a stable windows build ...

The argument of switching to C to c++ barely exists .. the languages are
comparable, with the added benefit of more features in C++ than pure C.
I would also suspect there is still active development of the c++
language, so that provides a good future-proof pathway.
>> I came across an interesting posting on Youtube by someone whose=20
>> team had successfully ported their app to QT:
>>   https://www.youtube.com/watch?v=3DON0A1dsQOV0
>>   Gtk to Qt - a strange journey [linux.conf.au 2014]=20
>>  =20
>> I have played around with some of the QT5 demo examples, it looks
>> quite promising to be a good replacement for GTK3.
> Personnally I decided deliberately to use GTK for my own projects a lon=
g
> time ago because I could not stand Qt (and its associated tool, called
> MOC if I remember correctly).
>
>     Gabriel
That's indeed a choice, often coloured by your distro's core apps being
coded in one or the other. I live in the 'Qt' camp because my desktop OS
uses KDE - mostly written in Qt, and for the most part, it works really
well. I do use some Gtk apps, and code one/two using wxWidgets, but the
interface for Gtk seems quite cludgy, not that I've started my pet
project to port said application to Qt yet, but the tools definitely
exist, and are mature now.

</bikeshed>


--26CR8soWKkDTKQQIA3L4W5jaO8VXkhS9s
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJXNazGAAoJEEwwM0+TwiNxu+wP/iytuwrUp1YkOP8C7h4p44uw
/VrRQNfKjsVK5/4Dku0Agzo7nvG8Gu3aF1wOGo1TdKjxfI/pyllAhd+Ug9g9+XzV
i47psOKYMMCFAmdBT/nLDM/soIPU+OLIH9UsMuo4YdcCURzNfRjajLw153/vPeJ2
u/7L7+kyVNt1r1UW6zX5Mq/O9aEdEmrFPKVVLk0I7bl7xvubp7xfCPI2PCGOi78N
Tfhgb03k64ncZ+p3jHOuv0FtmKc/WN3jY1kPDn7RTys55XiFGKXdFTVweHFrBDrW
C2MN4pKFi1aZMfnQrxSThZchjo54jGVayB+EhdX2mSZAzVVJgbcup8I+HSAAnO7G
YELYXO7VtpMGkO61epS7DBLRs00PCg3Zq6fZLOhmSU71Ypg4wwz+BCMHIQw/yb4X
hdMrqTZWaRyGMYfubOTlvGl4hsyA5ATgQcb6De2yWmBK4QQDqgDMGR4QebCltmk8
0RjyUHj2hlIVnXJSSQAp0DzD4KbHa2AiUjdsiWGDIKHjASRMAOOgXMCSAWEWT8Nv
zNjd63HxYLBFYksaYsV0urRhBwllM9Z2REGFR4Mcf1Vz3zmitoYPFNFoj9A3ZstC
KGH+LpwzsuVwlyyiQUm45VuaxrmLC+IQq2lT9hotvRRhOV+45Z0Old0gWiVMCuH0
Wr53WNqEsUzQIXsL7uJs
=S3gP
-----END PGP SIGNATURE-----

--26CR8soWKkDTKQQIA3L4W5jaO8VXkhS9s--

- Raw text -