Joe,<div><br></div><div>We install all the packaged modules in Vtiger 6 (without the option disable during install time). </div><div>Post install we plan to design a wizard that lets the administrator to pick the module that is required for the work. Other module can be enabled at-anytime in future without having to install.</div>
<div><br></div><div>Regards,</div><div>Prasad</div><div><br clear="all"><div><span style="border-collapse:collapse;font-family:arial,sans-serif;font-size:13px"><b>Connect with us on: </b><a href="http://twitter.com/vtigercrm" style="color:rgb(0,0,204)" target="_blank">Twitter</a> <b>I</b> <a href="http://www.facebook.com/pages/vtiger/226866697333578?sk=wall" style="color:rgb(0,0,204)" target="_blank">Facebook</a> <b>I</b> <a href="http://blog.vtiger.com/" style="color:rgb(0,0,204)" target="_blank">Blog</a><b> I</b> <a href="http://wiki.vtiger.com/index.php/Main_Page" style="color:rgb(0,0,204)" target="_blank">Wiki</a> <b>I </b><a href="http://forums.vtiger.com/" style="color:rgb(0,0,204)" target="_blank">Forums </a><b>I</b> <a href="http://vtiger.com/" style="color:rgb(0,0,204)" target="_blank">Website</a></span></div>
<br><br><div class="gmail_quote">On Wed, Jul 17, 2013 at 2:56 AM, Joe Bordes <span dir="ltr"><<a href="mailto:joe@tsolucio.com" target="_blank">joe@tsolucio.com</a>></span> wrote:<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>This brings up a doubt I have and that
is happening now in the 5.x versions.<br>
I have translated all modules, mandatory and optional, if you
select all these modules and the es_es language during install,
there is no problem, the modules are installed and then the
language pack fills in the translations into place, but if
somebody decides not to install some optional module then the
language pack creates the language directory for it and the
optional module can't be installed after or somebody deletes the
directory and they lose the translation.<br>
<br>
I see this problem disappears with the new structure of just one
language directory for all modules and base system. So I'm not
sure if you are bringing back this problem or not by maintaining
per-module language files.<br>
<br>
<br>
<br>
El 16/07/13 20:05, Prasad escribió:<br>
</div><div class="im">
<blockquote type="cite"><span style="color:rgb(34,34,34);font-size:13.333333969116211px;font-family:arial,sans-serif">Joe,</span>
<div><span style="color:rgb(34,34,34);font-size:13.333333969116211px;font-family:arial,sans-serif"><br>
</span></div>
<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"><span style="color:rgb(34,34,34);font-size:13.333333969116211px;font-family:arial,sans-serif">Looking
at the structure proposed I don't understand why files like
Assets or Import have been moved to their own module
structure and eliminated from the language directory. I mean
in the previous svn Assets.php was in the main en_us
directory and in this new svn it has been eliminated from
there and put inside the Assets package structure. Then
others like Google are only in their package directory....</span></blockquote>
<div><br>
</div>
<div>Module zip found under packages/ folder are installed at
run-time using vtlib package API (their source are available
in pkg/ of SVN). We plan to a model where modules/ folder will
have some pre-installed (bootstrap) files and then rest be
installed as packages. Assets, Google, ... are a step in this
direction.</div>
<div><br>
</div>
</div>
</blockquote>
<br>
<br>
<br>
<br></div>
Joe<br>
TSolucio<br>
</div>
</blockquote></div><br></div>