Mathias asks, concerning [Issue 4914],
Can any developer tell whether there is any progress
since 2007 or explain, if there are technical
limitations for it?
+1 on that question.
-- replying below to --
From: Mathias Röllig [mailto:[email protected]]
Sent: Wednesday, February 11, 2015 03:22
To: Development AOO
Subject: annotations to [Issue 4914] "normal" view option needed
Hallo!
Can any developer tell whether there is any progress since 2007 or
explain, if there are technical limitations for it?
https://issues.apache.org/ooo/show_bug.cgi?id=4914#c40
http://wiki.services.openoffice.org/wiki/Writer_Views
In my opinion this feature should get a higher priority (if there is any
at the moment).
Regards, Mathias
<orcmid>
Mathias points the importance of progress on
https://issues.apache.org/ooo/show_bug.cgi?id=4914
http://wiki.services.openoffice.org/wiki/Writer_Views
Agreed. [Issue 4914] is amazing. A feature request that gets 281 votes is
certainly not trivial (either in importance or in difficulty to implement).
That this has been lingering since 2002 is remarkable.
I suspect this was closed as RESOLVED FIXED prematurely, apparently over
confusion about what happens when print layout view is deselected.
It's not a bug report but a feature-request issue. I am not clear whether
confirmation is required, but it is easy to verify.
The wiki page goes into more analysis. There probably needs to be an issue
that depends on 4914 but that specifies exactly what is required for the
specific requested view (excluding outline views, mind-mapping, etc., although
users could do some of this themselves in early skeletal drafts, separate from
automatic features for those purposes).
I foresee three problems:
1. Defining exactly how the view is proposed to work from the user
perspective, with possible iteration based on feasibility of development. I
think <https://wiki.openoffice.org/wiki/Writer_Views#Draft_Layout> is very
close.
2. Coming up with a name that reflects the nature of the view without tying it
to a specific use case. It will need to translate well too. (My first effort
is "Text Flow," thinking that "Draft Text" and "Draft Layout" are too use-case
suggestive. I don't like my first thought. Better ideas are needed. Maybe
"Draft Text" because layout niceties, especially columns and fitting of frames
are not dealt with at that level.)
3. Identifying developers who are available and equipped to work in this area
of the AOO code. I think that means identifying the necessary modifications,
their integration, and their testing at the code level. Having someone with
the capability and availability to undertake this is important. If that can
include mentoring others in working on the code and documenting as necessary,
even better.
Item (3) seems very much to fall into the Priority #2 activity proposed by
Andrea. It all depends on who is willing and capable to step up to this in
competition with other activities such developers are attracted to.
</orcmid>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
