First, you have to decide if you want to use Leo as a data store/editor or a metadata store/editor or a combination of both. To understand the difference, let's look at a case study and use Leo for storing books or articles. How would yould you store metadata (author, title, publisher, etc.), abstracts and cover pictures (a kind of metadata), and the full text of articles und books in Leo? What would this mean if outline and body panes were unified?
A librarian would use Leo as a metadata store: He's interested in data *about* books and articles and might use the Leo outline for some higher level metadata (i.e. author, title, publisher, etc.) and the body for some details about the main entrys. These details could as well be stored in the outline itself. Unifying outline and body wouldn't bring much. Storing abstracts in a unified solution might be ok; but storing full text in a unified solution would be disastrous without breaking the text down into headlines, subheadlines, etc - something a librarian definitely is not interested in. An author on the other hand would use Leo as a data store while he develops the structure and text of the book or article. Probably he would benefit from a unified view, because he wouldn't have to jump between outline and body pane. This is the functionality, that - among others - the outline function of Microsoft Word provides. So it's not an either/or, but depends on what you want to do. If you want to combine data and metadata, the existing solution probably is good enough. If you want to edit mainly data, a unified view might be beneficial. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
