Note that I'm calling the first argument in the ulink input string (currently 'l') the "trigger". Maybe there is another term for it...

My suggestion is to allow the user, via the ulink settings page, to define aliases/macros the would allow a user supplied trigger keyword to be mapped to a supported ulink expression.

An example - instead of having to do all of this to get an image gallery:

|l|files/photos/...||filter=image|

a user could define an 'igallery' trigger keyword such that it would have the same effect, but they would only have to enter

|igallery|files/photos/...|

in their node content.

Comments

garthee’s picture

garthee commented

Sorry for the late follow up..

I am trying to cover this along with the Auto completion module as its benefit will be greater only if it is going along with that.. Soon this feature will be added. However I am thinking about implementing that using MACRO as well..

garthee’s picture

garthee commented
Status: Active » Closed (fixed)

now it has been implemented.. but only in a basic form, which will will be further improved in future.. thanks