Hi Tobias, If you edit/change TagSearchPlugin. Do you think about my feature request, to enable/disable every element in the tagsearch dialog. It would be nice to have maximum flexibility. -mario
On Oct 5, 7:03 pm, Tobias Beer <[email protected]> wrote: > Mainly @Eric Shulman, > > GotoPlugin has become a valuable resource when it comes to using it in > other plugins [1]. I would want to extend its use even further. For > that however I am facing a few (minor) restrictions or event handling > problems. > > 1) Frst and foremost, please extend function processItem to -- instead > of managing the selected listitem with GotoPlugin internals -- notify > a function that has been registered as an attribute to the input > element to receive a selection notification. > > The code reads like this... > > var n=here.getAttribute('notify'); > //notify of selection > if(n)eval(n+'("'+title+'",here)'); > // otherwise show tiddler (default behaviour) > else story.displayTiddler(null,title); > > Thus the function is being given the selection and a reference to the > input element. The latter is required in order to figure out from > which page element the call came, as in my new plugin there can be > more than one. > > 2) In my new plugin, I am using the GotoPlugin input to enter a new > item title (or select one if present). Hitting enter in the input will > trigger an action in my plugin. However, so it does for > GotoPlugin ...which is to display the select-list. In my case, this is > not wanted as the input loses focus and I have to click or hit ESC to > get back to it. I would therefore be glad if you would allow for > another parameter to not show the results when ENTER is being hit in > an empty input... which is not really required either, as one can use > the down key. > > 3 Embedding the GotoPlugin input field would be simpler if there was a > unique name to the input element that can be used to address it. As I > intend to use two goto inputs in one form... I currently need to wrap > the input in another form element so that I can address it like > this... > > form.gotoForm1.gotoTiddler > form.gotoForm2.gotoTiddler > > So an alternative would be for GotoPlugin by default do the same by > using a form wrapper with display:inline. > > 4) Not dev related... It would be nice if -- when the first listitem > is selected and one hits the up arrow the focus would move back to the > input box again while either leaving the select list open or closing > it... I don't mind much. > > Cheers, Tobias. > > [1]http://tobibeer.tiddlyspace.com/#TagSearch -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
