Hey sorry I some how missed that
original post.
"
- fork the existing sdkuilib and attempt to update it to the
newer code
+ requires
minimal changes to the rest of the Andmore codebase
+ fits the
Eclipse UI
- own future
maintainence
- fork the necessary Android
Studio UI code,
its swing based which isn't an issue but unfortunately appears
to also rely on Intellij classes
+ if we
minimize the changes, future upgrades may simply be merging
patches
- there may
not be 1:1 replacements for UI pieces"
I think we probably fork the sdkuilib, since it requires the
least amount of changes and especially if it is no used any
longer. We probably also want to do the same to the old
SDKManager app as well since they have gotten rid of it, and
bring it into the project.
I know we will probably need to fork and mange the AVD Manager
or try and bring in the new UI components within Eclipse. The
other alternative if they still provide a standalone UI manager
for the AVD creation and SDK Managers we may just want to defer
to those, and update the necessary launching code when they make
changes in the future.
Sounds like you had started it so, if you want to continue on
it, I'll make time to do any reviews and testing for the work
you submit for it.
Dave
On 3/17/2017 2:12 PM, Matthew Piggott wrote:
