On 24/01/2007, at 6:49 PM, Aliacta wrote:
It is very easy to export individual classes and drag them into
another project to update it. Partitioning work at the class level
makes a lot of sense.
And thus use container controls... (So you'll also import the
interface, not just classes.)
The reason I recommended a class focus rather than container controls
was a high degree of wariness about using an extra container level on
the RB GUI.
I don't see why you should warp your UI design that much to
facilitate splitting work.
There are dozens of reports relating to container controls still Open
in the feedback system (I did a search for Container with status
Open, didn't bother looking for Verified or Reviewed status) and they
are a pro-only feature.
You may like them but it seems dangerous advice to hand out without
massive disclaimers.
RS history in fixing particularly buggy areas of the framework,
especially with nesting (eg: pagepanels/tab panels) is not very
confidence inspiring. I know from my own cross-platform c++ work that
nesting views is one of the more painful areas so until something is
provably robust, am wary.
Andy Dent BSc MACS http://www.oofile.com.au/
OOFILE - Database, Reports, Graphs, GUI for c++ on multiple platforms
REALbasic, C++, Python, Mac and Windows development and porting
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
