<div>Joe,</div>
<div> </div>
<div>I'm with you ! I can help by providing a list of all the things I've had to modify in the core to add my modules in vtiger.</div>
<div> </div>
<div>David V.<br><br> </div>
<div><span class="gmail_quote">2007/6/19, Joe Bordes <<a href="mailto:joe@tsolucio.com">joe@tsolucio.com</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi Richie,<br><br>Yes, me again. You knew I was going to answer, right? :-))<br><br>Having already seen the code and the implications of modularization of
<br>vtigerCRM I would focus this goal in a very pratical way.<br><br>- I would start by trying to create a new module for vtigerCRM and watch<br>myself all the way.<br>- Every step should be studied and the implicated files/code must be
<br>marked to be changed so it can be module independent and parameters<br>added to a new Admin-Module-Control-Section<br>- Once all the code dependencies detected we must decide the best way to<br>make them independent and clean up the code
<br>- All parameters should be coupled together in a plugin.xml file who's<br>structure must be documented.<br>- Once we have an easy way to plugin a module I would grab the fantastic<br>work that has already been done on the forge-module project and modifiy
<br>it to adapt to the new situation.<br>- With this and a new section to help install/uninstall modules we<br>should get a preatty good module control with a grphical interface to<br>create/install/uninstall modules.<br>
<br>I discard the options of making big structural changes and spending a<br>lot of time looking how others have done it because I don't wan't to<br>break any of the currently working modules while we spend the next 6
<br>months talking of how wonderful it is going to be. vtigerCRM's code base<br>is too tightly coupled to try and make a "different" kind of module<br>control. You might just as well start from scratch and build it with
<br>modularity in mind.<br><br>The only other thing I would change is the activity dependency you have<br>in the code. It is terrible and makes it very difficult to add different<br>types of tasks/activities. This would also benefit those modules
<br>(tsprojects) that need to add these kind of features.<br><br>Obviously you know I have been waiting for this opportunity for a very<br>long time and I have been on your back for just as much time. I firmly<br>believe that this is the most important thing vtigerCRM needs right now
<br>and I am willing to help.<br><br>I can be more concise in the details if you need me to be.<br><br>As before (always) I am waiting for you to contact me.<br><br>Regards, Joe<br>TSolucio<br><br><br>richie escribió:<br>
> Dear Team,<br>><br>> Modularization is an important need for vtiger.<br>> I would like to get your ideas on this front please.<br>><br>> Thanks,<br>> *Richie*<br>> ------------------------------------------------------------------------
<br>><br>> _______________________________________________<br>> Reach hundreds of potential candidates - <a href="http://jobs.vtiger.com">http://jobs.vtiger.com</a><br><br>_______________________________________________
<br>Reach hundreds of potential candidates - <a href="http://jobs.vtiger.com">http://jobs.vtiger.com</a><br></blockquote></div><br>