Community
Participate
Working Groups
New Oxygen splash screen as replacement of the Neon splash screen (bug 475499)
Created attachment 264538 [details] Oxygen splash screen (BMP format) Oxygen splash screen proposal
If you could get rid of bubbles directly around letters, it would be better IMHO.
What's the usual process for splashscreens? Could we adopt this first iteration right now in Platform and keep the bug open for future improvements?
Created attachment 264545 [details] Without bubbles around logo and letters (In reply to Andrey Loskutov from comment #2) > If you could get rid of bubbles directly around letters, it would be better > IMHO. See attachment
Created attachment 264546 [details] SVG source file (created with Inkscape)
(In reply to Holger Voormann from comment #4) > Created attachment 264545 [details] > Without bubbles around logo and letters > > (In reply to Andrey Loskutov from comment #2) > > If you could get rid of bubbles directly around letters, it would be better > > IMHO. > > See attachment Yes, I like it better :-) This is a cool splash screen, all what is missing now, that the bubbles are slowly moving up with some cool "blup blup" sound during startup :-) P.S. A bit less noise around letters would be even better, but animation is *the* key to make me happy.
(In reply to Mickael Istria from comment #3) > What's the usual process for splashscreens? Could we adopt this first > iteration right now in Platform and keep the bug open for future > improvements? There's work in the plug-in involved to make sure the additional/dynamic info shows correctly. So, we should at least have a splash screen which is close to what we want.
(In reply to Andrey Loskutov from comment #6) > A bit less noise around letters would be even better +1
(In reply to Mickael Istria from comment #3) > What's the usual process for splashscreens? Could we adopt this first > iteration right now in Platform and keep the bug open for future > improvements? There is no "official" process. For Mars and Neon I opened a bug and worked with the community and our contract designer at Eclipse. Then we worked from the splash concept to create the rest of the marketing around the release. Neon Splash bug 475499 Neon webpage: http://www.eclipse.org/neon/ Thank you for creating that Holger, it's a cool concept, the same one I had in mind actually! I just find it very dark.
Created attachment 264963 [details] Oxygen splash screen (BMP format): bigger bubbles and brighter background (In reply to Dani Megert from comment #8) > (In reply to Andrey Loskutov from comment #6) > > A bit less noise around letters would be even better > > +1 (In reply to Roxanne Joncas from comment #9) > I just find it very dark. Feedback welcome.
Created attachment 264965 [details] SVG source file (created with Inkscape)
Created attachment 264978 [details] Fewer bubbles? While I was waiting for my browser to render the SVG, I noticed that it looked better to me with fewer bubbles. The attachment is only for illustration purpose as I have no means of controlling which bubbles are drawn first.
Created attachment 265134 [details] Oxygen splash screen (BMP format): (fewer) bigger bubbles and brighter background (In reply to Jay Arthanareeswaran from comment #12) > Fewer bubbles? > Fewer bubbles.
Created attachment 265135 [details] SVG source file (created with Inkscape)
Created attachment 265136 [details] Oxygen splash screen (BMP format): (fewer) bigger bubbles and brighter background
(In reply to Holger Voormann from comment #14) > Created attachment 265135 [details] > SVG source file (created with Inkscape) That one looks nice! (In reply to Holger Voormann from comment #15) > Created attachment 265136 [details] > Oxygen splash screen (BMP format): (fewer) bigger bubbles and brighter > background That one seems to have a black bottom, which doesn't look great.
Created attachment 265266 [details] Oxygen splash screen (BMP format): fewer bigger bubbles, brighter background and less dark bottom (In reply to Dani Megert from comment #16) There should be no difference in color between the BMP and the SVG image. Anyhow, here is one with less dark bottom.
Created attachment 265267 [details] SVG source file (created with Inkscape)
(In reply to Holger Voormann from comment #17) > Created attachment 265266 [details] > Oxygen splash screen (BMP format): fewer bigger bubbles, brighter background > and less dark bottom > > (In reply to Dani Megert from comment #16) > There should be no difference in color between the BMP and the SVG image. > Anyhow, here is one with less dark bottom. Still looks different than the SVG which I like better. Screenshot to come...
Created attachment 265268 [details] SVG - BMP Maybe it's a rendering issue in Firefox, but they look different and there's still a black bottom.
Created attachment 265270 [details] Proposed splash screen with white/black border (In reply to Dani Megert from comment #20) Your attached screenshot (attachment 265268 [details]) does not show a splash screen. In front of a white background the bottom of the splash screen looks darker than in front of a black background. This effect is increased by viewing the splash screen in a browser where the area bellow the image is white in contrast to the area above the image. It is a trade-off between dynamic range and optimization of a white (bottom) background (see attachment: latest proposed splash screen with white/black border; the darkest pixel of the splash screen is #0a0819).
Created attachment 265271 [details] SVG - BMP
(In reply to Dani Megert from comment #22) > Created attachment 265271 [details] > SVG - BMP In Firefox the SVG layer that shades the bottom will not be shown. Do you prefer the splash screen without bottom shading or something between the Firefox SVG and the BMP splash screen? Note, a progress bar and white(!?) text will be displayed at the bottom of the splash screen.
(In reply to Holger Voormann from comment #23) > (In reply to Dani Megert from comment #22) > > Created attachment 265271 [details] > > SVG - BMP > > In Firefox the SVG layer that shades the bottom will not be shown. Do you > prefer the splash screen without bottom shading or something between the > Firefox SVG and the BMP splash screen? Note, a progress bar and white(!?) > text will be displayed at the bottom of the splash screen. I definitely prefer to go with the SVG version and then tweak for the progress bar if necessary.
Created attachment 265283 [details] Oxygen splash screen (BMP format): fewer bigger bubbles, brighter background and minimal bottom shading (In reply to Dani Megert from comment #24) Splash screen with minimal bottom shading which is required for the white text overlay.
(In reply to Holger Voormann from comment #25) > Created attachment 265283 [details] > Oxygen splash screen (BMP format): fewer bigger bubbles, brighter background > and minimal bottom shading > > (In reply to Dani Megert from comment #24) > Splash screen with minimal bottom shading which is required for the white > text overlay. I like it.
Created attachment 265448 [details] SVG source file (created with Inkscape)
Created attachment 265736 [details] Oxygen Concepts Not sure if you're still looking for ideas and suggestions for the Eclipse Oxygen splash screen, but here are a couple of concepts we wanted to share with the community! Taking a slightly different approach.
@Kat: I like them a lot. My favorite would be #2.
Nice job. The #2 and the #1 are my favorites (in respective order).
#1 than #2 would be my preference.
(In reply to Katharine Hirsch from comment #28) > Created attachment 265736 [details] > Oxygen Concepts I'm not a big fan of visually splitting the word Oxygen into two, especially since gen by itself is a word. I still like the one from comment 25 best.
By the way, shouldn't splash screens try to say "Eclipse IDE" rather than just "Eclipse" ?
(In reply to Katharine Hirsch from comment #28) What are the meanings of the symbols (spirals, pyramids) shown in #4? For which text is the "Lorem ipsum" placeholder in #1 and #4? What is about Oxygen.1, Oxygen.2, etc.? Where to put the ".1", ".2", etc.? So far the splash screen had 452 x 302 pixels. Should the size and aspect ratio be changed to 856 x 638 pixels? (In reply to Mickael Istria from comment #33) Currently, the org.eclipse.platform splash screen is used by the Eclipse SDK, by the Eclipse Platform and by the EPP packages (in contrast to the about dialog, where there are different images for different EPP packages). Therefore, I would prefer "[logo] eclipse oxygen" only.
(In reply to Holger Voormann from comment #34) > (In reply to Katharine Hirsch from comment #28) > > What are the meanings of the symbols (spirals, pyramids) shown in #4? > > For which text is the "Lorem ipsum" placeholder in #1 and #4? > > What is about Oxygen.1, Oxygen.2, etc.? Where to put the ".1", ".2", etc.? > > So far the splash screen had 452 x 302 pixels. Should the size and aspect > ratio be changed to 856 x 638 pixels? > > > (In reply to Mickael Istria from comment #33) > > Currently, the org.eclipse.platform splash screen is used by the Eclipse > SDK, by the Eclipse Platform and by the EPP packages (in contrast to the > about dialog, where there are different images for different EPP packages). > Therefore, I would prefer "[logo] eclipse oxygen" only. @Holger In option #4 - the symbols were supposed to visualize wind, air, and mountains. Perhaps too much of a stretch, but done in an attempt at a different approach to conceptualization Oxygen in an image. The "Lorem Ipsum" is being removed. Doesn't serve a purpose, left in accidentally.
(In reply to Mickael Istria from comment #33) > By the way, shouldn't splash screens try to say "Eclipse IDE" rather than > just "Eclipse" ? Forwarded this question to Wayne Beaton.
Created attachment 265750 [details] Oxygen Concepts v2 Given the feedback provided, the attached v2 file has the "Lorem ipsum" text removed, and v3 has "Oxygen" written out all on one-line, instead of broken down into "oxy" and "gen".
(In reply to Mickael Istria from comment #33) > By the way, shouldn't splash screens try to say "Eclipse IDE" rather than > just "Eclipse" ? Yes. Please.
(In reply to Mickael Istria from comment #33) > By the way, shouldn't splash screens try to say "Eclipse IDE" rather than > just "Eclipse" ? I would also like to consider that we stop using the Eclipse Foundation logo for the Eclipse IDE, and invest in creating an IDE logo. Is that something that you can investigate, Kat?
(In reply to Katharine Hirsch from comment #37) > Given the feedback provided, the attached v2 file has the "Lorem ipsum" text > removed, and v3 has "Oxygen" written out all on one-line, instead of broken > down into "oxy" and "gen". Better. I don't like the vertical white line.
(In reply to Wayne Beaton from comment #39) > (In reply to Mickael Istria from comment #33) > > By the way, shouldn't splash screens try to say "Eclipse IDE" rather than > > just "Eclipse" ? > > I would also like to consider that we stop using the Eclipse Foundation logo > for the Eclipse IDE, and invest in creating an IDE logo. I'm -1 for that. The Eclipse logo is a brand that we want to use and show, also for the IDE. Unless of course, the new IDE icon looks similar.
Created attachment 265752 [details] Oxygen Concept (no line) @Dani Line removed, as per your feedback.
(In reply to Katharine Hirsch from comment #42) > Created attachment 265752 [details] > Oxygen Concept (no line) > > @Dani Line removed, as per your feedback. Even better :-)
(In reply to Wayne Beaton from comment #39) > (In reply to Mickael Istria from comment #33) > > By the way, shouldn't splash screens try to say "Eclipse IDE" rather than > > just "Eclipse" ? > > I would also like to consider that we stop using the Eclipse Foundation logo > for the Eclipse IDE, and invest in creating an IDE logo. > > Is that something that you can investigate, Kat? a) Product-specific splash screen also for non-IDE applications The default application of the Eclipse SDK, Eclipse Platform and the simultaneous release packages is an IDE (org.eclipse.ui.ide.workbench), but e. g. the standalone help which is included in all these products is a non-IDE application. Technically, the splash screen is specified by the product and not by the application: the command line argument "-application <id>" does not change the splash screen. Usually, a product contains also non-IDE applications but all applications of a product show the same splash screen by default. b) Please keep the Eclipse logo for what it represents for most The trademark "Eclipse" and the Eclipse logo were introduced for the Eclipse Platform (http://eclipse.org/org/pr.html). For most people "Eclipse" is the (Java) IDE used in computer programming: https://en.wikipedia.org/wiki/Eclipse_(software) If the Eclipse Foundation needs to have their own logo then it would be easier and for most people less confusing to create a new logo for the Eclipse Foundation. c) Consistency and branding In my view, name/title and icon/logo should be the same everywhere: in the executable file, in the application window and in the splash screen. Because Eclipse is "for anything and nothing in particular" and e. g. Eclipse for PHP Developers can be extended/transformed to e. g. a Java or to a C/C++ IDE only "Eclipse" (without a suffix) fits for all. I would prefer one strong brand name/logo instead of many.
(In reply to Katharine Hirsch from comment #42) > Created attachment 265752 [details] > Oxygen Concept (no line) > > @Dani Line removed, as per your feedback. Great work Kat. I like the bubble theme a lot! The first design "feels" a bit empty, maybe a "zoomed in" version with bigger bubbles could work. Second design is also nice with the background, but having the Oxygen circle below the Eclipse logo looks a bit odd to me. (In reply to Holger Voormann from comment #34) > What is about Oxygen.1, Oxygen.2, etc.? Where to put the ".1", ".2", etc.? I have the same question. Would it be sufficient to have a bigger circle that leaves room for .1, .2, .3?
As we already know the date of the Oxygen simultaneous release (June 28th, 2017), can we have the splash screen mention the release date as discussed in bug 484765 ?
(In reply to Mickael Istria from comment #46) > As we already know the date of the Oxygen simultaneous release (June 28th, > 2017), can we have the splash screen mention the release date as discussed > in bug 484765 ? -1. We don't want to create 3 (or maybe 10 in the future) splash screens for one release stream. Everyone can enable to show the build id, which maps to the date.
(In reply to Dani Megert from comment #47) > -1. We don't want to create 3 (or maybe 10 in the future) splash screens for > one release stream. Everyone can enable to show the build id, which maps to > the date. Don't we already have different splash screens for different versions? IIRC, the 2 last streams do have one splash for each maintenance release (bug 472209 and others) so what I'm suggesting here isn't a big change to the current state. Moreover, as we know the release dates in advance, it would be possible to create all splashscreen at once. At the moment, we're not doing continuous delivery of the IDE, so I have the impression doing this statically on splashscreen is the simplest and more elegant solution (in term of presentation to users as we don't use a technical buildId but can use an actual human friendly date, and as doing it together with the splash allows to propose a consistent design with the splash in term of color and fonts without effort from developers). Note that if you think it's an issue for the Eclipse SDK, we could have the Eclipse SDK using a non-dated splash, and EPP using dated ones.
(In reply to Mickael Istria from comment #48) > (In reply to Dani Megert from comment #47) > > -1. We don't want to create 3 (or maybe 10 in the future) splash screens for > > one release stream. Everyone can enable to show the build id, which maps to > > the date. > > Don't we already have different splash screens for different versions? IIRC, > the 2 last streams do have one splash for each maintenance release (bug > 472209 and others) Ah, yep. But I'm still -1 to add this to the image. It should be configurable like the build ID. Ideally, even the release name should be configurable to avoid 3 (or more) splash screens.
(In reply to Dani Megert from comment #49) > But I'm still -1 to add this to the image. It should be configurable like > the build ID. Ideally, even the release name should be configurable to avoid > 3 (or more) splash screens. That's indeed the ideal solution, but it will take years before it gets implemented ;) The benefit of my proposal is that if it gets agreement, it can be solved before Oxygen gets actually resolved and without effort from the Platform contributors as the splash screen is "outsourced".
(In reply to Mickael Istria from comment #50) > (In reply to Dani Megert from comment #49) > > But I'm still -1 to add this to the image. It should be configurable like > > the build ID. Ideally, even the release name should be configurable to avoid > > 3 (or more) splash screens. > > That's indeed the ideal solution, but it will take years before it gets > implemented ;) > The benefit of my proposal is that if it gets agreement, it can be solved > before Oxygen gets actually resolved and without effort from the Platform > contributors as the splash screen is "outsourced". It's not that easy. LTS might ship another release past the last official one. It would be a pity if the date in their splash screen would be wrong or they have to create a new one. My take: if someone cares about the date (I do not!) then he can fix this bug as suggested in comment 49 or wait, as you indicated, for years. Still -1 for this!
(In reply to Dani Megert from comment #51) > My take: if someone cares about the date (I do not!) then he can fix this > bug as suggested in comment 49 or wait, as you indicated, for years. Still > -1 for this! Users unaware of whether their IDE is current or not is a real issue (see bug 484765 and bug 493490). Editing and exporting an svg from times to times to change a date isn't a difficult task. Implementing comment #49 and Markus' feedback on https://git.eclipse.org/r/#/c/70045/ is a much more difficult. Pragmatically, if we want to help our users soon, just having dated splash screens is a good solution, and contrarely to what you think, it doesn't introduce a bug maintenance overhead for LTS provided the splash is available as SVG -and it is- and can be tweaked and re-exported on demand. Your veto is from Platform perspective right? So despite it, we could have the actual IDEs from EPP provided this useful info to users, right?
(In reply to Mickael Istria from comment #52) > Your veto is from Platform perspective right? Yes.
Let's forget the discussion about the dates. Is it ok to move to having "Eclipse IDE" on the splash screen? If so, can we see a proposal soon?
(In reply to Mickael Istria from comment #54) > Let's forget the discussion about the dates. Is it ok to move to having > "Eclipse IDE" on the splash screen? If so, can we see a proposal soon? -1. The splash screen is in the Platform where anyone can use it, whether it's a calculator or an IDE.
(In reply to Dani Megert from comment #55) > -1. The splash screen is in the Platform where anyone can use it, whether > it's a calculator or an IDE. Just curious here, are you aware of a real use case of non-IDE RCP apps using the Eclipse splashscreen?
(In reply to Mickael Istria from comment #56) > (In reply to Dani Megert from comment #55) > > -1. The splash screen is in the Platform where anyone can use it, whether > > it's a calculator or an IDE. > > Just curious here, are you aware of a real use case of non-IDE RCP apps > using the Eclipse splashscreen? That's irrelevant. The Platform is IDE agnostic and this will not change.
(In reply to Dani Megert from comment #57) > That's irrelevant. The Platform is IDE agnostic and this will not change. The current splash screen is not IDE agnostic. It mentions Neon and Oxygen which are downstream efforts of the Platform, and which are extensively used to brand the IDE release. Overall, the change to add "IDE" doesn't change the current state of things.
(In reply to Mickael Istria from comment #58) > (In reply to Dani Megert from comment #57) > > That's irrelevant. The Platform is IDE agnostic and this will not change. > > The current splash screen is not IDE agnostic. It mentions Neon and Oxygen > which are downstream efforts of the Platform, and which are extensively used > to brand the IDE release. Yes "used". That does not mean I can build a non-IDE app on top of the Platform and use the Oxygen splash screen. You can suggest to add it to the EPP splash screen, but for the Platform it's a no go.
(In reply to Dani Megert from comment #59) > Yes "used". That does not mean I can build a non-IDE app on top of the > Platform and use the Oxygen splash screen. Yes, but it wouldn't make sense; and similarly, building a non-IDE app on and `Eclispe IDE` splashscreen wouldn't make sense neither. It's not worth. > You can suggest to add it to the EPP splash screen, but for the Platform > it's a no go. I suggested and try that, but I did hit bug 510460 (which at first sight could be an issue related to product to product inclusion)
(In reply to Mickael Istria from comment #54) > Let's forget the discussion about the dates. > One last note: Besides the possibilities to manually change the splash screen and configure the build ID there is a third possibility: with the following simple Ant task (which I wrote some years ago) text can be automatically written on a splash screen: https://sourceforge.net/projects/helpaddons/files/DrawString-Ant-Task-1.0.0.zip/download
(In reply to Holger Voormann from comment #61) > One last note: Besides the possibilities to manually change the splash > screen and configure the build ID there is a third possibility: with the > following simple Ant task (which I wrote some years ago) text can be > automatically written on a splash screen: > https://sourceforge.net/projects/helpaddons/files/DrawString-Ant-Task-1.0.0. > zip/download Another approach to let splash screen be tweaked by Platform developers would be to have it an SVG and to tweak the splash handler to render SVGs as well as BMP. As SVG are XML files, they can easily be tweaked by developers to edit some text. However, at this point, the issue isn't technical; it's mostly that Dani will veto any change to the Platform splash. So if we want the IDE to be able to show more data than platform does, we need to fix bug 510460 first.
Can we move this bug forward? I vote for Oxygen Concept (no line) but the other options are also fine for me.
(In reply to Lars Vogel from comment #63) > Can we move this bug forward? > > I vote for Oxygen Concept (no line) Let's go with that.
(In reply to Lars Vogel from comment #63) > Can we move this bug forward? > > I vote for Oxygen Concept (no line) but the other options are also fine for > me. There are two option attached in that file. The one with bubbles, and the one with the underwater imagery. Please specify and I will get the design file in the required format needed. Thank you! Kat
@Kat: by the way, in order to fix bug 484765, can you please also provide together with the final splash a version that shows the release date (month/year should be enough)?
(In reply to Mickael Istria from comment #66) > @Kat: by the way, in order to fix bug 484765, can you please also provide > together with the final splash a version that shows the release date > (month/year should be enough)? Certainly - will get that put together today!
(In reply to Katharine Hirsch from comment #65) > There are two option attached in that file. > > The one with bubbles, and the one with the underwater imagery. Please > specify and I will get the design file in the required format needed. The first one makes it easier to place the build ID and progress.
Is there any chance of at least slightly updated program icons, maybe by just tuning the colors to be a bit similar to those in the splash screen? (BTW I really like the proposals) The splash screen is only visible for few seconds, but the icon is visible all day long, so having a refreshed icon would probably make the yearly upgrade experience way more impressive :-)
(In reply to Till Brychcy from comment #69) > Is there any chance of at least slightly updated program icons, maybe by > just tuning the colors to be a bit similar to those in the splash screen? > (BTW I really like the proposals) > > The splash screen is only visible for few seconds, but the icon is visible > all day long, so having a refreshed icon would probably make the yearly > upgrade experience way more impressive :-) New bug report please.
(In reply to Dani Megert from comment #70) > New bug report please. Done, Bug 514427 I've put it into Platform/Releng like this one, I hope that's OK.
(In reply to Till Brychcy from comment #71) > (In reply to Dani Megert from comment #70) > > New bug report please. > > Done, Bug 514427 > I've put it into Platform/Releng like this one, I hope that's OK. Thanks, that's perfect!
(In reply to Dani Megert from comment #68) > (In reply to Katharine Hirsch from comment #65) > > There are two option attached in that file. > > > > The one with bubbles, and the one with the underwater imagery. Please > > specify and I will get the design file in the required format needed. > > The first one makes it easier to place the build ID and progress. +1
(In reply to Dani Megert from comment #68) > (In reply to Katharine Hirsch from comment #65) > > There are two option attached in that file. > > > > The one with bubbles, and the one with the underwater imagery. Please > > specify and I will get the design file in the required format needed. > > The first one makes it easier to place the build ID and progress. +1 Will upload shortly.
Oxygen Concept (no line) bubbles - so the first one comes with a current flat design by keeping the Eclipse Logo
Created attachment 267553 [details] Oxygen Splash Screen FINAL Dear all, The attached ZIP file contains the following: - Final .ai Oxygen splash screen - Final .ai Oxygen splash screen (with month/year) - Both versions in .bmp - Both versions in .svg - Both versions in .pdf - Version without date in .psd I will add the file for the splash screen with the month/year to Bug 484765 for completeness. I am working on the matching program/application icon today, and will respond to Bug 514427 accordingly. If I missed anything, please let me know. Kat
(In reply to Katharine Hirsch from comment #76) To promote Eclipse Oxygen, it would be nice if the graphic would be usable without any restriction: Can the graphic be copied, modified and distributed even for commercial purposes, all without asking permission and without attribution (CC0)? How will the graphic look for Oxygen.1, Oxygen.2 and Oxygen.3? Is the BMP intentionally about twice as wide and high as the present splash screen and previous splash screens?
(In reply to Holger Voormann from comment #77) > (In reply to Katharine Hirsch from comment #76) > > To promote Eclipse Oxygen, it would be nice if the graphic would be usable > without any restriction: Can the graphic be copied, modified and distributed > even for commercial purposes, all without asking permission and without > attribution (CC0)? The graphic is contributed via bugzilla so it will come under the EPL. This means anyone can use it under the terms of the EPL. However, Eclipse Oxygen is also a trademark so the usage of the graphic must respect our trademark guidelines, meaning it can only be used in the context of discussing/promoting Oxygen.
(In reply to Holger Voormann from comment #77) > (In reply to Katharine Hirsch from comment #76) > > To promote Eclipse Oxygen, it would be nice if the graphic would be usable > without any restriction: Can the graphic be copied, modified and distributed > even for commercial purposes, all without asking permission and without > attribution (CC0)? > > How will the graphic look for Oxygen.1, Oxygen.2 and Oxygen.3? The release name will get a .1, .2, etc. Nothing else. > Is the BMP intentionally about twice as wide and high as the present splash > screen and previous splash screens? That would be strange.
(In reply to Ian Skerrett from comment #78) Is it allowed to use the graphic to create an animations and share it on YouTube (e. g. like I did for Neon.3: https://youtu.be/qRLUXxU_VvE )? Is it allowed to use the graphic in an article about Eclipse Oxygen as an eye-catcher (e. g. instead of the header image in an article like the following: https://heise.de/-3663652 )?
(In reply to Katharine Hirsch from comment #76) > Created attachment 267553 [details] > Oxygen Splash Screen FINAL > > Dear all, > > The attached ZIP file contains the following: > > - Final .ai Oxygen splash screen > - Final .ai Oxygen splash screen (with month/year) > - Both versions in .bmp > - Both versions in .svg > - Both versions in .pdf > - Version without date in .psd > > I will add the file for the splash screen with the month/year to Bug 484765 > for completeness. > > I am working on the matching program/application icon today, and will > respond to Bug 514427 accordingly. > > If I missed anything, please let me know. > > Kat Hi, I am trying to use this splash screen. In this regard I have some requests 1. Can you please provide me this as a gimp xcf format. This is the format we are using to create splash screens. I am able to convert psd format to XCF format so XCF format should be good enough 2. Currently in the PSD file I am not able to modify test for Month Year and Oxygen. These I need to modify for every service release. I would prefer these as editable text layers (I use gimp). I tried using inkspace for ai format I found the text is stored as paths. This makes adding .1, .2 for service releases quite difficult. Thanks Sravan
(In reply to Holger Voormann from comment #80) > (In reply to Ian Skerrett from comment #78) > Is it allowed to use the graphic to create an animations and share it on > YouTube (e. g. like I did for Neon.3: https://youtu.be/qRLUXxU_VvE )? Is it > allowed to use the graphic in an article about Eclipse Oxygen as an > eye-catcher (e. g. instead of the header image in an article like the > following: https://heise.de/-3663652 )? Yes to both. Thank you for doing both these things for Neon. It would be great to have you help promote Oxygen.
Hi, can we get new splash screens where the the text for Oxygen, month/year stored as test. this will make easier to edit the name when we need to change the name for service releases Thanks Sravan
(In reply to Sravan Kumar Lakkimsetti from comment #83) > Hi, > > can we get new splash screens where the the text for Oxygen, month/year > stored as test. this will make easier to edit the name when we need to > change the name for service releases > > Thanks > Sravan Ping! We need this.
(In reply to Dani Megert from comment #84) > (In reply to Sravan Kumar Lakkimsetti from comment #83) > > Hi, > > > > can we get new splash screens where the the text for Oxygen, month/year > > stored as test. this will make easier to edit the name when we need to > > change the name for service releases > > > > Thanks > > Sravan > > Ping! We need this. I apologize for the delay. Dani, Sravan, I'm not sure I understand what you mean by .test? .text? Our designer indicated that the .psd and .ai. are in writeable layer formats, I'm not sure why you ran into problems there. There isn't an easy way to get the splash screen into xcf gimp friendly format without recreating it from scratch. So please bear with me as we try to find you a timely solution. Thank you, Kat
(In reply to Katharine Hirsch from comment #85) > (In reply to Dani Megert from comment #84) > > (In reply to Sravan Kumar Lakkimsetti from comment #83) > > > Hi, > > > > > > can we get new splash screens where the the text for Oxygen, month/year > > > stored as test. this will make easier to edit the name when we need to > > > change the name for service releases > > > > > > Thanks > > > Sravan > > > > Ping! We need this. > > I apologize for the delay. > > Dani, Sravan, I'm not sure I understand what you mean by .test? .text? > > Our designer indicated that the .psd and .ai. are in writeable layer > formats, I'm not sure why you ran into problems there. > > There isn't an easy way to get the splash screen into xcf gimp friendly > format without recreating it from scratch. So please bear with me as we try > to find you a timely solution. > > Thank you, > > Kat Hi, The requirement here is that I should be able to modify month and year and release name for each of the service releases. Currently these are drawn as line paths. With this it will be difficult to modify. If these are created as text layers I can modify them when there is a need like service release. I can work with psd files and convert to xcf. So if the project is provided as psd file I can work with it. In summary here are the requirements 1. psd file is good for us. We work with gimp. gimp can handle psd files 2. Need two separate layers containing the work oxygen and June 2017 as text. (the provided psd file does not contain these as separate layers and the ai file contains them as line paths) Thanks Sravan
The .bmp splashscreen is twice as big as our previous ones. Is it fine to use such as big ones in Platform and EPP or should we re-export it to legacy size?
(In reply to Mickael Istria from comment #87) > The .bmp splashscreen is twice as big as our previous ones. Is it fine to > use such as big ones in Platform and EPP or should we re-export it to legacy > size? The sizes should not be changed.
Created attachment 267890 [details] Oxygen Splash Screen FINAL - Writable Formats Let's try this again. I am providing the following... File Formats: - .xcf version (for GIMP) - .bmp version - .svg version - .ai version - .psd version - .pdf version This includes both versions (with and without the date). You just have to show/hide the layers. The month and year can be modified. I've also included the font file and type. Sizes: - Both .bmp are provided in 856 x 638 px, which is the same as what we provided last year. BUT the resolution was defined as 150 so we lowered it to 72. Might solve your sizing issue. @MickaelIstria If I missed anything, or you still need additional changes please let me know asap. Kat
Thank you for the effort. There is still one issue left. for every service release we add .1, .2 etc. so the release name will become oxygen.1, oxygen.2 etc. For this I would need a editable layer for release name(currently oxygen ) as well.
(In reply to Sravan Kumar Lakkimsetti from comment #90) > Thank you for the effort. There is still one issue left. for every service > release we add .1, .2 etc. so the release name will become oxygen.1, > oxygen.2 etc. For this I would need a editable layer for release > name(currently oxygen ) as well. My pleasure. Unfortunately my designer is away on vacation until April 28. I will try to get this for you in a few days upon his return. Thanks for your patience. Kat
Created attachment 268098 [details] Oxygen Text - Writeable Formats @Sravan sorry for the delay. Please take a look at the attached files and let me know if these work for you. The "oxygen" text should be editable in the new version. Hope that resolves the problem. Have I missed anything else? Cheers, Kat
(In reply to Katharine Hirsch from comment #92) > Created attachment 268098 [details] > Oxygen Text - Writeable Formats > > @Sravan sorry for the delay. > > Please take a look at the attached files and let me know if these work for > you. > The "oxygen" text should be editable in the new version. > > Hope that resolves the problem. Have I missed anything else? > > Cheers, > > Kat Thank you for the effort. Unfortunately there is still a problem. the release name will be branded as Oxygen for june release Oxygen.1 for service release 1 Oxygen.2 for service release 2 etc. Another problem I have is this layer is not available in xcf format which we use. Can you please create this layer in xcf format file and send us? Thanks
New Gerrit change created: https://git.eclipse.org/r/96166
New Gerrit change created: https://git.eclipse.org/r/96173
Created attachment 268119 [details] Oxygen Text - Writeable Formats v2 @Sravan, try this. Please download the zip file. The files your team will need are in the "Export Folder". The date is written in Neris Thin and the word OXYGEN is written in Gotham Bold. Kat
(In reply to Katharine Hirsch from comment #96) > Created attachment 268119 [details] > Oxygen Text - Writeable Formats v2 > > @Sravan, try this. > > Please download the zip file. The files your team will need are in the > "Export Folder". > > The date is written in Neris Thin and the word OXYGEN is written in Gotham > Bold. > > Kat Thanks Kat. This is perfect. I am able to modify these without any trouble. Thanks for the effort. -Sravan
Gerrit change https://git.eclipse.org/r/96173 was merged to [master]. Commit: http://git.eclipse.org/c/epp/org.eclipse.epp.packages.git/commit/?id=c235ffc5d9aac8d7d969225708a3c5c8e7ac812f
(In reply to Sravan Kumar Lakkimsetti from comment #97) > (In reply to Katharine Hirsch from comment #96) > > Created attachment 268119 [details] > > Oxygen Text - Writeable Formats v2 > > > > @Sravan, try this. > > > > Please download the zip file. The files your team will need are in the > > "Export Folder". > > > > The date is written in Neris Thin and the word OXYGEN is written in Gotham > > Bold. > > > > Kat > > Thanks Kat. This is perfect. I am able to modify these without any trouble. > Thanks for the effort. > > -Sravan Happy to hear that! If you need anything else please let me know. :)
(In reply to Katharine Hirsch from comment #96) > Created attachment 268119 [details] > Oxygen Text - Writeable Formats v2 > > @Sravan, try this. > > Please download the zip file. The files your team will need are in the > "Export Folder". > > The date is written in Neris Thin and the word OXYGEN is written in Gotham > Bold. Kat, do we have CQs for those fonts or some other approval from the IP team that it is OK to use those fonts?
(In reply to Dani Megert from comment #100) > (In reply to Katharine Hirsch from comment #96) > > Created attachment 268119 [details] > > Oxygen Text - Writeable Formats v2 > > > > @Sravan, try this. > > > > Please download the zip file. The files your team will need are in the > > "Export Folder". > > > > The date is written in Neris Thin and the word OXYGEN is written in Gotham > > Bold. > > Kat, do we have CQs for those fonts or some other approval from the IP team > that it is OK to use those fonts? Dani, I am certain Kat has not done any CQs. This is something the Platform team would need to do.
(In reply to Ian Skerrett from comment #101) > (In reply to Dani Megert from comment #100) > > (In reply to Katharine Hirsch from comment #96) > > > Created attachment 268119 [details] > > > Oxygen Text - Writeable Formats v2 > > > > > > @Sravan, try this. > > > > > > Please download the zip file. The files your team will need are in the > > > "Export Folder". > > > > > > The date is written in Neris Thin and the word OXYGEN is written in Gotham > > > Bold. > > > > Kat, do we have CQs for those fonts or some other approval from the IP team > > that it is OK to use those fonts? > > Dani, I am certain Kat has not done any CQs. This is something the Platform > team would need to do. Assuming that the neutraface font included is this one https://houseind.com/hi/neutraface . The license for it https://houseind.com/license/ is clearly commercial so I think this is a no-go.
(In reply to Alexander Kurtakov from comment #102) > > Assuming that the neutraface font included is this one > https://houseind.com/hi/neutraface . > The license for it https://houseind.com/license/ is clearly commercial so I > think this is a no-go. Kat, can you please ask the graphic designer for a link to the font that he used and paste the link on this bug. Thanks
Here's are the links to the fonts used in the splash screen, which include details on the licensing agreements. https://www.typography.com/fonts/gotham/overview/ http://www.1001fonts.com/neris-font.html#license Kat
(In reply to Katharine Hirsch from comment #104) > Here's are the links to the fonts used in the splash screen, which include > details on the licensing agreements. > > https://www.typography.com/fonts/gotham/overview/ > http://www.1001fonts.com/neris-font.html#license > > Kat Do we really need those fonts? We were good without them the last 10 years.
(In reply to Katharine Hirsch from comment #104) > Here's are the links to the fonts used in the splash screen, which include > details on the licensing agreements. > > https://www.typography.com/fonts/gotham/overview/ > http://www.1001fonts.com/neris-font.html#license > > Kat So this is different font from the one in your last attachment? What is going on? The fact that redistribution is not allowed clearly puts in the gray zone aka unsafe for usage.
Folks: The license applicable to use of the Neris font [1] will not work for the Splash Screen. Please let me know if you require the other link to be investigated. Thanks, Sharon
(In reply to Sharon Corbett from comment #107) > Folks: The license applicable to use of the Neris font [1] will not work > for the Splash Screen. > > Please let me know if you require the other link to be investigated. > > Thanks, > Sharon Kat, can we get splash screen created with FOSS font? There are plenty of such to choose.
(In reply to Sharon Corbett from comment #107) > Folks: The license applicable to use of the Neris font [1] will not work > for the Splash Screen. > > Please let me know if you require the other link to be investigated. > > Thanks, > Sharon For completeness, the license terms do not work because of Clause #2. 2. It is FORBIDDEN to: modify, sell, or share the font files. As the Splash Screen is part of the Eclipse distribution, those terms are not compatible. Regards, Sharon
(In reply to Alexander Kurtakov from comment #108) > Kat, can we get splash screen created with FOSS font? There are plenty of > such to choose. Again, do we really need those fonts? We were good without them the last 10 years. Why was the well working scheme changed? Even with FOSS we would have to file a CQ in order to use it. Please provide a splash screen like in the past where we did not require fonts.
(In reply to Dani Megert from comment #110) > (In reply to Alexander Kurtakov from comment #108) > > Kat, can we get splash screen created with FOSS font? There are plenty of > > such to choose. > > Again, do we really need those fonts? We were good without them the last 10 > years. No we don't. It was a mistake and we will get it fixed.
Created attachment 268190 [details] Oxygen Text - Writeable Formats v3 (Roboto Font) - FINAL All, - The Neris font has been removed. Apologies, this was an oversight. - The Gotham font was used last year in the Eclipse Neon splash screen. That said, we have removed it from the Oxygen Splash Screen. - The IP Team / Sharon Corbett confirmed that we can use the google font "Roboto" in the Oxygen design. - Roboto details: https://fonts.google.com/specimen/Roboto, it is Apache 2.0 licensed - Please see attached for the revised splash screen design files. - The same changes have applied to the Landing Page design in Bug 514544: https://bugs.eclipse.org/bugs/show_bug.cgi?id=514544 - To be clear, the Eclipse logo font at no point changed in the design process (in case that was ever in question). @Sravan, I asked the designers to make sure the fonts are editable in GIMP on your end. Please let me know if there are any outstanding issues to resolve. Kat
Created attachment 268194 [details] Oxygen Text - Writeable Formats v3 (Roboto Font) - FINAL Noticed a minor issue in the previous zip. Try this one instead please. Thanks, Kat
(In reply to Katharine Hirsch from comment #112) > - The IP Team / Sharon Corbett confirmed that we can use the google font > "Roboto" in the Oxygen design. > - Roboto details: https://fonts.google.com/specimen/Roboto, it is Apache 2.0 > licensed Sharon, do we/I need to file a CQ in order to use it?
(In reply to Dani Megert from comment #114) > (In reply to Katharine Hirsch from comment #112) > > - The IP Team / Sharon Corbett confirmed that we can use the google font > > "Roboto" in the Oxygen design. > > - Roboto details: https://fonts.google.com/specimen/Roboto, it is Apache 2.0 > > licensed > > Sharon, do we/I need to file a CQ in order to use it? Hi Dani: Thanks for asking. Yes, for the Splash Screen, we should track the use of the Google Roboto Fonts. You should be able to Piggyback off CQ 9938. Cheers, Sharon
(In reply to Sharon Corbett from comment #115) > Hi Dani: Thanks for asking. Yes, for the Splash Screen, we should track > the use of the Google Roboto Fonts. You should be able to Piggyback off CQ > 9938. > > Cheers, > Sharon Sravan, please file a PB CQ.
The content of attachment 268190 [details] has been deleted for the following reason: User request
(In reply to Dani Megert from comment #116) > (In reply to Sharon Corbett from comment #115) > > Hi Dani: Thanks for asking. Yes, for the Splash Screen, we should track > > the use of the Google Roboto Fonts. You should be able to Piggyback off CQ > > 9938. > > > > Cheers, > > Sharon > > Sravan, please file a PB CQ. Hi Dani, Since I am not a committer on eclipse.platform project I will not be able to raise a cq for this. Shall I raise it on releng project? Thanks Sravan
(In reply to Sravan Kumar Lakkimsetti from comment #118) > > Sravan, please file a PB CQ. > > Hi Dani, > > Since I am not a committer on eclipse.platform project I will not be able to > raise a cq for this. > > Shall I raise it on releng project? No. Ive raised https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13456 Sharon, can you approve asap? Thanks!
(In reply to Eclipse Genie from comment #98) > Gerrit change https://git.eclipse.org/r/96173 was merged to [master]. > Commit: > http://git.eclipse.org/c/epp/org.eclipse.epp.packages.git/commit/?id=c235ffc5d9aac8d7d969225708a3c5c8e7ac812f > This is using a splash screen based on a commercial font and must be changed to use the new one, but before, EPP must file a CQ since it redistributes the font with the BMP.
(In reply to Dani Megert from comment #120) > This is using a splash screen based on a commercial font and must be changed > to use the new one Thanks for the reminder. > but before, EPP must file a CQ since it redistributes > the font with the BMP. Are you sure it is necessary for the BMP? The font is used but not shipped nor required for the BMP to work. Isn't the CQ necessary only for the SVG (which IIRC may embed the font)?
(In reply to Mickael Istria from comment #121) > > but before, EPP must file a CQ since it redistributes > > the font with the BMP. > > Are you sure it is necessary for the BMP? The font is used but not shipped > nor required for the BMP to work. Isn't the CQ necessary only for the SVG > (which IIRC may embed the font)? IAMNAL. See comment 115.
Gerrit change https://git.eclipse.org/r/96166 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.git/commit/?id=876b3108f7c745eaee65efe0e3a2d44bfa8ac8fc
For "us" this is fixed. I think EPP should track their splash screen in a separate bug report.
The new splash screen is available here http://git.eclipse.org/c/platform/eclipse.platform.git/plain/platform/org.eclipse.platform/splash.bmp.
New Gerrit change created: https://git.eclipse.org/r/96660
Verified in eclipse-SDK-I20170509-2000-win32-x86_64.
Verified in I20170509-2000 on windows x64 with platform product and linux 64-bit with SDK product
Gerrit change https://git.eclipse.org/r/96660 was merged to [master]. Commit: http://git.eclipse.org/c/epp/org.eclipse.epp.packages.git/commit/?id=0c084400d3e479a6ea5f774abf6ec103a25410fa
Thanks for putting on the release year on the splash screen. I recently visited a customer who was still using a 6 year old Eclipse release (3.7). The customer was not aware that 3.7 is already that old and updated to 4.6 after learning that. I hope that having the release date on the splash screen will motivate more people to upgrade.
About dialog branding also needs update. See Bug 516464.
(In reply to Lars Vogel from comment #131) > About dialog branding also needs update. See Bug 516464. Good catch!
For continued discussions about the hardcoded English "JUNE" and about proper alignments, see bug 516462.
Created attachment 268774 [details] Oxygen Pixelated Hello all, It was brought to my attention that this is the splash screen that loads when users open Eclipse Oxygen Release Candidate 2. It seems to have been uploaded in low quality and is pixelated (especially "June 2017"). Kat
(In reply to Katharine Hirsch from comment #134) > Created attachment 268774 [details] > Oxygen Pixelated > > Hello all, > > It was brought to my attention that this is the splash screen that loads > when users open Eclipse Oxygen Release Candidate 2. It seems to have been > uploaded in low quality and is pixelated (especially "June 2017"). > > Kat It looks good for me on Windows 7 (not HiDPI). I suggest to file a new bug with all the details (OS, screen resolution, etc.).
(In reply to Dani Megert from comment #135) > (In reply to Katharine Hirsch from comment #134) > > Created attachment 268774 [details] > > Oxygen Pixelated > > > > Hello all, > > > > It was brought to my attention that this is the splash screen that loads > > when users open Eclipse Oxygen Release Candidate 2. It seems to have been > > uploaded in low quality and is pixelated (especially "June 2017"). > > > > Kat > > It looks good for me on Windows 7 (not HiDPI). > > I suggest to file a new bug with all the details (OS, screen resolution, > etc.). +1, will have the end user do so. Thanks!
Created attachment 268863 [details] Blurry Splash - June Oxygen (22 inch screen) The splash is blurry for me too. I downloaded the PHP version of Oxygen on my macOS, 64 bit. Tried it on both my screens: 22 inch (1680 x 1050) screenshot attached 13.3 inch (2560 x 1600) also attached Intel Iris Graphics 550 1536 MB
Created attachment 268864 [details] Blurry Splash - June Oxygen (13.3 inch screen)
Does the image http://git.eclipse.org/c/platform/eclipse.platform.git/plain/platform/org.eclipse.platform/splash.bmp itself look good when you open it?
(In reply to Dani Megert from comment #139) > Does the image > http://git.eclipse.org/c/platform/eclipse.platform.git/plain/platform/org. > eclipse.platform/splash.bmp > itself look good when you open it? Thanks, Dani. It looks the same as it does in the IDE. Is it possible to save the original in high resolution?
I also see it on Linux, the spash in the IDE and on Git repo is more blurry than the initial proposal. I think it's caused by the initial proposal being too wide (comment #77 ) and the manual resize done by Sravan being sub-optimal (probably resized the bmp rather than reexporting the SVG in different size). Not sure there are still cycles to fix this in Platform, but it might still be soon enough to fix it in EPP packages.
(In reply to Mickael Istria from comment #141) > Not sure there are still cycles to fix this in Platform, but it might still > be soon enough to fix it in EPP packages. If there is a patch/fix available, we could certainly try to get this into this weeks EPP builds for RC4.
The fix for bug 516462 might have caused this. Can someone look at https://git.eclipse.org/r/#/c/97266/ and compare the two splash.bmp and report whether the old one was better? Of course we then have to decide whether blurry is worse than what's reported in bug 516462. At the moment I think we should defer this to 4.7.1.
I am not sure what the next steps are, but if you need me to provide the original in the correct (or a different) size/format please let me know (specify the exact size), as I didn't realize there was an issue with the width in the previous version submitted.
The fix for bug 516462 looks innocent. The problem is indeed that the initial design phase didn't consider the size of the final splash.bmp. The Eclipse launcher has never supported HiDPI splash screens. I've filed bug 518138 for that. If bug 518138 doesn't get implemented for Photon, then we can consider using a bigger splash screen image for that release. For Oxygen, it's too late to touch this, since changing the size of the splash.bmp would also require changes in all the product files that contain the coordinates for additional information that gets painted on top of the base image.
Created attachment 268872 [details] Proposal: optimization for 452x302 px
Created attachment 268888 [details] Splash Screen .ai fix FYI An issue was noted with the .ai version of the final splash screen design, in which horizontal lines were intermittently appearing on the design in photoshop or in previews. This upload of the splash screen should resolve that issue.
Created attachment 268892 [details] SVG without bitmaps and with pixel-grid-aligned text (In reply to Katharine Hirsch from comment #147) IMHO, the blurry effect is caused by non-pixel-grid-aligned text. It can be seen especially at small and thin fonts ("June 2017"). To avoid it, set the page size to 452x302 px and the text y-position and font size to integers.
