It may help to not think of them as "backgrounds" anymore. They are shared groups. Any card can use any of the shared groups. This is really a vastly superior way of managing things, especially since the whole card = record moniker doesn't really work well in Livecode. Cards are really like forms now, into which you load your data, which is how dynamic web content works. The leap from Pascal to Hypercard was MUCH greater than from Hypercard to Revolution/Livecode. I don't find it that onerous, or I don't anymore once I gave up trying to do everything like I used to in Hypercard. Those on the list like Jacque can tell you I struggled a bit when I started, especially with databases. Once you get your hands dirty, it all falls into place though.
Bob On Feb 1, 2013, at 3:42 PM, Joe Lewis Wilkins wrote: > 2. Though I certainly appreciated the multi-platform aspects and a few other > "tweaks"; I was flabbergasted to discover that RunRev had mangled the H/C > framework by eliminating the Background layer in stacks, providing a very > clumsy alternative method, so that the millions who could be adopting it from > H/C would have to re-implement most of their legacy stacks. It just wasn't > the same Object Hierarchy any more. I tried to be upbeat with the articles I > wrote on MacInstruct about Revolution, but Revolution just wasn't a better > H/C. What RunRev did later in transitioning to LiveCode is a totally > different issue. The damage had already been done. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
