[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tools-pmc] Definition about icon to be used for branding
|
Yes. Point is that the about dlg should be fixed IMO.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
-----Original Message-----
From: Schaefer, Doug
Sent: Friday, March 18, 2011 9:35 PM
To: Oberhuber, Martin; 'tools-pmc@xxxxxxxxxxx'
Subject: RE: [tools-pmc] Definition about icon to be used for branding
Well. That's kinda what we're doing already. Projects do what they need to do and we stay out of the way.
D.
-----Original Message-----
From: Oberhuber, Martin [mailto:Martin.Oberhuber@xxxxxxxxxxxxx]
Sent: Friday, March 18, 2011 12:46 AM Pacific Standard Time
To: Tools PMC mailing list
Subject: Re: [tools-pmc] Definition about icon to be used for branding
Perhaps a compromise is having an icon for “major blocks of functionality”, essentially allow a project do an icon if they want but not directly encourage it. Funny enough in the past those have been striving for an icon and actually designing one themselves who really wanted the publicity and felt it was important for them… that’s the right granularity IMO.
What we have today isn’t that bad after all: there’s separate icons for webtools, modeling, CDT, Eclipse, Mylyn, DTP from what I can remember. Each of these span up almost an ecosystem of their own. However the individual webtools or modeling projects don’t do an icon themselves.
I think the best approach is an icon granularity as we have today, and changing the about dialog code to group by icon only (not by project name). Then hovering over the icon should show a list of related project names, and clicking the icon should show all features related to that icon (even if from multiple project names).
This would still give some visibility into the project names, while keeping the immediate user-visible effect of the icons on a slightly more granular level.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From: tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-bounces@xxxxxxxxxxx] On Behalf Of Jeff McAffer
Sent: Thursday, March 17, 2011 2:23 PM
To: Tools PMC mailing list
Subject: Re: [tools-pmc] Definition about icon to be used for branding
Indeed you are right. My 2c, it is goofy to have duplicate icons in the about dialog and a bit overwhelming for users to see 10s of icons. I certainly can see the value of surfacing the projects there but don't think it scales well. Having said that, if we are going that way, we'll go with the flow and look at icons for Equinox etc...
Jeff
On 2011-03-17, at 1:50 PM, Konstantin Komissarchik wrote:
Observationally, it is bitwise compare of image and string compare on provider. If you look at the Helios SR2 Java EE package, there are three buttons with standard Eclipse icon with Eclipse.org, Eclipse Packaging Project and Eclipse Data Tools Platform. The about box has worked that way for several years at least.
Regarding the practice of using different provider names for each project, I seem to recall this being a directive from one of the councils (maybe planning council) a year or two ago.
- Konstantin
From: tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-bounces@xxxxxxxxxxx] On Behalf Of Jeff McAffer
Sent: Thursday, March 17, 2011 10:06 AM
To: Tools PMC mailing list
Subject: Re: [tools-pmc] Definition about icon to be used for branding
Unless something changed, the About dialog does a bitwise compare of the images and does not present multiple of the same image. So if your feature, regardless of provider string, uses the standard eclipse icon, it should not show up separately.
Jeff
On 2011-03-17, at 12:15 PM, Oberhuber, Martin wrote:
Hi Jeff,
I fully aggree… just note that AFAIK the way the about dialog works today, you’ll already get a separate icon for each contributor with a separate provider name.
Given Dave’s requirement that every (sub) project specifies their own provider name, we’ll be getting 50-100 IDENTICAL feature icons in the about dialog if each project uses the Eclipse.org <http://Eclipse.org/> icon.
Unless we change the about dialog code, which might be what we should do (ie grouping identical icon names even if the provider name differs).
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From: tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-bounces@xxxxxxxxxxx] On Behalf OfJeff McAffer
Sent: Thursday, March 17, 2011 12:12 PM
To: Tools PMC mailing list
Subject: Re: [tools-pmc] Definition about icon to be used for branding
Personally I would recommend using the Eclipse icon for the feature branding. If every project had its own icon then the various EPP packages and product configurations would have 50-100 different feature icons and it starts loosing its value/meaning. Despite each project feeling it is special/central, to the end users more often our stuff is just "Eclipse".
Jeff
On 2011-03-17, at 10:51 AM, David M Williams wrote:
No, no standard icon. You are free to create your own, or, I'd suggest, use the "standard" Eclipse one, if you don't have your own.
As for Provider name, it should not be "Eclipse.org <http://Eclipse.org/> " (for anyone). It should be "Eclipse <project name>" ... or, for those in "Tools" TLP, you could say "Eclipse <sub project name>".
Thanks,
From: Daniel Pastore <kpqb38@xxxxxxxxxxxx>
To: tools-pmc@xxxxxxxxxxx, Sequoyah Developers <sequoyah-dev@xxxxxxxxxxx>
Date: 03/17/2011 10:45 AM
Subject: [tools-pmc] Definition about icon to be used for branding
Sent by: tools-pmc-bounces@xxxxxxxxxxx
________________________________
Hi guys,
We from Sequoyah have just moved to Tools project, and we would like to know if is there a standard icon to be used for branding in our plugins/features (that shows in the about screen, for instance).
We used to have a DSDP icon for that, but since we migrated, it doesn't make sense anymore to use it.
Also, we have checked that other subprojects from Tools use "Eclipse.org <http://Eclipse.org/> " as provider name property. Should we use this too?
--
Thanks,
Daniel Pastore
Sequoyah Team
_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tools-pmc <https://dev.eclipse.org/mailman/listinfo/tools-pmc>
_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tools-pmc
_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tools-pmc
_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tools-pmc
