btw: if I fill bugs in issuezilla, I could be sure (if these will be solved) that there will be another x11 version that pluby can use for neooffice 2.x? I read somewhere that after the intel x11 version the Oo staff will work only on cocoa version. So, I do not want to fill bugs in issuezilla that will be used only in linux and windows version, and not in neooffice version (I do not believe in a cocoa version until I see a working version, I'm still waiting the 1.1.x one).
I'm missing something?
Thank you.
f. _________________ eadem sed non eodem modo facere
Joined: Jun 16, 2003 Posts: 10957 Location: California, USA
Posted: Tue Apr 25, 2006 1:13 pm Post subject:
fabriziovenerandi wrote:
btw: if I fill bugs in issuezilla, I could be sure (if these will be solved) that there will be another x11 version that pluby can use for neooffice 2.x? I read somewhere that after the intel x11 version the Oo staff will work only on cocoa version. So, I do not want to fill bugs in issuezilla that will be used only in linux and windows version, and not in neooffice version (I do not believe in a cocoa version until I see a working version, I'm still waiting the 1.1.x one).
I'm missing something?
I don't use the OOo X11 team's custom builds. Instead, I use the code that Sun uses for OOo's official releases. So, when OOo 2.0.3 comes out, I'll include that code in the next Neo release. Also, while the compiling work that the OOo X11 team does saves me a little time, the savings isn't very much so if they stop doing X11 compiles, it won't affect my work that much. After all, I don't need the X11 vcl code to actually work as I completely replace any X11 code with Java, Cocoa, or Carbon code.
This is probably true. The size of the OOo binaries alone increased from 108 MB to 169 MB with the switch to OOo 2.0.2. OOo 2.0.2 is bigger than OOo 1.1.x.
This is true, but I do not notice this problem with the x11 version and not with the linux version that I try some times ago. I think there is also some optimization coming or alpha problem: for example actually neooffice has closed all the windows and it is using 211mb...
Quote:
I don't use the OOo X11 team's custom builds. Instead, I use the code that Sun uses for OOo's official releases. So, when OOo 2.0.3 comes out, I'll include that code in the next Neo release.
Good to know. When I'll find the time I'll try to use isuezilla for the big problems of the Base.
Thank you for the answers.
f. _________________ eadem sed non eodem modo facere
Joined: Jun 16, 2003 Posts: 10957 Location: California, USA
Posted: Tue Apr 25, 2006 2:49 pm Post subject:
fabriziovenerandi wrote:
This is true, but I do not notice this problem with the x11 version and not with the linux version that I try some times ago. I think there is also some optimization coming or alpha problem: for example actually neooffice has closed all the windows and it is using 211mb...
Are you working with a lot of images? Displaying and scaling images is very memory intensive in NeoOffice Java code. X11's is much faster because it uses Carbon where Java (which uses Cocoa) doesn't handle images nearly as fast or as well.
Joined: Nov 21, 2005 Posts: 1285 Location: Witless Protection Program
Posted: Tue Apr 25, 2006 3:47 pm Post subject:
pluby wrote:
I don't use the OOo X11 team's custom builds. Instead, I use the code that Sun uses for OOo's official releases. So, when OOo 2.0.3 comes out, I'll include that code in the next Neo release.
Also, while the compiling work that the OOo X11 team does saves me a little time, the savings isn't very much so if they stop doing X11 compiles, it won't affect my work that much.
After all, I don't need the X11 vcl code to actually work as I completely replace any X11 code with Java, Cocoa, or Carbon code.
Patrick
Thanks for this information Patrick,
It's good to know that we are not dependant on the X11 efforts. Gives me a little ray of sunshine/hope that NeoOffice will keep getting better and better.
I'm looking forward to testing NeoOffice 2.OH! (sorry, I just like saying that way - no offense meant). Alpha is an excellent start!
Are you working with a lot of images? Displaying and scaling images is very memory intensive in NeoOffice Java code. X11's is much faster because it uses Carbon where Java (which uses Cocoa) doesn't handle images nearly as fast or as well.
I feel it is another kind of problem. I made a simply test this morning: I opened 3 Write files using neooffice 1.2, neooffice 2.0 alpha and openoffice x11 2.0.1. Write files, only text:
Neo 1.2 uses around 130mb
Oo uses around 86mb (plus around 26 of x-stuff)
Neo 2 aplha uses 196mb
After I opened a Write file and a Base file, using neooffice 2.0 alpha e Oo 2.0.1
Oo uses around 90mb (plus around 26 of x-stuff)
Neo 2 alpha uses 210mb
No graphic or image in Write or Base documents. If I can help to investigate where the memory is used let me know how.
f. _________________ eadem sed non eodem modo facere
Joined: Jun 16, 2003 Posts: 10957 Location: California, USA
Posted: Wed Apr 26, 2006 2:17 am Post subject:
This is very interesting data. What is interesting is that I didn't change any of my Java code between Neo 1.2.x and Neo 2.0 Alpha. Can you file a bug in Bugzilla and attach a sample document that I can use to study where the memory differences are?
This is very interesting data. What is interesting is that I didn't change any of my Java code between Neo 1.2.x and Neo 2.0 Alpha. Can you file a bug in Bugzilla and attach a sample document that I can use to study where the memory differences are?
I'm going to file it.
f. _________________ eadem sed non eodem modo facere
Joined: Apr 26, 2006 Posts: 2 Location: Paris, France
Posted: Wed Apr 26, 2006 5:47 am Post subject:
I got the 2.0 Alpha a couple of hours ago and I must say I'm impressed. I don't know where the code has been optimized but it's pretty faster than before. Really nice to work with.
I simply wonder how I could get the UI fonts smaller because they're slightly too big right now.
Thanks val. Gee, those sites were quick off the mark. Bravo to them. There's a little bit of difference in tone between the English and French entries, it seems.
I simply wonder how I could get the UI fonts smaller because they're slightly too big right now.
I'm not sure there's a way to do this in the app itself.
This was done in the past (Neo/J 0.x, Neo/J 1.1 & Neo 1.2.x) via a "dpi hack" which seems not to have been migrated to the new codebase (or doesn't work in the new codebase).
Joined: Jun 16, 2003 Posts: 10957 Location: California, USA
Posted: Wed Apr 26, 2006 1:06 pm Post subject:
sardisson wrote:
This was done in the past (Neo/J 0.x, Neo/J 1.1 & Neo 1.2.x) via a "dpi hack" which seems not to have been migrated to the new codebase (or doesn't work in the new codebase).
Good work! The DPI hack was causing the super large text. I have removed the DPI hack and text size is back to pre-Neo 2.0 Alpha sizes. I'll put this fix in Neo 2.0 Alpha "Patch 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
Forum FAQ
Search
Usergroups
Profile
Private Messages
Log in
)