Hi Erich: On 2/11/07, Erich Focht <[EMAIL PROTECTED]> wrote:
> So Opder and Selector are used, those are what I had in mind. I don't > understand how it works if you delete them. Are you suggesting to delete the > src/ and never touch them again? Having trouble to understand what you exactly > plan to do... (Wasn't Selector subject to changes every now and then, > recently? Opder also needs some changes soon...) AFAIK, the code in src/ are all the _new_ GUI code that NCSA implemented before leaving the OSCAR core group. These were never completed/integrated into OSCAR. There is Opder and Selector code in src/, yes, but these are the _new_ code that are supposed to work with the new Qt-based Installer. For instance, see the check in message for Selector: http://svn.oscar.openclustergroup.org/trac/oscar/changeset/2535 It says "Initial checkin of the new OSCAR Installer compatible Selector. " So this is not the Selector code we have in lib/Qt. This document shows you screenshots of what the new widgets looks like: http://www.csm.ornl.gov/oscar04/proceedings/enos_oscar3-to-oscar4.pdf However, you brought up an interesting question - where are the .ui codes which generated the code in lib/Qt?? I think so far we have been modifying the .pm files in lib/Qt directly. P.S. My goal is to clean up the source tree. There seems to be some code that are no longer being used/maintained, so why not remove them and prevent future confusions regarding whether we need to maintain them or not... Cheers, Bernard ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
