Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse-dev] Screenshot Guidelines (Was: Re: Planning Meeting Notes - Feb 16, 2011)

Since Eclipse runs on different platforms and our developers work on 
different OSes, we allow everyone to use their OS to do the screenshots. 
There are some rules though:
1. Ensure consistent look among a document: if a document has most of its 
screenshots done under a certain OS then additional screenshots must also 
be made under that OS. Ask a friend to capture them for you if it's hard 
for yourself.
2. Use a default theme and not your custom colors and fonts.
3. Trim the screenshot to only show the relevant information.
4. Follow the guidelines (e.g. those for New and Noteworthy).

Dani


From:
John Arthorne <John_Arthorne@xxxxxxxxxx>
To:
"General development mailing list of the Eclipse project." 
<eclipse-dev@xxxxxxxxxxx>
Date:
23.02.2011 22:25
Subject:
Re: [eclipse-dev] Planning Meeting Notes - Feb 16, 2011



I missed this meeting, so I am wondering what was the outcome of the 
platform for screen shots discussion topic. My input is that for 4.1 we 
should certainly be using Windows 7, since almost all screen shots will 
need re-taking for 4.1 anyway. For 3.x, I'm less convinced that switching 
is worth the effort (the UI is stable enough that this would create a lot 
of new work for us). 

John 



Mike Wilson/Ottawa/IBM@IBMCA 
Sent by: eclipse-dev-bounces@xxxxxxxxxxx 
02/16/2011 10:36 AM 

Please respond to
"General development mailing list of the Eclipse project." 
<eclipse-dev@xxxxxxxxxxx>


To
eclipse-dev@xxxxxxxxxxx 
cc

Subject
[eclipse-dev] Planning Meeting Notes - Feb 16, 2011








------------------
Discussion Topic 
------------------

Debug:
- what should screen shots be taken in for platform doc? 
 - with Windows 7 becoming more and more common should we use the default
   Windows 7 theme?
 - should we use the 'Windows XP mode' (or whatever it is called) in
   Windows 7 to capture them?

User Assistance:
- after a security related bug is fixed how long do we wait to open the 
bug
report so anyone can read it

--------
Status 
--------

JDT Core:
- Java 7: continuing to implement jsr 334
- bug fixes/triage
- released one last fix for 3.6.2.
- working on getting new APIs in place for M6
- added "javadoc" as a new @SuppressWarnings token

Ant:
- bug fixing

Debug:
- bug fixing
- vacations

API Tools:
- bug fixing
- vacations
- producer-based migration task work progressing:
 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=332763

SWT:
- 3.6.2 testing went well
- reviewing code for application menu functionality (OSX and Windows 7)
- investigating drawing problems with GTK 2.20
- investigating surrogates for unicode use on GTK
- reviewing some BIDI patches

JDT UI:
- bug fixing

Platform Text and JDT Text:
- investigated and fixed intermittent issues with performance tests on 
Linux
- improved NLS tooling regarding invalid Unicode escapes
- continued work on smart indent/paste bugs
- bug fixing

User Assistance:
- committed changes to improve help view appearance ( plan item)
- continuing to work on defining API for help servlets
- bug fixing and triage

Performance:
- 3.7:
 I20110215-0800: nothing new
 N20110212-2000: nothing new
-3.6:
 M20110210-1200: nothing new

Workspace:
- bug 76386 - [History View] CVS Resource History shows revisions
 from all branches [in progress]
- bug 336686 - the regression in IBuilds [fixed]

._______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev





Back to the top