| 9708674a27e909730989017e31af8dffe6183893 |
|
25-Jun-2012 |
Siva Velusamy <vsiva@google.com> |
Stats Permission Dialog: Don't set focus on the link.
Doesn't look good on Mac.
Change-Id: Id7e953fa02a0303fe90964e1bfb97e7ff5e4b3a2
|
| d0357c27e602d6bec239897b8375d642bc590a62 |
|
22-Sep-2011 |
Tor Norbye <tnorbye@google.com> |
Welcome Wizard. Do not merge.
This changeset adds a new "Welcome Wizard" which is shown the first
time a user runs Eclipse with the ADT plugin.
The welcome wizard asks for two pieces of information:
(1) The location of the SDK.
(2) Whether the user agrees to gathering usage statistics.
We've needed this information before, but collection of the data had
been more ad-hoc: The usage data permission dialog would show up on
its own, and the SDK information would be requested the first time
some code path touched it (e.g. opening a layout or opening the
preference dialog's Android page etc).
In addition, the wizard also offers to *install* SDKs if you don't
already have one. It gives the option between the latest available
platform, and one supported by a large majority of devices (currently
API level 7), or both. If you select this option, then when finishing
the wizard the SDK manager is run in a special mode where it installs
the required packages with a progress dialog.
This changeset also starts recording the chosen SDK location in the
~/.android settings file. This allows us to detect when you're running
Eclipse in a brand new workspace and you've already gone through the
SDK selection before, and we don't need to ask again -- we'll just use
the most recently known location.
The wizard will only be shown once. If you bypass or cancel out of the
wizard, you can still configure your SDK the old way - via the
Preference dialog. Note also that the usage permission page is only
shown if the user has not already opted in via say ddms.
NOTE: If you want to test this, make sure you haven't set the
environment variable ADT_TEST_SDK_PATH (as some of us do for running
unit tests) since it is treated as the user having selected the given
SDK root, and in particular it means the wizard won't be shown even if
you've wiped adtUsed=true from your ~/.android/ddms.cfg etc.
(cherry picked from commit 292eefb8faa2f75ddbc5d6e20084c9f9a762da29)
Change-Id: Idb3f8775ef62a84905cde95b25eeb8691ef0afab
|
| 292eefb8faa2f75ddbc5d6e20084c9f9a762da29 |
|
22-Sep-2011 |
Tor Norbye <tnorbye@google.com> |
Welcome Wizard
This changeset adds a new "Welcome Wizard" which is shown the first
time a user runs Eclipse with the ADT plugin.
The welcome wizard asks for two pieces of information:
(1) The location of the SDK.
(2) Whether the user agrees to gathering usage statistics.
We've needed this information before, but collection of the data had
been more ad-hoc: The usage data permission dialog would show up on
its own, and the SDK information would be requested the first time
some code path touched it (e.g. opening a layout or opening the
preference dialog's Android page etc).
In addition, the wizard also offers to *install* SDKs if you don't
already have one. It gives the option between the latest available
platform, and one supported by a large majority of devices (currently
API level 7), or both. If you select this option, then when finishing
the wizard the SDK manager is run in a special mode where it installs
the required packages with a progress dialog.
This changeset also starts recording the chosen SDK location in the
~/.android settings file. This allows us to detect when you're running
Eclipse in a brand new workspace and you've already gone through the
SDK selection before, and we don't need to ask again -- we'll just use
the most recently known location.
The wizard will only be shown once. If you bypass or cancel out of the
wizard, you can still configure your SDK the old way - via the
Preference dialog. Note also that the usage permission page is only
shown if the user has not already opted in via say ddms.
NOTE: If you want to test this, make sure you haven't set the
environment variable ADT_TEST_SDK_PATH (as some of us do for running
unit tests) since it is treated as the user having selected the given
SDK root, and in particular it means the wizard won't be shown even if
you've wiped adtUsed=true from your ~/.android/ddms.cfg etc.
Change-Id: I0a4e2c4efce84aca9beae394ce67e4c145cbb000
|
| 44e49e03435b2d35f21510c8c70605a9c341fac2 |
|
23-Aug-2011 |
Siva Velusamy <vsiva@google.com> |
Use SWT Label's instead of Link's for proper wrap behavior.
On Mac, Link widgets to not enforce SWT.WRAP style. As a result,
text is just clipped instead of being wrapped. Split the privacy
policy text into two separate components - one with the text, and
one with the link, and use Label's for the longer text content.
Change-Id: Ic667b9ec62c0ce26c43611b97e0bbdc89dbc68d6
|
| bbd4f1dff7c6940bf4439569f19e8705cd2c3818 |
|
22-Aug-2011 |
Siva Velusamy <vsiva@google.com> |
Open SDK stats dialog from an existing shell.
This patch addresses Issue #15267. The primary issue is that the SDK
stats permission dialog was opened from a separate Job, and this
dialog shows up when the user opens the preference page for the
first time. Since both of them happen to be modal dialogs, the
behavior is inconsistent, and many times results in a blocked UI.
The patch fixes this issue by opening up the stats dialog as a child
of the preference page dialog within ADT, and as a child of a new
shell within DDMS.
Change-Id: I8c9ed9e9bbfac855435690f287b4f60975f336fb
|