On Friday 13 June 2008 06:45:25 am Nate Lowrie wrote: > On Fri, Jun 13, 2008 at 7:22 AM, Ed Leafe <[EMAIL PROTECTED]> wrote: > > On Jun 13, 2008, at 3:20 AM, johnf wrote: > >> The classic: > >> > >> You have a customer screen and need to retrieve the info. Or lookup > >> a invoice > >> number to retrieve the detail lines. > >> > >> In my case I have a class that uses a table containing meta data. > >> The table > >> has the name of the required table, the associated field name, > >> etc.. Then > >> the class determines the size of the grid for the display. > >> > >> But if you think about it almost every app needs a why to do a > >> lookup . > > > > So you're creating an app for a local company that has 50 > > customers. Do you use the same design as you do for a major international > > corporation that may have hundreds of thousands of customers? > > > > Personally, I would never think of creating something that I would > > recommend be used in all cases. Perhaps what you may do is create your > > solution and share it with others. You can create a Wiki page > > describing how it is used, and I can post it for download. But I have > > to agree with Uwe that it doesn't seem like something that would a > > framework-level tool. > > I second Ed's opinion. I have a metadata table for customer info in > some of my applications. However, those apps are for small businesses > and if they ever grow in scale to greater than 5000 orders a day my > design is in trouble performance wise. They are aware of the apps > limitations though and for them the benefit of the metadata far > outweighed a redesign down the road due to growth. > > Are you talking about a generic lookup UI control with which you just > have to fill in the backend details about the lookup? I know I have a > generic search panel precisely for lookups that gets reused. Its UI > layout is coded in the ClassDesigner as saved as a panel class while I > have the unit tested controller backend that will get subclassed to > handle specific searches. Works rather well. > > Nate L.
Yea that's worth considering. I see that as a Dabo supplied tool. Created in ClassDesigner and available to be used either in hand coding apps or ones created in ClassDesigner. The idea would allow for the delevoper to add what ever type lookup dialog/form/grid. Anyway, you are thinking like I am. -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
