Most of this is very out of date. --John, 2011-01-15 How to implement
I suppose we'll want to create a "magic" ...
Possible rename: folder, holder, batch, group, referrer, set, equal, peer, linker
list
from initial design: +braindump, +questions Design for multiple values
Short property syntax
The translation from single to multiple of ...
Card permissions
- Only those who can view a card should be able to perform any of the following acts on it: read, comment, delete
...
we're thinking of unifying datatypes and cardtypes into cardegories. (This was in fact done.) this means cardegories will be addressing all the needs presented by ...
(temporarily here while we can't create new cards) Specifications for new edit and new card interfaces
New card Interface
Cardtype changing always visible (as in Edit mode, see ...
leverage rails api 1. basic operations should be same as standard rails models: create, destroy, updates through attribute accessors. this helps coders ...
- domain name of the wagn forms a kind of Primary namespace-- can create pointer cards to cards in other wagns
- main design area is "sub"-namespaces within
...
future versions of wagn will use - basically Restful-Rails interface, plus
- card names: if there are no slashes beyond the first id and the method is not
...
I believe that this ruby code gets the user ids from the sessions updated in the last 15 minutes Session.find (:all, :conditions=>["updated_at > ?", 15.minutes.ago]).each do ...
Algorithm starting string .underscore .split(/[^\w]+/) .plot(:singularize) .reject {|x| x=""} .join("_")
Key: a string identifying a casespace-- all string in casespace can be resolved to this key via above algorithm
Languages operate similarly to namespaces-- by default wql filters for the primary language of the logged in users. certain queries will skip this constraint: for...
A place to list potential or planned refactoring jobs
- Transition from Cardtype to datatype
- Datatypes with extensions (ie. User) should create the card and extension in a
...
common structure: all tables have an id field-- auto increment primary key primary tables
- cards
- name
- key
- type (sti)
- namespace_id (namespace)
- language_id (language)
- translation_id (card)
- trunk_id (card)
- tag_id (card)
- current_revision_id (revision)
- extension_id, extension_type (any)
- reader_id, reader_type (user or
...
From Datastructure conversation: what we want to capture: how can we make building complex relationships simple & clean field v. tag 3-way relations: A+B=C vs. (A+B)+C Natural language: subj,
...
