Live data from Hacker News

LibreOffice tells Oracle to fork off

documentfoundation.org

1–10 of 26 posts

Re: LibreOffice tells Oracle to fork off

#5
post #4

Could someone describe what's the difference between LibreOffice approach and GoOo approach now? Why didn't they build on GoOo, but forked again instead?

Good point. Judging from http://www.documentfoundation.org/supporters/ , which apparently includes Novell and most everybody, they got their ducks in a row.

However, not everybody seems thrilled at http://planet.go-oo.org/ ...

P.S. more coverage over at http://lwn.net

Re: LibreOffice tells Oracle to fork off

#6
Is it just me, or are the OOo .. eh, LibreOffice sources somewhat messy? Just checked out the build repo and the writer repo (http://cgit.freedesktop.org/libreoffice), and I really have to wonder if this kind of arrangement is workable at all.

Now I'm not an insider, so I don't know, by from my lay-man perspective I think the first thing they need to do is clean up the repositories and project structure before anything else is done.

Re: LibreOffice tells Oracle to fork off

#7
post #5
post #4

Could someone describe what's the difference between LibreOffice approach and GoOo approach now? Why didn't they build on GoOo, but forked again instead?

Good point. Judging from http://www.documentfoundation.org/supporters/ , which apparently includes Novell and most everybody, they got their ducks in a row. However, not everybody seems thrilled at http://planet.go-oo.org/ ... P.S. more coverage over at http://lwn.net

Damn it, another misclicked arrow on my phone. sorry about the downvote.

Re: LibreOffice tells Oracle to fork off

#8

Is it just me, or are the OOo .. eh, LibreOffice sources somewhat messy? Just checked out the build repo and the writer repo ( http://cgit.freedesktop.org/libreoffice ), and I really have to wonder if this kind of arrangement is workable at all. Now I'm not an insider, so I don't know, by from my lay-man perspective I think the first thing they need to do is clean up the repositories and project structure before anyt…

Well, it's got some organisation inside. inc/source/tool/data folders are pretty much standard in the whole tree. Everything is very modular. What exactly didn't you like?

On the other hand, I just found this:

    DBG_ASSERT(nTab
Seriously?

Re: LibreOffice tells Oracle to fork off

#9
post #8

Is it just me, or are the OOo .. eh, LibreOffice sources somewhat messy? Just checked out the build repo and the writer repo ( http://cgit.freedesktop.org/libreoffice ), and I really have to wonder if this kind of arrangement is workable at all. Now I'm not an insider, so I don't know, by from my lay-man perspective I think the first thing they need to do is clean up the repositories and project structure before anyt…

Well, it's got some organisation inside. inc/source/tool/data folders are pretty much standard in the whole tree. Everything is very modular. What exactly didn't you like? On the other hand, I just found this: DBG_ASSERT(nTab Seriously?

It's German.

Re: LibreOffice tells Oracle to fork off

#10
post #8

Is it just me, or are the OOo .. eh, LibreOffice sources somewhat messy? Just checked out the build repo and the writer repo ( http://cgit.freedesktop.org/libreoffice ), and I really have to wonder if this kind of arrangement is workable at all. Now I'm not an insider, so I don't know, by from my lay-man perspective I think the first thing they need to do is clean up the repositories and project structure before anyt…

Well, it's got some organisation inside. inc/source/tool/data folders are pretty much standard in the whole tree. Everything is very modular. What exactly didn't you like? On the other hand, I just found this: DBG_ASSERT(nTab Seriously?

if I had to take a guess, I'd say that this code is a relic of the old Star Office days. Remember: Open Office has its root in Star Office which was bought out by Sun back in the days.

Star Office was a product by a german company. While it's really bad style to write non-english code, it's understandable that it might happen in debug code like this and if that assertion is never hit, nobody ever sees it to correct it.

"Tab zu gross" is German for "tab too big"

Post reply on HN