On Thu, Aug 6, 2009 at 7:00 PM, Sam Anklesaria<[email protected]> wrote: > Models for buttons > ============= > 4 lines > syntax: "label" <button*> > > Though buttons have a model, they don't use it be default. However, it can be > useful to use the clicks of the button as the updates of the model, especially > when you would otherwise have to curry other objects into the button's quot. > (Contrast merger (quot style) to sudokus (model style)).
<button*> is not a good name for this; what about <model-button>? And this could easily go into its own vocabulary ui.gadgets.model-buttons. > Better model-fields > ============= This sounds like a good change. > Quot tables > =========== > 17 lines > syntax: model <quot-table> > > Having to make a separate renderer for every table you make gets to be a pain. > Rather, like buttons, it seems easier to just have a quot that gets called. > That's what these do. Also, they have "actions" and "hooks" slots, which > function like the button's models (changes the models on updates rather than > calls a hook). Why not make a quot-renderer? [ ... ] <quot-renderer> <table> > Lists > ===== > 2 lines > syntax: model <list> > > A very common type of table is a list: it takes an array of objects, and > displays them one to a row. That's what these do. Is this just a custom renderer then? Slava ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
