? NPM Resource Changed ? ? Failure

User tests: Successful: Unsuccessful:

avatar dgrammatiko
dgrammatiko
13 Aug 2020

Pull Request for Issue # .

Summary of Changes

This is still work in progress read the comments bellow

Testing Instructions

Actual result BEFORE applying this Pull Request

Expected result AFTER applying this Pull Request

Documentation Changes Required

ad9e909 13 Aug 2020 avatar dgrammatiko Init
avatar dgrammatiko dgrammatiko - open - 13 Aug 2020
avatar dgrammatiko dgrammatiko - change - 13 Aug 2020
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 13 Aug 2020
Category Administration com_templates Language & Strings JavaScript Repository NPM Change Libraries
avatar dgrammatiko
dgrammatiko - comment - 13 Aug 2020

So, as I promised I am going to work on finalising the child templates proposal.
The approach here is the one that was proposed by @Fedik #30149 (comment)

Move button "Create Child" to a template style form, and rename to "Override template files" (or something similar)

Screenshot 2020-08-13 at 12 03 24

This "new template" should not be visible in "templates list", only via template style. (this need to avoid confusing between all these template things)

Screenshot 2020-08-13 at 12 04 34

So far this PR is based on mild changes on the current workflow of com_templates and if this is what people are ok then the code should be ready in the coming days for testing. But since I'm spending some time reworking basically most parts of the component a better workflow, more intuitive could be a better approach here. Let me explain:

  • right now we have 2 list views (templates & styles) that in the component level are not really connected
  • we could merge these 2 list views in one and have a list of the templates (as is right now) with an additional accordion like component so when someone clicks on the template the styles are revealed (and clicking on a style the toolbar reveals the appropriate buttons)
  • also there was some work already done by @kawshar 's team which maybe a good idea to bring it in (I mean if they're ok with it)

Anyways, suggestions, ideas, feedback is welcome here...

avatar kawshar
kawshar - comment - 13 Aug 2020

You are welcome to adopt anything from our concept. For Joomla :)

About the multiple views, we can easily merge both without breaking anything.

avatar brianteeman
brianteeman - comment - 13 Aug 2020

Definitely in favour of merging the template views.

avatar dgrammatiko dgrammatiko - change - 13 Aug 2020
Labels Added: ? NPM Resource Changed ? ?
avatar dgrammatiko
dgrammatiko - comment - 14 Aug 2020

Definitely in favour of merging the template views.

Just a comment here about merging the 2 views together: there are quite some issues that need to be addressed:

  • Extremely hard to get thee filters working with both the templates and their styles
  • The toolbar might need a bit of custom code to follow selections (template/style)
  • pagination
  • probably a few more that I can't even think about right now

That said combining the views is really not that hard (code wise) but we need at least for the first step some sort of design, eg and unstyled, not really functional page was just few lines:
Aug-14-2020 14-51-24

avatar dgrammatiko
dgrammatiko - comment - 1 Apr 2021

moving to #32896

avatar dgrammatiko dgrammatiko - change - 1 Apr 2021
Status Pending Closed
Closed_Date 0000-00-00 00:00:00 2021-04-01 16:58:33
Closed_By dgrammatiko
avatar dgrammatiko dgrammatiko - close - 1 Apr 2021

Add a Comment

Login with GitHub to post a comment