Jesús Martínez wrote:
Nested comments:
2007/9/14, DanTMan wrote
It also isn't a very good idea not to reload the sidebar and tabs.
The Toolbox in the sidebar is always dependent on what page you are on.
It will list user contributions if in the user area of an existent area.
Permanent links to a page, etc...
It all could be done with javascript. Not only the content would be
returned with Ajax. Also some javascript code like the code is
injected in all headers. Some of the variables: wgCanonicalNamespace,
wgCanonicalSpecialPageName, wgNamespaceNumber.
Then there's the tabs. Each page has it's own set of tabs. The Special
tab for Special pages always has the same link you are currently on,
each article has the article, talk, and various edit, watch, delete, and
protect tabs. And these all change depending on what access the user
has, what level of protection the page has, and if the user has the page
in their watchlist or not.
wgUserGroups = ["bureaucrat", "sysop", "*", "user", "autoconfirmed",
"emailconfirmed"]; and so on :)
And you're saying we rewrite half the MediaWiki code in JS to set tabs
and toolbox items, using groups without rights info which Wikia could
change at any time. That just doesn't work.
Another issue with removing the page load from happening is with User
scripts. I add a User tabmenu when I'm in a userspace to give me a few
useful tools. As well as a number of other things, some of these are
dependent on what is on the page and therefore will not load right if
the page load is eliminated.
If people is using addOnloadHook() function to load personal stuff,
the load of new content could do a call to addOnloadHook(), or call
other global function so users could adapt its scripts to the
different "concept" of page load.
Ya... then I get a brand new WikiSwitch tab each time addOnloadHook is
called and you fill up users screens because user's scripts are not
designed to have addOnloadHook called multiple times on a page.
And what If I'm not using addOnloadHook? Some people could be using
YUI's load functions, or they may have code which is actually run when
the code is actually being run through. Also remember that user's
methods of loading extra JS or CSS, which is also page dependent can
only be one during the real loading of the page.
Whatever you do, with this idea you'll always require half the users
around to rewrite their scripts, and not all of them know enough JS to
actually do that. Unless you plan on rewriting the way JavaScript works
itself and forcing every browser to change it's code and then force
everyone in the world to update ;)
And the last issue is with site JS... If you remove the page load... You
remove the ability to use Collapsible tables, the Show/Hide NavFrame,
Table Sorting, and the new TabView extension one of the techs nicely put
together from YUI. ^_^ And now... you have 85% of Wikia staring at you
with murderous faces because you broke 90% of their fancy features and
ability to customize their own experience...
Same as last commnet. And it's not the first time Wikia breaks our
fancy features...
<http://www.wikia.com/wiki/Forum:Images_in_%22sortable%22_tables>
<http://www.wikia.com/wiki/Forum:Miniupload_and_image_licensing>
<http://www.wikia.com/wiki/Forum:Myskin_problem>
and more! :)
Ok, it would be a major change, but the idea is great. just an
"extension" of TabView extension
<http://toys.wikia.com/wiki/TabViewTest>
_______________________________________________
Wikia-l mailing list
[email protected]
http://lists.wikia.com/mailman/listinfo/wikia-l
Ya... Wikia has done some things which /some/ users have issues with.
But they've never added features which have broken user's ability to
properly use userscripts.
~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment
Project, and Wiki-Tools.com
_______________________________________________
Wikia-l mailing list
[email protected]
http://lists.wikia.com/mailman/listinfo/wikia-l
