<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">1 - Unfortunately we're in the same
boat. I am hoping that at least some vtlib module migrations will
be straight forward, however have ignored this completely so far
as I await a rc.<br>
2 - This is the price we pay for forking the base of the system
right?<br>
<br>
On 20/02/13 10:14, Adam Heinz wrote:<br>
</div>
<blockquote
cite="mid:CAKBdvM9hFzA4JrMComsprkf-XBOvY72BgfHKGvgNGZh2wgiYSw@mail.gmail.com"
type="cite">
<div dir="ltr">I don't know about anybody else, but in order to
migrate to vt6, I'm looking at:
<div>1. rewrite sixteen custom modules</div>
<div style="">2. reimplement all vt5 patches for vt6</div>
<div style=""><br>
</div>
<div style="">Without any sort of adapter to provide backwards
compatibility, I am forced to do all this work at once,
instead of being able to spread it out over time as I respond
to our normal queue of bugs and feature requests. As far as
one might "<span
style="font-size:13px;font-family:arial,sans-serif">prefer
one hard redesign, without compatibility," I think that's
only true when you have a deprecation period to make the
transition.</span></div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Feb 19, 2013 at 11:00 AM,
Stefan Warnat <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ich@stefanwarnat.de" target="_blank">ich@stefanwarnat.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> I don't have look at
details of the vtiger6 structure vtiger6 and I think it
isn't a perfect system, <br>
but I think anything inside the modules directory will be
deleted on release date and later modules will be only in
vtiger6 directory.<br>
<br>
My experience is, that files from "modules" Directory
won't be used inside new vtiger6 theme.<br>
<br>
But probably it's true, most/all vtiger developer prefer
one hard redesign, without compatibility, before lots of
little changes, which needs lots of tests/work with every
version.<br>
<br>
<div><small><small>Freelancer@Webdevelopment</small></small><br>
<br>
<small><small><b>Web</b>: <a moz-do-not-send="true"
href="http://www.stefanwarnat.de" target="_blank">http://www.stefanwarnat.de</a></small></small><br>
<small><small><b>Xing</b>: <a moz-do-not-send="true"
href="https://www.xing.com/profile/Stefan_Warnat2"
target="_blank">https://www.xing.com/profile/Stefan_Warnat2</a></small></small><br>
<small><small><b>eMail</b>: <a moz-do-not-send="true"
href="mailto:ich@stefanwarnat.de" target="_blank">ich@stefanwarnat.de</a></small></small><br>
<small><small><b><br>
Telefon</b>: 0162 / 2548568 </small></small><br>
<small><small>(Werktags 12 - 18 Uhr)</small></small><br>
</div>
<br>
Am 19.02.2013 16:36, schrieb Adam Heinz:
<blockquote type="cite">
<div>
<div class="h5">
<div dir="ltr">"Keep the vtiger6 code operational?"
How about keeping the vtiger5 code operational?!
You forked your own modules to create the vtiger6
subfolder. I have no idea how I'm supposed to
merge a branch that contains a partial copy of
itself, much less attempt to preserve any sort of
merge/edit history. This is the largest bowl of
copy pasta I've ever encountered in fifteen years
of professional development. It shows a grave
lack of restraint and/or understanding of how to
refactor a system while keeping it operational.</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Feb 18, 2013 at
11:30 PM, Prasad <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:prasad@vtiger.com"
target="_blank">prasad@vtiger.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex"> Adam,
<div><br>
</div>
<div>We did have a look at several frameworks
and evolved a simple one that</div>
<div>can give us better control to keep the
vtiger6 code operational with 5.x while</div>
<div>our dev-team is on making progress.</div>
<div><br>
</div>
<div>Please do share your feedback if you find
anything essentially lacking in vtiger6
framework.<br>
<div><br>
</div>
<div>Regards,</div>
<div>Prasad<br>
<br>
<br>
<div class="gmail_quote">
<div>On Tue, Feb 19, 2013 at 3:06 AM,
Adam Heinz <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:amh@metricwise.net"
target="_blank">amh@metricwise.net</a>></span>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div>
<div dir="ltr">I'm poking around in
vgcal right now and am extremely
glad to see how much Zend code it
uses. Did you guys consider using
ZendFramework 2 MVC instead of
rolling your own for vtiger6?</div>
<br>
</div>
_______________________________________________<br>
<a moz-do-not-send="true"
href="http://www.vtiger.com/"
target="_blank">http://www.vtiger.com/</a><br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
_______________________________________________<br>
<a moz-do-not-send="true"
href="http://www.vtiger.com/"
target="_blank">http://www.vtiger.com/</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<pre>_______________________________________________
<a moz-do-not-send="true" href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a></pre>
</blockquote>
</div>
<br>
_______________________________________________<br>
<a moz-do-not-send="true" href="http://www.vtiger.com/"
target="_blank">http://www.vtiger.com/</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
<a class="moz-txt-link-freetext" href="http://www.vtiger.com/">http://www.vtiger.com/</a></pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Richard Hills
TechnologyWise Ltd, Tauranga, NZ
<a class="moz-txt-link-abbreviated" href="mailto:richard@tw.co.nz">richard@tw.co.nz</a>
<a class="moz-txt-link-abbreviated" href="http://www.technologywise.co.nz">www.technologywise.co.nz</a>
ph: +64 (0)7 571 1060
fax: +64 (0)7 571 1061</pre>
</body>
</html>