Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322188 - Improve Compare Packages page
Summary: Improve Compare Packages page
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Website (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: phoenix.ui CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-09 17:10 EDT by Remy Suen CLA
Modified: 2015-08-11 12:27 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Remy Suen CLA 2010-08-09 17:10:39 EDT
The table on the package comparison page is rendered completely of images.
http://www.eclipse.org/downloads/compare.php

Please give the <img> elements some alt text. If I turn images off in Firefox, I just see a blank table populated by white rows.
Comment 1 Nathan Gervais CLA 2011-04-07 10:44:29 EDT
I'll be tackling the compare page for Indigo, this should get some love then.
Comment 2 Denis Roy CLA 2013-05-10 10:39:43 EDT
The Compare Packages page at http://www.eclipse.org/downloads/compare.php needs an overhaul.

Since we have data on the features provided in each package (org.eclipse.cdt, org.eclipse.egit) here's what I suggest:

- we isolate the features we want to be used for comparison, and give them human-readable name (ie, no acronyms). For instance, org.eclipse.cdt = "C/C++ Editor", org.eclipse.egit = "Git client", org.eclipse.emf.core = "Modeling framework"

- we map these select features in a database table

- we allow users to select up to four packages to compare, with checkboxes
Comment 3 Wayne Beaton CLA 2013-05-10 10:50:20 EDT
(In reply to comment #2)
> The Compare Packages page at http://www.eclipse.org/downloads/compare.php
> needs an overhaul.
> 
> Since we have data on the features provided in each package
> (org.eclipse.cdt, org.eclipse.egit) here's what I suggest:
> 
> - we isolate the features we want to be used for comparison, and give them
> human-readable name (ie, no acronyms). For instance, org.eclipse.cdt =
> "C/C++ Editor", org.eclipse.egit = "Git client", org.eclipse.emf.core =
> "Modeling framework"
> 
> - we map these select features in a database table
> 
> - we allow users to select up to four packages to compare, with checkboxes

+1
Comment 4 Christopher Guindon CLA 2013-05-16 13:43:00 EDT
I made some progress on the comparison page:
http://www.eclipse.org/downloads/compare_404861.php

How it works:

-XML list of the features we want to display: 
http://eclipse.org/downloads/downloads/data/features.xml

-JSON feed: it includes a description, name & id of features. (provided by Wayne):
http://www.eclipse.org/downloads/downloads/data/kepler_features.json

* I will need to move these files soon.

I am matching each feature id listed on the package details page, http://eclipse.org/downloads/packages/eclipse-classic-43-m7/keplerm7 with both feeds.

I am also verifying if the source is included by looking for a feature id that ends with .source

org.eclipse.cvs	
org.eclipse.cvs.source

It's currently possible to compare 2 or more packages.

If you click on a package from the "new" comparison page, you will be redirected to the a new package detail page. I am also displaying readable features on that page.
Comment 5 Wayne Beaton CLA 2013-05-16 15:08:03 EDT
IMHO, "RCP" should be removed from the list. I believe that it really means "Platform" and this should be included in all packages. I'm a little confused that it's not in some.

GEF should be removed from the list. It's framework/runtime stuff, not tools. Something in the automotive package is using it to build editors. It's not a "featured feature".

I'm inclined to remove all features from the list that are just project names. Project names are generally meaningless to the target audience.

"EGit" should be "Git Client" or something like that.

"End-User Runtime" is meaningless and shouldn't be there.

I'd like to see something better than "Mylyn Task List". Something like "Task-focused Development Tools" would be better. Though I'm not in love with that, either.

"Data Tools Platform Intro" isn't right, either. Maybe it's not the right feature. For the target audience, I think we need to say something about the tools, not the platform.

"BIRT Framework" also isn't interesting. It should be "Business Intelligence and Reporting Tools".

I'm not sure how I feel about "RAP Tools".

Should we favour "SWT Designer"/"Swing Designer" over "WindowBuilder Core"?

I don't think that "m2e" adds any value to "Maven Integration for Eclipse". I'm not sure that "Eclipse" is necessary? Is "Maven Integration" enough?

I'm not sure how I feel about "Code Recommenders Developer Tools". "Code Recommendation Tools"?

I don't think that "Xbase", "Xtend" and "Graphiti" belong on the list. Maybe if they provide a little more information, I'd change my  mind. e.g. "Xtend language support" or something like that.

I've posted a note on the Cross Project mailing list. The projects themselves should be making the name changes. In some cases, we can help them (e.g. remove "End-User Runtime" on their behalf), but the projects themselves are the best source of this information.
Comment 6 Wayne Beaton CLA 2013-05-16 15:48:47 EDT
I'm also inclined to drop features that are only in one package. 

BIRT is, for example, only in the Java/Report package.

Parallel Tools Platform (PTP) End-User Runtime is only in the "Parallel Application" package.

These aren't useful for comparison, and their inclusion is--I think--obvious from the package name.
Comment 7 Eclipse Genie CLA 2015-05-07 11:57:01 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 8 Christopher Guindon CLA 2015-08-11 11:48:59 EDT
Can we close this bug or is there anything else we need to do here?
Comment 9 Ian Skerrett CLA 2015-08-11 12:20:35 EDT
(In reply to christopher Guindon from comment #8)
> Can we close this bug or is there anything else we need to do here?

+1 please close
Comment 10 Christopher Guindon CLA 2015-08-11 12:27:47 EDT
Closing