[Vtigercrm-developers] New Extensions Store! - Take a Tour

[Holbok István]

Dear Vtiger Team and All other list members,

There are several good examples how to organize module install manager. 
Please look at the Joomla! project solutions:



This approach can be utilized by the vtiger project also.
In the Joomla! project you can find a method to
- install from the web (e.g. from the vtiger store)
- install from package (this method was used in earlier vtiger version), 
the package can be placed in a directory or in a URL

and there is a method to install extension by Discover.

For the vtiger - counting future demands - would be very useful:

  * possibility to install from vtiger store
  * possibility to install from package
  * possibility to install by bootstrap string (for developing using
    vtlib API)
  * or possibility to install by CLI

And should be there a possibility to Update all earlier installed 
extensions.

I do not suggest to close any earlier used possibility to install 
extensions into vtiger.
By my opinion the install from store possibility should be an extra over 
the earlier used methods but not a replacement.

Kindest regards:
Istvan


üdvözlettel:

*Holbok István*

+3670-342-0900
*e-mail:* holbok at gmail.com
*SkyPe:* holboki

2014.06.23. 10:29 keltezéssel, Sreenivas Kanumuru írta:
> 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.
>
> Blazej,
>
>     /If you will not publish modules that modifying system files, we
>     are forced to create our own fork./
>
>
> 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).
>
> Andrew,
>
>     /I understand that after migration from 6.0 to 6.1 custom modules
>     will not be migrated but i have to install 'em manually.
>     It means that database tables will be untouched. Is it correct?/
>
>
> 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).
>
>     /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. /
>
>
> 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.
>
> Regards,
> Sreenivas
>
>
> On Mon, Jun 23, 2014 at 12:33 PM, Matteo Baranzoni 
> <info at greenbitweb.com <mailto:info at greenbitweb.com>> wrote:
>
>     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!
>
>
>     2014-06-23 8:31 GMT+02:00 Pabiszczak, Błażej
>     <b.pabiszczak at opensaas.pl <mailto:b.pabiszczak at opensaas.pl>>:
>
>         Hi
>
>             Even if we publish an extension, we will list similar
>             extensions published by other developers, as long as they
>             meet the guidelines (*_not modifying system files_*).
>
>
>         If you will not publish modules that modifying system files,
>         we are forced to create our own fork.
>
>         Z poważaniem / Regards
>         Błażej Pabiszczak
>         M: +48.884999123 <tel:%2B48.884999123>
>         E: b.pabiszczak at opensaas.pl <mailto:b.pabiszczak at opensaas.pl>
>
>         _______________________________________________
>         http://www.vtiger.com/
>
>
>
>     _______________________________________________
>     http://www.vtiger.com/
>
>
>
>
> _______________________________________________
> http://www.vtiger.com/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20140623/7687b958/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: joomla-vtiger.png
Type: image/png
Size: 188009 bytes
Desc: not available
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20140623/7687b958/attachment-0001.png>