https://bugs.freedesktop.org/show_bug.cgi?id=34390
--- Comment #22 from y3kcjd5 <hastra...@gmail.com> --- (In reply to comment #19) > Additionally this report is more or less Invalid, far away from our > guidelines (1 problem per report, ...) > > We will not get any progress by rising importance of all bugs 1 level. But > we can get progress if we find ways how to solve possible problems. > > Step1: > We need a task Bug for tracking all "enhance find and replace capabilities" > (may be we should do that with this one) and separate bug reports for each > single problem. So may be we can make them Easyhacks, what will ease the > task to find a developer very much. Functionally, I'd think that the issue(s) in this bug are essentially the same problem, or at least they should be solvable in pretty much the same way. I haven't looked at code myself, but from what I've gathered reading, the different style types seem to be defined and managed in very similar ways (sounded resemblant of CSS in HTML). That suggests to me that much of the code for this enhancement can be derived from the already present paragraph styles search capability. It would therefore appear to me that adding function for several (frame, list, character etc.) style types would take roughly the same effort as adding just one, making the addition of several style types essentially one single problem. If, however, there is some reason these can only be added one at a time, judging by popular vote, character styles take priority. Creating a task bug may be a good idea, but I would avoid using this one; the contents here are all closely related, whereas some of the other find & replace enhancement requests (e.g. bug 58744) would probably require work in very different parts of the code. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
