Skip to content

Standard Translation Framework #2

Description

@GoogleCodeExporter
Smali/BakSmali, ApkTool, and related systems need to establish a 
comprehensive standard data format so that version dependent and host 
dependent issues such as android sdk failing to be stable do not effect 
the recoverability and portability of existing and future tools. Their 
interdependency is obvious and should be merged/standardized, but inline 
trace and runtime verification should be handled on-board as should an 
api/interface to standard data for visualization and editing. There is no 
reason a client wishing to use (restrict) only one application should have 
anything else running or accessable on the machine, full decomp-inline-rip-
optimize and rewrite core with tool is an easy target for these projects.

I am more concerned with code audit and on-board compiler and system 
visualization especially when the host changes so severely due to 
Google/etc's incompetence.

Original issue reported on code.google.com by wilfredg...@gmail.com on 25 Apr 2010 at 1:48

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions