Closed hfossli closed 10 years ago
Yes, I've read that, but I find it a bit short. How this works different from e.g. injectionforxcode is of great value to newcomers like myself.
Well, as about dyci - here's a description about how it works under the hood
https://github.com/DyCI/dyci-main/wiki/How-it-Works
As about other tools - it's really hard to check what is the difference. They're not static :) They're evolving
In general there few points from the readme
https://github.com/DyCI/dyci-main#differences-from-other-tools
To write less or more concrete differences for each another tool is kind'a not the main concept of this project, right?
Well, I'm just sharing my point of view (as a user and potential contributor).
You need minimum moves to enable dyci
Yes, good point!
You aren't writing some kind of script, you are writing your code!
Which tools require "some kind of script"?
You don't need to prepare/modify/lock your code for dyci
I don't really know how to relate to that. Is that something other tools require?
You aren't writing some kind of script, you are writing your code!
Which tools require "some kind of script"?
There were few tools that do some logic by using debugger console. So you were need to wrote simple commands in "some language", that is different from objective-c
There also Interactive console in RubyMotion https://www.youtube.com/watch?v=rejYKzLglSE, where you writing it in ruby
You don't need to prepare/modify/lock your code for dyci
At some point, injectionfroxcode was required to lock files before injection and unlock them after. Also I think that even now injectionforxcode have some step of project patching.
As I said - there are some tools :) It's hard to track all changes of them
:D
It would be great if you could add a note in the readme about alternative solutions, how this compares to the others and what's different. I know there's a project called injectionforxcode.
Thanks!