search

sawhney17 / logseq-smartblocks

MIT License
171 stars 12 forks source link

Can we create a dropdown as input source? #14

Closed rodrigofaerman closed 2 years ago

rodrigofaerman commented 2 years ago

was wondering if it is possible to create a dropdown as input source? instead of creating a variable with <%setinput: inputName%>, I would pre-populate a list of values to then selecte one of them.

Tvs3d5uw

i have a different number of events, for example. i would populate as possible input those 5 options, and then select one.

Meh-S-Eze commented 2 years ago

This would great! If I am understanding it correctly. I was hoping to try an convert a smartblock from roam research over to logseq and this feature request would be superhelpful https://github.com/dvargas92495/SmartBlocks/issues/104

piyush-das commented 2 years ago

This would indeed be a great feature. For example say some of my notes have a difficulty property and the only valid options would perhaps be ["Easy", "Medium", "Hard"]. And during taking the input for template rendering perhaps these values can be displayed for the user to pick from. Not only would this lead to better ease of use, but would also ensure that the particular properties always take the right value since selecting from a list of options would make sure there are no Typos.

Hopefully this feature request does get incorporated. Thanks

sawhney17 commented 2 years ago

This is the feature I’ll be working on next.

Any ideas for the syntax?

<%setInput: event{call, hang up, hello, bye}%>

This would create an event block with 4 options, call, hang up, hello and bye On 12 Jun 2022, 9:37 AM +0400, piyush-das @.***>, wrote:

This would indeed be a great feature. For example say some of my notes have a difficulty property and the only valid options would perhaps be ["Easy", "Medium", "Hard"]. And during taking the input for template rendering perhaps these values can be displayed for the user to pick from. Not only would this lead to better ease of use, but would also ensure that the particular tags always take the right value since selecting from a list of options would make sure there are no Typos. Hopefully this feature request does get incorporated. Thanks — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

rodrigofaerman commented 2 years ago

I think it's perfect.

would those values be considered as pages, or we can explicitly declare with [[ ]]?

On Sun, Jun 12 2022 at 3:04 AM, sawhney17 < @.*** > wrote:

This is the feature I’ll be working on next.

Any ideas for the syntax?

<%setInput: event{call, hang up, hello, bye}%>

This would create an event block with 4 options, call, hang up, hello and bye On 12 Jun 2022, 9:37 AM +0400, piyush-das @.***>, wrote:

This would indeed be a great feature. For example say some of my notes have a difficulty property and the only valid options would perhaps be ["Easy", "Medium", "Hard"]. And during taking the input for template rendering perhaps these values can be displayed for the user to pick from. Not only would this lead to better ease of use, but would also ensure that the particular tags always take the right value since selecting from a list of options would make sure there are no Typos. Hopefully this feature request does get incorporated. Thanks — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub ( https://github.com/sawhney17/logseq-smartblocks/issues/14#issuecomment-1153080401 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AADMQNV3HW3RIPR2MTI45V3VOV4XJANCNFSM5TST3OIQ ). You are receiving this because you authored the thread. Message ID: <sawhney17/logseq-smartblocks/issues/14/1153080401 @ github. com>

sawhney17 commented 1 year ago

I'm thinking explicit declaration.  Just like with the current implementation of set input. You can still of course use other commands like current page, NLP etc. On 12 Jun 2022 at 7:57 PM +0400, Rodrigo Faerman @.***>, wrote:

I think it's perfect.

would those values be considered as pages, or we can explicitly declare with [[ ]]?

On Sun, Jun 12 2022 at 3:04 AM, sawhney17 < @.*** > wrote:

This is the feature I’ll be working on next.

Any ideas for the syntax?

<%setInput: event{call, hang up, hello, bye}%>

This would create an event block with 4 options, call, hang up, hello and bye On 12 Jun 2022, 9:37 AM +0400, piyush-das @.***>, wrote:

This would indeed be a great feature. For example say some of my notes have a difficulty property and the only valid options would perhaps be ["Easy", "Medium", "Hard"]. And during taking the input for template rendering perhaps these values can be displayed for the user to pick from. Not only would this lead to better ease of use, but would also ensure that the particular tags always take the right value since selecting from a list of options would make sure there are no Typos. Hopefully this feature request does get incorporated. Thanks — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub ( https://github.com/sawhney17/logseq-smartblocks/issues/14#issuecomment-1153080401 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AADMQNV3HW3RIPR2MTI45V3VOV4XJANCNFSM5TST3OIQ ). You are receiving this because you authored the thread. Message ID: <sawhney17/logseq-smartblocks/issues/14/1153080401 @ github. com>

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>