This is a great module! I feel that the current JSONP SPARQL block settings all located in the same settings page could be split into a settings page for each block. One of the reasons for this is the vertical tabs which right now are hiding a lot of form elements, including required ones, which is not best UX practice. I feel like having a overview of existing JSONP SPARQL blocks with a button to edit each separately would be better. On each block setting form, you could then expand all the vertical tabs (turning them into regular fieldsets). Another advantage of this is that the user would not be limited to 4 blocks, but could add as many JSONP SPARQL blocks as needed.

Does that make sense?

Comments

eiriksm’s picture

eiriksm
he/him
Primary language Norwegian Bokmål
Location Norway
commented

This makes very much sense, and I have to admit that the reason it is set up like this was just because it started with a much simpler form and just one block. The number 4 of course is just randomly chosen.

So I would say that the UX suffered from extending the configurable options. Will look into it. And the tokens also, would make for more options for users that does not have the php filter access.

Thanks for testing!

eiriksm’s picture

eiriksm
he/him
Primary language Norwegian Bokmål
Location Norway
commented
Status: Active » Fixed

All these ideas are now implemented. Settings are now at block config, you can have an unlimited number of blocks, and you can use token values for input.

This makes for extended functionality and better UX. Thanks to scor for ideas! Please feel free to test if you are reading this update.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.