![]() Make the class public accessible and overwrite from the IniSection class from the Greenshot.IniFile namespace.Īdd the properties you’ll will need to upload your images to your server or application. Right click your plugin project and choose to add a new class. We’ll start with the configuration class that will help us with storing the necessary settings in the Greenshot config file so we can retrieve them later in the process. Now that the project is set up, we can start to add the necessary classes for our plugin. You probably will see the GreenshotDemo Plugin folder there too. Run Rebuild on the solution and you’ll see in the output window that for every plugin a new folder is created under. Last but not least, add a reference to the GreenshotPlugin by right clicking the references node in your plugin project and browse to the correct project and click add. Hit save and close the properties window. ![]() The last statement is only useful if you add multiple languages to your plugin. This will make sure after you build the project, it is automatically copied and placed into the greenshot plugin folder of your development environment as a gsp package file (I suppose gsp stands for GreenShotPlugin). Mkdir “$(SolutionDir)bin\$(Configuration)\Languages\Plugins\$(ProjectName)”Ĭopy “$(ProjectDir)\Languages\*.xml” “$(SolutionDir)bin\$(Configuration)\Languages\Plugins\$(ProjectName)\” Mkdir “$(SolutionDir)bin\$(Configuration)\Plugins\$(ProjectName)”Ĭopy “$(ProjectDir)bin\$(Configuration)\$(TargetFileName)” “$(SolutionDir)bin\$(Configuration)\Plugins\$(ProjectName)\*.gsp”Ĭopy “$(ProjectDir)bin\$(Configuration)\$(ProjectName).pdb” “$(SolutionDir)bin\$(Configuration)\Plugins\$(ProjectName)\” In the Build Events tab edit the post build event command line and paste the next statements in: NET 2.0 framework as the rest of the project is build in 2.0.Īfter the project is added to your solution open up the properties of the project (right click on project and then select properties). Right click on the Greenshot solution and choose to add a new project.Ĭhoose to create a class library and give it a name. In Visual Studio the project would look like the screenshot below: If you want to contribute, be sure to read the instructions on the bitbucket page! I’m using Visual Studio 2013 that’s is going to upgrade the existing projects. (if you’re using git: git clone in a git console)Īfter you downloaded the source code, go to the greenshot folder and open up Greenshot.sln. One remark, I’m a very happy user of Greenshot, and must say, even without documentation, the code base is clearly well build up and professional! Setting up developmentįirst go to to fetch the latest source code. In this post you’ll find the steps you’ll have to do to create your own plugin. As there is no (or I didn’t found it) documentation how to create your own plugin, I started to digging in the existing code base. It gives you the possibility to capture a region, edit the image and then copy/paste or use one of the existing plugins to upload the picture to JIRA, Office, …įor a project I’ve wanted to create a new plugin so we can add screenshot to our work log without have to take the screenshot, save the image somewhere and then go to the web application and upload the file. Therefor I’m already a long time user of the open source Greenshot product. When you have to make screenshots on a daily bases, to add in a manual, to report issues, to share views with colleagues, you’’ll find that the default screenshot capabilities of Windows aren’t sufficient enough.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |