|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
|
|
Plugin settings root.Hi,
I was wondering if it would be good if the plugins could have their own hierarchy point in the preference folder. i.e. Currently looks like the "junction" point for a plugin to put their setting page is in one of the values defined in "SettingsConstants". The plugin author can put a setting page where-ever he wants which would not differentiate between SmartSVN internal page or a plugin setting page. I was thinking something like this. A junction point called "Plugin" - the plugin author can then put their plugin page under this node. The user will know that this is related to a plugin and not smartsvn original options. And then plugin author can put their plugin page under that node. This way the end user knows where to find the plugin's setting page. For the plugin that I wrote, I could not find a good location in the existing nodes. It is related to commit, but there is already a commit node. For now i will stick it under commit or actions, but I don't think it is a good place. -prakash ps: I was not sure if the mail was sent the last time... Sending it again. [Non-text portions of this message have been removed] ------------------------------------ Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/smartsvn/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/smartsvn/join (Yahoo! ID required) <*> To change settings via email: mailto:smartsvn-digest@... mailto:smartsvn-fullfeatured@... <*> To unsubscribe from this group, send an email to: smartsvn-unsubscribe@... <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/ |
|
|
Re: Plugin settings root.Hi Prakash,
Adding a plugin should integrate as good as possible into an application. The user should not see, that it has been "plugged in". Hence I think, it would be less good to add plugin-settings pages by default under a certain "Plugin" category. For your plugin, I think the optimal location for the settings would be a subnode below "Commit" (returning the SettingsConstants.GLOBAL_COMMIT in ISettingsPageFactory.getInsertLocation()), because it offers commit-specific options. But if you like, you can also create a page with the name of your plugin (so the user can find it easier) and append it at the end of the list by returning null. -- Best regards, Thomas Singer ============= syntevo GmbH http://www.syntevo.com http://blog.syntevo.com Prakash Nadar <gpnadar@...> wrote: > Hi, > > I was wondering if it would be good if the plugins could have their own > hierarchy point in the preference folder. > > i.e. > Currently looks like the "junction" point for a plugin to put their setting > page is in one of the values defined in "SettingsConstants". The plugin author > can put a setting page where-ever he wants which would not differentiate > between SmartSVN internal page or a plugin setting page. > > I was thinking something like this. > > A junction point called "Plugin" - the plugin author can then put their plugin > page under this node. > The user will know that this is related to a plugin and not smartsvn original > options. > And then plugin author can put their plugin page under that node. This way the > end user knows where to find the plugin's setting page. > > For the plugin that I wrote, I could not find a good location in the existing > nodes. It is related to commit, but there is already a commit node. > For now i will stick it under commit or actions, but I don't think it is a > good place. > > -prakash > > ps: I was not sure if the mail was sent the last time... Sending it again. > > > > > > [Non-text portions of this message have been removed] > > > > ------------------------------------ > > Yahoo! Groups Links > > > > ------------------------------------ Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/smartsvn/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/smartsvn/join (Yahoo! ID required) <*> To change settings via email: mailto:smartsvn-digest@... mailto:smartsvn-fullfeatured@... <*> To unsubscribe from this group, send an email to: smartsvn-unsubscribe@... <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/ |
|
|
|
|
|
Re: Plugin settings root.> Btw, off topic... Is there any plans for SmartHg in the near future?
> (Mercurial) No, but SmartGit is quickly growing: http://www.syntevo.com/smartgit/ -- Best regards, Thomas Singer ============= syntevo GmbH http://www.syntevo.com http://blog.syntevo.com Prakash Nadar <prakash.nadar@...> wrote: > Ok, > > Now I understand how you guys want the plugins to be integrated with > SmartSVN. > > Btw, off topic... Is there any plans for SmartHg in the near future? > (Mercurial) > > -Thanks. > > > On Fri, Oct 9, 2009 at 6:35 AM, syntevo Support <smartsvn@...>wrote: > > > > > > > Hi Prakash, > > > > Adding a plugin should integrate as good as possible into an application. > > The > > user should not see, that it has been "plugged in". Hence I think, it would > > be > > less good to add plugin-settings pages by default under a certain "Plugin" > > category. > > > > For your plugin, I think the optimal location for the settings would be a > > subnode below "Commit" (returning the SettingsConstants.GLOBAL_COMMIT in > > ISettingsPageFactory.getInsertLocation()), because it offers > > commit-specific > > options. But if you like, you can also create a page with the name of your > > plugin (so the user can find it easier) and append it at the end of the > > list > > by returning null. > > > > -- > > Best regards, > > Thomas Singer > > ============= > > syntevo GmbH > > http://www.syntevo.com > > http://blog.syntevo.com > > > > > > Prakash Nadar <gpnadar@... <gpnadar%40yahoo.com>> wrote: > > > > > Hi, > > > > > > I was wondering if it would be good if the plugins could have their own > > > hierarchy point in the preference folder. > > > > > > i.e. > > > Currently looks like the "junction" point for a plugin to put their > > setting > > > page is in one of the values defined in "SettingsConstants". The plugin > > author > > > can put a setting page where-ever he wants which would not differentiate > > > between SmartSVN internal page or a plugin setting page. > > > > > > I was thinking something like this. > > > > > > A junction point called "Plugin" - the plugin author can then put their > > plugin > > > page under this node. > > > The user will know that this is related to a plugin and not smartsvn > > original > > > options. > > > And then plugin author can put their plugin page under that node. This > > way the > > > end user knows where to find the plugin's setting page. > > > > > > For the plugin that I wrote, I could not find a good location in the > > existing > > > nodes. It is related to commit, but there is already a commit node. > > > For now i will stick it under commit or actions, but I don't think it is > > a > > > good place. > > > > > > -prakash > > > > > > ps: I was not sure if the mail was sent the last time... Sending it > > again. > > > > > > > > > > > > > > > > > > [Non-text portions of this message have been removed] > > > > > > > > > > > > ------------------------------------ > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > -- > -Prakash > > > [Non-text portions of this message have been removed] > > > > ------------------------------------ > > Yahoo! Groups Links > > > > ------------------------------------ Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/smartsvn/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/smartsvn/join (Yahoo! ID required) <*> To change settings via email: mailto:smartsvn-digest@... mailto:smartsvn-fullfeatured@... <*> To unsubscribe from this group, send an email to: smartsvn-unsubscribe@... <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/ |
|
|
|
| Free embeddable forum powered by Nabble | Forum Help |