Comments (6)
This is what was presented as a "strategy based" behavior to avoid prompting for versions name, base editions, prerequisites, etc.
from tonel-vast.
I know that this about the Tonel reader, but it is an area where preferences decisions could be specified in the Rowan component file (i.e., for GemStone one can specify on a per package basis, the symbol dictionary where classes will be created). Just a thought.
from tonel-vast.
Today I'm working on it, the reason for this is that the ENVY Manager tools are very UI-bound, so what I'm creating is a set of strategies that you can use, by default you have the "interactive" strategy (it is, falls back to the UI prompters, etc.), and the others are to load the latest edition (e.g. as a Base edition), use the computed prerequisites, etc.
from tonel-vast.
I understand ... but once decisions have been made it would be convenient to record them on disk (in a component?) ... with that said, being able to choose to interactively drive the decisions is also important ...
from tonel-vast.
There is an initial support for this in 56ffb41.
I'll write a doc on how to use each strategy next week.
from tonel-vast.
It is working now.
from tonel-vast.
Related Issues (20)
- Prerequisite comparison in Applications must use defined prerequisites
- Prerequisite modification should be optional
- Add option to avoid writing extension methods categorized with asterisk prefix
- Rebuild namespaces after loading declaration methods
- #readUtf8StreamDo: should allocate enough buffer size
- Remove EsCodePageUtilitiesApp prereq from TonelFileSystem
- Methods that failed to compile should be updated when loading
- Add a setting to ignore extensions to classes not in the image
- Debugger class reset
- TonelLoaderStrategy instVars get reinitialized after copying them
- Applying an app suffix when loading a VAST app doesn't update the Application class name
- Create custom Error Reporter for Tonel Loader
- Use application manager/class owner when modifying ENVY records
- Add option/strategy to define package name when exporting
- Add option to avoid writing extension methods using Monticello categories
- Add support to have nil as superclass identifier
- Provide the ability to file in a single tonel file such as a class
- Wrong argument names in `TonelReaderClassDefinition>>#initializeWithName:...`
- Normalize instance variables names when creating TonelReaderClassDefinition HOT 1
- Improve the behavior of `#autogenerateInstanceInitializers` to avoid multiple initialization HOT 2
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-vast.