From: Jeroen De Dauw [mailto:jeroendedauw@...]
Sent: Tuesday, December 20, 2011 8:29 AM
Subject: Re: [Semediawiki-user] Semantic Forms slow and #info display in
> [SQ] This effect is unfortunately why I'm stuck in the 1.16.x world. Are
> stuck with this? Despite it being theoretically better, it would have
> nice to be able to globally enable / disable this feature.
Many user studies have been done on blocking vs non-blocking loading, and
it's pretty clear non-blocking is preferred. You really think letting a user
wait 2 secs before they see ANYTHING is better then showing them most of the
page after half a sec and only applying the style stuff a second and a half
[SQ] It does matter: When management is trying to decide between foswiki
and mediawiki, and they don't care about all the extras that SMW brings to
the mediawiki side, all they see if a page loaded versus seeing something so
slow that it has to partially render before it completely renders. In that
competition, my SMW work looks better than foswiki, it's slightly slower at
times, but the amount of rich data is something foswiki isn't even close to
achieving (as implemented). But with 1.17, they not only see the partial
rendering, it also takes longer than the 1.16 pages, when things like
complex forms, headertabs, #info, etc. are involved.
Also note that since these resources are cached by your browser, you will
only experience the jumping the first time you look at a page, at which
point you probably do not know what it will look like exactly anyway.
[SQ] My site promotes full cross-referencing and parametric searches, so
looking at the same page only happens in a few cases (like team pages). IE,
Firefox, Chrome, and Safari always show headertabs and complex forms
rendering. Perhaps I'm doing something wrong?
Seriously, if it was bad for users, it would not have been deployed to
[SQ] Wikipedia is a cool site with lots of cross-referenced links and a huge
amount of data. But it seems to me that most of their content pages are
simple compared to some of the SMW form and template based examples many of
us have discussed on this list. I could run with the notion of making my
site simpler, but the engineers in my organization like information at their
fingertips, and dropping down 120 lines into a page from the TOC and then
going back again (or paging up or down) to find the next section is tedious.
Headertabs is a much better solution, in both pages and forms.
Jeroen De Dauw
Don't panic. Don't be evil.