Re: [dev] rio for linux
> The problem is the complexity of writing a replacement and all the > compatibility layers needed to make it usable in the productive world. The "window to a framebuffer" thing appeals to me because it would be simple, performant, easy to implement, easy to code for, easy to port libs and apps to use it. I don't need partly obscured windows or enforced clipping. Also don't need every bogus app under the sun to work on it right away.
Re: [dev] rio for linux
Greetings. On Thu, 02 May 2013 06:06:33 +0200 Sam Watkins wrote: > Is it unacceptable to dis X11 here? Although we may have to live with it I don’t get how what was said and the topic can be used to come up with such an implication. > and write code for it, X11 is very far from suckless. The problem is the complexity of writing a replacement and all the com‐ patibility layers needed to make it usable in the productive world. Sincerely, Christoph Lohmann
Re: [dev] rio for linux
On Wed, May 01, 2013 at 09:21:32AM +0200, Christoph Lohmann wrote: > For now all the monkeys are jumping on the wayland train. I don't much like the smell of wayland, although it might be simpler / better than X11. Is it unacceptable to dis X11 here? Although we may have to live with it and write code for it, X11 is very far from suckless.
Re: [dev] rio for linux
On Wed, May 01, 2013 at 05:43:30PM +0200, KarlOskar Rik?s wrote: > By replying to his comment you make yourself not just an idiot in his eyes. By mocking me and/or calling me an idiot, without offering any relevant comment on my topic, you disgrace yourself exceedingly in my eyes! but whatever, who cares - it's the internet - everyone is rude and silly Anyway, to clarify, I was interested to make a window system where each window has the same 'api' as the full screen (framebuffer), and the window manager could be run nested in a window like with rio. I am thinking the window api would provide direct access to the video buffer, not a network-transparent drawing language. Would probably not use a virtual filesystem for this, just the mmaped framebuffer device and some paramters to describe the window / viewport. Feel free to reply with customary derision and/or helpful suggestions!
Re: [dev] rio for linux
By replying to his comment you make yourself not just an idiot in his eyes. On May 1, 2013 3:42 PM, "Sam Watkins" wrote: > On Wed, May 01, 2013 at 10:43:06AM +0200, hiro wrote: > > You could try > http://www.omgubuntu.co.uk/2012/03/how-to-easily-skin-ubuntus-unity-desktop/first? > > I'm guessing that you are mocking my idiocy? (in your eyes) > >
Re: [dev] diffdisplays
wtf, 20h.
Re: [dev] rio for linux
On Wed, May 01, 2013 at 10:43:06AM +0200, hiro wrote: > You could try > http://www.omgubuntu.co.uk/2012/03/how-to-easily-skin-ubuntus-unity-desktop/ > first? I'm guessing that you are mocking my idiocy? (in your eyes)
Re: [dev] diffdisplays
On Wed, May 1, 2013 at 1:54 AM, Carlos Torres wrote: > this doesn't have to be in dwm, i don't think it does anyway. fine, if you want to recompile dwm for a function you might want to use with other window managers of similar type. I guess a stand-alone program would do. :) cheers! mar77i
Re: [dev][sic][PATCH]Colors
I forgot to say: when you send a message to channel or user, it prints the message in red. So, you can easily notice when you started a private conversation. Best Regards -- H.Mo.
[dev][sic][PATCH]Colors
Hi, I installed sic and it's a great tiny software. I love it. Here a patch, which includes colors. You can easily tweak colors yourself. Maybe, you don't need colors, but it helps a lot and I wanted to share it. Here the colors: Channel: bold magenta Date: bold cyan JOIN/QUIT/NOTICE messages: bold blue Username: green -- H.Mo. color.patch Description: Binary data
Re: [dev] rio for linux
On 2013-05-01, at 07:30, Sam Watkins wrote: > I don't love X11, and I'm wondering if anyone has ported or made anything > in the sprit of rio / 9wm to run on top of Linux framebuffer. Port drawterm to run on fb rather than x11? Then you can run the actual plan 9 desktop by connecting to a 9vx process or something? Other ideas are to make 9vx's console itself run on fb, or similar for hosted inferno. Somebody probably did one of these already. http://www.google.com/search?q=(plan9+OR+9vx+OR+drawterm+OR+inferno)+linux+framebuffer -Truls
Re: [dev] diffdisplays
In addition to what Carlos said about using damage evens and transparent overlays, you probably want some sort of notification of activity in windows not currently displayed on screen. This is similar to urgency wm hints, but triggered by window content change rather than explicit application requests. One approach is simply to set the urgency hint when change is detected. Note that this is different from indicating what has changed between two points in time as in the image diff suggestion. One way to use this technology is to dim all windows except the focused one, and then change opacity of parts with activity. More in line with the research article would be to only dim windows on non-focused monitors. -Truls
Re: [dev] diffdisplays
Hi 20h,
On 29 April 2013 18:34, Christoph Lohmann <2...@r-36.net> wrote:
> on my news mailbox something interesting appeared [0]. Applying such a
> »display diff« to a dwm tag would be interesting, to only show the new
> difference from the last time it was switched to that tag. Making it a
> common tool you can use to watch certain displays from one state would
> make it more usable everywhere. The gimmick of the webcam would be some
> eye tracker which does not need to be combined with the display diff.
>
> Are here any X11 experts that know how this could be implemented?
You could take a screenshot each time you perform Mod1+{1,...} and
then define another key combination like Ctrl-Shift-Mod1+{1...} to
take another one and then to call feh with some image diff tool to
display the result.
Due to the fact that dwm's keypress() function executes all matching
key combinations, this would be very easy.
Afair there is the compare tool in order to create diffs from screenshots:
compare shot1.png shot2.ong -compose src diff.png
Best regards,
Anselm
Re: [dev] rio for linux
Do I get this right, you want to port a plan9 GUI to linux framebuffer for performance and low security? And then you want a potential X compatibility layer on top of it? And you want to trust your applications more? Do you think they feel bad if you don't trust them enough? You could try http://www.omgubuntu.co.uk/2012/03/how-to-easily-skin-ubuntus-unity-desktop/ first?
Re: [dev] rio for linux
Greetings. On Wed, 01 May 2013 09:21:32 +0200 Sam Watkins wrote: > I don't love X11, and I'm wondering if anyone has ported or made anything > in the sprit of rio / 9wm to run on top of Linux framebuffer. I realise > rio relies on Plan 9 dynamic namespaces and such, but we might be able to > do something similar on Linux. > > Would this be worthwhile, or not? For now all the monkeys are jumping on the wayland train. If the big graphic driver vendors follow this path then it would be worth to ex‐ plore wayland first and look at how this compositor model can be used like a framebuffer. Wayland looks in its current state like a misdesigned wonderland de‐ signed to adapt to frameworks and to make GUI designers (monkeys!) hap‐ py. Sincerely, Christoph Lohmann
