The same you can do with plugins... but in an easier way :)<div><br></div><div>Two use cases:</div><div><br></div><div>1) Let the user do data management on layers. E.g. load layers, apply symbologies, etc. </div><div>These operations are not bounded to a specific layer. They should be available as "Global Actions". </div>
<div><br></div><div>2) Let's suppose I create a plugin with some utility functions, e.g. to do analysis, data management, etc.</div><div>I would like to give the end-user the opportunity to use them, but without the need to create a plugin (it's still too difficult for the end-user).</div>
<div><br></div><div>giovanni</div><br><div class="gmail_quote">2012/3/1 Nathan Woodrow <span dir="ltr"><<a href="mailto:madmanwoo@gmail.com">madmanwoo@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I see what you mean. What would you do with these global actions? <div><br></div><div>Just trying to get an idea of what is needed/missing currently.<br><div><br></div><div>- Nathan<br><br><div class="gmail_quote">On Thu, Mar 1, 2012 at 8:25 PM, G. Allegri <span dir="ltr"><<a href="mailto:giohappy@gmail.com" target="_blank">giohappy@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Nathan,<div>I don't mean using some derived BASIC language. The Macros should be the same as Action types (generic, python, etc.). The only difference being not bounded to layers, but available in a menu list.</div>
<div>The menu could be a fixed Actions menu for the moment. In the future it could be a customizable option...</div><div><br></div><div>giovanni<div><div><br><br><div class="gmail_quote">2012/3/1 Nathan Woodrow <span dir="ltr"><<a href="mailto:madmanwoo@gmail.com" target="_blank">madmanwoo@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi giovanni,<div><br></div><div>Can you give me a use case for these Marcos? I have used MapBasic before but that is more like what QGIS provides via Python, although MapBasic can be a bit easier to learn due to it being a DSL[1]</div>
<div><br></div><div>[1] <a href="http://en.wikipedia.org/wiki/Domain-specific_language" target="_blank">http://en.wikipedia.org/wiki/Domain-specific_language</a></div><div><br></div><div>- Nathan<br><br><div class="gmail_quote">
<div><div>On Thu, Mar 1, 2012 at 8:12 PM, G. Allegri <span dir="ltr"><<a href="mailto:giohappy@gmail.com" target="_blank">giohappy@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>Hi all,<div>I don't know if this has been already suggested/asked before, and I don't know if it's already available somehow.</div>
<div>I feel there is a hole between Layer Actions and Plugins, which various softwares fill with Macros (like OO StarBasic, Mapinfo's MapBasic, etc.).</div>
<div>It would be nice to be able to write Macros, like in Actions, but on a application level and not bounded to a layer.</div><div>The plus would be to let the user assign Macros to custom menu items...</div><div>The last step would be being able to call plugin methods.</div>
<div><br></div><div>Ok, one step at a time :)</div><div>First question: have I missed this option, is it already available?</div><div>Second question: what do you think about it?</div><div><br></div><div>giovanni</div>
<br></div></div>_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div></div></div>
</blockquote></div><br></div></div>
</blockquote></div><br>