All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: yocto@yoctoproject.org
Subject: Re: Web Hob design update
Date: Fri, 22 Jun 2012 15:59:50 +0100	[thread overview]
Message-ID: <4FE48866.5040600@communistcode.co.uk> (raw)
In-Reply-To: <CAG+EMXg1Gu3UbAeD6p7cpVy_cjhez60jTD6uBeLgVobsrE1aJQ@mail.gmail.com>

On 22/06/12 15:16, Jim Kosem wrote:
> Hi,
>
> The update of the WebHob design is up on the wiki
> https://wiki.yoctoproject.org/wiki/Yocto_Web_Hob_Design
>
> There's a PDF of all the screens of the latest version (v.1.9) of the 
> application 
> <https://wiki.yoctoproject.org/wiki/images/0/01/Webhob.1.pdf>, a link 
> to the GitHub <https://github.com/jkosem/Yocto-WebHob-Design> we have 
> setup for the HTML5 prototype development and a screencast of the 
> v.1.8 
> <https://wiki.yoctoproject.org/wiki/images/c/cb/Yocto_webHob.1.9_screencast.0.2.mov> 
> showing our design thinking around WebHob and our vision for how it 
> will work.
>
> As always, feedback is welcome. Thanks.
>
> -- 
> Jim Kosem
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

I like the design screens in the PDF, however it looks like it will be a 
LOT of work! Just one question, how is it intended that this will be 
setup? Will it be a standalone application with included web server 
(twisted-web? I assume it will be python based...).

Are you intending to use Twitter's bootstrap (as that is what the design 
screens resemble)? How about initial implementation, will it be using 
websockets or event driven AJAX? What happens when two people try to 
edit things at the same time? Is there going to be a separate 
database/configuration files or will it be editing config files directly?

I'm not being awkward here, it's just the project I've been working on 
the last 6 months is using some very similar technology and these are 
some of the design decisions I've made (and still attempting to make!), 
so it's more interest and understanding design decisions than anything else.

Regards,

-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--



  reply	other threads:[~2012-06-22 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 14:16 Web Hob design update Jim Kosem
2012-06-22 14:59 ` Jack Mitchell [this message]
     [not found] <2372513.aqW0HuKdxJ@helios>
     [not found] ` <CAG+EMXjrph3Bnxc=62BAZ1PwL4by4J6YdipEtoHutyA31kkKhw@mail.gmail.com>
2012-06-25 11:47   ` Jim Kosem

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=4FE48866.5040600@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=yocto@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.