Hi,
Well, that was kind of what I was referring to. I would however really
like to know how you think version/language/server/os can all be
_independent_ variables,
First of all I don't think that it is desireable to have it in
independent variables, see above. If you have it independently you have
to assemble it. And that is errorprone.
['win', '2.0', '2.0.2',
'localized/de/2.0.2/OOo_2.0.2_Win32Intel_install_de.exe'],
['win', '2.0', '2.0.2 (inkl. JRE 1.5.0.06)',
'localized/de/2.0.2/OOo_2.0.2_Win32Intel_install_de_wJRE.exe'],
Sorry, with independent I didn't mean that one should not keep track of
the available versions for the different versions. I got that issue :)
With independent variables I meant that to the end user they seem
independent. So a dropdown which combines version and language, or os
and language (as you proposed in your e-mail of 2006-03-14) are not a
good idea. If we however keep version static for the end-user (as in
'the latest version') however, there is no problem imho using the german
version array for switching languages.
[...]
since the german script currently is simpler in
the sense that it only supports 3 of them,
3? At what script are you looking guys. It always seems to me that
you're refering to some completely different script than the one
currently in use on the german dl page.
It offers 11 "platforms", it offers ~7 version entries, it has more than
20 mirrors in its list. So what "3" are you refering to?
Here is how I reasoned:
(I) platforms, (II) version, (III) mirrors
adding language would be 4.
Currently the de-script is build to deal with these 3 variables, and we
are about to introduce a 4th, namely language. If we do not change the
script, we should remove one variable, and replace it by language, so
that it stays 3, or we should rewrite it to accommodate for all 4 variables.
and the solutions, correct me
if I'm wrong, you brought up so far were only a kind of work-around,
matching language to version, or language to os. Therefore my suggestion
was to drop the version variable.
No, they were not workarounds at all! It would just be not to use the
arrays for what they are currently used, but to shuffle things around.
Why do you think these are workarounds? Just because I write that the
platform array will then host the languages instead?
I was referring here again to your e-mail of 2006-03-14 in which you
proposed things like win2.0 and win_fr... but...
You've already answered my question in that same e-mail! (I'm sorry I
forgot about it, but that was because I had some problems understanding
it at first)
I would like to give the "ACCORDING TO MURB THE BEST OPTION SO
FAR"-AWARD to the second option, instead of the third option you
proposed in that e-mail. I'll will quote it here (Christian in "the
quest for randomized DL servers", 2006-03-14):
Another solution is to make a per-language version array.
Pros:
Languages cleanly seperated
"platform entries" not obligatory, although one can add specific ones
for languages that are only available on special mirrors
cons:
Needs some minor modification to the script (e.g. make it select the
versions-array depending on the selected language).
currently the versions-array looks like this:
var versions = [
['win', '2.0',
'2.0.2','localized/de/2.0.2/OOo_2.0.2_Win32Intel_install_de.exe'],
['win',
'1.1.5','1.1.5','localized/de/1.1.5/OOo_1.1.5_Win32Intel_install_de.zip'],
['win',
'1.1.0','1.1.0','localized/de/1.1.0/OOo_1.1.0_Win32Intel_install_de.zip'] [more]
that means: For the platform "win" (that is used to define what mirrors
carry what version, see above) there are three versions defined. One
with the ID "2.0", one with ID "1.1.5" and one with ID "1.1.0" - the
next column is the text that is displayed in the control that the user
sees.
We made this two seperate entries so one can load "known-issues pages"
when selecting a given category (we had this for the beta for example).
The next entry is the path where on the mirror the version can be found.
And then in reply to me:
> So you mean creating new arrays, e.g. var versionsNL, var versionsDE,
> var versionsENUS etc? or something like that?
Yes.
And you already found your solution for the server issue.
Kay are you there?
g.,
Maarten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]