Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
audidude
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
17 ms
·
151.
▲
by
audidude
10y ago
@sandGorgon: Hard to say at this point. My personal opinion is that when it comes to building, shipping, and securing desktop applications, Flatpak is the better design. That is why I put my energy behind that project. I make my bets with c
152.
▲
by
audidude
10y ago
I should mention that this is just a way to simplify how you contribute to GNOME apps (and libraries/services for the adventurous). We are using technologies that were incubated in GNOME to simplify contributing to GNOME. This includes
153.
▲
by
audidude
10y ago
The GNOME project is a great group of people to develop your skill-set with. We can help find you projects to work on and there is pretty much everything you can imagine that needs doing. #newcomers on irc.gnome.org is a great place to star
154.
▲
by
audidude
10y ago
If you have any issues (no doubt we still have bugs) feel free to ping us on irc.gnome.org in #gnome-builder. I'm usually around hacking on things.
155.
▲
by
audidude
10y ago
I use it regularly to hack on GLib, Gtk+, Builder, Shell, Mutter, Sysprof, etc. The primary issue is that for things that are libraries or system services, we don't have a way to install that and run some sort of test suite. We have a
156.
▲
by
audidude
10y ago
The problem at hand is that applications are "single instance" by default. For Builder 3.26 we'll get something in place that starts a dbus-session to separate the built application from your host system. Another option is to
157.
▲
by
audidude
10y ago
The flatpak support is provided as a plugin. So assuming they do the same work and commit to maintaining it upstream, I'll accept it.
158.
▲
by
audidude
10y ago
git clone $project_url flatpak-builder builddir org.gnome.Foo.json
159.
▲
by
audidude
10y ago
It requires Wayland features that are used by GNOME 3.24 (so F26).
160.
▲
by
audidude
10y ago
you've mentioned something i've not heard about without linking to it or providing a name to help me find it myself. so i'm not sure what you'd like from me.
161.
▲
by
audidude
10y ago
Interesting how one person is a common denominator in all those interactions ;)
162.
▲
by
audidude
10y ago
gtk+ certainly does use server-side textures and positioned draws. That is why the documentation is so adamant about using API like create_similar_surface(). Even the pixelcache uses server-side textures when available. This is what Xshm do
163.
▲
by
audidude
10y ago
How would you suggest we fix the core pointer protocol? (It's not an extension)
164.
▲
by
audidude
10y ago
Indeed. Especially since TCP-based X would require that you stall operations if you drop a packet so that draw-ordering is preserved.
165.
▲
by
audidude
10y ago
> GNOME does have a history of starting over from scratch every few years; The GNOME project will be 20 years old in a couple of months. So while it might feel like "every few years", we really don't change direction all t
166.
▲
by
audidude
10y ago
I work on Builder, not Gedit. However, Gedit does get various features as we push them up into Gtk/GtkSourceView. The overview map is one such example. The pixelcache in GtkTextView enabling smooth 60fps scrolling is another.
167.
▲
by
audidude
10y ago
That's precisely why I stated 20 years. Those programs were written before that and largely haven't changed since. If you wan't anti-aliasing in any of those above (gitk/emacs come to mind) you'll be doing client si
168.
▲
by
audidude
10y ago
How have you managed to make an argument about embedding a web browser about GNOME? As it were, GNOME's IDE (which I wrote) uses 0% CPU at idle.
169.
▲
by
audidude
10y ago
> Not to mention network transparency when I need it You realize that no X client draws like this nor has for 20 years right? They all use xshm to upload pixels so this "network transparency" is just buffer copying over the net
170.
▲
by
audidude
10y ago
I already spend most of my day writing an IDE (GNOME Builder) and making it Wayland ready out of the box. However, I am responsive on #gtk+ answering questions to people working on this.
171.
▲
by
audidude
10y ago
It does X11 specific calls unconditionally, so it is not currently possible to run emacs as a native Wayland client.
172.
▲
by
audidude
10y ago
Every sentence here is inaccurate, so you might want to check your sources. 1) (It's GNOME in upper case) 2) gtk+ was not "taken over" by a bunch of GNOME developers. gtk+ always was largely shouldered by the GNOME project. T
173.
▲
by
audidude
10y ago
This decision isn't finished. There will be extensive discussion about it during the followup hackfest in August. But as for shipping -alpha, -beta, etc, it would also look very weird if GNOME shipped -alpha as a dependency.
174.
▲
by
audidude
10y ago
Totally, just wrong value. This thread is already making a bigger deal of it than I expected it to.
175.
▲
by
audidude
10y ago
Generally agree, (and that's what we usually do in GLib). However, for a general purpose DNS user-space implementation I think it would be good to have something that can be used in both scenarios.
176.
▲
by
audidude
10y ago
Sure, but in this case it was signed to unsigned promotion.
177.
▲
by
audidude
10y ago
stream_buffer_init() calls malloc directly, so it's not protected by safe_malloc(). (Unless there is some funky re-define stuff I didn't see). %x takes unsigned int, not a char. (Although I guess you could just rely on promotion h
178.
▲
by
audidude
10y ago
// SECURITY IMPROVEMENTS REQUIRED. VULNERABLE TO INTEGER AND BUFFER OVERFLOWS. well at least it's pretty clear up front. No malloc result checks, invalid format in printfs, probably more. (I don't mean to be disparaging,
179.
▲
by
audidude
10y ago
> No it's not. In case of device only a small bunch of things break. For gtk+ everything breaks without a fix. That's because about every other year they have the equivalent of a major ABI break (and they you target explicitly
180.
▲
by
audidude
10y ago
I was very much pushing for a single version number, but there was some hesitation to it. I'll try again when we discuss it next.
More ›