Writing Outliner for MS Word Soon on BitsDuJour

Posted by Graham Rhind
Aug 2, 2013 at 04:18 PM

@22111 Yes, this is more or less correct. Nothing is really physically moved as such when you drag things around except the order that WO knows the files needs to be handled in when you output the data into a new (full) Word file. I don’t know about referencing (not something I need or use) and yes, when you drag a branch, it takes the children with it.

@DrAndus: it’s horses for courses. I’ve never had an issue with Word (except its first incarnations in the 1990s, but that’s ancient history) and I need very complex formatting from the very start. I’m not writing in WO, I’m managing documents. Word’s the only word processor I’ve ever come across which can handle the file sizes I need with the formatting and stability I, likewise, need, so I don’t feel the need to look for another tool. But WO saves me a lot of time and grief so for me it’s ideal. It may not suit everybody, naturally ... :-)

Graham

22111 wrote:
I see, and I did not want to spread false info.
> >On bitsdujour, Peter Martin wrote:
> >If only one has the ability to sort the titles (left side) then I would
>say it is perfect.
> >which was left uncommented by the developer there, so I falsely assumed
>the entries could not be moved; it now appears Martin wanted to say (I
>suppose) “sort automatically, alphanumerically” or something along this
>line.
> >So if I understand well:
> >- you have several Word files
> >- you “import” those into a “project” of this tool
> >- then, another day, you load this “project”, which in reality means the
>tool will load all the corresponding Word files, and present their
>structures within a “compound” tree, as if all these separate files were
>one file, and which also means there would be a virtual, global
>structure, in which subtitle 3.5.2 of file 12 would be item 5.8.2 within
>this overall structure?
> >- within this overall structure, you click on any entry, and you gain
>access to the respective Word document, at the respective position
>(hence a click on entry 5.8.2 would “open” document 12 at subtitle 3.5.2
>in this example)?
> >- also, within this overall structure, you freely move parts around, as
>it was one single file, which means if you move around point 1.3.4 after
>point 12.5.6, in the tree, in the actual files the corresponding part
>would be deleted in one file and rewritten at the correct position
>within another of these files?
> >If my above assumptions are right now, I think this should be a
>tremendous piece of software.
>