From: Justin moore <silve...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Re: Void Updater conceptual GUI design
Date: Thu, 7 May 2015 19:42:49 -0700 (PDT) [thread overview]
Message-ID: <e1b2f489-d606-430b-899d-1e5ca3081825@googlegroups.com> (raw)
In-Reply-To: <53c6c5a4-5a56-4421-b37c-5faf21eaef98@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1446 bytes --]
<https://lh3.googleusercontent.com/-7DGaLn2SGyo/VUwik_4zMbI/AAAAAAAABNM/2w4a_9UJqMk/s1600/Screenshot-3.png>
<https://lh3.googleusercontent.com/-fFR9cO7n-1Y/VUwipOmw5sI/AAAAAAAABNU/fYg9KsZFX9Y/s1600/Screenshot-4.png>
On Thursday, May 7, 2015 at 9:36:09 PM UTC-5, Justin moore wrote:
>
> Since community is the base of most Linux distributions, I thought I'd
> share some ideas a friend and I have. The main idea is a graphical updater,
> the details however are still up for debate. In the end we want to create
> some sort of daemon that runs in the system tray (like you've probably seen
> in other distributions) and notifies the user when updates for local
> packages are available. Our language of choice is Python and our GUI
> toolkit is Qt5, which we both have limited to no experience with. Last
> night I opened up Qt5 Designer for the first time and started playing with
> different tools and came up with something very simple, yet effective (or
> at least I think so).
>
> I ended up converting the UI file to python code which I have attached to
> this post. If anyone is remotely interested in the idea, let me know if
> you'd possibly be willing to help out. Of course your feedback is valuable
> so please don't hesitate to share your thoughts. At this point there is no
> git repository as there is no real work being done, though when things
> start moving I'll create one.
>
[-- Attachment #1.2: Type: text/html, Size: 2200 bytes --]
prev parent reply other threads:[~2015-05-08 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 2:36 Justin moore
2015-05-08 2:42 ` Justin moore [this message]
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=e1b2f489-d606-430b-899d-1e5ca3081825@googlegroups.com \
--to="silve..."@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).