Comments (5)
Speaking of packages ... I just noticed that similar to FileTree, you've taken the approach of subclassing the various Monticello classes, so it looks like the port to the GemStone base will be a pretty significant departure in terms of implementation and will definitely result in an almost completely new set of packages for Cypress1
format and probably another set of packages for Cypress2
ideally the BaselineOfTonel
will be shared across the different implementations: Monticello (which should work for Pharo/GemStone/Squeak, like FileTree), Cypress1 (pretty much GemStone only), and Cypress2 (which will target multiple Smalltalk dialects)
from tonel.
well... I copied the design of filetree with the hope it would easy the porting effort (since there was already a port). I'm sorry to hear that is not the case :(
let me know how can I easy the task.
from tonel.
btw, I am favouring "src" as package location.
I'm not against on move them if needed.
from tonel.
haha ... filetree was the first github repo and I'm afraid that there are a number of decisions I made that at the end of the day I would have done differently, but by then the commitment was too great and the number of moving parts that would have to change was too great to make it worth changing ....
I've settled on src
myself ... I'll go ahead and make this change in my current development and then merge things in when I'm ready
from tonel.
With this commit ef109a0, I've moved the packages into a src
directory .... will be available when I merge
from tonel.
Related Issues (20)
- run tests on github actions HOT 1
- Tonel should not use MonticelloMocks package - but have own mocks
- Cleanup: Condense MonticelloTonel packages
- Check that there is no user of withSqueakLineEndings or friends
- Tonel doesn't support custom #compilerClass
- Tonel cannot write the attach method
- Conversion from filetree to tonel: package wrongly converted HOT 5
- Tonel ignores MCVersion package name
- Tonel breaks with dots after selector
- Shadow variable in TonelWriter
- Tonel does not check for duplicated methods in .tonel file HOT 1
- TonelWriter should use traceCr: HOT 2
- TonelWriter>>writeSnapshot: includes tag name in package name when there's no OrganizationDefinition HOT 1
- Improve can't parse error
- Missing License
- STON should depend on GitHub STON not STHub STON HOT 1
- Read/write problem when a method has certain "unfinished statements" HOT 3
- Category cleanups and alignments
- Better error report
- TonelWriter uses the platform line ending HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from tonel.