Home | Blog | Software | Reviews and Features | Forum | Help | Donate | About us
topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • December 09, 2016, 08:56:42 PM
  • Proudly celebrating 10 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: Plugin related feature requests  (Read 4809 times)

phitsc

  • Honorary Member
  • Joined in 2008
  • **
  • Posts: 1,187
    • View Profile
    • Donate to Member
Plugin related feature requests
« on: October 21, 2008, 05:54:38 AM »
During the development of FarrMilk a few things came to my mind which would have given me further possibilities to enhance FarrMilk's user experience. I'd like to put these up for public discussion. None of these are essential for FarrMilk and they could well be totally unnecessary for a lot of other plugins. The reason I post these here (I've sent them to mouser a few weeks ago) is so that other plugin writers can offer their opinion of how useful these features would be to them.

1. It would be good for plugins if they could query (and possibly set) certain FARR options. A couple of examples:
 - With the option 'Hide when focus is lost' set FarrMilk currently can't complete the authorisation process. It would be good if the plugin could temporarily disable that option and put it back once authorisation is complete, or at least tell the user to do so.
 - I'm currently assuming that the user has 'Max. entries to display in normal results' set to 9 (and specify so in the help file). But if the plugin could query this value, it could present certain results in a more dynamic manner, i.e. only using the first (Max - 1) results and make the last one a 'More' entry.
 - Another requirement is that the user is showing the Location column. Well, the plugin works without this but it wouldn't be obvious to the user what he misses. So I think it would be good if the plugin could at least tell the user that he could enable the Location column to enhance his user experience.

2. To further enhance the power of the list view it would be cool if it was possible for plugins to do certain formatting of the output, stuff like bold, italics, etc. and using colours. For FarrMilk I would currently use that to better highlight overdue tasks (currently I print a * behind overdue tasks) and to display the matching part on substring matching of a list name (or whatever), e.g. if the user typed blah '/list=mi' I would print 'List: Farrmilk' to show that it matches the FarrMilk list.

3. Plugins like FarrMilk have no use for the Score value. It would be cool if the Score line in the results could be used like the Location column to display additional information. In FarrMilk I would probably move the URL there or show titles of notes.

4. If plugins could be triggered on keyboard input other than the current Enter / F-key that would offer additional possibilities. In the context of FarrMilk I'm thinking about making it possible to complete tasks by selecting it and the pressing 'c', or deleting it by selecting it and then pressing 'DEL', stuff like that.

czb

  • Honorary Member
  • Joined in 2007
  • **
  • Posts: 336
    • View Profile
    • My open-source online piano game
    • Donate to Member
Re: Plugin related feature requests
« Reply #1 on: October 21, 2008, 09:46:47 AM »
It sounds to me like you need completely rewriten list mode. Fot that I would create my own "list mode" in HTML view mode (since I know javascript only :-[ ) and do all the necessary stuff there using premade libraries like scriptaculous etc. You would be able to solve all the issues mentioned ;)

Or I think you can get handle of the window a put there anything you wish. This might also solve that?

BTW: if you decide to write your own list mode pls share ;)
My open-source online piano game: https://github.com/musicope/game

s.newave

  • Supporting Member
  • Joined in 2006
  • **
  • default avatar
  • Posts: 124
    • View Profile
    • Donate to Member
Re: Plugin related feature requests
« Reply #2 on: October 21, 2008, 12:13:31 PM »
phitsc all great ideas that i would love to see implemented. I think a lot of your requests could be satisfied when Mouser releases the long awaited gridmode :D. Not sure how far away it is but ideally this will give plugin writers complete control of which columns/rows they can display and what their content is.

I had also asked Mouser about cell formatting and i believe he had said something about support for bold, italics, and underline although i could be wrong. It would be great to be able to specify color, font size etc.

The holy grail would be some type of gridmode that supports html cells. As czechboy mentions this is somewhat possible using javascript and html mode which he used for his Table Data plugin. The only limitation with this technique is its limited interface with FARR itself. For example it would be great to be able to scroll through results with the up/down arrow keys, be able to launch or perform actions on a result etc.. I'm sure this is possible using html/js but it might require some work.

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 36,431
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
Re: Plugin related feature requests
« Reply #3 on: October 26, 2008, 07:50:35 AM »
as newave hints, i have planned to offer a gridmode to plugin writers, that will let you output any number of columns in any format you want.  i *will* be writing this.  but you may have to wait a couple of months as i work my way through all of my programs.

phitsc

  • Honorary Member
  • Joined in 2008
  • **
  • Posts: 1,187
    • View Profile
    • Donate to Member
Re: Plugin related feature requests
« Reply #4 on: October 26, 2008, 03:22:32 PM »
That's obviously not what I wanted to hear ;). I understand though that you have long term plans with FARR and that they don't correspond with my immediate needs. In context with these long term plans my suggestions might even seem to be wasted time. What I tried to suggest was stuff which I thought would be fairly easy to implement (well, probably not point 2, and I can obviously only guess as I have never seen any FARR source code) but would offer new possibilities for plugins immediately.

To be honest, I'm actually pretty happy with list mode, even as it is now. I think I have shown with FarrMilk that it can already now be used to implement quite powerful plugins (that's what I hope at least). I can see that with the planned grid mode, much more would be possible. I'm just not sure if it's worth the effort when with (what I think) much less effort it would be possible to sufficiently improve what is already there.

These ideas and suggestions are obviously from my very limited view, which stems from my personal requirements of what I think FARR should do for me (besides launching applications of course). The amazing variety of existing FARR plugins shows me though that the public requirements are much broader than my own. The intent of this thread was to show me (and you in the end) how important certain features that would be relevant to me right now would be to others willing to extend FARR's functionality. Well, I think I got my answer.

s.newave

  • Supporting Member
  • Joined in 2006
  • **
  • default avatar
  • Posts: 124
    • View Profile
    • Donate to Member
Re: Plugin related feature requests
« Reply #5 on: October 26, 2008, 03:38:48 PM »
I was also hoping that gridmode might have been a few weeks out instead of months but to be honest im continually amazed at how fast and responsive you are whilst managing so many different projects.

1. It would be good for plugins if they could query (and possibly set) certain FARR options. A couple of examples:
 - With the option 'Hide when focus is lost' set FarrMilk currently can't complete the authorisation process. It would be good if the plugin could temporarily disable that option and put it back once authorisation is complete, or at least tell the user to do so.
 - I'm currently assuming that the user has 'Max. entries to display in normal results' set to 9 (and specify so in the help file). But if the plugin could query this value, it could present certain results in a more dynamic manner, i.e. only using the first (Max - 1) results and make the last one a 'More' entry.
 - Another requirement is that the user is showing the Location column. Well, the plugin works without this but it wouldn't be obvious to the user what he misses. So I think it would be good if the plugin could at least tell the user that he could enable the Location column to enhance his user experience.

Have to agree with all points mentioned above and i have often times wished that plugins could be able to specify at least which columns/rows are displayed and perhaps even which display style (large vs report).

It would also be great if these fields could be turned on/off for each result. For example certain options such as those used to navigate a plugin or simply to display status info may not need the same fields displayed as other results. Would definitely tidy the display up a little make using the plugin more intuitive.

phitsc

  • Honorary Member
  • Joined in 2008
  • **
  • Posts: 1,187
    • View Profile
    • Donate to Member
Re: Plugin related feature requests
« Reply #6 on: April 21, 2009, 03:00:01 PM »
3. Plugins like FarrMilk have no use for the Score value. It would be cool if the Score line in the results could be used like the Location column to display additional information. In FarrMilk I would probably move the URL there or show titles of notes.

Mouser, I had an idea today how this could be done in a very pragmatic way (maybe). Although you'll probably not like the idea, I'm going to offer it anyway. To repeat the problem: Most plugins using the list view probably have no use for the Score line (or the type or date for that matter). For these, the Score line is wasted space which could be used to display additional information. If FARR accepted a two line groupname (e.g. divided with \n), it could display the second line where the Score is now displayed. While probably kind of obscure, at least this would leave the plugin interface unchanged.