no master page change needed

Jun 9, 2013 at 2:58 PM

Instead of changing the master page (which is a pain for upgrades) you should consider to add the 3 scripts through a solution/feature: just use a declarative way, such as "scriptlinks". tested it already with a sandboxed solution; works great :)

Cheers and thanks for the great project,
Jul 11, 2013 at 7:09 PM
Really great idea!!

At first, I started to think in share something that's easy to deploy and easy to use (without worrying about auditing, policies, approval, SP Admin intervention, and many requirements of companies related to SharePoint farm solutions). Of course, it has a price: you need to edit the code of a master page and know a little bit about SharePoint Designer and Asp.Net.

But, I completely forgot about sandboxed solutions!! And it could be a really good approach!

Now I'm improving the usage (building a custom option to export on Site Actions Menu, instead using browser console), but it will really be the next version change :)

Thinking more about SharePoint 2013, what about an app??

Thank you so much :D