Jacob Floyd wrote:
On Mon, 14 Feb 2005 13:30:07 +0100, Kay Ramme - Sun Germany - Hamburg
<[EMAIL PROTECTED]> wrote:

Jacob,

regarding your interest in developing a new toolkit or chrome for OOo, I
am wundering about what the abstraction level will be and if we can
reuse something already available. Personal being a friend of domain
specific languages, I would favor XUL or other (XML) GUI description
languages. Do you have an opinion on that?


Kay


I was thinking that XUL, or XUL-like files would be an excellent
choice for the GUI description. I'm not an expert on any of these
perfect. So, you may be interested in doing some prototyping?

technologies (XUL, UNO, ...) and so It'll take me a little longer to
get any substantial code going. Oh, and I'm going to have to wait till
about July to submit any code to the project because I'm a minor and
thus the JCA won't be valid until then (when I turn 18). That and
That's fine.
school seems to like to pile on the homework everytime I start
something new.
I still need to read this 1000+ page developer guide, and I heard a
new one was supposed to be coming out with 2.0. (Is that correct? and
will there be any major changes to it that will affect me? Is there a
way I can just get this new version now, so that I don't have to
RE-read anything?)
Everything in the current version of the dev. guide will certainly be valid for the upcomming version. Actually, I have to admit that I don't know what exactly the differences will be, despite certainly covering the new UNO features and additional APIs. Juergen, can you comment on this?

Another problem I'll have is I don't have all the requirements to
build OpenOffice on either OS X or Win. I don't have apple developer
tools (xcode now) and I don't have VS.net 2003. Does anyone know
what's required to get the VS.net C++ toolkit 2003 working? What's
missing. I should be able to develop for a while only compiling my
source, but in a few months I'll start modifying OOo source, which
will leave me in the lurch. Any suggestions?
AFAIR for windows, you only need the MS SDK and some GNU tools, which are AFAIK available for free. Please someone correct me if I am wrong. For doing Mac builds, Dan certainly knows what's needed, the info also seems to be available on http://porting.openoffice.org/.

Thanks, Jacob
Kay


--------------------------------------------------------------------- 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]



Reply via email to