<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Tabbed UI (Writer): Division/section-per-tab (similar to Lotus WordPro)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=33173#c47">Comment # 47</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Tabbed UI (Writer): Division/section-per-tab (similar to Lotus WordPro)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=33173">bug 33173</a>
from <span class="vcard"><a class="email" href="mailto:roland@logikalsolutions.com" title="roland@logikalsolutions.com">roland@logikalsolutions.com</a>
</span></b>
<pre>This needs to return to high priority.
It cannot be done in an AGILE hacking on the fly manner. It has to be
architected.
What also __really__ needs to happen is ensure LO has __all__ of the lwp file
support from Lotus Symphony. I remember Symphony handling lwp waaaay better
than LO currently does.
Ummmm Could the person who uses LWP most days find a nice complex and large lwp
document which could be released publicly? Something with numerous tabbed
divisions, some hidden, some not. Images. Running page headers and footers.
etc.
In short, do you have a book you never finished/published that you don't mind
tossing up here where it will eventually be found by someone who will put it on
Lulu.com for sale without giving you a dime? I go through that with this Java
book.
<a href="https://theminimumyouneedtoknow.com/xbase_book.html">https://theminimumyouneedtoknow.com/xbase_book.html</a>
I wrote and donated the book to the xBaseJ project. It's included in their
download and available as a free PDF elsewhere, yet I continually have to scan
Lulu.com and other "upload and go" book sites that check absolutely nothing
because people keep trying to sell a POD printed version for $35.
I checked my remaining lwp files the other day. The only files I still have
left is documentation I did for Navistar. The systems are still in use and the
company is still in business, so those can't be placed in the wild. They also
weren't complex enough.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>