AFAICT, there is *already* a really good candidate for the
download/other.html page:

https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds

The tables in the middle are easy to follow and AFAIK contain all the
required information.

No Javascript needed for the table itself.

Can't the script which was used to create that content be tweaked a
bit to create downloads/other.html?

On 2 September 2013 22:26, Marcus (OOo) <marcus.m...@wtnet.de> wrote:
> Am 09/02/2013 10:33 PM, schrieb Alexandro Colorado:
>
>> On Mon, Sep 2, 2013 at 1:09 PM, Marcus (OOo)<marcus.m...@wtnet.de>  wrote:
>>
>>> Am 09/02/2013 06:51 PM, schrieb Alexandro Colorado:
>>>
>>>   It also looks a bit 'dumb' that we dont have a link to others from the
>>>>
>>>> download page within our no script tag:
>>>>
>>>
>>> Of course it doesn't make sense to refer to a page with JS when JS is
>>> disabled in the broeser. That's why there is no link to the webpage.
>>>
>>
>> downloads, need to provide a download link, that is just common sense.
>> There is another problem with othes.html but not offering ANY link, is no
>> solution.
>
>
> Sure, that's the reason why we are discussing how to ensure this for more
> users than now.
>
> Marcus
>
>
>
>>>   On Mon, Sep 2, 2013 at 11:49 AM, Alexandro Colorado<j...@oooes.org>
>>>>
>>>>   wrote:
>>>>
>>>>   On 9/2/13, Andrea Pescetti<pesce...@apache.org>   wrote:
>>>>>
>>>>>
>>>>>> In the last few weeks we've seen users unable to see the big
>>>>>> "Download"
>>>>>> button in
>>>>>> http://www.openoffice.org/**download/<http://www.openoffice.org/download/>due
>>>>>> to broken (but still
>>>>>> used) browsers that failed to parse the JavaScript correctly. And
>>>>>>
>>>>>> http://www.openoffice.org/**download/other.html<http://www.openoffice.org/download/other.html>cannot
>>>>>> be used as a
>>>>>> fallback due to the same issue.
>>>>>>
>>>>>> The JavaScript in other.html is used only to generate the page
>>>>>> content,
>>>>>> and the result is independent of the user's browser: as Marcus
>>>>>> explained, it is there for convenience in creating the page.
>>>>>>
>>>>>
>>>>> How are we using the<noscript>   tag within others? and which kind of
>>>>> content is it trying to plug?
>>>>>
>>>>>   Would it make sense to do the following?
>>>>>>
>>>>>>
>>>>>> 1) Add an "All Apache OpenOffice downloads" link in the
>>>>>> right-hand-side
>>>>>> column of
>>>>>> http://www.openoffice.org/**download/<http://www.openoffice.org/download/>near
>>>>>> the top: this way, we
>>>>>> ensure that browsers with poor JavaScript support still display the
>>>>>> link.
>>>>>>
>>>>>
>>>>> Problaby the quicker solution, still is just a patch instead of just
>>>>> doing good webdev.
>>>>>
>>>>>   2) Rename other.html to other_js.html
>>>>>>
>>>>>>
>>>>>
>>>>> This is a bad idea, I've seen many alternative clones being
>>>>> unmantained by webmasters.
>>>>>
>>>>>   3) Modify other.html by pasting the actual download table (can be
>>>>>>
>>>>>> retrieved, for example, with Firebug from other_js.html) in its HTML.
>>>>>>
>>>>>> This way we add a manual step (step 3) once per release, but we can be
>>>>>> sure that virtually all users can download OpenOffice in all cases
>>>>>> (working JavaScript, no JavaScript, broken JavaScript).
>>>>>>
>>>>>> Regards,
>>>>>>      Andrea.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to