<div dir="ltr"><b>We expect that in the same way it will be solved.</b><br></div><div class="gmail_extra"><br clear="all"><div><div><br></div><div><div>Z poważaniem / Regards</div><div>Błażej Pabiszczak</div><div>M: +48.884999123<br>
E: <a href="mailto:b.pabiszczak@opensaas.pl" target="_blank">b.pabiszczak@opensaas.pl</a></div></div></div>
<br><br><div class="gmail_quote">2014-06-23 11:04 GMT+02:00 Holbok István <span dir="ltr"><<a href="mailto:holbok@gmail.com" target="_blank">holbok@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>Dear Vtiger Team and All other list
members,<br>
<br>
There are several good examples how to organize module install
manager. Please look at the Joomla! project solutions:<br>
<br>
<img alt="" src="cid:part1.06070107.04030100@gmail.com" height="437" width="1200"><br>
<br>
This approach can be utilized by the vtiger project also.<br>
In the Joomla! project you can find a method to<br>
- install from the web (e.g. from the vtiger store)<br>
- install from package (this method was used in earlier vtiger
version), the package can be placed in a directory or in a URL<br>
<br>
and there is a method to install extension by Discover.<br>
<br>
For the vtiger - counting future demands - would be very useful:<br>
<ul>
<li>possibility to install from vtiger store</li>
<li>possibility to install from package</li>
<li>possibility to install by bootstrap string (for developing
using vtlib API)</li>
<li>or possibility to install by CLI<br>
</li>
</ul>
And should be there a possibility to Update all earlier installed
extensions.<br>
<br>
I do not suggest to close any earlier used possibility to install
extensions into vtiger. <br>
By my opinion the install from store possibility should be an
extra over the earlier used methods but not a replacement.<br>
<br>
Kindest regards:<br>
Istvan<br>
<br>
<br>
<div>üdvözlettel:<br>
<br>
<b>Holbok István</b><br>
<br>
+3670-342-0900<br>
<b>e-mail:</b> <a href="mailto:holbok@gmail.com" target="_blank">holbok@gmail.com</a><br>
<b>SkyPe:</b> holboki<br>
<br>
</div>
2014.06.23. 10:29 keltezéssel, Sreenivas Kanumuru írta:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Yes, Matteo. We will improve framework APIs to
reduce the need to modify system files. We understand that is
important for the success of the Store.
<div>
<div class="gmail_extra">
<div><br>
</div>
Blazej, </div>
<div class="gmail_extra"><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><i>If
you will not publish modules that modifying system files,
we are forced to create our own fork.</i></blockquote>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Console (command line tool) will
allow the installation of such modules that are not listed
on the store. It is a complementary tool that will be useful
for developers and users who want to install extensions that
are not yet published on the store. In essence, there are 2
ways to install extensions. first through the store
(certainly more easier), and the other is through the
Console. If we are finding that users are having difficulty
with the Console, then we will try to provide a UI for the
console (that is separate from the store).<br>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Andrew,</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">
<blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex" class="gmail_quote">
<i>I understand that after migration from 6.0 to 6.1
custom modules will not be migrated but i have to
install 'em manually.<br>
It means that database tables will be untouched. Is it
correct?</i></blockquote>
</div>
<div class="gmail_extra">
<br>
</div>
<div class="gmail_extra">Yes, upgrading framework from 6.0 to
6.1 will leave custom modules untouched. They will need to
be updated manually through the Store (possible only if the
name matche) , or from outside the store (through the
Console).</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">
<blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex" class="gmail_quote">
<i>Can I claim one extension to be published - email
campaigns? Vtiger really need it to make marketing guys
happy and stick to one app only. </i></blockquote>
<div><br>
</div>
</div>
<div class="gmail_extra">Thanks for the suggestion. We are
discussing internally on the On Demand features we can
release to open source and support well. I expect we will be
releasing a couple of extensions initially (Quickbooks,
Magento connectors for example) and add more over time.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Regards,</div>
<div class="gmail_extra">Sreenivas</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">
<div class="gmail_quote">
On Mon, Jun 23, 2014 at 12:33 PM, Matteo Baranzoni <span dir="ltr"><<a href="mailto:info@greenbitweb.com" target="_blank">info@greenbitweb.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">I think that not allow modifyng system
files in extensione store was the only possible
solution but vtiger needs to improve to ensure that
they are not necessary!
<div> </div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2014-06-23 8:31 GMT+02:00
Pabiszczak, Błażej <span dir="ltr"><<a href="mailto:b.pabiszczak@opensaas.pl" target="_blank">b.pabiszczak@opensaas.pl</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>
<div>
<div dir="ltr">
<div><span style="font-family:arial,sans-serif;font-size:13px">Hi</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">
<div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div>
</span>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-family:arial,sans-serif;font-size:13px"><font color="#0000ff">Even if we publish
an extension, we will list similar
extensions published by other
developers, as long as they meet the
guidelines</font> (<b><u><font color="#ff0000">not modifying
system files</font></u></b>).</span></blockquote>
</div>
<div>
<div><br>
</div>
<div>If you will not publish modules that
modifying system files, we are forced to
create our own fork.<br>
</div>
<div>
<div><br>
</div>
<div>
<div>Z poważaniem / Regards</div>
<div>Błażej Pabiszczak</div>
<div>M: <a href="tel:%2B48.884999123" value="+48884999123" target="_blank">+48.884999123</a><br>
E: <a href="mailto:b.pabiszczak@opensaas.pl" target="_blank">b.pabiszczak@opensaas.pl</a></div>
</div>
</div>
</div>
</div>
<br>
</div>
</div>
_______________________________________________<br>
<a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><br>
</blockquote>
</div>
<br>
</div>
<br>
_______________________________________________<br>
<a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
<a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a></pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
<a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><br></blockquote></div><br></div>