(In reply to comment #12)
> From outside, copying the implementation from LO-Draw to LO-Writer doesn't 
> seem
> to be much work. I haven't looked into the code yet. Is there someone who can
> really estimate, how much effort it will be to port this from LO-Draw to
> LO-Writer? Is it worth to create a build environment etc.?

I looked a bit into the code:

First of all, a crop button can be added to writer by editing

(draw)
http://cgit.freedesktop.org/libreoffice/core/tree/sw/uiconfig/swriter/toolbar/graphicobjectbar.xml

similar to

(writer)
http://cgit.freedesktop.org/libreoffice/core/tree/sw/uiconfig/swriter/toolbar/graphicobjectbar.xml


The button is then always deactivated and further editing is needed.

The files

(draw) 
http://cgit.freedesktop.org/libreoffice/core/tree/svx/source/tbxctrls/grafctrl.cxx
and
(writer) 
http://cgit.freedesktop.org/libreoffice/core/tree/sw/source/ui/shells/grfsh.cxx

are quite similar.

There are blocks labeled "SID_ATTR_GRAF_CROP" in
SvxGrafAttrHelper::ExecuteGrafAttr() and
SvxGrafAttrHelper::GetGrafAttrState() in the first file.

The corresponding functions SwGrfShell::ExecAttr() and
SwGrfShell::GetAttrState() in the second file have quite similar
structure but have different number of parameters. If I just copy the
Crop-blocks from draw to writer there are a lot of errors of course.


Is there somebody who knows how to translate the draw-part into the 
writer-part? Is translating draw into writer the correct approach or shouldn't 
writer and draw use about the same functions when handling graphics?

Is there some further work to do that I missed?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/491746

Title:
  [Upstream] No interactive crop in Writer

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/491746/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to