Welcome to NeoOffice developer notes and announcements
NeoOffice
Developer notes and announcements
 
 

This website is an archive and is no longer active
NeoOffice announcements have moved to the NeoOffice News website


Support
· Forums
· NeoOffice Support
· NeoWiki


Announcements
· Twitter @NeoOffice


Downloads
· Download NeoOffice


  
NeoOffice :: View topic - 1.1.5 RC released by OpenOffice.org
1.1.5 RC released by OpenOffice.org
 
   NeoOffice Forum Index -> NeoOffice Development
View previous topic :: View next topic  
Author Message
yoxi
Cipher


Joined: Sep 07, 2004
Posts: 1799
Location: Dawlish, Devon
PostPosted: Thu Jul 14, 2005 12:54 am    Post subject: 1.1.5 RC released by OpenOffice.org
Since everyone's bound to be asking this - what's the significance of this release for the nearer future of NeoOffice/J?

As it has OpenDocument support, how soon - if at all - will the 1.1.5 code make its way to Neo/J? (I mean: is the plan to head straight for the v2 code, or will there be integration of the 1.1.5 code in the meantime, given the amount of work involved in getting v2 lined up?)

- yoxi
Back to top
jjmckenzie51
The Anomaly


Joined: Apr 01, 2005
Posts: 1055
Location: Southeastern Arizona
PostPosted: Thu Jul 14, 2005 8:54 am    Post subject: Re: 1.1.5 RC released by OpenOffice.org
yoxi wrote:
Since everyone's bound to be asking this - what's the significance of this release for the nearer future of NeoOffice/J?

As it has OpenDocument support, how soon - if at all - will the 1.1.5 code make its way to Neo/J? (I mean: is the plan to head straight for the v2 code, or will there be integration of the 1.1.5 code in the meantime, given the amount of work involved in getting v2 lined up?)


Not the answer you are looking for, but as soon as I get a copy of the 1.1.5 source, I will look at it and see if I can get a build done of it for the X11 branch. If this works, it may be possible to move Patrick and Eds work to incorporate the Carbon/Java framework and have an RC very soon for Neo/J with 1.1.5 capabilities. Then again, it may take months.....Thus, no promises and Patrick and Ed continue to work on gcc 4.0 compatibility as this must happen if we are to see Neo/J on MacIntel.

James
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949
PostPosted: Thu Jul 14, 2005 8:57 am    Post subject:
Given that our current development plan is to add Java 1.4.x support and native widgets before we upgrade to OOo 2.0, IMO the most logical thing to do is to upgrade Neo/J to use the OOo 1.1.5 code either after the Java 1.4.x work is done and push out a Neo/J 1.1.5 release.

I diffed all of the OOo 1.1.4 and 1.1.5 sources and the changes seem to be limited to filter changes and translation updates. So, I don't think it will take me more than a week to upgrade the Neo/J code to use the OOo 1.1.5 code.

Using the OOo 1.1.5 code would buy us a lot of time as we would have a stable release with that supports the OOo 2.0 file formats.

Patrick
Back to top
jjmckenzie51
The Anomaly


Joined: Apr 01, 2005
Posts: 1055
Location: Southeastern Arizona
PostPosted: Thu Jul 14, 2005 8:59 am    Post subject:
pluby wrote:
Given that our current development plan is to add Java 1.4.x support and native widgets before we upgrade to OOo 2.0, IMO the most logical thing to do is to upgrade Neo/J to use the OOo 1.1.5 code either after the Java 1.4.x work is done and push out a Neo/J 1.1.5 release.

I diffed all of the OOo 1.1.4 and 1.1.5 sources and the changes seem to be limited to filter changes and translation updates. So, I don't think it will take me more than a week to upgrade the Neo/J code to use the OOo 1.1.5 code.

Using the OOo 1.1.5 code would buy us a lot of time as we would have a stable release with that supports the OOo 2.0 file formats.


Thanks for the update. Where did you get the source code, as I'm looking for it.

James
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949
PostPosted: Thu Jul 14, 2005 9:28 am    Post subject:
I just did a "cvs diff -r SRX645_m57" in each of the OOo modules in my Neo/J build directory.

Patrick
Back to top
yoxi
Cipher


Joined: Sep 07, 2004
Posts: 1799
Location: Dawlish, Devon
PostPosted: Thu Jul 14, 2005 9:42 am    Post subject:
Quote:
I don't think it will take me more than a week to upgrade the Neo/J code to use the OOo 1.1.5 code.

Good news - that would indeed buy you some time as we'd have a Neo/J that could read/write OpenDocument docs regardless of how long it takes to get to v2 itself, so there'd be no breakdown of compatibility with win/linux users.

Good luck with the upgrading!

- yoxi
Back to top
Waldo
Oracle


Joined: Dec 03, 2004
Posts: 239
PostPosted: Thu Jul 14, 2005 5:54 pm    Post subject:
yoxi wrote:
Quote:
I don't think it will take me more than a week to upgrade the Neo/J code to use the OOo 1.1.5 code.


This is great news Smile

W
Back to top
Adam_Moore
Pure-blooded Human


Joined: Jul 10, 2005
Posts: 36
PostPosted: Fri Jul 15, 2005 8:44 am    Post subject:
Guys I get a build, but I would watch out with 1.1.5 There has been a few critical issues that have come out with the RC. One of them being that it can read open document format but cannot save in open document format. I think until it's announced to everyone that the RC is out I would be careful about bugs you encounter. There has been 3 RC's in the last 2 weeks, mostly installation and l10n issues so that shouldn't be a problem for you.

Just a suggestion
_________________
Adam Moore
OpenDocument Fellowship
Adam.Moore@opendocumentfellowship.org
Demand Microsoft Support OpenDocument
http://opendocumentfellowship.org/petition/
Back to top
jjmckenzie51
The Anomaly


Joined: Apr 01, 2005
Posts: 1055
Location: Southeastern Arizona
PostPosted: Fri Jul 15, 2005 9:39 am    Post subject:
Adam_Moore wrote:
Guys I get a build, but I would watch out with 1.1.5 There has been a few critical issues that have come out with the RC. One of them being that it can read open document format but cannot save in open document format. I think until it's announced to everyone that the RC is out I would be careful about bugs you encounter. There has been 3 RC's in the last 2 weeks, mostly installation and l10n issues so that shouldn't be a problem for you.

Just a suggestion


How does one pull down through CVS the 1.1.5 RC code? I would like to look at it and see if the patches I've been working with on SRX645_m57 still work or are needed.

James
Back to top
jjmckenzie51
The Anomaly


Joined: Apr 01, 2005
Posts: 1055
Location: Southeastern Arizona
PostPosted: Fri Jul 15, 2005 3:32 pm    Post subject:
pluby wrote:
I just did a "cvs diff -r SRX645_m57" in each of the OOo modules in my Neo/J build directory.


Did you have any troubles with the xmerge directory?

James
Back to top
Adam_Moore
Pure-blooded Human


Joined: Jul 10, 2005
Posts: 36
PostPosted: Sat Jul 16, 2005 7:49 am    Post subject:
So everyone knows 1.1.5 will not support saving in open document format. It will only read the format and you have to save in something else.
_________________
Adam Moore
OpenDocument Fellowship
Adam.Moore@opendocumentfellowship.org
Demand Microsoft Support OpenDocument
http://opendocumentfellowship.org/petition/
Back to top
ovvldc
Captain Naiobi


Joined: Sep 13, 2004
Posts: 2352
Location: Zürich, CH
PostPosted: Sat Jul 16, 2005 8:33 am    Post subject:
Adam_Moore wrote:
So everyone knows 1.1.5 will not support saving in open document format. It will only read the format and you have to save in something else.


Does that mean a 1.1.6 will be forthcoming that does support saving in open document?
_________________
"What do you think of Western Civilization?"
"I think it would be a good idea!"
- Mohandas Karamchand Gandhi
Back to top
sardisson
Town Crier
Town Crier


Joined: Feb 01, 2004
Posts: 4588
PostPosted: Sat Jul 16, 2005 11:55 am    Post subject:
ovvldc wrote:
Adam_Moore wrote:
So everyone knows 1.1.5 will not support saving in open document format. It will only read the format and you have to save in something else.


Does that mean a 1.1.6 will be forthcoming that does support saving in open document?


There's apparently a 1.1.6 target, since that's what Patrick's dontated code is now targeted for, FWIW.

Import-only is not exactly going to spur adoption of the OpenDocument formats, either, but it at least provides a modicum of interoperability between people running the betas (or alphas in the Mac OS X case!) of 2.0 without having to bug the sender to resend in another format. If the sender is using KOffice, however, I'm not sure it's so helpful since one would have to send .sx*/MS format back....

Smokey
_________________
"[...] whether the duck drinks hot chocolate or coffee is irrelevant." -- ovvldc and sardisson in the NeoWiki
Back to top
Adam_Moore
Pure-blooded Human


Joined: Jul 10, 2005
Posts: 36
PostPosted: Sat Jul 16, 2005 2:26 pm    Post subject:
Reading e-mails it seems that they didn't want to put too much developer time into it. Now I don't know if that is because they wanted to get a 1.1.5 out or they just don't want to do it. I think it's a bad decision, but I don't work on these things so I don't know what's involved.
_________________
Adam Moore
OpenDocument Fellowship
Adam.Moore@opendocumentfellowship.org
Demand Microsoft Support OpenDocument
http://opendocumentfellowship.org/petition/
Back to top
Display posts from previous:   
   NeoOffice Forum Index -> NeoOffice Development All times are GMT - 7 Hours
Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group

All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © Planamesa Inc.
NeoOffice is a registered trademark of Planamesa Inc. and may not be used without permission.
PHP-Nuke Copyright © 2005 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.