Re: [andmore-dev] How out of date is Andmore

[Doug Schaefer <cdtdoug@xxxxxxxxx>]

Crazy thought of the day and the reason I can't get to sleep tonight: Start over. From scratch. Toss the legacy and create a new set of plug-ins that use Gradle off the bat, focus on the using the LaunchBar to launch, blend in with the other IDE plug-ins. Steal stuff from the code we forked from ADT that we figure we couldn't do a better job of, like the layout editor. Start small, support basic use cases and grow from there. Make it a real community thing built by the community, give them a real sense of ownership over it.

I'm going to give this some though. I'm heavily into building IDE mode lately with the work I've done with the LaunchBar and Qt and Arduino build and launch support in CDT. All that is fresh on my mind. Just need to figure out how to set up JDT properly. I think it can be done and done well. I'll see if I call my own bluff before you guys do :). At the very least, I'm going to start prototyping and see where it leads.

- Doug.

On Fri, Jan 1, 2016 at 9:43 PM, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:

Hey gang,

I have to apologize, but a year or so later I'm finally getting around to trying out Andmore looking for things to fix up. It turns out to be pretty easy to find things that are broken.

So my first question comes as I try to create a new project targeting my Priv which is 5.1.1 which is API 22. The layout editor complains "This version of the rendering library is more recent than your version of ADT plug-in. Please update ADT plug-in." And I see bug 462620 stating that we don't actually support that level and 23.

Have we updated Andmore with the latest patches to ADT? ADT is clearly evolving at least a little to keep up with API releases. What is our plan to keep up with it? Is it as simple as seeing what they've done and applying the same code fixes albeit with the new package names?

To take that thought even further, did we really hurt ourselves by changing the package names, and thus file paths, in the code making it almost near impossible to keep up? I fully expect Google to keep ADT at least up to date with API releases which means we will need to update Andmore as well.

I love the fact I can easily clean up things in Andmore that violate Eclipse IDE UX especially when combined with other plug-ins for Web and IoT development. But it's really unusable if we can't keep it up to date easily with API releases.

Thoughts on how we can fix this? Do we need to redo the fork and keep it as a fork and not update so much?

Thanks!

Doug.