Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of olemis@gmail.com designates
 209.85.212.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50BA79FC.4010505@wandisco.com>
References: 
 <CAJSKAsijOt3s4SX2kRM925CH1+G-oYafBqBMjRzpXvrZ0z6iHg@mail.gmail.com>
	<CAGMZAuN65PGNQii2zoaT95Rok0Seg3-+_EQohPWgPTNtk99wCg@mail.gmail.com>
	<50B9B90C.2000507@wandisco.com>
	<CAGMZAuNAvcKpxUgp+7UqmjhK9bHangRBmHTB-W60CDp7C0UW7w@mail.gmail.com>
	<50BA79FC.4010505@wandisco.com>
Date: Sun, 2 Dec 2012 18:40:10 -0500
Message-ID: 
 <CAGMZAuOrvo39qu6tS9JqzVweVMs0L=jw51FmFhmtZJn9br533A@mail.gmail.com>
Subject: Re: Browser, HTML and JS support
From: Olemis Lang <olemis@gmail.com>
To: bloodhound-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 12/1/12, Branko =C4=8Cibej <brane@wandisco.com> wrote:
> On 01.12.2012 17:41, Olemis Lang wrote:
>> On 12/1/12, Branko =C4=8Cibej <brane@wandisco.com> wrote:
>>> On 01.12.2012 07:41, Olemis Lang wrote:
>
[...]
>
>> Instead of =C2=ABsupporting non-JS clients=C2=BB maybe it's more accurat=
e to say
>> =C2=ABnot to turn non-JS clients unusable=C2=BB since the idea is not to=
 spend
>> time developing a marvelous non-JS experience . The idea consists in
>> providing quick navigation paths so that such users will be able to
>> perform basic tasks . A na=C3=AFve approach is to design templates and ,
>> before anything else, check they work with nothing else on top . Let's
>> add the rest later.
>
> This is /precisely/ what Peter is worried about: designing UX on top of
> a dumb interface instead of the other way around. You're letting your
> personal experience cloud your thinking.
>

you are right ...

[...]
>
> It's high time this project showed some real progress if you want to
> attract a user base. Hanging an albatross around your neck isn't going
> to help at all.
>

... thus I won't try to influence your decision about non-JS support anymor=
e .

[]
>
>> If we don't design with that goal in mind since the beginning then it
>> will always be a loose end . IMO there are other major obstacles when
>> it comes to analyze what might jeopardize the existence of the project
>> .
>
> I think you should take a hint from Jira, which says:
>
> " Warning: either you have JavaScript disabled or your browser does not
> support JavaScript. To work properly, this page requires JavaScript to
> be enabled."
>
> My best guess at the reason for this is that it's /hard/ to write a
> Javascript-less fallback for a good UI. The 80/20 rule would certainly
> apply.
>

Nonetheless if we are going to see Atlassian as a reference , just
know that I am not fond of their (recent?) decisions to turn
functional software into beautiful but useless tools .

FWIW I hope you'll understand why I second previous comments posted by
Gary and Joachim , and also that this does not mean that I think you
are wrong . Probably we are just looking at the same subject from a
different perspective .

[...]

--=20
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article: