I recognize that unix approach for frontends is a bit limitted because of the impossibility to multiplex multiple paralel calls over a same resource at a time.
The thing to use rpc for everything is nice, but not as cool as it should be, because it is slow. I have been thinking about it and I was concluded on some random tips. - Today lot of python apis are growing up to handle idb and binary files. - Limitting to one scripting language is a bad approach Today exist javax.scripting and parrotvm that allows you to run lot of dynamic languages - Writing a frontend is a waste of time (GUI programming is not nice) - Java is portable and have a good support for handling all we need in radare - JavaGnome (GTK+) api now is thread-safe - Developing a Java api to manage radare, memory structures, process ones, etc.. - Java is not the best language for handling binary files - Don't want to use .net - I can easily imagine a Java api for analyzing a binary and using the eclipse apis create a decent frontend similar to ida or ht. - People that should run the frontend will do it on a desktop (no ram problems ;) - radare servers can run on pdas with 'radare listen://9999' - Extending radare with tcp monitors multiple views can be taken from the same session at the same time. Storing all the info that gives radare (disasembly, flags, xrefs, pA, ...) on data structures like sql or memory ones with objects it will be relatively easy to show a complete source-assembly view with interactive items and support for comments and so. I just want to poll you about these random ideas, any participation? What about doing it with python? (i really dislike this idea for multiple reasons) Tell me what you think about all this shit. --pancake _______________________________________________ radare mailing list [email protected] https://lists.nopcode.org/mailman/listinfo/radare
