It's Cards all the Way Down+Chapters
Atomic Data
Atomicity has a number of technical definitions mostly relating to making the actions on groups of data items behave as single events.  That is part ...
Names and Namespaces
If cards are data atoms, then namespaces are collections or containers of those data atoms.  We will wait to explore how multiple namespaces might relate ...
One Kind of Content
Actually, there is considerably more flexibility in data representation than this title implies, but underneath the hood there is one way to store the content ...
Formatters
This is another core component of the card system.  Initially there was only one formatter to render different views of cards to view and edit ...
Linking and Inclusion
So we know that referencing other cards from content isn't part of the common content abstraction, it's just an internationalized text string, and we have ...
Sets and Rules
Up to this point we have talked about the idea of sets without saying much about how they work.  That's because all the ideas above ...
Patterns
Lets start with our simple set card 'Set+*type'.  It is an instance of a particular pattern that is connected in code.  Currently, it is defined ...
Rules
Rules are just a tool the module developer can use.  They are used for core features like permissions, look and feel, help messages, and the ...
Model Views and Events
We can think of all of these like rules in code.  Back to our example set, we have this file: mod/05_standard/set/type/set.rb  Which has all ...
Web of Applications
To this point we have only mentioned the web to talk about context for the development of the cards model, and to note the lack ...
The Web Service Model
Although we are working pretty hard to package the card model independant from any web application, the model is designed to integrate with web applications. ...
The Big Picture
This project is situated within the history of software development.  The full sweep of this history has a ways to go to get to a ...

 

Wheeled by Wagn v. 1.18.1