7 Commits

Author	SHA1	Message	Date
Ben Alpert	a8c484119b	Add new kittens after last row ... New kittens were being added before the last kitten instead of after it because we weren't taking into account the first (header) row.	2015-04-03 12:40:53 -07:00
Ryan Nystrom	c657411a2e	Batch fetch with small data sets	2015-02-26 22:29:13 -08:00
Ryan Nystrom	09ade3dd00	ASTableView batch API and context object	2015-02-26 22:23:32 -08:00
Ryan Nystrom	4fa03a01d1	Functioning Preload range ... Refactor how we do ranges so they can be arbitrarily managed. Introduce the concept of a preload range.	2015-02-26 15:41:32 -08:00
Li Tan	831aa47ae0	Address comments	2015-02-11 19:15:08 -08:00
Scott Goodson	f7d91bb877	Implement -reclaimMemory API and switch to manually controlled content clearing. ... ASDisplayNode and several subclasses had previously cleared memory-heavy objects like the backing store and text layout manager when the node's view or layer is removed from a visible heirarchy. This works great in any system that uses a "working range", where exiting the range removes the node from the hierarchy and reclaiming memory at that time is important. However, for standard UIViewController patterns (unused in Paper), this behavior causes highly undesirable thrashing (leading to visible flashes & wasteful re-rendering of content). After this change, node subclasses should implement -reclaimMemory if they need to perform any other cleanup besides backing store destruction when they leave a working range or other scenario where memory reduction is valuable. To trigger this behavior, calling code should use -recursivelyReclaimMemory. r=nadi	2014-10-14 18:45:56 -07:00
Nadine Salter	bd612fd725	Example projects.	2014-10-01 16:27:00 -07:00