Community
Participate
Working Groups
Create a new web page for the Build To Manage Instrumentation and WSDM Tooling tech previews to make it easier for someone to download these tools and try them. The web page can include new packages for these tools that include all the necessary plugins in one package.
Ashish and I have talked about the new website, and he and I will work on a prototype and get some feedback from the other BtM members.
*** Bug 144436 has been marked as a duplicate of this bug. ***
Targetting to iteration 3
I have reworked the TPTP download pages and have attached the source content and screen caps. Please review and let me know if there any changes. The layout targets for simplicity of downloading components. I will send a note on the newsgroup asking for peoples opinion as well.
Created attachment 51436 [details] Screenshots Screenshots of newly proposed download page.
Created attachment 51437 [details] Web Page source Webpage source code.
In regars to the attachment, I know of one error in IE6< where the expansion of the Offerings and Tech Preview sections don't work - but all is well in Firefox. I will fix soon. Also I plan to add platform detection and print out the OS for which the all-in-one drivers apply to.
before someone asks :) - the link called "Tips" next to the language packs will pop up a list of the -nl <lang> arguments to use when starting eclipse. I haven't finished adding this in yet. A side node: The Eclipse Webserver uses PHP, which will be exploited when the page becomes approved - so don't mind the fact that the source code on the web template duplicates some sections.
I'd like to see Build to Manage on the download site; in addition to ARM, mention that JMX and CBE instrumentation options are supported. Will this feature support installing TPTP and the tech previews as an update site in Eclipse itself?
Hi All, In the interests of full disclosure, I should admit that I currently have automation that screen scrapes the existing TPTP download page, and downloads and extracts all the components of TPTP. So this change will cause me to do some rework. However, I'd like to see the download experience improved, so this is all good. Having said that, there are a number of things I don't really like in the proposed replacement. Here are my thoughts: 1) The main download page is very confusing. Is the main link supposed to be the all-in-one bundle? (It says it includes "all the required eclipse items" -- does that include eclipse itself?) My first guess would be no, but if that's what it's meant to be, I suggest the link name include the ubiquitous "all-in-one" moniker, and I suggest we state explicitly what the bundle contains. Providing the packaging is nice, but many users will need to actually know what they got at some point (is BIRT in there? What about WTP?) I assume we will bundle the full Eclipse SDK as the other "all-in-one" bundles do -- we should say that as well. 2) Where's the Agent Controller? Since the download is not platform specific, it's clear that the AC is not bundled. And for users on Windows and Linux, the IAC will be enough for some of them. But for everyone else, it's not obvious that they should click on "component downloads" to get the AC. The wording on the page ("if you would like to download individual components, please click here") implies that the component download page is the place to get the "individual components" that are bundled in the all-in-one download. At least that's how I read it. The same can be said for the "Integration Packs" -- by including them in the individual component area, many users will never find them. I suggest another section on the main page called "optional components" where you can expose both the AC (though it's only optional for Windows & LinuxIA32) and the Integration Packs (or some other name) 3) Integration Packs: I like the idea of better explaining our optional dependencies, but I'd like it more if it was about functionality vs. integration. i.e. I'd guess that more users are interested in profiling on servers than are interested in WTP integration, and more users are interested in enhanced reporting than are interested in BIRT integration. I'm not saying we shouldn't explain that we're doing these integrations. I'm just saying that we should advertise the functionality, not the integration. Perhaps "Optional Feature Packs: Server profiling (via WTP integration) and Reporting (via BIRT integration)"? 4) My biggest pet peeve about the existing download mechanism (which may be caused by the Phoenix project) is the corruption of the browser history when you click on a download link. You know what I'm talking about -- you click on one download link, and when you click the back button, it doesn't go back. The entire eclipse.org history in the browser session is munged, and you have to renavigate back to the download page. I know this has nothing to do with your request, but if you can make this go away, I'll send you a 12 pack. 5) One additione request -- if it's not too difficult. Could we publish an additional file, alongside the download page itself, which is just a simple, parsable collection of the links that are scattered about the download area for that build? This would be very useful for automation purposes. I'm okay if those links go to php pages with mirrors (since I have worked around that navigation problem), but if it went to known, real downloadable links and thus was known to work right after the build is first published (before all the mirror sites were populated), that would be super-cool. Thanks for undertaking this. I hope these comments aren't too critical -- I just want to see it get lots better than it is today.
Created attachment 51446 [details] Fixes expand/collapse javascript bug. Ashish, To avoid referencing the wrong element you need to change each UL's ID to be different from the name of the anchor tag that's right above it. Next the logic in the javascript should be slightly different. From checking to see if an element's display style is set to "block" (which IE doesn't support correctly) it should be checking for "none". Expand/Collapse should be working fine now.
A couple of comments: 1) The 'all-in-one' download should provide the details of its contents, such as contents and version. What would be cool is an interactive UI that allows the user to pick and choose the correct mix (e.g. version) of components (e.g. TPTP Platform and Test with BIRT) in their customized 'all-in-one' download. 2) We should have a link to the JRE and OS support statement in very close proximity to any download, including the 'all-in-one' download so users can easily locate and download the correct version/vendor's JRE. 3) The component links could be one of the expandable sections, similar to Standalone Offerings and Technology Previews. 4) Add a link to the TPTP Documentation site the Documentation section. Also, consider making it an expandable section. 5) I think all Standalone Offerings and Technology Previews should have documentation (e.g. tutorial or readme) and viewlet demos. 6) I believe we were not exposing the old Agent Controller for the platforms supported by the new Agent Controller.
=> +1 vote for Joe's comment #10 point #3. (If you have time for no other changes to this page, please implement this one.) => +1 vote for Joe's comment #10 point #4. I think what's happening is that someone put in an instantaneous redirect (e.g. <meta http-equiv="Refresh" content="0;url=http:myNewURL" />.) It doesn't have anything to do with Phoenix. If the person adding that redirect changed the "0" to a larger number such as "5" then you could go back to the page and would have five seconds to hit back again. This is one of Jakob Nielsen's top 10 web design mistakes of 1999 http://www.useit.com/alertbox/990530.html Joe, if you see this again, I suggest that you open a bugzilla against the page owner to fix the problem. => +1 vote for Paul's comment #12 point #2. Perhaps the download page could also include links to the various JREs in a prerequisite section? I don't want to start to bundle the JRE in the TPTP download itself because of the legal issues and many users will already have a JRE installed. => +1 vote for Paul's comment #12 point #5. If you want people to use a tool then you need to tell them why it benefits them and how to use it. I don't think that a viewlet demo is necessary but the docs are. A viewlet demo alone would be insufficient because users with vision difficulties wouldn't benefit from it, but it's a nice-to-have option for other users.
Created attachment 51486 [details] Updated WebContent Updated in regards to comments.
Created attachment 51487 [details] Main Download Page Main Download Page
Created attachment 51488 [details] Tech Preview Tech Preview
Replying to David: Made modification to the instrumentation items in the Tech preview to group them together. Still kept a separate download for people just wanting to consume ARM - due to the demand of having just this component. Replying to Joe: 1) "Main page is confusing": I have made some changes that hopefully addresses your concerns. Keep in mind that there is a "Getting Started" link block on the right hand side that users can use to jump around to their favourite component to download. 2) "Where's the Agent Controller?" The All in one download has the IAC. If someone wants to get the AC they use the links in the Getting started or the links below the Download now section. 3) "Integration Packs"- feel free to contribute more clear wording. I have merely copied the wording from the existing site. I don't think I'm the right person to explain WTP/BIRT integration since I have no clear understanding of what exactly the value add is. I encourage all TPTPers to contribute clarity to the wording on this download page. 4) "you click on one download link, and when you click the back button, it doesn't go back" - Unfortuntely I'm not the Eclipse/TPTP webmaster or build master. I'm a TPTP committer, just like you, wishing to ease my own pain of downloading from the TPTP website :) Feel free to open a defect on Phoenix project. 5) "Could we publish an additional file, alongside the download page itself" - you should open a separate defect for this. I like the idea too, but in the scope of this defect I'm merely trying to make the download pages more seamless. Replying to Paul: 1) (a)"The 'all-in-one' download should provide the details of its contents" - please refer to my modified proposal. (b)"What would be cool is an interactive UI that allows the user to pick and choose the correct mix (e.g. version) of components (e.g. TPTP Platform and Test with BIRT) in their customized 'all-in-one' download." - I had a similar idea too. I wanted to make it like a shopping experience. The only catch is that there is build work around this, and I wanted to take this in steps. First we need a usable and friendly download page and one that seamlessly provides an "eclipse" look and feel. Once we get the build items for this worked out we can explore fancy ideas. However, in the grand scheme of things, I believe Eclipse needs to provide a utility for all eclipse projects that makes downloading easy no matter which project you're using. I'm working on drafting an enhancement for Eclipse to look into this. 2) "JRE and OS support statement in very close proximity to any download" - in the original download page this was all the way at the bottom of the web page -- no where in proximity to anything really. I have put this into the "documentation" section of the main page. When you look at the main page you can see the All in one download and the Documentation section clearly on the page without having to click on anything - I'm thinking this close enough proximity? Adding more text below the Download Now in the all in one section is just going to get us into trouble like with the old website - that is, too many fine lines to read :) I have moved the statement as the first bullet into the Documentation section - does this help? Do you think adding a link to the document in the Getting Started section would help too? That way any page you're on you'll have that link handy. I think this may help address having the statement near "any" download - such as AC or components, etc.. 3) "The component links could be one of the expandable sections" - I want to keep the main page simple as possible. Any generic TPTP user just wants an All-in-one...asking for a specific component (ie. say Trace) is a more advanced request, so they must use the "component download" link - which is provided clearly in two places on the page. I could make every section an expandable section - but there is no point of that because then the page just becomes what we have now but just hides the complexity. I think either way we go there are pros and cons. 4) "Add a link to the TPTP Documentation site" - Can you provide me this link? 5) "I think all Standalone Offerings and Technology Previews should have documentation (e.g. tutorial or readme) and viewlet demos." - This is presently there. Next to the title of each section there are set of icons...one for "Download Now", one for "Documentation", and one for "Viewlets". The latter two only appear if there is such content. ie) take a look at AGR and Code coverage. 6) "I believe we were not exposing the old Agent Controller for the platforms supported by the new Agent Controller." - but we are :) If you click the "Agent Controller" link I've added to the All-in-one and Getting started sections, you can read the AC blurb. Then there is a link to "pick a platform" or "try the new agent controller". Click those and you will see. The All-in-one already has the IAC - so again, an advanced TPTP user would have to use the links and navigate. One of the major design considerations I've taken into play here is simplicty. I do not want to overwhelm users with all the TPTP components or platforms right from the bat. From what I have heard, people using TPTP just want TPTP - its the developers and integrators that want specific platforms or components - and hence, I've separated these two requests. I greatly thank you all for your feedback, I know its a change from the current page but I feel its an improvement to what is present today.
(In reply to comment #17) 2) Having the JRE and OS support statement as the first bullet into the Documentation section AND Getting Started section would solve the problem while eliminating the clutter. 4) http://www.eclipse.org/tptp/ >> Documentation or http://www.eclipse.org/tptp/home/documents/index.html. 5) I was referring to making bot mandatory before publishing to the web site. However, Ruth's point on accessibility is valid so maybe just documentation should be mandatory. 6) If you look on the existing download page, the links for the old Agent Controller on Windows and Linux are now pointing to the new Agent Controller. Thanks for executing on this suggestion. This defect will greatly improve the user experience when access TPTP drivers.
Created attachment 51558 [details] Web Source Included modifications for Paul's comments.
Since this bugzilla has evolved into a redesign of the main TPTP Download page I'll change it to focus on that and open another bugzilla for the specific requirements of a Monitoring Tools technology preview web/download page. I am reassigning to Hubert as the CVS owner of the download page but others are more than welcome to contribute to the design and implementation of it. Thanks to Ashish for initiating and contributing an inital design/implementation. Note, the PMC/PG will have the final approval of this redesign.
As additional input, please read https://bugs.eclipse.org/bugs/show_bug.cgi?id=53149#c31
Phoenix version of this page has been checked in with some modifications: 1. I replaced all of the images with placeholder images because I was suspicious that Ashish hadn't created these images. If I'm wrong and Ashish has artistic abilities that I am unaware of then please let me know and I'll put the images that are attached to this bugzilla into the TPTP web CVS. (It would be a copyright violation for us to copy images from someone else and use them. We could use links to those images but not copy them.) 2. I removed the link to the "Migration guide for users" because that guide should be disappearing shortly. The information in that guide should be translated and I realize in retrospect that it should never have been a web-only document. The information in those guides will be merged into the TPTP on-line documentation that is shipped with the driver. 3. I added a few placeholder pages (you'll see them as you click on the links). 4. I did not make the left-hand column match the column in Ashish's prototype because Dale & I designed the new left-hand column of the TPTP Phoenix page and we need that information & links there. (It's the same column shared by all of the TPTP web site and I can't customize the column to just the download page.) And now that I see the proposed redesign, I'd like to add my vote to Hubert's to remove the tabs at the top of the page. I think that they add too much clutter to the page given the standard Eclipse tabs in the header. Hubert mentioned that other projects were following another standard and perhaps he can identify what that convention is? Ashish, the files were checked into /tptp/performance/resources/downloadPagePrototype because you have write access to that directory and will be able to alter the pages yourself directly from now on. (That's excepting the left-hand column which is in the root directory of the TPTP web site.) Folks, to see the page live please navigate to it from the TPTP Phoenix web site: http://www.eclipse.org/tptp/newindex.php
Oh, and one more suggestion: I think that it would be helpful to have the languages sorted alphabetically in the drop-down list. The user shouldn't have to know which group a language is in. It's easier to find a language if it's sorted alphabetically in a list.
1) All images came from Eclipse.org or from TPTP itself. I created more.gif and less.gif myself. So we are safe here. 2) I've updated the following pages. Please review. a) Download page -http://www.eclipse.org/tptp/performance/resources/downloadPagePrototype/newdownload_byTopic.php - added missing javascript files from my design - updated images in placeholders - added BTM link to BTM website b) Component Page - http://www.eclipse.org/tptp/performance/resources/downloadPagePrototype/newcomponentdownload.php - added missing javascript files from my design - updated images in placeholders c) BTM page - http://www.eclipse.org/tptp/performance/resources/downloadPagePrototype/btm/ d) Main TPTP page - http://www.eclipse.org/tptp/newindex.php - fixed layout issues for IE and mozilla - cleaned up content ordering - I request we get some better looking graphics put up here etc. There is still more to be done to get the entire download user experience complete. So stay tuned.
The HTML download page provided by Ashish is used for the candidate build. I have opened bug 165922 to integrate the new download page into the build framework in the 4.4 timeframe.
(In reply to comment #24) All the clean up work mentioned in this comment has been handled when the page template was integrated into the build system. I am considering the redesign complete. If anyone has additional suggestions please open a new defect with specifics. David - can you please close if you are satisified?
I have three problems with the new design (although I like it's look): 1. the Back button doesn't work after you click a component link, I always need to go in the browser history to select the previous page to get back to the specific driver download page 2 from the Components & prerequisites and Agent Controller pages if I click Back it goes back to the current main download page, I need to click again on the driver link to get back to that driver download page 3. the logo too big and distracting and makes it hard to find the driver Runtime/SDK download link, I think would be better to use a smaller image and a larger font for the links would improve (like on the Eclipse download page). Also the fact that the two collapsible sections are automatically collapsed when you use Back button to go back from a documentation link it's annoying. I can open another defect for these problems if you think would be required.
(In reply to comment #27) Please ignore "would improve" and read "logo is too big".
I opened bug 166856.
(In reply to comment #27) The browser back button is a known problem, and its a limitation of the build system only allowing one template file for the entire download page. Hubert will be modifying the build system in the future to have more than one page template where we can fix this problem. I'm not sure I can comment on the logo size. Most who reviewed my initial design found that the icon helps to make the page look slick and separates the all in one driver from the rest of the individual components. I tend to agree here. thanks for your feedback!
(In reply to comment #30) > I'm not sure I can comment on the logo size. Most who reviewed my initial > design found that the icon helps to make the page look slick and separates the > all in one driver from the rest of the individual components. I tend to agree > here. > If it will be like the ones on the http://download.eclipse.org/ page I will also agree (look at the icon and link text size there and also the visual separation created between Eclipse distros and Eclipse SDK download links). The icon on our page actually spreads across the "all in one" , "components and prerequisite" and "agent controller" links, kind of confusing for a first time users. Also the note about the fact that all in one driver contains several projects uses a very small font. We should show the size of the zip files everywhere we have a link to them and also provide context about a page, for example you cannot tell what driver is specified on http://www.eclipse.org/tptp/home/downloads/drops/TPTP-4.3.0-200611160100C.html until you look at the actual URL of the page, or at any URL of the links from the "Components & prerequisites". I also found the navigation kind of cumbersome (you need to click 3 links to get a driver starting with http://www.eclipse.org/downloads/index_project.php), I think something like on http://www.eclipse.org/emft/downloads/ would be more accessible (that approach is used in some other places also). One more thing, on the http://www.eclipse.org/downloads/index_project.php page, we list all the TPTP sub projects there but all the links point to the same page TPTP 4.2, I'm not sure how a sub-project download page will look like (at least today) or if we really need one.
(In reply to comment #31) > We should show the size of the zip files everywhere we have a link to them and > also provide context about a page, for example you cannot tell what driver is > specified on > http://www.eclipse.org/tptp/home/downloads/drops/TPTP-4.3.0-200611160100C.html > until you look at the actual URL of the page, or at any URL of the links from > the "Components & prerequisites". Click on "Components & prerequisites" after you click the above link, that's the page I was talking about. The way we use JavaScript on the download page it seems to introduce more problems (as Joe mentioned earlier) than it solves.
Marius, it would be easier for everybody to keep this defect in a close state and open new defects for extra requirements. I expect to have new requests and proposals to further improve the download page but this defect has done it's job and I think it deserves to stay closed. Please reopen a different defect for your comments and close this one
Reverted as fixed as it has been before. Please follow the discussion started in this bug at comment #27 in bug 166856.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
