As I've said to Thierry some time ago in different thread,
I would be interested in idea of having everything on disk
side and Pharo would only somehow refresh it's content (just
like a Java IDE / text editor would). But that may be a lot o
work so I can only dream about it, as nobody has time for that
(me included).
But to bottom line this thread (for me at least, because
I'm getting lost):
1. methodProperties.json provide compatibility for
FileTree, so I don't want to get rid of it (for now)
2. the large amount of file changes is probably a bug (I'll
try to be more observant about the commits in the future and
hopefully some pattern will emerge.)
3. I shouldn't want to break things for now at least
4. more people are starting to work on Git
5. I need to learn about FileTree at some point if I want
to contribute and experiment with (my) ideas (which won't be
soon as I'm preparing for my finals)