content and media development http://mi.cz
----------------------------------------------------------------- http://www.campware.org -- http://crash.mi.cz -- http://suemi.de
"I told our marketing guys to speak now or forever be silent."
(Aleksandar Brajanoski)
-----------------------------------------------------------------
------------------------------------------
Posted to Phorum via PhorumMail
content and media development http://mi.cz
----------------------------------------------------------------- http://www.campware.org -- http://crash.mi.cz -- http://suemi.de
"I told our marketing guys to speak now or forever be silent."
(Aleksandar Brajanoski)
-----------------------------------------------------------------
------------------------------------------
Posted to Phorum via PhorumMail
This is a multipart message in MIME format.
--=_alternative 001B3663C1256FB2_=
Content-Type: text/plain; charset="us-ascii"
One of my favorite peeves as a web designer would be how, inevitably, on
every project I worked on, I'd always get some truly annoying person
saying 'yeah, but does it work with Lynx?'. Which is the same as hearing
some amateur rock critic say 'yeah, but have you heard their _early_
stuff?'
content and media development http://mi.cz
----------------------------------------------------------------- http://www.campware.org -- http://crash.mi.cz -- http://suemi.de
"I told our marketing guys to speak now or forever be silent."
(Aleksandar Brajanoski)
-----------------------------------------------------------------
One of my favorite peeves as a web designer would be how, inevitably, on every project I worked on, I'd always get some truly annoying person saying 'yeah, but does it work with Lynx?'. Which is the same as hearing some amateur rock critic say 'yeah, but have you heard their _early_ stuff?'
I suppose the only other consideration is it "Accessible" from the
standpoint of WCAG or any of the standards regarding disabled people
needing access...
I really hope nobody would be absurd enough to expect lynx to be able
to function as a control to something this complex.
On Thu, 24 Feb 2005 05:57:25 +0100, Douglas.Arellanes@mdlf.org wrote:
>
> One of my favorite peeves as a web designer would be how, inevitably, on
> every project I worked on, I'd always get some truly annoying person saying
> 'yeah, but does it work with Lynx?'. Which is the same as hearing some
> amateur rock critic say 'yeah, but have you heard their _early_ stuff?'
>
> doug
>
>
>
>
> sava.tatic@mdlf.org
>
> 02/23/2005 04:28 PM
> Please respond to livesupport-dev
>
> To: livesupport-dev@campware.org
> cc:
> Subject: Re: [livesupport-dev] Browser compatibility
>
>
>
>
> We should just invite Opera fans to write a workaround. Shouldn't be too
> difficult, but Sebastian should NOT bother with that.
>
> Sava
>
>
>
> Micz Flor
>
>
> livesupport-dev@campware.org, livesupport-dev@campware.org
> > cc:
>
> Sent by: Subject: Re:
> [livesupport-dev] Browser compatibility
> micz.flor@web.de
>
>
>
> 02/23/05 04:25 PM
>
> Please respond to
>
> livesupport-dev
>
>
>
>
>
>
>
> At 16:21 23.02.2005, sava.tatic@mdlf.org wrote:
>
> >We can do without Opera.
>
> if the rest of the world can, we can, too
>
> no, seriously: it would be nice, but our target browsers should be firefox,
>
> mozilla and IE (if we want it or not).
>
>
> Micz Flor - micz@mi.cz
>
> content and media development http://mi.cz
> -----------------------------------------------------------------
> http://www.campware.org -- http://crash.mi.cz -- http://suemi.de
> "I told our marketing guys to speak now or forever be silent."
> (Aleksandar Brajanoski)
> -----------------------------------------------------------------
>
>
>
>
>
>
>
>
>
------------------------------------------
Posted to Phorum via PhorumMail
Nadine have done a nice work on design of HTML User Interface. Please visit
attched files.
As always, it?s a hard work to get the design suitable for all common
browsers. Nadine tested with firefox, netscape, ie and safari. Just IE on
Mac makes more problems than wanted.
Due to rarity of this browser, I guess we can ignore this at the moment.
This is a multi-part message in MIME format.
--------------090109030503020803050508
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit
I think that adding buttons like the C++ GUI might make the HTML =
interface bulkier than it needs to be, but I agree that the menu looks a =
little out of place. Maybe using similar colors to the C++ GUI and some =
rollovers might help as Charles mentioned. I made a test menu and also =
changed the font to the on/off air buttons to bitstream vera. You can =
see it at http://a.parsons.edu/~sangita/livesupport/navBar/navBar.html. =
Otherwise though, it looks great!
Sangita
----- Original Message -----=20
From: charles truett=20
To: livesupport-dev@campware.org=20
Sent: Friday, March 11, 2005 12:15 AM
Subject: [livesupport-dev] HTML GUI
wow nadine, the HTML looks really good.
just a few thoughts.
should the ON AIR and OFF AIR font be consistent with the rest of the=20
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=20
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=20
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=20
(scheduler_day.html) it might be a good idea.
and how about rollover states for the navbar, navbar dropdown menus =
and=20
buttons? that might be nice.
I think that adding buttons like the C++ GUI might make the =
HTML=20
interface bulkier than it needs to be, but I agree that the menu looks a =
little=20
out of place. Maybe using similar colors to the C++ GUI and some =
rollovers=20
might help as Charles mentioned. I made a test menu and also =
changed the=20
font to the on/off air buttons to bitstream vera. You can see it =
at
href=3D"http://a.parsons.edu/~sangita/livesupport/navBar/navBar.html">htt= p://a.parsons.edu/~sangita/livesupport/navBar/navBar.html. =20
should the ON AIR and OFF AIR font be consistent =
with the=20
rest of the site? it sticks out to me because it's another sans=20
serif.
maybe the navbar items should be aligned so they spread =
all the=20
way across the content - so Campware Home should align to the=20
right with the Now Playing Box.
do you want to use the same =
buttons=20
we're using in the application in the web version? i can =
understand=20
arguments to keep it simpler, no graphics and all. But since we're =
using=20
the tabs from the app (scheduler_day.html) it might be a good=20
idea.
and how about rollover states for the navbar, navbar =
dropdown=20
menus and buttons? that might be nice.
but all in all i =
think it=20
looks super.
thanks a =
lot,
charles
/color>/fontfamily><=
/BODY>
------=_NextPart_000_2B19_01C52646.EB61D270--
------------------------------------------
Posted to Phorum via PhorumMail