From: Antonio Malcolm <antonio...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Re: Walking The Dog - A New Library Of Useful Openbox Pipe Menus
Date: Sun, 21 Jun 2015 18:32:38 -0700 (PDT) [thread overview]
Message-ID: <ea29a967-ab8f-4e9c-9552-936c9f5b73ce@googlegroups.com> (raw)
In-Reply-To: <44dd7140-5e40-4ee8-addc-0a4bbe751642@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1315 bytes --]
Ok, so, a work-in-progress update, here are some screenshots for the
up-and-coming *Displays* pipe menu, which should be finished, tested, and
released by mid-week.
<https://lh3.googleusercontent.com/-vRFnm-rtK1c/VYdUjuT-H5I/AAAAAAAAAcY/fbGa3Rq0JQw/s1600/corgi-openbox-menu-displays-wip-connections-details.png>
<https://lh3.googleusercontent.com/-e0qBlHY9ujg/VYdUjqL1pqI/AAAAAAAAAcY/voe8JBAJj8U/s1600/corgi-openbox-menu-displays-wip-screens.png>
<https://lh3.googleusercontent.com/-oR7FZaIqy8E/VYdUju8-aFI/AAAAAAAAAcY/-kdvoWEDMqY/s1600/corgi-openbox-menu-displays-wip-devices.png>
<https://lh3.googleusercontent.com/-Cvo-rETe2Sw/VYdUju-qjvI/AAAAAAAAAcY/yyKI3JPxd9w/s1600/corgi-openbox-menu-displays-wip-connections-resolutions.png>
<https://lh3.googleusercontent.com/-0QsAyC7sDz4/VYdUjitre_I/AAAAAAAAAcY/SploCSxto88/s1600/corgi-openbox-menu-displays-wip-connections-move.png>
<https://lh3.googleusercontent.com/-ZgHqt1UIvBw/VYdUjrYAqRI/AAAAAAAAAcY/gI3FMP1PHpE/s1600/corgi-openbox-menu-displays-wip-inactive.png>
<https://lh3.googleusercontent.com/-0QsAyC7sDz4/VYdUjitre_I/AAAAAAAAAcY/SploCSxto88/s1600/corgi-openbox-menu-displays-wip-connections-move.png>
<https://lh3.googleusercontent.com/-e0qBlHY9ujg/VYdUjqL1pqI/AAAAAAAAAcY/voe8JBAJj8U/s1600/corgi-openbox-menu-displays-wip-screens.png>
[-- Attachment #1.2: Type: text/html, Size: 4110 bytes --]
next prev parent reply other threads:[~2015-06-22 1:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 1:03 Antonio Malcolm
2015-06-18 2:17 ` Antonio Malcolm
2015-06-22 1:32 ` Antonio Malcolm [this message]
2015-06-22 7:26 ` JD Robinson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ea29a967-ab8f-4e9c-9552-936c9f5b73ce@googlegroups.com \
--to="antonio..."@gmail.com \
--cc=voidlinux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).