Hi, Bernd Thank you for your reply! It's very helpful for us. We are very interesting about VCL and making it separated from OOo like URE did. But as you said, a lot of work to do. So we have to consider the VCL solution for us very carefully, although in my opinion, I would like to do this so much. Thank you again. Best Wishes~
-----邮件原件----- 发件人: Bernd Eilers [mailto:[EMAIL PROTECTED] 发送时间: 2008年5月23日 21:07 收件人: [email protected] 主题: Re: [dev] Can we use AWT in our product? Hi Lizhan! Well I am not a lawyer but well it´s LGPL so principally you could use it as long as you stick to the LGPL license terms. For example you must make sure that anyone can get the source code of the libraries you use which can be easily done by providing just a link to the OpenOffice.org website as long as you didn´t need to modify anything. If you need to modify and fork the libraries and you must publish those modifications also under the terms of the LGPL license. You must make sure that anyone can exchange eg. the vcl library in your product(s) by one compiled by him/herself, etc. etc. http://about.openoffice.org/index.html#licenses http://www.openoffice.org/licenses/lgpl_license.html Note though that this is currently not offered as a real toolkit which can be downloaded separate from other OpenOffice.org source code, so the work to extract the necessary things and to create an environment where only the AWT/VCL stuff is being compiled than is up to you. If you plan to do that work anyway it would be considered good OpenSource practice to contribute these changes back to the OpenOffice.org community than. Maybe this could lead to a situation where someday in the future there would be a separate downloadable VCL-Toolkit from the OpenOffice.org website as an additional thing to the OpenOffice.org program, no matter how good or bad such toolkit might be compared to other available cross-platform toolkits. With the same license restrictions you might also consider Juergens suggestion and use java for the GUI together with the OpenOffice.org UNO component technology (and corresponding OpenOffice.org libraries which also use the LGPL license) to call the C++ components you develop via UNO). Doing this would give you the advantage of being able to use GUI Editors like the one netbeans offers which is something not available for VCL while still developing your core components in C++. More information on UNO can be found in the Developers Guide which has just moved to the Wiki http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/OpenOffice.org_Developers_Guide But you probably already found this. Just my 2 cents. Bernd Eilers LiZhan(李湛) wrote: > Hi Juergen > Thank you for your help and suggestion. > The product we are to develop will use C++ for developing language. It's > purely new, also we lack experiences for cross-platform. So we prefer to use > AWT. > What we are consider is whether AWT is allowed to use in a commercial > software. Can you give us some advises about corresponding legal issue? > Thanks again! > Best Wishes. > > > -----邮件原件----- > 发件人: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > 发送时间: 2008年5月23日 13:07 > 收件人: [email protected] > 主题: Re: [dev] Can we use AWT in our product? > > LiZhan(李湛) wrote: >> Hi everyone, we are planning to develop several new commercial products for >> our company, and we need a cross-platform GUI lib used as their base GUI >> module. >> >> So can we use AWT(certainly with GSL and VCL) of OpenOffice.org in our >> program? > well you can use it but i don't think that it wouldn't be the best > descision. We use VCL because it is historical and it would be a lot of > work to exchange it. A lot of things are missing like a layout manager, > a graphical GUI editor, ... But if you plan new applications from > scratch there are might be better cross platform toolkits available. > > It depends also on the programming language you want to use. I > personally would consider to use Java. It's platform independent and the > tools support is great. Take a look on the GUI editor of NetBeans for > example. > > You can use our component model to use Java as GUI frontend and use C++ > core components via UNO. It would be an interesting use case. > > Just my 2 cents > > Juergen > >> Does every module in OpenOffice.org follow the LGPL? >> >> Hope for your reply, thank you! >> >> >> >> > > > --------------------------------------------------------------------- > 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]
