I'm trying to learn good coding practices--keeping my presentation classes separate from my domain classes. But it's hard sometimes ... the old, newbie ways just seem easier!
Consider this example: In the UI you've got a StringGrid, which is editable. Each row in the grid ultimately represents separate objects, and each column separate attributes or properties. So, what do you do about creating new objects? In my "old ways" this wasn't an issue--users just type their info into the grid, and the various operations on the grid are taken care of via UI form code event handlers ... convoluted, hard to understand, sometimes difficult to debug--but conceptually simple. As users, however, we're accustomed to simply typing in a grid a la spreadsheets. So how is the program set up to recognize when you're changing attributes of an existing object, and when you want to create a new object? I know that some people use StringGrids as read only displays and simply have them display the attributes of each object in a collection anytime there's a change inside the collection. ... But I'm talking about an editable grid. I hope this makes sense! Thanks, as always -- Al _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
