ssossossosso

Forums

Covering OroCRM topics, including community updates and company announcements.  Subscribe

This topic contains 2 replies, has 2 voices, and was last updated by Bill Curtis Bill Curtis 3 years, 3 months ago.

  • Creator
    Topic
  • #3702
    Bill Curtis
    Bill Curtis
    Participant

    Hi guys,

    Just installed v1.0.0 and really impressed with the additional modularity for extensions in the UI, specifically with placeholders in twig.

    I have a suggestion to make things more modular. On the OroCRM contact page, I can add placeholders to the ‘Additional Information’ section by my bundle’s placeholders.yml – this is great.

    Taking this a step further, I’d like to add my own section to this page, are there plans for being able to do this via placeholders too?

    Desired result is something like this https://twitter.com/sweettooth/status/451076461596639232/photo/1 (we’ve had to bundle inheritance for this which has potential to conflict with other extensions, ew)

    I think giving devs the ability to add dataBlocks like in Oro/Bundle/UIBundle/Resources/views/actions/view.html.twig line 121 through a placeholder-like config would be awesome.

    Thanks

Viewing 2 replies - 1 through 2 (of 2 total)
  • Author
    Replies
  • #3705
    Dima Soroka
    Dima Soroka
    Oro Core

    You are right, current flexibility of entity views and forms is limited to template override approach and will be a problem in case of multiple extends. We are planning to refactor this in nearest future and allow user to control page layout and elements (fields) as well as allow developer to inject additional sections and blocks without overriding a template.

    #3706
    Bill Curtis
    Bill Curtis
    Participant

    Thanks – looking forward to the update

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.