Greetings.
On Wed, 20 Aug 2014 11:14:43 +0200 Dmitrij D. Czarkoff czark...@gmail.com
wrote:
Greetings!
Sorry for reviving old thread, but what happened to porting surf to
GTK3?
There was a discussion in January 2014, where Christoph Lohmann said:
Are there any arguments against
Greetings!
Sorry for reviving old thread, but what happened to porting surf to
GTK3?
There was a discussion in January 2014, where Christoph Lohmann said:
Are there any arguments against switching to GTK3? Otherwise I will
switch surf to GTK3 using the smootscrolling patch.
surf still
On Tue, 14 Jan 2014 02:40:36 +0100
Fernando C.V. ferk...@gmail.com wrote:
Hi Fernando,
I believe most of the implementation details are up to the compositor,
Wayland is just a protocol.
At least in archlinux, the wayland package has only 2 dependencies:
libffi and expat
Yes, that's true.
On 2014-01-14, at 11:42, FRIGN wrote:
My advice would be to take a look at tinyx[2] and tinyxlib[3], which is
relatively small and fitting the purpose well (dwm runs on it).
Let's see what the future will bring us, but it now is all about making
a decision.
I'd like to mention that you
Hello,
FRIGN wrote:
-1) Compositor's demands:
Not everyone has a full drm-kms-setup. Hell, I don't even use evdev
on my devices (It's more secure when you strip out the Event Interface
from the Kernel).
Can you explain your thinking here on security? Is it just that less
compiled code ==
Dnia 2014-01-14, o godz. 11:42:14
FRIGN d...@frign.de napisał(a):
Yes, that's true. However, you need to stress here that Wayland is
just the protocol implementation for communication between clients and
server and glue-code between clients and EGL-calls.
It doesn't pull in the big libs
On Tue, 14 Jan 2014 09:43:03 -0500
Bobby Powers bobbypow...@gmail.com wrote:
Can you explain your thinking here on security? Is it just that less
compiled code == more secure?
No, it's just my problem with hotplugging input-devices. As my setup
doesn't change (I only have a mouse and
Hi FRIGN,
I tried to respond to most of your points as best I could.
On Tue, 14 Jan 2014 11:42:14 +0100, FRIGN d...@frign.de wrote:
I believe most of the implementation details are up to the compositor,
Wayland is just a protocol.
At least in archlinux, the wayland package has only 2
On Tue, 14 Jan 2014 21:11:20 +
Michael Forney mfor...@mforney.org wrote:
Hey Michael,
thanks for your response!
I'm glad to get some remarks from a real Wayland-expert (I'm far from
that) and be able to have more insight into the topic.
Sure, many compositors will use EGL, but that
On Tue, 14 Jan 2014 20:41:40 +0100, Hadrian WÄgrzynowski hadr...@hawski.com
wrote:
EGL as API is quite lean. There could be small implementation not
depending on Mesa 3D.
Is there another problem with EGL?
EGL is fine, but it implies an implementation of OpenGL, which would be
quite
On Sun, Jan 12, 2014 at 11:39 AM, FRIGN d...@frign.de wrote:
I am still wondering if Wayland really is the way to go, given the fact
it requires a lot of dependencies for basic tasks (*(E)GL, dbus, PAM,
DRI (mostly)) and hogs memory.
I believe most of the implementation details are up to the
Hi
On Sat, Jan 11, 2014 at 09:43:44AM +0100, FRIGN wrote:
On Sat, 11 Jan 2014 01:38:13 +
Michael Forney mfor...@mforney.org wrote:
I'm of the opinion that the compositor and window manager should be
separate projects, which is why I implemented swc as a library. Look at
the number
Well, maybe that GTK3-programs suck? They feel very slow imho and don't fit
well into a world where GTK2 is still the least-painful way to go.
At least on OpenBSD GTK+3 is already required for GTK+2 webkit:
surf is an interface to a world of suck, so keeping up to date with
whatever crappy
On Sat, 11 Jan 2014 01:38:13 +
Michael Forney mfor...@mforney.org wrote:
I'm of the opinion that the compositor and window manager should be
separate projects, which is why I implemented swc as a library. Look at
the number of tiling X11 window managers out there. It doesn't make
sense to
FRIGN said:
Well, maybe that GTK3-programs suck? They feel very slow imho and don't fit
well into a world where GTK2 is still the least-painful way to go.
At least on OpenBSD GTK+3 is already required for GTK+2 webkit:
/usr/ports/www/surf $ make full-run-depends | grep gtk
Greetings.
On Fri, 10 Jan 2014 17:35:18 +0100 Markus Teich markus.te...@stusta.mhn.de
wrote:
Heyho,
are there plans to port surf to gtk3, so it can be used under wayland?
That would be the first argument to support GTK3, if that’s the only way
to make it work under Wayland.
Since surf is
Hello,
Christoph Lohmann wrote:
Are there any arguments against switching to GTK3? Otherwise I will
switch surf to GTK3 using the smootscrolling patch.
GTK3's Windows support is pretty new and not as well tested.
yours in sarcasm,
Bobby
On Fri, 10 Jan 2014 17:35:18 +0100
Christoph Lohmann 2...@r-36.net wrote:
That web crap is al‐
ready pulling in nearly the whole software industry.
Thanks, Christoph; you made my day!
Are there any arguments against switching to GTK3? Otherwise I will
switch surf to GTK3 using the
FRIGN wrote:
Looking at it in relativity to Wayland: Let's be honest; who's already using
Wayland today?
I would like to. I already tested weston and it works fine so far in the sense
of drawing fancy rotating things, simulated smoke and flowers - the usual things
you would expect from a window
On Fri, 10 Jan 2014 18:49:13 +0100
Markus Teich markus.te...@stusta.mhn.de wrote:
If I can, I would like to help. Where is the code hosted? I also found swc[0]
written by the same guy who wrote the st port to wayland. However I feel it is
not really as simple as it claims to be.
The code is
On Fri, 10 Jan 2014 19:19:48 +0100
Markus Teich markus.te...@stusta.mhn.de wrote:
Some random idea:
Have you thought about weston-launch yet? It's a wrapper suid-binary getting
all
necessary resources and forking the real weston afterwards. I think it can be
done in one suid binary dropping
FRIGN wrote:
I'll definitely give you guys an update on my status, but I'm sure there
should be a way to write a simple tiling-wm in less than 5k SLOC.
Some random idea:
Have you thought about weston-launch yet? It's a wrapper suid-binary getting all
necessary resources and forking the real
On Fri, Jan 10, 2014 at 01:09:01AM +0100, Markus Teich wrote:
Markus Teich wrote:
I am confused. Are you talking about NetSurf [0] or surf [1]?
And here are the links I knew I would forget…
[0]: https://www.netsurf-browser.org/
[1]: http://surf.suckless.org/
Ooops! I read netsurf all
Hi,
On Fri, 10 Jan 2014 17:05:17 +0100, FRIGN d...@frign.de wrote:
On Fri, 10 Jan 2014 18:49:13 +0100
Markus Teich markus.te...@stusta.mhn.de wrote:
If I can, I would like to help. Where is the code hosted? I also found
swc[0]
written by the same guy who wrote the st port to wayland.
Heyho,
are there plans to port surf to gtk3, so it can be used under wayland?
--Markus
Hey -
Check the smoothscroll patch[1]. Maybe this is what you want?
[1]: http://surf.suckless.org/patches/smoothscrolling
Bryan
On Thu, Jan 09, 2014 at 03:24:59PM +0100, Markus Teich wrote:
Heyho,
are there plans to port surf to gtk3, so it can be used under
wayland?
--Markus
It's a bit on the side of the topic but GTK+ is now hard
dependent through pango on harfbuzz, a c++ component (object
oriented cluster
Sylvain BERTRAND wrote:
It's a bit on the side of the topic but GTK+ is now hard dependent through
pango on harfbuzz, a c++ component (object oriented cluster f), which
pulls a dependency on c++ compiler/runtime.
WebKitGTK is also written in C++ so we need a C++ compiler and runtime
Bryan Bennett wrote:
Check the smoothscroll patch[1]. Maybe this is what you want?
[1]: http://surf.suckless.org/patches/smoothscrolling
Thank you. I would have never found this by just looking for gtk3. I'll try it
soon.
--Markus
Markus Teich wrote:
I am confused. Are you talking about NetSurf [0] or surf [1]?
And here are the links I knew I would forget…
[0]: https://www.netsurf-browser.org/
[1]: http://surf.suckless.org/
30 matches
Mail list logo
