From: Gary Thomas <gary@mlbassoc.com>
To: webhob@yoctoproject.org
Subject: Re: [Webhob] RFC: Visual design
Date: Fri, 22 Mar 2013 06:52:21 -0600 [thread overview]
Message-ID: <514C5405.1020202@mlbassoc.com> (raw)
In-Reply-To: <CD71F402.2589E%belen.barros.pena@intel.com>
On 2013-03-22 05:41, Barros Pena, Belen wrote:
> I must apologise profusely for not sharing the visual design work that has
> been going on before now. To make amendments, I've posted everything we
> have so far in the wiki:
>
> http://wiki.yoctoproject.org/wiki/Web_UI#Visual_design
I don't see anything in these that cover how to configure a build, etc.
Looking at the milestones (just following the screenshots mentioned),
I see these:
Stage II & III
Scenarios Covered
Create Build
Set up Project
Choose Hardware
Set Preferences
Specify Layer(s)
Specify base image and package(s)
Run Build
Install Web Hob Server
Configure team servers
Select team options and configure
Error Messaging
View error logs
Where are the design screenshots for these items (which I think are much
more important than graphs about task/time usage, etc)?
>
> The final version from the design agency is due today, but please
> understand this does not mean we are all done. It just means we need
> community feedback to move forward. So if you have an opinion about the
> designs, please share it here.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2013-03-22 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 11:41 [Webhob] RFC: Visual design Barros Pena, Belen
2013-03-22 12:52 ` Gary Thomas [this message]
2013-03-25 15:04 ` Barros Pena, Belen
[not found] <514C677C.5060408@mlbassoc.com>
2013-03-22 14:54 ` Barros Pena, Belen
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=514C5405.1020202@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=webhob@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.