+1. We need feedback and plenty of it. I agree that aqua keyname should be used.
Here is something that I think needs a little more clarification. aquavcl01 should be for the VCL changes needed to get OpenOffice.org to be Aqua'fied' and NO MORE. AquanativeFilePicker01 should be for the Mac OS X Native File Picker and NO MORE. These should be kept separate. Why? If I want to back into the X11 code, I don't want to search through a bunch of aqua code dealing with VCL. Likewise, once the Native File Picker is done, we can then move towards integration into the Master. Keeping projects simple and separate is best. I will use Warnings01 as a way NOT to do a cws (over 6000 changes were in this CWS and they were all over the module code and project.) As to the builds, we need ONE source. I say that if Maho can provide the builds with aquavcl01 and aquanativefilepicker01, that we ask him to do so. If not, then we should use a dedicated resource (macport01, macport02) to build with. Also, before we announce a public alpha, the readme, warnings and notices need to be completed and verified. There should be an issue in IZ as a TASK to accomplish this. This weekend should be very busy. James -----Original Message----- >From: Pavel Janík <[EMAIL PROTECTED]> >Sent: May 26, 2007 5:06 AM >To: [email protected] >Subject: Re: [mac] My opinion about providing builds > >> My purpose was : do that only once (means provide alpha is unusual >> way), to save time waiting the real integration is effective. >> Nothing else. > >So you think the first alpha will be the "alpha"? I do not think so. >-- >Pavel Janík > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
