How to Install an OOo Build from DEV300_m45

I have noticed some of my fellow classmates are still appearing to have some trouble getting the install working from an OOo build. To make their lives easier, and the lives of anyone else trying to do this task, I will post how I got my build to install.

From the DEV300_m45 folder type in:

setup_native/unxlngi6.pro/bin/install /home/bartosz/Desktop/DEV300_m45/instsetoo_native/unxlngi6.pro/OpenOffice/rpm/install/en-US/RPMS /home/bartosz/Desktop/OOoTEST

Obviously you have to change the /home/bartosz/Desktop to wherever you have the DEV folder checked out. Also the last parameter (/home/bartosz/Desktop/OOo) you can change that to whatever you want the installation folder to be.

Then cd into your installation folder, in my case

cd /home/bartosz/Desktop/OOo

then type

./opt/openoffice.org3/program/soffice

or simpress or whatever program you need to run.

Assignment Update

During my talk with Thorsten last week he told me to complete my project I would need to write the master page to the clipboard, to the best of my knowledge that would require me to get a Windows build going since all of the operating systems appear to have different ways of writing to a clipboard.

I found the Windows way of doing it, unfortunately I do not have a Windows build yet. I might get that done over the summer break when I can afford to tie up my computer for 8 hours or more.

I wanted to look for how the other parts of Open Office write to the clipboard since they already must have the code somewhere. So I turned to my trusty friend OpenGrok.

And found some interesting pieces of code: I initially found a clipboard.java file, the file looked very helpful, but of course its just a tutorial so I wanted to look for a real working example. I eventually found a g_clipboard.inc, sadly some of that is not in English. So I translated the text, it sounds like what I've been looking for, but clicking the InhaltEinfuegen name led me to this. Which was not very helpful.

I decided to just try to use the tutorial and fool around with the code myself. Of course I would need to add something to the menu bar. I tried adding an item to the menu bar, but it didn't work out, so I figured there must be other places where the menu items are created.

OOo Class Project Updates

During the past couple weeks, we have had project updates on our Open Office projects. We were told to make notes about the presentations and write a blog about them. My initial reaction was that I realized that everyone is in a similar spot in the project.

The first project that was presented was upgrading to python 2.6. I thought it was a little weird that they don't just spend the extra time and upgrade to 3.0 right away, but the explanation of 3.0 being completly different then 2.6.1 was a good enough reason for me.

The next presentation was improving Impress' style. I am still not quite sure what kind of improvements they want, I guess I'll see next presentation. It was really cool how Daeson would change the code and rebuild during the presentation, even though sometimes the rebuild didn't seem to work.

Building Open Office on Open Solaris seemed like a really cool project, I might want to help out Thiago on this one if I get some free time. Of course that would mean I'd need to install another OS which might take my interest out of the project.

I liked how Ladan showed her bug in action during her presentation. I think the way that Microsoft solves that problem in Excel would probably be the best way for Open Office to solve the bug, but I'm not sure how Ladan plans on solving the issue.

Implementing additional slide show transitions was probably the most graphically appealing presentation. Some of the transitions in the video Jerry showed looked very impressive. However it was weird that a binary output was not generated but dmake was up to date. He says its a source code error, but I assumed a source code error wouldn't result in a dmake up to date message.

Finally understanding Impress. I feel bad for Fred, I hated drawing class diagrams for some of our tiny projects. I dont know how he is going to get one done for something so big.