<HTML><BODY><div><div><div>It is possible that the model we need is in sw/source/core/inc/swfont.hxx.</div><div> </div><div>Also, sorry for the grammatical error, i meant GrabBag, not a GrabBug.</div></div><br><blockquote style="border-left:1px solid #0857A6; margin:10px; padding:0 0 0 10px;">Вторник, 29 августа 2023, 13:26 +04:00 от Амин Иргалиев <irgaliev01@mail.ru>:<br> <div id=""><div class="js-helper js-readmsg-msg"><div><div id="style_16933011880673054781_BODY"><div class="cl_329774"><div>Hi, sorry it took so long to reply, just now we were able to start this task.<br><br>We are found how to remove tint from GrabBug, but we still do not quite understand where the model can be located, in which we need to add a new attribute. As we understand it, you should look in the sw module, but could you tell us exactly where to look?<br><br> <div class="mail-quote-collapse"><blockquote style="border-left:1px solid #0857A6;margin:10px;padding:0 0 0 10px;"><span data-type="sender">Суббота, 22 июля 2023, 13:48 +04:00 от Tomaž Vajngerl <<a href="/compose?To=quikee@gmail.com">quikee@gmail.com</a>>:<br> </span><div data-type="body"><div id=""><div class="js-helper_mr_css_attr js-readmsg-msg_mr_css_attr"><div><div id="style_16900193151701835340_BODY_mr_css_attr">Hi,<br><br>On Thu, Jul 20, 2023 at 4:53PM владислав тараканов<br><<a>vladislav.tarakanov@bk.ru</a>> wrote:<br>><br>> Hello<br>><br>> We, together with irgaliev01@mail.ru, want to try adding support for various text styles (glow, tint, shadow, etc.) in Writer. But we are still only beginner developers, so we would like to ask where exactly in the code should we start fixing this problem? We've previously looked at the oox and sfx2 modules but didn't find anything relevant.<br><br>Great. There are multiple things you need to do to add a missing<br>feature like this:<br>- extend the model to store the additional data about the feature -<br>for example glow radius (inside sw)<br>- use the new data in the model to influence the rendering (inside sw)<br>- access the new data via UNO if needed (sw, offapi)<br>- add file format support for OOXML - import and export (mainly<br>writerfilter, also oox and sw)<br>- add support for ODF - import and export (sw, xmloff)<br>- extend the UI to manipulate the new data (sw)<br><br>I would first make it so that you get the data into the model and that<br>it is properly filled when you open an OOXML file and properly saved<br>to an OOXML file when you save the document. Currently we preserve the<br>data of text effects, but we preserve it by putting it into what we<br>call a "GrabBag". This stores the data inside the model, but only for<br>the purpose that it survives a import/export cycle and not to be a<br>proper part of the model. Tests for these things are in [1] but the<br>import is located in [2] and export is located in [3] - so first you<br>have to change those to not use "GrabBag" anymore for the text effects<br>you want to implement (glow for example) and store the data at the<br>same level that the text color, outline or shadow data is already<br>saved. One you have this, then you can look into how to actually<br>render these things (probably very similar to how shadows are already<br>rendered), but first I would make sure that you have properly solved<br>the model part of this.<br><br>[1] sw/qa/extras/ooxmlexport/ooxmlw14export.cxx<br>[2] writerfilter/source/dmapper/TextEffectsHandler.cxx<br>[3] sw/source/filter/ww8/docxattributeoutput.cxx<br><br>If you have any questions, don't hesitate to ask.<br><br>> --<br>> Vladislav Tarakanov<br><br>Best regards,<br>Tomaž Vajngerl</div></div></div></div></div></blockquote></div> <div> </div><div>--<br>Sincerely,<br>Irgaliev Amin</div><div> </div></div></div></div></div></div></div></blockquote><div> </div><div>--<br>Sincerely,<br>Irgaliev Amin</div><div> </div></div></BODY></HTML>