[Libreoffice-ux-advise] [Bug 135373] It is impossible to move text blocks independently of the Headings that they're underneath

https://bugs.documentfoundation.org/show_bug.cgi?id=135373

--- Comment #9 from Cougar Brenneman <cougar.b@gmail.com> ---
Created attachment 163926
  --> https://bugs.documentfoundation.org/attachment.cgi?id=163926&action=edit
unintended attachment

Three hours ago, Mike Kaganski asked me to show a screencast of what I'm
talking about, and I don't have the software to make a screencast. So I took
the first six pages from one of my i-Flow books from 2000, which is in a PDF
format, and then pasted those words into MS Word without any format. In the two
hours since then, I have created screenshots of how I organized some of those
sentences into two pages using Word's outliner.

I tried to upload them to Bugzilla, but it wouldn't accept a document with
pictures on it, and it wouldn't accept all of the screenshots that i took. So
you'll find them on the following web page. That took a little more time to
figure out, but they're there now.

https://www.joyfulwisdom.org/steps.html

THESE ARE NOT A FINAL DRAFT! As writing goes, this is pretty ugly.

But what this document does show is how I can use the outliner in Word to begin
to re-create the organization of those first six pages of the i-Flow Developers
Guide — a book I haven't personally read in 20 years. On each page of the final
step-by-step document attached, it shows how I use drag-and-drop on text
elements to sort them into headings.

I'm trying to think of an OOP way of describing this process, but alas, I don't
know OOP well enough. Suffice it to say that what you learned to do in high
school when writing an essay is a little bit like procedural coding, and what
I've done here is implemented a different paradigm of writing — one which
creates a hierarchy of the smallest possible objects and organizes those
concrete objects into children of abstract classes or objects which are also
children of other abstract classes or objects.

Once again, excuse me if this is a poor choice of analogy, but I'm thinking
that it may be a little bit like an abstract factory design pattern modified
for writing. 

I'm sorry if that doesn't make sense to OOP programmers out there, but I'm
studying OOP right now, and it's the best I can do. I've been using this
writing process for 25 years before having any idea what a design pattern is.
I'm just trying to use programming concepts that I'm learning about to describe
what I'm asking for.

-- 
You are receiving this mail because:
You are on the CC list for the bug.