Here's a first stab at the HTML GUI: http://a.parsons.edu/~sangita/summer04/index.html. I'm still not sure what
the contents of the menu should be and I'm also not a javascript whiz, so
its not perfect. The more that I look at Mambo, the more I like the menu.
However, its a mammoth of one at that, and there is quite a bit of code that
accompanies it. If that is something that you all would like then perhaps
Tomas and Sebastian can work on putting something like that together and I
can handle the design.
Charles and I had a meeting today and we're still not completely sure on
what the HTML GUI should encompass. It seems like it might be logical for
me to work with Sebastian and Tomas and design according to what they are
building. Designing the HTML GUI seems quite different than designing the
GUI GUI in that sketching out screens won't really work for the HTML GUI.
What do you all think the most effective and efficient next steps would in
terms of the HTML GUI design?
Regards,
Sangita
------------------------------------------
Posted to Phorum via PhorumMail
should the ON AIR and OFF AIR font be consistent with the rest of the
site? it sticks out to me because it's another sans serif.
maybe the navbar items should be aligned so they spread all the way
across the content - so Campware Home should align to the right
with the Now Playing Box.
do you want to use the same buttons we're using in the application in
the web version? i can understand arguments to keep it simpler,
no graphics and all. But since we're using the tabs from the app
(scheduler_day.html) it might be a good idea.
and how about rollover states for the navbar, navbar dropdown menus and
buttons? that might be nice.