-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request file-in support for Pharo files #56
Comments
Sorry about that. It turns out that the import works for Topaz format (and maybe VW?), but not for Pharo. I'll edit this into a request for Pharo support but honestly it will be a low priority (unless the work is sponsored!). My advice is to use Monticello to export from Pharo and load into GemStone. |
Well, that would be the better way ... but looking at Pharo 9.0 I was not able to find that option anyway. |
I do have a file-out from Pharo that I'd like to load into GemStone, so the chance of me at least investigating this is a bit higher than it was! |
Create Topaz script from Pharo script (proposal for #56).
I've chosen to do this as a file-to-file translation since it is faster to load via Topaz and it is easier to catch and fix errors. See the new menu command on Transcript->File. Please reopen this with comments if you have issues or suggestions. |
If I paste source code into a workspace, slect it all and the filein just gives me a strange dialog and nothing is happening
PMAccuracy.txt
.
The text was updated successfully, but these errors were encountered: