Last year we presented CuisUniversity and DenotativeObjects, now we have more features we would like to show: delegation, different cloning techniques, transition from concrete objects to classes, refactorings, didactic improvements to tools, and even graphical denotative objects. Everything in constant evolution as we use them in different universities. Also we'll see how easy is to inspect and modify Cuis to introduce a change!

1. Denotative Objects are
growing fast! Nahuel Garbezza
@ngarbezza

2. CuisUniversity

3. CuisUniversity

4. Happy birthday!

5. We’re a small community

6. Denotative Objects!

7. Tools adapted (Browser, Inspector, Debugger) to work with these objects
Delegation with parent objects a-la-Self
Clones and replicants: different ways of sharing behavior at object-level
Smooth transition to classes
DenotativeObjects

8. Denotative Object for assertions: Assert
Graphical Denotative Objects (linked to a Morph object)
DenotativeObjects

9. Refactorings!

10. Implemented from scratch
Some refactors implemented, a lot of refactors pending to be implemented
Model flexible enough to support “complex” refactors in the future. (e.g.
replace if with polymorphism)
Refactorings

11. Libraries!

12. Aconcagua: measures model
https://github.com/hernanwilkinson/Cuis-Smalltalk-Aconcagua
Chaltén: Gregorian Calendar model (based on Aconcagua)
https://github.com/hernanwilkinson/Cuis-Smalltalk-Chalten
Assertion helpers
Libraries included

13. Didactical addons

14. Auto (or manual) restore of lost changes
Stack size watcher / Recursion detection at parse-time
Proper vocabulary (e.g “collaborators” instead of “inst vars”)
Didactical addons

15. Demo!

16. Documentation / Examples
Add more graphical objects support
Managing images / Self-Upgrading
More refactorings
We’ll continue working on

17. Conclusions

18. Many changes on CuisUniversity also imply improving Cuis in general
We have not dedicated too much time on development, but we have a decent
set of features
We’re constantly shaping the tools while keeping simplicity. This is helpful not
just for teaching, but any kind of experiment in general
There’s a lot of room for improvement. We need your help!
Conclusions

19. Thank you!

20. Creative Software Development