[Vtigercrm-developers] about new template manager (Vtiger 6.4)

[Prasad]

Thank you for the order of fallback - which sounds good - I see a gap in
our understanding of what Layout refers to.

Layout defines the overall UI structure of the application.
If the intent is to extend part of it doing with (headerscript or skins is
a choice).

The structural changes between layouts could be vast and depends on the its
feature sets.
v7 falling back on vlayout (6.0) is unlikely a choice with respect UI
matchup. However, v7
itself would have fallback UI for custom module view.

Regards,
Prasad

PS: v7 layout is still under development and being improved. It would
possibly be released in other 8-12 months.


--
FB <http://www.facebook.com/vtiger> I Twit <http://twitter.com/vtigercrm> I
LIn <https://www.linkedin.com/company/1270573?trk=tyah> I Blog
<https://blogs.vtiger.com> I Website <https://www.vtiger.com/>

On Mon, Nov 9, 2015 at 3:09 PM, makeyourcloud <info at makeyourcloud.com>
wrote:

> Hi,
>
> To be more detailed, I think the right fallback checks for vTiger could be
> in the following order and should be done for each type of layout resources
> (tpl,js and css):
>
> FALL BACK ORDER
> 1 - customlayoutname/modules/ModuleName/FileName
> 2 - vlayout/modules/ModuleName/FileName
> 3 - customlayoutname/modules/Vtiger/FileName
> 4 - vlayout/modules/Vtiger/FileName
>
> Hope this could be a good starting point, I don’t want to open another
> discussion but I would just to clarify that we choose to not directly
> collaborate with vtiger community team (committing fixes and patches)
> because we are disappointed seeing how  many differences (fundamental
> optimizations) are present between the ondemand version and our poor
> opensource version, I think the community could do more and share more,
> improving the 2 platforms, but we think that this collaboration must be two
> way, and not just 1 and 1/4 way as it seems to be now!
>
> It would be a really good starting point to share the new bootstrap3 layout
> present in the ondemand version, so the community could have a base updated
> layout to work on, also we could define bootstrap3 as the new STANDARD
> official css framework for vTiger, so there will be no major problems
> managing the fallback layouts with the purposed solution and the extensions
> developers could simply update their extension layouts to merge the new
> bootstrap 3  classes, with the advantage that a module developed for the
> community edition could be made available also for the on demand version
> following the same structure.
>
> If there is a remote possibility to share the v7 layout we will start doing
> some collaboration and warrantee our first one will be the fallback
> solution, if no one does not do it first.
>
>
>
>
> Kind Regards,
> Federico Bempensato,
> MakeYourCloud Development Team - http://www.makeyourcloud.com
>
>
>
> --
> View this message in context:
> http://vtiger-crm.2324883.n4.nabble.com/Vtigercrm-developers-about-new-template-manager-Vtiger-6-4-tp17848p17863.html
> Sent from the vtigercrm-developers mailing list archive at Nabble.com.
>
> _______________________________________________
> http://www.vtiger.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20151109/5cd6b282/attachment.html>