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

[Prasad]

Thanks for the inputs. I'm not quite clear on the fallback at layout level
(at this moment).

If there is prototype anyone can share - it would be really helpful.

Regards,
Prasad

--
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:31 AM, Richard Hills - Technologywise <
richard at tw.co.nz> wrote:

> Good to see others also see the need for fallback, I will add +1 to this
> and without it see no reason to use the new templating system.
>
>
> On 08/11/15 01:46, makeyourcloud wrote:
>
>> Hi Prasad,
>>
>> I agree with the others about the importance of a fallback solution to
>> manage the views for custom modules,
>>
>> In my opinion (and this is what we had done with our layouts), the vtiger
>> viewer should pick anyway the files from the vlayout dir if the needed
>> files
>> are not availables in the custom layout, so the layout developer could
>> find
>> an alternative way to make the missing view looking well just using custom
>> css rules.
>>
>> As layout developers we could create new layouts customizing just the
>> needed
>> files, for example to create a new layout with just a different navigation
>> bar we could create a simple layout structure with just few files, I think
>> for this simple purpose it would be fine to edit just Header and MenuBar
>> and
>> add the needed js code in the application file.
>>
>> In this way we will work anyway using the core vtiger layout, and if
>> someone
>> would for example develop a new layout using a different css framework (eg
>> bootstrap3 or foundation) it would be a developer choice to adapt the
>> custom
>> module views (eg redefining the missing boostrap2 classes in the css) or
>> create new views adapted for his layout.
>>
>> About your questions:
>>
>> 1 - If we still have the vlayout resources as fallback  files, we can
>> simply
>> choose what file need to change and it would be competence of the layout
>> developer to check that the modified/added files are not corrupted and not
>> cause conflict with other files
>>
>> 2 - The layout developer should consider the option to change framework
>> and
>> in this case should create a totally different layout structure, replacing
>> all the core vtiger files in his layout but choosing a solution for custom
>> modules as explained above
>>
>> 3 - Yes it should.
>>
>> 4 - No, the list view should exactly fallback to the vlayout listview for
>> the  current module (if present) or to the generic vtiger listview, and
>> all
>> files should follow this behavior.
>>
>>
>> Hope this reply will help you understand our needs, and possibly inspire
>> the
>> vtiger team to a new solution for  this.
>>
>> 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-tp17848p17856.html
>> Sent from the vtigercrm-developers mailing list archive at Nabble.com.
>> _______________________________________________
>> http://www.vtiger.com/
>>
>
> --
> Richard Hills
> TechnologyWise Ltd, Tauranga, NZ
> richard at tw.co.nz
> www.technologywise.co.nz
> ph: +64 (0)7 571 1060
> fax: +64 (0)7 571 1061
>
> _______________________________________________
> http://www.vtiger.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20151109/4724f3ac/attachment.html>