Comments (5)
We should remove all methods that are in deprecated categories or with deprecated comments.
from cormas.
At the moment, what is important is not compatibility with old CORMAS models.
What is important now is to have something working, even if we break compatibility.
This is not a good idea to have a lot of deprecated methods. We don't even know in which CORMAS versions these methods works. We should use the Pharo deprecated API.
Action: remove old and deprecated code in the Pharo version. We will fix the old models later.
from cormas.
as for the issue about IndexedSet, your question leads back to another question.
Do we want to keep some king of compatibility with the models developed under cormas/vw.
Because, actually the deprecated protocol is often use to store all methods, that might be still called by old models and that we keep there when we release a new version.
So
- if we decide not to try to have a compatibility with models developed in vw, then we can delete all those deprecated methods
- if we try to have this compatibilty, we should keep them
from cormas.
We have to look at the senders of these methods. If they have no sender (or the sender is also deprecated), we can safely remove them.
from cormas.
Some methods like CormasModel>>updateAgents are still use in Cormas-core.
from cormas.
Related Issues (20)
- Remove useless things from CMCell HOT 1
- Rename theCSE to arguments and theESE to theCells
- Remove OrderedNeighbourhood and keep only neighbourhood
- Remove flag instance variable from CMEntity
- Remove outline instance variable from CMSpatialEntity
- Store model metadata directly in AbstractModel and not in ProjectFramework
- The saved model can not be loaded
- CMApplicationProject should not inherit from PFProjectApplication
- CMProjectManager should not inherit from PFProjectManager
- Saving does not work because of CMApplication
- Rewrite the implementation of CMClassAttributeValueDataSource class >> inheritedInstVarNamesForClass:
- Cormas Space View is blinking
- Pluralization: Common issue when pluralizing specific words HOT 1
- Remove asGetterForEntityClass
- CMSpaceModel should not inherit from Model
- neighbourE, neighbourN, etc. don't work properly on edges
- Allow to use different shapes for agents
- TCMLocated should not implement cormasModel as explicit requirement
- Replace CMR3ShapesBuilders with ShapeBuilders to build individual shapes
- Feature request : use `.dot` file to create skeleton of a model
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 cormas.