× Warning! This forum is in archival status. New contributions may not work.
[livesupport-dev] GUI
  • now i understand. but we are missing some information.

    in order for Sangita and i to create the GUI that you need, we need to
    have a list of all of the windows that are going to exist. we are aware
    of only the ones posted

    at http://a.parsons.edu/~livesupport/designs

    the existence and functionality of any other windows besides these is
    unknown to us.

    is there somebody who has this information that can help us with this?

    if we have a complete list of all windows and a description of their
    specific functionality, Sangita and i can make this document. without
    it, we can only guess at how it's supposed to work, and that would be
    of little value.

    for example,
    what happens in the login window? are there passwords? are there
    conditions for people who forget password/ username? are there
    different kinds of logins for different types of users?

    if it is the group's understanding that Sangita and I would be
    designing the functionality and content of all of these windows, then
    there is some major confusion.

    my revised design for the Live Mode should be done in a few hours, with
    all of Robert's revisions included.



    Charles




    On Nov 30, 2004, at 2:38 PM, Akos Maroy wrote:

    > charles truett wrote:
    >> Akos, were you able to do anything with the stuff we sent you already?
    >
    > not really.
    >
    > I understand that the design itself takes more time. thus I figured
    > that first we could do a functional GUI, which might not look nice,
    > but contentwise should be OK. but for that, I'd need the layouts for
    > each window that's going to be in the GUI, starting from the login
    > window. this would enable me to work on it, and later add the nice
    > visuals.
    >
    > without this, I can come up with the layouts myself, but then I'll
    > have to rewrite everything for the final layouts. that's basically
    > double work..
    >
    >
    > Akos
    >
    >

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • 2 Comments sorted by
  • charles truett wrote:
    > now i understand. but we are missing some information.
    >
    > in order for Sangita and i to create the GUI that you need, we need to
    > have a list of all of the windows that are going to exist. we are aware
    > of only the ones posted
    >
    > at http://a.parsons.edu/~livesupport/designs
    >
    > the existence and functionality of any other windows besides these is
    > unknown to us.
    >
    > is there somebody who has this information that can help us with this?

    this is the question I'm trying to find the answer for myself Smile

    I think the keyword here is 'usability'. how would we imagine the GUI
    would be easy to use? with what windows, etc?

    > if we have a complete list of all windows and a description of their
    > specific functionality, Sangita and i can make this document. without
    > it, we can only guess at how it's supposed to work, and that would be of
    > little value.

    I myself don't really feel qualified to design the window layouts (and
    all the windows actually), in terms of ease of use. it's inevitable,
    that a GUI layout design made by people doing the programming will
    reflect the inner logic of the software itself - typically not a good idea.

    I guess we need help from project management side - Micz? Doug? what do
    you think?


    Akos

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • Hi there. I'm new around here.



    Just a thought after looking at the most screenshot (11/20/04?).



    That is a good start. I'll add that a window that contains Hot Buttons (promos / drop-ins / music-beds) would be useful. While it's nice to think automation will handle everything, access to often-used clips like those I just mentioned is helpful -- mostly for a live situation or a "oh **** it's not working" moment. Nice to have something to dump into.



    Anyway... as for logins... definitely should be different users with different permissions. To be able to fix something in the studio as "person in charge of automation-y things" whether in the studio or not is a good thing... but also need to have aspects of the automation's inner-workings off limits to basic live on-air folks or what have you.



    In the LiveMode window, it would be useful to have a zoom-out option so as to be able to see at a glance what's ahead for the next hour or even the entire daypart.



    And there should be a window that allows for importing live audio to record, edit, mix, etc.



    Since none of you know who the heck I am and may not care what I just wrote above... that's cool. I am just very interested in this project now that I've stumbled upon it.

    I produce a national show for public radio and have worked with AudioVault and ScottSystems.



    I hope I can be of help if you think it could be useful.

    I'll be checking in again.

    Todd Witter

    tfwitter@wisc.edu