<div dir="ltr">Hi Richard,<div><br></div><div>thank you very much for this link to TJC! I do tend to forget about TJC as a source of useful information.</div><div><br></div><div>However, in the example for plugin distribution (<a href="https://together.jolla.com/question/10713/create-the-example-of-including-your-own-library-and-standard-qt-module-in-a-harbour-compatible-way/">https://together.jolla.com/question/10713/create-the-example-of-including-your-own-library-and-standard-qt-module-in-a-harbour-compatible-way/</a>), the path for QML imports has been altered in C++ main (<a href="https://github.com/d0b3rm4n/harbour-simpletorch/blob/6c1e36513269cc6f13921fd65ee7c5c222184fa8/src/harbour-simpletorch.cpp#L49">https://github.com/d0b3rm4n/harbour-simpletorch/blob/6c1e36513269cc6f13921fd65ee7c5c222184fa8/src/harbour-simpletorch.cpp#L49</a>). That probably doesn't work for Python-based apps which are expected to be rather prominent users for my plugin. </div><div><br></div><div>Any idea on how to alter QML import path for Python? While we would be probably fine outside the harbour, some devs may publish there as soon as QtLocation debacle is resolved.</div><div><br></div><div><br></div><div>Best wishes,</div><div><br></div><div>Rinigus</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 29, 2017 at 11:20 AM, richard grooff <span dir="ltr"><<a href="mailto:rgrnetalk@yahoo.com" target="_blank">rgrnetalk@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:Helvetica Neue,Helvetica,Arial,sans-serif;font-size:13px"><div></div>
<div>Hi, </div><div><br></div><div>There's some info on this topic in <a href="https://together.jolla.com/question/10713/create-the-example-of-including-your-own-library-and-standard-qt-module-in-a-harbour-compatible-way/" class="m_7304447769356101952enhancr_card_7277660098" target="_blank">this question on tjc</a> (in case you are not aware of it). </div><div><br></div><div id="m_7304447769356101952enhancr_card_7277660098" class="m_7304447769356101952yahoo-link-enhancr-card m_7304447769356101952yahoo-link-enhancr-not-allow-cover m_7304447769356101952ymail-preserve-class m_7304447769356101952ymail-preserve-style" style="max-width:400px;font-family:Helvetica Neue,Helvetica,Segoe UI,Arial,sans-serif"><a href="https://together.jolla.com/question/10713/create-the-example-of-including-your-own-library-and-standard-qt-module-in-a-harbour-compatible-way/" style="text-decoration:none!important;color:#000!important" class="m_7304447769356101952yahoo-enhancr-cardlink" rel="noreferrer" target="_blank"><table border="0" class="m_7304447769356101952card-wrapper m_7304447769356101952yahoo-ignore-table" cellpadding="0" cellspacing="0" style="max-width:400px"><tbody><tr><td width="400"><table border="0" class="m_7304447769356101952card m_7304447769356101952yahoo-ignore-table" cellpadding="0" cellspacing="0" width="100%" style="max-width:400px;border-width:1px;border-style:solid;border-color:rgb(224,228,233);border-radius:2px"><tbody><tr><td><table border="0" class="m_7304447769356101952card-info m_7304447769356101952yahoo-ignore-table" cellpadding="0" cellspacing="0" style="background:#fff;width:100%;max-width:400px;border-radius:0 0 2px 2px;border-top:1px solid rgb(224,228,233)"><tbody><tr><td style="background-color:#ffffff;padding:16px 0 16px 12px;vertical-align:top;border-radius:0 0 0 2px"></td><td style="vertical-align:middle;padding:12px 24px 16px 12px;width:99%;font-family:Helvetica Neue,Helvetica,Segoe UI,Arial,sans-serif;border-radius:0 0 2px 0"><h2 class="m_7304447769356101952card-title" style="font-size:14px;line-height:19px;margin:0 0 6px 0;font-family:Helvetica Neue,Helvetica,Segoe UI,Arial,sans-serif;word-break:break-word;color:#26282a">Create the example of including your own library and standard Qt module ...</h2><p class="m_7304447769356101952card-description" style="font-size:12px;line-height:16px;margin:0px;color:#979ba7;word-break:break-word">Harbour rules let you use only few QML modules and libraries. You can ship libraries and modules together with y...</p></td></tr></tbody></table></td></tr></tbody></table></td></tr></tbody></table></a></div><div><br></div><div>Best regards, Richard </div><div><br></div>
<div id="m_7304447769356101952ydpad1c7fffyahoo_quoted_7134805988" class="m_7304447769356101952ydpad1c7fffyahoo_quoted">
<div style="font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;color:#26282a"><div><div class="h5">
<div>
On Thursday, September 28, 2017, 1:13:55 PM GMT+2, rinigus <<a href="mailto:rinigus.git@gmail.com" target="_blank">rinigus.git@gmail.com</a>> wrote:
</div>
<div><br></div>
<div><br></div>
</div></div><div><div><div class="h5"><div id="m_7304447769356101952ydpad1c7fffyiv7526669267"><div dir="ltr">Hi,<div><br></div><div>I am preparing QML plugin that I would like to distribute. Since this plugin will be used by QML+Python applications, its probably the best to install it into /usr/lib/qt5/qml/PluginName directory. As far as I could see, several plugins are installed like that (QtLocation, for example), while others are using subdirectories to build the hierarchy of plugins. Hence the question: do we have any convention that should be followed in SFOS? Mer?</div><div><br></div><div>I am aware that Jolla Store does not accept third-party plugins at this moment. Hopefully, this will change in future.</div><div><br></div><div>Best wishes,</div><div><br></div><div>Rinigus</div></div></div></div></div>______________________________<wbr>_________________<br>SailfishOS.org Devel mailing list<br>To unsubscribe, please send a mail to <a href="mailto:devel-unsubscribe@lists.sailfishos.org" rel="nofollow" target="_blank">devel-unsubscribe@lists.<wbr>sailfishos.org</a></div>
</div>
</div></div></div></blockquote></div><br></div>