May 30, 2019
Mike,

Great stuff, I must restart doing some D/GtkD programming!

Debian is, I believe, in release freeze so this release will not be packaged for Debian Sid any time soon. Will it be packaged into Debian Experimental so we can install GtkD 3.9.0 via packages?

gstreamer 1.16.0 is in the same position, released post freeze, packaged into Debian Experimental.


On Wed, 2019-05-29 at 22:30 +0200, Mike Wey via Digitalmars-d-announce wrote:
> GtkD is a D binding and OO wrapper of Gtk+ and is released on the
> LGPL
> license.
> 
> At this point it feels long overdue, but finally there is an GtkD release that is updated for the latest GTK+ libraries.
> 
> And i finally took the time to change the documentation on the
> website
> from candydoc to one generated by Adam's adrdox. https://api.gtkd.org
> 
> Full changelog: https://gtkd.org/changelog.html
> Download: https://gtkd.org/download.html
> 
-- 
Russel.
===========================================
Dr Russel Winder      t: +44 20 7585 2200
41 Buckmaster Road    m: +44 7770 465 077
London SW11 1EN, UK   w: www.russel.org.uk



June 02, 2019
On Wednesday, 29 May 2019 at 22:07:14 UTC, Mike Wey wrote:
> I was already using that

I see you fixed that, but I introduced a regression with my public import thing.

So for a while, I had modules with a single class just go straight to that class

e.g.
https://api.gtkd.org/gdk.Color.html

would just automatically go to here:
https://api.gtkd.org/gdk.Color.Color.html


and I accidentally broke that by making it list public imports as "members" so it bypassed that logic.

Do you feel it is good to go straight to the classes? Or do you see value in having it still list the modules and classes separately?
June 03, 2019
On 02-06-2019 22:19, Adam D. Ruppe wrote:
> On Wednesday, 29 May 2019 at 22:07:14 UTC, Mike Wey wrote:
>> I was already using that
> 
> I see you fixed that, but I introduced a regression with my public import thing.
> 
> So for a while, I had modules with a single class just go straight to that class
> 
> e.g.
> https://api.gtkd.org/gdk.Color.html
> 
> would just automatically go to here:
> https://api.gtkd.org/gdk.Color.Color.html
> 
> 
> and I accidentally broke that by making it list public imports as "members" so it bypassed that logic.
> 
> Do you feel it is good to go straight to the classes? Or do you see value in having it still list the modules and classes separately?

A list of publicly imported modules could be useful, and you would lose that if you go straight to the class.

-- 
Mike Wey
1 2
Next ›   Last »