cropperplugins Forum Rss Feed

New Post: Capture also Captures Cropping Window

slbryant — Mon, 20 May 2013 20:32:57 GMT

I have tried the options in the options menu. I'm able to turn off the cropping window during recording but then I have to return to the task bar to stop the recording.

Can you help me with this?

Thank you otherwise!

New Post: A question on output to printer

robcastaldo — Fri, 08 Feb 2013 15:54:17 GMT

I was wondering if there is anyway to scale the output for output to printer?

I've tried modifying the printer settings but it doesn't seem to work. It would be helpful if the output were scaled to fit the default paper size of the printer when doing print screen.

I'm using cropper with win7 pro 64

New Post: Another plugin for Office 365

BhanuSingh — Thu, 06 Dec 2012 11:38:38 GMT

Hello Friends,

There is another plugin for Office 365. For this plugin to work you just need your Office 365 ID.

http://capturepoint.codeplex.com/

Thanks!

New Post: OAuth lib works with image upload API

robertod — Wed, 31 Oct 2012 13:47:50 GMT

Ah, that turned out to be not so difficult, just add:

contents.AppendLine(separator)

contents.AppendLine("Content-Disposition: form-data; name=""in_reply_to_status_id""")
contents.AppendLine()
contents.AppendLine(IDofTweetToReplyTo)

New Post: OAuth lib works with image upload API

robertod — Wed, 31 Oct 2012 13:10:07 GMT

Works fantastic, but how can this be used with the in_reply_to_status_id parameter ?

New Post: Plugin "Send to ImageShack" doesn't work anymore

Get_free — Mon, 29 Oct 2012 14:47:24 GMT

ImageShack did some changes on their image submitting mechanism, and so the plugin for uploding to ImageShack doesn't work anymore.

New Post: New Release: v1.3

Cheeso — Thu, 26 Jul 2012 21:10:58 GMT

Peter - thanks for reporting this and sorry about the error.

I will need to test that here on my end., and I'll get back to you.

Will update this thread with info as I am able to diagnose it.

New Post: New Release: v1.3

PeterNZ — Wed, 25 Jul 2012 23:24:36 GMT

The facebook plug in doesn't work for me. When I used it the first time I got the usual login to facebook and approval to use the plug in but then I get an empty browser window with the word "Success" and if I close this I get

---------------------------No Authorizaiton for Facebook plugin---------------------------

You must approve Cropper for use with Facebookbefore uploading an image.

---------------------------OK ---------------------------

No uploads are done.

Cheers

Peter

New Post: Request to separate file format from destination.

Cheeso — Sun, 16 Oct 2011 18:04:26 GMT

Hi,

Your observation is spot on, and I think yours sounds like a reasonable request. I noticed the same thing of course, as I reproduced the format selection in various plugins I was maintaining. I also noticed a nice opportunity for the kind of chaining you described, with the send-to-paint plugin. It currently implements its own chaining, to allow the image to get sent to a remote service, after it is finished being edited in Paint.

So I think it's a good idea.

But, I can't do anything about it. The change you are describing would first require a change to Cropper itself. I am not a contributor for the cropper project; I am a contributor to cropper plugins. I'm more than willing to commit to updating the various plugins here to work with a new plugin model that supports chaining and format independence. I don't know how willing Terry Hughes would be to do the work required in Cropper.

New Post: Using OAuth.cs with parameters containing special characters

Cheeso — Sun, 16 Oct 2011 17:55:48 GMT

Christoffer,

I am glad to hear that you solved your problem, and you were able to get some use out of Oauth.cs .

Thanks for letting me know. Good luck.

-Dino

New Post: Using OAuth.cs with parameters containing special characters

ephracis — Sat, 15 Oct 2011 14:28:38 GMT

Thank you so much for all your help. It turns out that you were right, the problem is how the stuff is encoded. I did find the encoding method provided by OAuth.cs and in the comments it said that one should use that method instead of the built in one. So I changed it and used that method to encode my parameters and now it works. All because of the lower/upper case stuff. :)

However, I did find that swedish characters (åäöÅÄÖ) messed things up a bit. If they were encoded (as they should be according to the RFC) then I got an error from the provider but if I just let them be (added them to the unreservedChars string) then it worked. However, this seem to be a bug in the provider code and not OAuth.cs since the RFC clearly states that åäö should be encoded.

Thanks for your help! Have a sunny day!

/ Christoffer

Creator of Stoffi Music Player

www.stoffiplayer.com

New Post: OAuth lib works with image upload API

Cheeso — Tue, 11 Oct 2011 02:50:57 GMT

This code worked for me, uploading an image to Twitter.

    string twitterUrl1 = "http://api.twitter.com/1/statuses/update.xml?status=";
    string twitterUrl2 = "https://upload.twitter.com/1/statuses/update_with_media.xml";

    private string GetTwitterUpdateUrl()
    {
        return (imageFile == null) ?
            twitterUrl1 + message :  twitterUrl2;
    }

    private static string GetMimeType(String filename)
    {
        var extension = System.IO.Path.GetExtension(filename).ToLower();
        var regKey =  Microsoft.Win32.Registry.ClassesRoot.OpenSubKey(extension);

        string result =
            ((regKey != null) && (regKey.GetValue("Content Type") != null))
            ? regKey.GetValue("Content Type").ToString()
            : "image/unknown" ;
        return result;
    }

    private void Tweet()
    {
        var url = GetTwitterUpdateUrl();
        var authzHeader = oauth.GenerateAuthzHeader(url, "POST");
        var request = (HttpWebRequest)WebRequest.Create(url);

        request.Method = "POST";
        request.PreAuthenticate = true;
        request.AllowWriteStreamBuffering = true;
        request.Headers.Add("Authorization", authzHeader);

        if (imageFile != null)
        {
            string boundary = "======" +
                          Guid.NewGuid().ToString().Substring(18).Replace("-","") +
                          "======";

            var separator = "--" + boundary;
            var footer = "\r\n" + separator + "--\r\n";

            string shortFileName = Path.GetFileName(imageFile);
            string fileContentType = GetMimeType(shortFileName);
            string fileHeader = string.Format("Content-Disposition: file; " +
                                              "name=\"media\"; filename=\"{0}\"",
                                              shortFileName);
            var encoding = System.Text.Encoding.GetEncoding("iso-8859-1");

            var contents = new System.Text.StringBuilder();
            contents.AppendLine(separator);
            contents.AppendLine("Content-Disposition: form-data; name=\"status\"");
            contents.AppendLine();
            contents.AppendLine(message);
            contents.AppendLine(separator);
            contents.AppendLine(fileHeader);
            contents.AppendLine(string.Format("Content-Type: {0}", fileContentType));
            contents.AppendLine();

            request.ServicePoint.Expect100Continue = false;
            request.ContentType = "multipart/form-data; boundary=" + boundary;
            // actually send the request
            using (var s = request.GetRequestStream())
            {
                byte[] bytes = encoding.GetBytes(contents.ToString());
                s.Write(bytes, 0, bytes.Length);
                bytes = File.ReadAllBytes(imageFile);
                s.Write(bytes, 0, bytes.Length);
                bytes = encoding.GetBytes(footer);
                s.Write(bytes, 0, bytes.Length);
            }
        }


        using (var response = (HttpWebResponse)request.GetResponse())
        {
            if (response.StatusCode != HttpStatusCode.OK)
                MessageBox.Show("There's been a problem trying to tweet:" +
                                Environment.NewLine +
                                response.StatusDescription +
                                Environment.NewLine +
                                Environment.NewLine +
                                "You will have to tweet manually." +
                                Environment.NewLine);
        }
    }

To use it, I created the oauth manager class, and set the message and imageFile fields. like this:

    oauth = new OAuth.Manager();
    oauth["consumer_key"] = APP_CONSUMER_KEY;
    oauth["consumer_secret"] = APP_CONSUMER_SECRET;
    oauth["token"]           = accessToken;
    oauth["token_secret"]    = accessSecret;
    message = "This is the twitter status message";
    imageFile = "C:\\users\\Melvin\\Documents\\MyPhoto.jpg";

New Post: Using OAuth.cs with parameters containing special characters

Cheeso — Tue, 11 Oct 2011 01:03:52 GMT

Yes, I just tested this, and it works with Twitter whether the status message is url-encoded before calling GenerateAuthzHeader or not.

so, the conclusion is, you should look to your provider, as I said before.

New Post: Using OAuth.cs with parameters containing special characters

Cheeso — Mon, 10 Oct 2011 22:41:12 GMT

I looked again and ran some tests and it seems that the double-encoding should be a non-issue. It gets run through a the System.Uri class which prevents any double-encoding. I think you could safely eliminate any external Url-encoding of the url, before calling GenerateAuthzHeader(), but I think including it (as I have shown in the documentation for that and other methods) also does not cause a problem.

New Post: OAuth lib works with image upload API

Cheeso — Mon, 10 Oct 2011 22:15:24 GMT

This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.

New Post: OAuth lib works with image upload API

Cheeso — Mon, 10 Oct 2011 22:14:39 GMT

Thanks for posting this - very good.

Seems like the right thing to do is to create a new plugin for this, and let the existing twitpic plugin remain.

New Post: Using OAuth.cs with parameters containing special characters

Cheeso — Mon, 10 Oct 2011 22:12:24 GMT

I don't know, but the obvious place to look is in the Url Encoding.

When connecting to Twitter, the Oauth.cs code works correctly as it is. I've tested it and it works. But this could be provider-specific. In other words there could be some flexibility that is built in to Twitter that is not present in your provider.

I cannot remember what the "specification" said about url-encoding the URL before generating the authorization header. So I looked.

The OAuth 1.0a spec says:

The signature base string is often the most difficult part of OAuth for newcomers to construct. The signature base string is composed of the HTTP method being used, followed by an ampersand ("&") and then the URL-encoded base URL being accessed, complete with path (but not query parameters), followed by ....

....It goes on in some additional detail about how to create the signature base string.

Looking in the code I wrote for OAuth.cs, the GenerateAuthzHeader does Url-encode the URL before signing it. But I see you have url-encoded the url before passing it to GenerateAuthzHeader(). (This is actually how I do it when interacting with Twitter, and it's also the way the documentation for OAuth.cs shows to do it) This would mean the URL gets url-encoded twice, which would be redundant of course. It could be that Twitter's provider is flexible enough to tolerate the double-pass, and your provider is not. If that is the case, you could test by simply not url-encoding before calling GenerateAuthzHeader().

If that simple test does not work, I'd suggest that you look at where the failure is generated on the server side, in the provider, and trace it back.

New Post: Using OAuth.cs with parameters containing special characters

ephracis — Sat, 08 Oct 2011 17:52:10 GMT

Hi,

I am using the OAuth.cs file to send requests as a consumer in my C# application. I love the simplicity of it but today I stumbled upon a problem. I want to send some parameters along with my request. So I do it like this:

var url = "http://www.domain.com/some/path?foo=" + HttpUtility.UrlEncode("using space");
var authzHeader = oauth.GenerateAuthzHeader(url, "POST");
var request = (HttpWebRequest)WebRequest.Create(url);
request.Method = "POST";
request.PreAuthenticate = true;
request.AllowWriteStreamBuffering = true;
request.Headers.Add("Authorization", authzHeader);
try
{
	using (var response = (HttpWebResponse)request.GetResponse())
	{
		if (response.StatusCode != HttpStatusCode.OK)
			Console.WriteLine("Error!");
		else
		{
			Stream s = response.GetResponseStream();
			StreamReader sr = new StreamReader(s);
			string str = sr.ReadToEnd();
			U.L(LogLevel.Information, "SERVICE", "Shared song, got response: " + str);
		}
	}
}
catch (WebException exc)
{
	U.L(LogLevel.Error, "SERVICE", "Error while trying to share song: " + exc.Message);
}

Problem is, this seems to make the provider throw me off to the login page, probably because there's something wrong with the signature. The provider is setup following these instructions: http://stakeventures.com/articles/2007/11/26/how-to-turn-your-rails-site-into-an-oauth-provider

I have tried with some different parameters and as long as it's just a-z 0-1 it works. But if I try something like space, colon, slash or any other character that needs to be encoded I'm screwed.

So am I doing something wrong in the C# code, is there some bug in the OAuth.cs file (I couldn't find anything) or is it the provider that's behaving strangely?

Thanks!

New Post: OAuth lib works with image upload API

russau — Mon, 22 Aug 2011 07:08:34 GMT

Twitter now has an API for uploading images direct to twitter: https://dev.twitter.com/docs/api/1/post/statuses/update_with_media

Something you might want to consider using from the cropper plugins?

I've got it going with the OAuth lib. I'm using the Upload.PostFile from Salient as the System.Net.WebClient won't allow me to name the file's form variable.

OAuth.Manager man = new OAuth.Manager(CONSUMER_KEY, CONSUMER_SECRET, token, secret);
string url = "https://upload.twitter.com/1/statuses/update_with_media.xml?"+
    "status=" + OAuth.Manager.UrlEncode("setting up my twitter &#31169;!!"
    );
string header = man.GenerateAuthzHeader(url, "POST");

NameValueCollection headers = new NameValueCollection();
headers.Add("Authorization", header);
            
WebResponse fileResponse = Upload.PostFile(new Uri(url)
    , new NameValueCollection()
    , @"C:\Users\Russ\4063b622-4716-4c19-9050-c7cf8f9f7ec2.jpg"
    , "img/jpeg"
    , "media[]"
    , null
    , headers);


Stream s = fileResponse.GetResponseStream();
using (StreamReader sr = new StreamReader(s))
{
    string res = sr.ReadToEnd();
    Console.Write(res);
}

New Post: Request to separate file format from destination.

goodeye — Mon, 15 Aug 2011 00:16:49 GMT

Hi,

Love cropper. This request is to separate the selected file format from the selected "destination." That is, for plug-ins such as SendToEmail, SendToWherever, let the plug-in use a selected format, independent of selecting that plug-in. e.g., SendToEmail has a separate selection for the file format, that doesn't contain .gif (because that's a separate plug-in). (Even without the .gif plug-in issue, the built-in formats don't sync with the plug-in's options.) It's as if these plug-ins are having to take over and repeat functionality elsewhere in cropper.

Perhaps this could be done with explicit "knowledge" of a format vs a destination. Alternatively, maybe this is describing a more generic chained plug-in approach. Run the .jpg output (or .gif plug-in), then run the SendTo... plug-in.

Thanks,

Bob