The nice part of doing this is you don't have to use much core for the method source, which was a big deal in 1978. You can easily strip the sources and changes files if you don't need them. eg. when distributing a build to customers. It also lets you remember the change history and enables recovery from crashes and other errors. The basic mechanism is also fairly easy to repurpose to support other change tracking approaches.
The interesting trick, is if you don't have a .sources or .changes, the system will run the Decompiler, which almost always produces readable code that is structured like the original source but with no comments and the local variable names changed to t0, t1, t2,... etc. There have been proposals to keep local var names in the image as to make it a bit less painful. It is surprisingly easy to code like this. There have also been proposals to store the whole source text in the image. You could do it and it wouldn't be hard, but you'd lose the advantages of the external code storage.
This does not count the various project facilities and change lists so you can keep related changes grouped.
I basically never saw any source files. According to wikipedia, you could export them though. But it's a long time ago and I never did much with smalltalk. I was still in university and this was part of our object oriented programming course.
A file that is easy to read and index sounds like a database to me. Not an sql database obviously.
https://news.ycombinator.com/item?id=32432411
except when it was using ENVY/Developer
https://www.google.com/books/edition/Mastering_ENVY_Develope...
Also my guess is that with Gemstone the code was in the database (but I am just guessing).
That is why there are export/import tools.
https://www.google.com/books/edition/Mastering_ENVY_Develope...