openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias Seidel <matthias.sei...@hamburg.de>
Subject Re: Homepage
Date Mon, 05 Dec 2016 22:00:30 GMT
I understand your concern...

But the 100k favicon.ico has been there for about 2 years. ;-)

regards, Matthias


Am 05.12.2016 um 22:58 schrieb Marcus:
> Am 12/05/2016 10:41 PM, schrieb Matthias Seidel:
>> the new Google+ design is criticised by a lot of users and is giving me
>> a hard time to adapt all the logos/graphics.
>> It is now similar to the phone/tablet layout...
>>
>> About your thoughts concerning the size of the favicon.ico:
>> I reworked it. It now contains 16x16, 32x32, 48x48 and 64x64. Every
>> browser should be happy with that and the size shrunk to 32k.
>>
>> Can you live with that? ;-)
>
> sure, that's better than 100k.
>
> PS:
> I just want to be sure that you understand my concern:
> We have to make sure that the loading time is not decreased just due
> to some fence stuff. We have to think about pro and contra. The
> webpage is opened thousand of times. The G+ webpage only by much less
> people.
>
> Even when it's just the favicon it is opened by every browser request.
> So, it starts - as always - with the first step. ;-)
>
> Marcus
>
>
>
>> Am 05.12.2016 um 12:29 schrieb Marcus:
>>> Am 12/03/2016 12:18 AM, schrieb Matthias Seidel:
>>>> I did all changes now... It could take some time to be visible.
>>>>
>>>> If you go to:
>>>>
>>>> https://plus.google.com/+openoffice
>>>>
>>>> there is a a link to our homepage underneath the logo. Behind the link
>>>> there is a check mark. If you point the mouse on it it says
>>>> "Verknüpfte
>>>> Website". This is only to ensure that this website really belongs
>>>> to the
>>>> profile.
>>>>
>>>> But wait! It can be, that you see the "new" design from Google+. So it
>>>> may be not visible for you.
>>>> In my eyes the new design is quite ugly and not ready for release. But
>>>> Google thinks it should be default... :-O
>>>>
>>>> Hard to explain, here is a picture (classical Google+):
>>>> https://dl.dropboxusercontent.com/u/48386075/Google%2Bverification.png
>>>
>>> thanks for the screenshot. Than it makes sense. As you thought already
>>> I see a different webpage style.
>>>
>>> Marcus
>>>
>>>
>>>
>>>> Am 02.12.2016 um 23:52 schrieb Marcus:
>>>>> Am 12/02/2016 08:33 PM, schrieb Matthias Seidel:
>>>>>> Am 02.12.2016 um 19:59 schrieb Marcus:
>>>>>>> Am 12/02/2016 06:44 PM, schrieb Matthias Seidel:
>>>>>>>> Am 02.12.2016 um 17:42 schrieb Marcus:
>>>>>>>>> Am 12/02/2016 01:11 PM, schrieb Matthias Seidel:
>>>>>>>>>> Last night I did some changes to our homepage...
;-)
>>>>>>>>>
>>>>>>>>> thanks for your update. I've some questions:
>>>>>>>>>
>>>>>>>>>>      - Renewed the google-site-verification. Now
we have a
>>>>>>>>>> confirmed
>>>>>>>>>> link to
>>>>>>>>>> https://www.openoffice.org on Google+
>>>>>>>>>
>>>>>>>>> What is the reason to exchange the old one? Got it invalid?
>>>>>>>>
>>>>>>>> No, the old one was for http, now the link is for https.
Google
>>>>>>>> needed a
>>>>>>>> new verification code for that.
>>>>>>>> Originally this was done by Rob Weir (?), so I just changed
the
>>>>>>>> string
>>>>>>>> in index.html.
>>>>>>>
>>>>>>> OK, but what is now with HTTP? Isn't it then needed to have 2
>>>>>>> codes?
>>>>>>> Or does the code for HTTPS include HTTP automatically?
>>>>>>
>>>>>> Yes. It is just to verify the quality of the link (See the checkmark
>>>>>> behind the link on Google+)
>>>>>
>>>>> sorry, I'm not familar with G+. Wich checkmark do you mean?
>>>>>
>>>>>>>>>>      - Added favicon.png (Which now seems unnecessary,
but
>>>>>>>>>> doesn't
>>>>>>>>>> hurt
>>>>>>>>>> either)
>>>>>>>>>
>>>>>>>>> There is already one. Please see
>>>>>>>>> ".../branding/images/favicon.ico".
>>>>>>>>> So, please don't put other files into the root directory
except
>>>>>>>>> dirs
>>>>>>>>> and HTML files. It's already enough filled with things
that do
>>>>>>>>> not
>>>>>>>>> belong there. ;-)
>>>>>>>>
>>>>>>>> Nice to have a favicon in a subfolder, when it is not
>>>>>>>> referenced in
>>>>>>>> html. It will never be used! ;-)
>>>>>>>>
>>>>>>>> Browsers look by default in the root for favicon.ico. There
was
>>>>>>>> already
>>>>>>>> one since 2014. It was 100k, the new one is 99k.
>>>>>>>> But we can surely move the favicon.ico and change the link
>>>>>>>> accordingly.
>>>>>>>
>>>>>>> Yes, please.
>>>>>>
>>>>>> OK, I will move it to /branding/images. What to do with the old
>>>>>> unused
>>>>>> icon? Can I rename it?
>>>>>
>>>>> "favicon_16x16.ico" looks like a good name for the backup.
>>>>>
>>>>>> And I will delete favicon.png. Hopefully everything will work
>>>>>> without
>>>>>> it...
>>>>>
>>>>> No risk, no fun ... ;-)
>>>>>
>>>>>>>>>>      - Added a link to favicon.ico and favicon.png
to get a
>>>>>>>>>> thumbnail
>>>>>>>>>> for
>>>>>>>>>> the link to our homepage on YouTube
>>>>>>>>>>      - Increased the size of the orb in favicon.ico,
so it
>>>>>>>>>> looks much
>>>>>>>>>> clearer now.
>>>>>>>>>
>>>>>>>>>      From 1kB to 100kB is IMHO not really an improvement.
>>>>>>>>> Compared with
>>>>>>>>> some Youtube visitors, this will increase the loading
time of
>>>>>>>>> every
>>>>>>>>> webpage request.
>>>>>>>>
>>>>>>>> As I said before, that 1k favicon.ico wasn't used. Who ever
put it
>>>>>>>> there...
>>>>>>>>
>>>>>>>> But I think we can delete favicon.png. That was just a fallback.
>>>>>>>> Eventually Google only needed some time to crawl the webpage.
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Where can I see the icon in the Youtube channel [1]?
When
>>>>>>>>> checking
>>>>>>>>> the
>>>>>>>>> graphic links nothing refers back to get them from our
webpage.
>>>>>>>>
>>>>>>>> There are four links at the right side of the channel graphic.
>>>>>>>> Homepage
>>>>>>>> is the first and had a generic icon until recently.
>>>>>>>>
>>>>>>>> The icons are automatically pulled, when YouTube (Google)
>>>>>>>> checks the
>>>>>>>> link. That did work for Facebook, Twitter and Google+, but
not
>>>>>>>> for our
>>>>>>>> homepage.
>>>>>>>
>>>>>>> So, that means Youtube goes to "www.openoffice.org", looks in
>>>>>>> "index.html" for an favicon entry and if existing take it from
the
>>>>>>> given path?
>>>>>>
>>>>>> Right. Google pulls only the proper resolution.
>>>>>>
>>>>>>>
>>>>>>>> If you can't see the AOO orb in front of the link now, you
may
>>>>>>>> have to
>>>>>>>> empty your browser cache and reload the page.
>>>>>>>
>>>>>>> Sure, I can see it. But I don't see an increase of quality. It's
>>>>>>> the
>>>>>>> same size as on our homepage. So, why is there a new and bigger
>>>>>>> favicon needed?
>>>>>>
>>>>>> Until recently, you couldn't even see the icon...
>>>>>>
>>>>>> It contains graphics for different resolutions like before.
>>>>>> Therefore it
>>>>>> is bigger, but more versatile than a small 16x16 icon.
>>>>>> We live in the times of HiDPI- and Retina-Displays!
>>>>>> And the one I adapted has been there since 2014 (file date). The
>>>>>> size of
>>>>>> the new file is even slightly smaller now.
>>>>>>
>>>>>> Let me clarify, the dimensions are the same, only it uses the
>>>>>> available
>>>>>> space better and looks "bigger".
>>>>>>
>>>>>> I think you can see the difference here:
>>>>>>
>>>>>> old: https://dl.dropboxusercontent.com/u/48386075/favicon_old.png
>>>>>> new: https://dl.dropboxusercontent.com/u/48386075/favicon.png
>>>>>
>>>>> It's indeed looking bigger - or better said it's filling the complete
>>>>> available space.
>>>>>
>>>>> Again, thanks for the updates.
>>>>>
>>>>> Marcus
>>>>>
>>>>>
>>>>>
>>>>>>>>>> BTW, in the near future Google (Chrome) plans to
mark all
>>>>>>>>>> websites
>>>>>>>>>> without https as "unsafe".
>>>>>>>>>> We already have a certificate for our homepage, do
we want to
>>>>>>>>>> make
>>>>>>>>>> https
>>>>>>>>>> as default?
>>>>>>>>>>
>>>>>>>>>> (Some pages have problems
>>>>>>>>>> (https://www.openoffice.org/stats/downloads.html)
so that
>>>>>>>>>> must be
>>>>>>>>>> investigated in advance)
>>>>>>>>>
>>>>>>>>> Hm, I don't see a problem here.
>>>>>>>>
>>>>>>>> I can see the text, but not the graphics, because they are
loaded
>>>>>>>> from
>>>>>>>> an "unsafe place" (Firefox, Chrome and IE block this by default)
>>>>>>>> This is only a problem, if we set https as default. Now the
>>>>>>>> page is
>>>>>>>> loaded with http. You need to use the above link to see it.
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks for taking care.
>>>>>>>>>
>>>>>>>>> [1] https://www.youtube.com/channel/UC5VAaY4mqQVhNe8j7fZCEfw
>>>>>>>>>
>>>>>>>>> Marcus
>>>>>>>>
>>>>>>>> That is just eye candy for our visitors... ;-)
>>>>>>>>
>>>>>>>> regards, Matthias
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Am 01.12.2016 um 19:41 schrieb Marcus:
>>>>>>>>>>> Am 12/01/2016 12:21 AM, schrieb Matthias Seidel:
>>>>>>>>>>>> I did it already,
>>>>>>>>>>>>
>>>>>>>>>>>> Upload via CMS is OK, download works via
SVN.
>>>>>>>>>>>
>>>>>>>>>>> great, thanks. :-)
>>>>>>>>>>>
>>>>>>>>>>> Marcus
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Am 01.12.2016 um 00:02 schrieb Marcus:
>>>>>>>>>>>>> Am 11/30/2016 11:42 PM, schrieb Andrea
Pescetti:
>>>>>>>>>>>>>> Matthias Seidel wrote:
>>>>>>>>>>>>>>> I think the CMS treats it as
a text/html file.
>>>>>>>>>>>>>>> GIMP can not open it when downloaded.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The XCF Marcus uploaded to SVN is
usable.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Download it from here:
>>>>>>>>>>>>>> http://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/images/AOO_logos/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> (use right-click on the file name
to be sure the browser
>>>>>>>>>>>>>> doesn't
>>>>>>>>>>>>>> mess
>>>>>>>>>>>>>> with it)
>>>>>>>>>>>>>
>>>>>>>>>>>>> should I update the file property via
SVN? If so whats the
>>>>>>>>>>>>> SVN
>>>>>>>>>>>>> command
>>>>>>>>>>>>> to use?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> Marcus
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>



Mime
View raw message