filetree
filetree copied to clipboard
Monticello repository for directory-based Monticello packages enabling the use of git, svn, etc. for managing Smalltalk source code.
I'm in trouble, thus strongly require to fix this issue. I tried to clone the repository. But I can't and got the following errors; MINGW64 ~/hoge $ git clone https://github.com/dalehenrich/filetree.git...
Referring to MonticelloFileTree-Core-dkh.67 which is loaded by default into the current Squeak Trunk. This extension method shadows the existing method `DirectoryEntryFile >> #readStreamDo:` from the built-in Files package: https://github.com/dalehenrich/filetree/blob/28ab532548104ee38c55eaff8e8849ab3f595c5f/repository/MonticelloFileTree-Core.package/DirectoryEntry.extension/instance/readStreamDo..st Is...
I originally reported this issue here: https://github.com/hpi-swa/Squot/issues/316 (The `.ston` file is not relevant in this context, of course). It would be great if the JSON files could be formatted a...
As described in [this post](http://forum.world.st/Contributing-to-Pharo-tc4871604.html#none), it seems that a reasonable compromise for dealing with Monticello metadata, is that the `*.package/monticello.meta/version` file be a copy of the Monticello version history when...
Currently, you cannot load a project in OSX if the sources are on a shared drive or external drive because OSX generates hidden metadata files that filetree tries to load....
currently, `MCFileTreeStCypressReader>>methodSelectorFor:` does not take into account that a Class can have a custom compiler or parser. This is not an issue on GemStone, but Squeak and Pharo. In Squeak...
https://github.com/pharo-project/pharo/pull/1208 This means a change in the FileTree code. No test case in the Pharo pull request.
Example: I have two packages in FileTree: issue136-2.package/ and issue136-2.v3.package/ For Gofer, issue136-2.v3 is a correct answer for a request for issue136-2
instead of version numbers, and show all branches... Experimental.
https://github.com/dalehenrich/filetree/blob/pharo6.0_dev/repository/MonticelloFileTree-Core.package/MCFileTreeStCypressReader.class/instance/addClassAndMethodDefinitionsFromEntry..st#L8 When `README.md` is missing in the folder, then `classComment` will stay uninitialized and then will fail when specifying comment `self addClassDefinitionFrom: classPropertiesDict comment: classComment withSqueakLineEndings.` maybe a fix would...