Join Date:Joined: Mar 2009
four spam replies when one gets the point across.... I wonder which is worse, the poster or the barrage of "use search" after it;
If you mean actual porting, it can be done. You'd basically have to reverse engineer the apks to get them to work on the regular google framework. It should be a little easier now with JF's tool to dissasemble dex files. You can't look at the actual code, but just looking at the function and class names should give you an idea of what they do and how to code an equivalent function for when a certain apk makes a call, then you can either;
1. remake the apk, but using google's regular APIs or,
2. just move the apk, and make your own framework that passes those requests to the appropriate API handler if it exists within the google framework, if not, then make your own with either java or the just-released C++ builder. Kind of like WINE does.
I've always thought the best option is to just make comparable versions of the apks that run on the default google framework, it can be done, it's just exactly the way aHome and other home replacement apps do it, better and faster too. And for example, there are replica Hero widgets out there that look and behave much like their real counterparts, again, without requiring any of hero's libs or frameworks.
If people want real TouchFlo working on the phone, then we need real development to happen and actually make these programs instead of just taking the already built files (which were never meant for the Dream in the first place) and just trying to make them work.