Re: [twsocket] TTwitter component
v0.33 up with xAuth/SSL support. On Mon, Feb 28, 2011 at 4:02 PM, brian - hikarito...@gmail.com wrote: http://dev.twitter.com/pages/auth_overview http://dev.twitter.com/pages/auth_overviewThere's xAuth to skip the PIN step, but requires the twitter user/pass. Also I made a method in my lib to do almost like xAuth, simulating a browser login, catching the cookies and posting the form etc to retrieve the data, but that's prone to fail. I do like the PIN step to be honest, it's only required once and the user will feel more secure not giving their login details. On Mon, Feb 28, 2011 at 3:34 PM, Anton S. an...@rambler.ru wrote: There's already a method through httpcli, but PIN approach should always be encouraged. I don't know what PIN is but couldn't it be implemented without external apps/activeX? -- Anton -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
TWebbrowser? ShellExec?? Chromium?? Why don't you use ICS HTTPCli for authorizing? You may even display an original page with powerful ThtmlViewer component. -- Anton -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
There's already a method through httpcli, but PIN approach should always be encouraged. v0.32 up On Mon, Feb 28, 2011 at 10:32 AM, Anton S. an...@rambler.ru wrote: TWebbrowser? ShellExec?? Chromium?? Why don't you use ICS HTTPCli for authorizing? You may even display an original page with powerful ThtmlViewer component. -- Anton -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
There's already a method through httpcli, but PIN approach should always be encouraged. I don't know what PIN is but couldn't it be implemented without external apps/activeX? -- Anton -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
http://dev.twitter.com/pages/auth_overview http://dev.twitter.com/pages/auth_overviewThere's xAuth to skip the PIN step, but requires the twitter user/pass. Also I made a method in my lib to do almost like xAuth, simulating a browser login, catching the cookies and posting the form etc to retrieve the data, but that's prone to fail. I do like the PIN step to be honest, it's only required once and the user will feel more secure not giving their login details. On Mon, Feb 28, 2011 at 3:34 PM, Anton S. an...@rambler.ru wrote: There's already a method through httpcli, but PIN approach should always be encouraged. I don't know what PIN is but couldn't it be implemented without external apps/activeX? -- Anton -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
Updated the library and uploaded to my site to reflect this modification. Sadly though, OverbyteIcsHttpCCodZLib is still problematic, I have to keep using the modified version to make it work. On Sun, Feb 27, 2011 at 7:56 AM, Francois PIETTE francois.pie...@skynet.bewrote: I will modify the code to use a variable for this outside the ics unit, as this will create only extra complication when a new ICS is available. Good :-) But, you mention it's very different from your current one, do you mean a new version still in development? since I have the latest distribution available from your website, unless I've missed a link to a beta or newer version :) The latest version is always available from the subversion repository (svn://svn.overbyte.be/ics/trunk or daily snapshot). The zip file at www.overbyte.be is updated only once or twice a year at some fixed milestones. See http://wiki.overbyte.be/wiki/index.php/ICS_Download -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
Updated the library and uploaded to my site to reflect this modification. Super ! Sadly though, OverbyteIcsHttpCCodZLib is still problematic, I have to keep using the modified version to make it work. I can't find your unit. Is it the chnage that Henri Gourvest published (see attached message) and which never reached the source code ? -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
Don't see an attached message in your reply :( but anyway, lurking through the archives some time ago I found someone submitted a modification to apparently fix this problem, but that still didnt work for me. Changing this in OverbyteIcsHttpCCodZLib did the trick though: 55: Result := 'gzip, deflate'; Simply added deflate to the result. Without that, I don't get any data back. On Sun, Feb 27, 2011 at 3:05 PM, Francois PIETTE francois.pie...@skynet.bewrote: Updated the library and uploaded to my site to reflect this modification. Super ! Sadly though, OverbyteIcsHttpCCodZLib is still problematic, I have to keep using the modified version to make it work. I can't find your unit. Is it the chnage that Henri Gourvest published (see attached message) and which never reached the source code ? -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
On 27-02-2011 16:01, brian - wrote: Simply added deflate to the result. Without that, I don't get any data back. Juts tested your component here, without that modification, and works just fine. What exactly happen in your case. What data you don't get? -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
posted an update to my lib: http://eden.fm/2011/02/27/another-twitter-library-update-v0-3/ http://eden.fm/2011/02/27/another-twitter-library-update-v0-3/You can now use an alternate method to wont require the user to visit the twitter site to get the PIN code, the app will simulate a browser login, catch the cookies and proceed to auth on its own to retrieve the PIN. the issue about OverbyteIcsHttpCCodZLib is not related to this twitter library, just in general, if you try to retrieve a page with GZip there's no data returned. On Sun, Feb 27, 2011 at 5:54 PM, RTT p...@sapo.pt wrote: On 27-02-2011 16:01, brian - wrote: Simply added deflate to the result. Without that, I don't get any data back. Juts tested your component here, without that modification, and works just fine. What exactly happen in your case. What data you don't get? -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
posted an update to my lib: http://eden.fm/2011/02/27/another-twitter-library-update-v0-3/ Link to download on the page is broken ! -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
You can remove the b64ASM.pas dependency using the ICS equivalent //b64asm.Base64Encode(HMAC_SHA1_EX(SignBase,signkey)); OverbyteIcsMimeUtils.Base64Encode(HMAC_SHA1_EX(SignBase,signkey)); Probably not so fast, but not really important in this case of small length strings. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
Ahh thanks, should have looked there first :) replaced it now. Download link should work now. On Sun, Feb 27, 2011 at 6:45 PM, RTT p...@sapo.pt wrote: You can remove the b64ASM.pas dependency using the ICS equivalent //b64asm.Base64Encode(HMAC_SHA1_EX(SignBase,signkey)); OverbyteIcsMimeUtils.Base64Encode(HMAC_SHA1_EX(SignBase,signkey)); Probably not so fast, but not really important in this case of small length strings. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
On 27-02-2011 17:18, brian - wrote: use an alternate method to wont require the user to visit the twitter site to get the PIN code, the app will simulate a browser login, catch the cookies and proceed to auth on its own to retrieve the PIN. This will work until twitter decide to change these html pages. But with Twitter you can even bypass the need of a PIN. Just remove all the oauth_verifier references and you will see that works without PIN. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
that alternate method was mostly a test to see if I could make it work, I still encourage using the PIN system :) I like it tbh, even with the annoyance of havign to login and retrieve the pass for the user, it's only required once. ill most likely remove this alternate proc in next revision, and add XAuth support instead. On Sun, Feb 27, 2011 at 7:25 PM, RTT p...@sapo.pt wrote: On 27-02-2011 17:18, brian - wrote: use an alternate method to wont require the user to visit the twitter site to get the PIN code, the app will simulate a browser login, catch the cookies and proceed to auth on its own to retrieve the PIN. This will work until twitter decide to change these html pages. But with Twitter you can even bypass the need of a PIN. Just remove all the oauth_verifier references and you will see that works without PIN. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
On 27-02-2011 18:39, brian - wrote: I like it tbh, even with the annoyance of havign to login and retrieve the pass for the user, it's only required once. As I said, Twitter don't require the PIN, so you can ignore that step. User only need to authorize the application, and forget about the PIN. Instead of using the ShellExecute to open the browser, you can use the TTwitter approach. Start a modal Request Authorization form with a TWebBrowser pointed to that address. This way you can proceed with the RequestAccess after user close that authorization form. Using this idea, another thing you could do to make your component more user friendly, is to execute internally all the authentication steps, the first time they are needed. User will just need to create the component and call the SendTwit method. The callback will be used only to get the success/unsuccess of the send. ill most likely remove this alternate proc in next revision, and add XAuth support instead. With both methods you should use SSL, or you will be passing user and password in plain text. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
hmm interesting, I will test about the PIN; I guess Twitter associates the 1st auth token with the user's account after they allow the app. I don't really like the idea of embedding the TWebBrowser object, bulky and buggy activex stuff. On Sun, Feb 27, 2011 at 8:18 PM, RTT p...@sapo.pt wrote: On 27-02-2011 18:39, brian - wrote: I like it tbh, even with the annoyance of havign to login and retrieve the pass for the user, it's only required once. As I said, Twitter don't require the PIN, so you can ignore that step. User only need to authorize the application, and forget about the PIN. Instead of using the ShellExecute to open the browser, you can use the TTwitter approach. Start a modal Request Authorization form with a TWebBrowser pointed to that address. This way you can proceed with the RequestAccess after user close that authorization form. Using this idea, another thing you could do to make your component more user friendly, is to execute internally all the authentication steps, the first time they are needed. User will just need to create the component and call the SendTwit method. The callback will be used only to get the success/unsuccess of the send. ill most likely remove this alternate proc in next revision, and add XAuth support instead. With both methods you should use SSL, or you will be passing user and password in plain text. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
On 27-02-2011 19:29, brian - wrote:
I don't really like the idea of embedding the TWebBrowser object, bulky and
buggy activex stuff.
The WebBrowser control works very well for this simple navigate to a
page task.
If you want to test, just replace your RequestPIN code with the next one.
uses
forms, ShDocVw, Controls;
...
procedure TwitterCli.RequestPIN;
var
AuthForm: TForm;
WebBrowser: TWebBrowser;
begin
AuthForm := TForm.create(application.MainForm);
with AuthForm do
begin
BorderStyle := bsDialog;
Caption := 'Twitter Authorization - Authorize and close this
dialog';
width := screen.width - screen.width div 5;
height := screen.height - screen.height div 5;
Position := poScreenCenter;
end;
WebBrowser := TWebBrowser.Create(authForm);
TWinControl(WebBrowser).Parent := authForm;
WebBrowser.Align := alClient;
WebBrowser.Navigate(RequestPinURL);
authForm.ShowModal;
authForm.free;
end;
Also, if you in the end decide to maintain the ShellExecute, then better
specify the 'Open' verb. Some system may have the default verb defined
differently.
ShellExecute(0, 'open',
PChar('https://twitter.com/oauth/authorize?oauth_token=' + OAuthToken),
'', '', SW_SHOWNORMAL);
And you don't need to declare the ShellExecute import, just use the one
defined in the ShellAPI unit.
---
Why you decided to use the GPL v3?
IMHO, for small , and simple, code projects like this one, better use a
license that can be used in closed code applications, or commercial
users will just grab/mangle the code and don't give you any credit.
If credit is given, they will need to open the code too, and that isn't
going to happen. On the other hand, if license permits closed code, they
have no problem to include the reference.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
I was actually 'open' for years, but I've been seeing users not able to
launch urls from my apps with that, cause the default browser may not have
defined that command, was still using it in the first versions of twitter
lib. I added the ShellExecute import to avoid adding another unit; I rather
not include entire units for things where I need only a couple procs and
such, it adds up to the exe unnecesarily.
As for webbrowser, hmm, I think I still prefer either the PIN or self-auth
approach, else, how we know the user actually allowed the app, we can't just
blindly assume they'll do and think we are now authorized, so the last PIN
step takes care of that.
I read somewhere about embedding a chromium window in delphi btw, heard
anything? I'm curious to test, gonna check for it. I really still dont like
the twebbrowser at all. But maybe I could have a compiler conditional so the
user can opt for a way or another.
Doesn't GPL allow your code to be included in closed source applications as
well? as long as the code hasnt been modified; unless I understood it all
wrong. Tbh it's the first time in over ~12 years programming Im opening up
to release and share source code, so I never looked much into open source
licenses until just now. Would appreciate some insight about it :)
On Mon, Feb 28, 2011 at 12:08 AM, RTT p...@sapo.pt wrote:
On 27-02-2011 19:29, brian - wrote:
I don't really like the idea of embedding the TWebBrowser object, bulky
and
buggy activex stuff.
The WebBrowser control works very well for this simple navigate to a page
task.
If you want to test, just replace your RequestPIN code with the next one.
uses
forms, ShDocVw, Controls;
...
procedure TwitterCli.RequestPIN;
var
AuthForm: TForm;
WebBrowser: TWebBrowser;
begin
AuthForm := TForm.create(application.MainForm);
with AuthForm do
begin
BorderStyle := bsDialog;
Caption := 'Twitter Authorization - Authorize and close this
dialog';
width := screen.width - screen.width div 5;
height := screen.height - screen.height div 5;
Position := poScreenCenter;
end;
WebBrowser := TWebBrowser.Create(authForm);
TWinControl(WebBrowser).Parent := authForm;
WebBrowser.Align := alClient;
WebBrowser.Navigate(RequestPinURL);
authForm.ShowModal;
authForm.free;
end;
Also, if you in the end decide to maintain the ShellExecute, then better
specify the 'Open' verb. Some system may have the default verb defined
differently.
ShellExecute(0, 'open', PChar('
https://twitter.com/oauth/authorize?oauth_token=' + OAuthToken), '', '',
SW_SHOWNORMAL);
And you don't need to declare the ShellExecute import, just use the one
defined in the ShellAPI unit.
---
Why you decided to use the GPL v3?
IMHO, for small , and simple, code projects like this one, better use a
license that can be used in closed code applications, or commercial users
will just grab/mangle the code and don't give you any credit.
If credit is given, they will need to open the code too, and that isn't
going to happen. On the other hand, if license permits closed code, they
have no problem to include the reference.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
On 27-02-2011 23:31, brian - wrote:
I added the ShellExecute import to avoid adding another unit; I rather
not include entire units for things where I need only a couple procs and
such, it adds up to the exe unnecesarily.
The smart linking feature should work ok for the shellapi unit.
As for webbrowser, hmm, I think I still prefer either the PIN or self-auth
approach, else, how we know the user actually allowed the app, we can't just
blindly assume they'll do and think we are now authorized, so the last PIN
step takes care of that.
That's a user problem. But you can add a
InputQuery('Enter your PIN','PIN', Twit.AccessPIN);
just after the modal form closes.
Add also
initialization
OleInitialize(nil);
finalization
OleUninitialize;
So user can copy the pin text from the webbrowser to the clipboard.
I read somewhere about embedding a chromium window in delphi btw, heard
anything? I'm curious to test, gonna check for it. I really still dont like
the twebbrowser at all. But maybe I could have a compiler conditional so the
user can opt for a way or another.
http://www.progdigy.com/
Doesn't GPL allow your code to be included in closed source applications as
well? as long as the code hasnt been modified; unless I understood it all
wrong. Tbh it's the first time in over ~12 years programming Im opening up
to release and share source code, so I never looked much into open source
licenses until just now. Would appreciate some insight about it :)
V3 seems to change some things, but there is no general consensus about
this, (money always turn lawyers language in favor with who pays more),
so better stay away of it if you want to maintain closed source.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
I think you might want to use the BSD license -or- the Freeware License
ICS uses.
It is my understanding the GPL v3 license restricts any commercial
closed source use except in the case that the GPL'ed source code is
compiled into a separate library that is linked to during run-time vs.
being compiled into the exe file itself.
It is my understanding the BSD license allows anyone to do anything with
the source however you retain full copyright and ownership. For example
the Mac OS X is based off of FreeBSD
http://developer.apple.com/library/mac/#documentation/Darwin/Conceptual/
KernelProgramming/BSD/BSD.html
DISCALAIMER - I am not a lawyer and you should consult legal advice
concerning such matters.
-Original Message-
From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org]
On Behalf Of brian -
Sent: Sunday, February 27, 2011 6:32 PM
To: ICS support mailing
Subject: Re: [twsocket] TTwitter component
I was actually 'open' for years, but I've been seeing users not able to
launch urls from my apps with that, cause the default browser may not
have defined that command, was still using it in the first versions of
twitter lib. I added the ShellExecute import to avoid adding another
unit; I rather not include entire units for things where I need only a
couple procs and such, it adds up to the exe unnecesarily.
As for webbrowser, hmm, I think I still prefer either the PIN or
self-auth approach, else, how we know the user actually allowed the app,
we can't just blindly assume they'll do and think we are now authorized,
so the last PIN step takes care of that.
I read somewhere about embedding a chromium window in delphi btw, heard
anything? I'm curious to test, gonna check for it. I really still dont
like the twebbrowser at all. But maybe I could have a compiler
conditional so the user can opt for a way or another.
Doesn't GPL allow your code to be included in closed source applications
as well? as long as the code hasnt been modified; unless I understood it
all wrong. Tbh it's the first time in over ~12 years programming Im
opening up to release and share source code, so I never looked much into
open source licenses until just now. Would appreciate some insight about
it :)
On Mon, Feb 28, 2011 at 12:08 AM, RTT p...@sapo.pt wrote:
On 27-02-2011 19:29, brian - wrote:
I don't really like the idea of embedding the TWebBrowser object,
bulky and buggy activex stuff.
The WebBrowser control works very well for this simple navigate to a
page
task.
If you want to test, just replace your RequestPIN code with the next
one.
uses
forms, ShDocVw, Controls;
...
procedure TwitterCli.RequestPIN;
var
AuthForm: TForm;
WebBrowser: TWebBrowser;
begin
AuthForm := TForm.create(application.MainForm);
with AuthForm do
begin
BorderStyle := bsDialog;
Caption := 'Twitter Authorization - Authorize and close this
dialog';
width := screen.width - screen.width div 5;
height := screen.height - screen.height div 5;
Position := poScreenCenter;
end;
WebBrowser := TWebBrowser.Create(authForm);
TWinControl(WebBrowser).Parent := authForm;
WebBrowser.Align := alClient;
WebBrowser.Navigate(RequestPinURL);
authForm.ShowModal;
authForm.free;
end;
Also, if you in the end decide to maintain the ShellExecute, then
better
specify the 'Open' verb. Some system may have the default verb defined
differently.
ShellExecute(0, 'open', PChar('
https://twitter.com/oauth/authorize?oauth_token=' + OAuthToken), '',
'',
SW_SHOWNORMAL);
And you don't need to declare the ShellExecute import, just use the
one
defined in the ShellAPI unit.
---
Why you decided to use the GPL v3?
IMHO, for small , and simple, code projects like this one, better use
a
license that can be used in closed code applications, or commercial
users
will just grab/mangle the code and don't give you any credit.
If credit is given, they will need to open the code too, and that
isn't
going to happen. On the other hand, if license permits closed code,
they
have no problem to include the reference.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
It is my understanding the GPL v3 license restricts any commercial closed source use except in the case that the GPL'ed source code is compiled into a separate library that is linked to during run-time vs. being compiled into the exe file itself. LGPL (for LesserGPL) let you link to a library without making your application source code available. This is the license a lot of library use (ex.: QT) If you use GPL code in your application, you have to license it under GPL too. It is my understanding the BSD license allows anyone to do anything with the source however you retain full copyright and ownership. For example the Mac OS X is based off of FreeBSD The BSD license let you take the code and do whatever you want with it, even making it closed source. As an example, the TCP/IP stack of Windows is closed source, but is based on the BSD stack. So if you license your code on BSD, someone could take it, compile a Delphi component with it, then call it is own and sell it. DISCALAIMER - I am not a lawyer either :) -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
Ok, here's my twitter implementation : http://eden.fm/2011/02/27/twitter-library-for-delphi/ On Tue, Feb 22, 2011 at 12:13 PM, Francois PIETTE francois.pie...@skynet.be wrote: You should really consider making in freeware/opensource. You'll gain something: other people will find bugs and make enhancements. Your own applications will then be better. And you'll enter the hall of fames :-) Always been a bit skeptic about open source, how do you make money from that :) I do money with freeware. Well, not directly. You may not know it, but I'm an independant consultant, full time. A significant part of my customers have found me because of my freeware. I simply provide custome development, training, consultancy and other similar activity. Many companies have some developers finding my components, then they start writing their application and discover that they lack some resource or knowledge to build their application, or their application require some changes in the components. Then I'm here ! They hire me and I earn some money. Also, making the components freeware makes it better. People find bugs and added enhancements. My own applications benefit from that as well. They are more robust. You must really make a difference between components and applications ! I make frewware components, not applications. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
Hello Brian, Ok, here's my twitter implementation : http://eden.fm/2011/02/27/twitter-library-for-delphi/ It is very generous to make it OpenSource. Thanks a lot. There is still one big issue with your code: it make use of a modified ICS unit. Using a modified version make it almost impossible to use to build a program using ICS for other things. I checked you modified unit (HTTP Client) and it has a lot of changes compared to mine. Most of the changes are because you started from an old version and is not related to your code. As far as I can see, you have done only one change: you have added a new ExtraSendHeader property to send one header line. You can achieve the exact same behaviour without modifiyng the component by using the OnBeforeHeaderSend event and just add your header line to the Headers argument. This is really a minor change in your code ! Best regards, -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
Hi :) I actually send a mail to the list about this change: sender-time Sent at 11:37 PM (GMT+01:00). Current time there: 7:27 AM. ✆ to ICS twsocket@elists.org date Mon, Feb 21, 2011 at 11:37 PM subject THttpCli modification request, and gzip fix I made that minor change to ease the header modifications just before the calls, because else we have to use an extra variable and then check in the beforeheader event; guess I could have it done on the app side, but this seemed more convenient at the time and I had a problem before using that event which wrongly let me to believe the accessible headers there were read-only. I will modify the code to use a variable for this outside the ics unit, as this will create only extra complication when a new ICS is available. . But, you mention it's very different from your current one, do you mean a new version still in development? since I have the latest distribution available from your website, unless I've missed a link to a beta or newer version :) On Sun, Feb 27, 2011 at 7:04 AM, Francois PIETTE francois.pie...@skynet.bewrote: Hello Brian, Ok, here's my twitter implementation : http://eden.fm/2011/02/27/twitter-library-for-delphi/ It is very generous to make it OpenSource. Thanks a lot. There is still one big issue with your code: it make use of a modified ICS unit. Using a modified version make it almost impossible to use to build a program using ICS for other things. I checked you modified unit (HTTP Client) and it has a lot of changes compared to mine. Most of the changes are because you started from an old version and is not related to your code. As far as I can see, you have done only one change: you have added a new ExtraSendHeader property to send one header line. You can achieve the exact same behaviour without modifiyng the component by using the OnBeforeHeaderSend event and just add your header line to the Headers argument. This is really a minor change in your code ! Best regards, -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
I will modify the code to use a variable for this outside the ics unit, as this will create only extra complication when a new ICS is available. Good :-) But, you mention it's very different from your current one, do you mean a new version still in development? since I have the latest distribution available from your website, unless I've missed a link to a beta or newer version :) The latest version is always available from the subversion repository (svn://svn.overbyte.be/ics/trunk or daily snapshot). The zip file at www.overbyte.be is updated only once or twice a year at some fixed milestones. See http://wiki.overbyte.be/wiki/index.php/ICS_Download -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
You should really consider making in freeware/opensource. You'll gain something: other people will find bugs and make enhancements. Your own applications will then be better. And you'll enter the hall of fames :-) Always been a bit skeptic about open source, how do you make money from that :) I do money with freeware. Well, not directly. You may not know it, but I'm an independant consultant, full time. A significant part of my customers have found me because of my freeware. I simply provide custome development, training, consultancy and other similar activity. Many companies have some developers finding my components, then they start writing their application and discover that they lack some resource or knowledge to build their application, or their application require some changes in the components. Then I'm here ! They hire me and I earn some money. Also, making the components freeware makes it better. People find bugs and added enhancements. My own applications benefit from that as well. They are more robust. You must really make a difference between components and applications ! I make frewware components, not applications. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
On 2/21/2011 2:24 PM, brian - wrote: Always been a bit skeptic about open source, how do you make money from that :) What you would contribute to the ICS community as open source is just the base component -- not the application level implementation, which is where we all have the opportunity to make money. There are numerous examples of individuals here who have contributed at the component level with work that ends up in their commercial applications. I am regularly amazed by their contributions and level of help they provide to other developers. But, it certainly depends on your situation and willingness. -Jeff -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
I'm pretty sure I mailed mine a few years ago, but might as well send another :) I just do see more and more people lately using Indy by default since it started coming packed with Delphi, and they either don't know about ICS or prefer the simplicity of Indy. I prefer ICS for the control it gives me over everything that's going on, for the non-blocking calls, the performance, the extra stuff, and overall how it works, it's really a great piece of software, I use it in all my applications that required net access. I see Indy for example has components even to manage Cookies, leaving the user with no clue what's going on behind the scenes, I prefer handling that myself. On Sun, Feb 20, 2011 at 3:22 PM, Francois PIETTE francois.pie...@skynet.bewrote: I don't get why ICS isnt more widely used, Well ICS is widely used. More than one hundred thousands download so far. And about four thousands registration (That's how many postcards I've receive so far. BTW: Have you mailed yours ?). it's imo far more advanced and gives you a lot more control over what's happening, besides the ASync calls which I just love :) Spread the word ! Blog about it ! Write in Embarcadero and other forums. Take part or FaceBook and Linked-In groups. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
Always been a bit skeptic about open source, how do you make money from that :) On Sun, Feb 20, 2011 at 3:23 PM, Francois PIETTE francois.pie...@skynet.bewrote: closed source for now since im using it for another large project, and the libraries are not complete, it's mostly just the steps to auth with twitter and send the messages. :-( You should really consider making in freeware/opensource. You'll gain something: other people will find bugs and make enhancements. Your own applications will then be better. And you'll enter the hall of fames :-) -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
It doesn't need to be complete. If all one wants to do is tweet a message, then this would be enough, yes? I would be interested in using it for various status projects. Please post what you have. Thanks, Matt -Original Message- From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On Behalf Of brian - Sent: Monday, February 21, 2011 4:25 PM To: ICS support mailing Subject: Re: [twsocket] TTwitter component Always been a bit skeptic about open source, how do you make money from that :) On Sun, Feb 20, 2011 at 3:23 PM, Francois PIETTE francois.pie...@skynet.bewrote: closed source for now since im using it for another large project, and the libraries are not complete, it's mostly just the steps to auth with twitter and send the messages. :-( You should really consider making in freeware/opensource. You'll gain something: other people will find bugs and make enhancements. Your own applications will then be better. And you'll enter the hall of fames :-) -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
Always been a bit skeptic about open source, how do you make money from that :) Just ask RedHat or Canonical, for example. Better yet, ask François ! Like Jeff said, you're not open-sourcing your application, just the component. In return, you will get lots of debugging/testing and even improvements from other developers using your component. You can still sell your commercial app based on your component. B.t.w, hope you realize that your using open source components (ICS) to make money :) -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
I'll post the code in google code along with that tiny client :) it's nothing major and my code is probably embarrassingly messy and primitive though, I'm sure it can be improved a lot ^^ Just a small clarification though, it's not a component, it's only a unit with an object I called TTwitterCli, some properties and a few public procs, I never liked the components approach much for non-visual objects. will post back with a link On Tue, Feb 22, 2011 at 4:51 AM, Marc Charbonneau timebandit...@gmail.comwrote: Always been a bit skeptic about open source, how do you make money from that :) Just ask RedHat or Canonical, for example. Better yet, ask François ! Like Jeff said, you're not open-sourcing your application, just the component. In return, you will get lots of debugging/testing and even improvements from other developers using your component. You can still sell your commercial app based on your component. B.t.w, hope you realize that your using open source components (ICS) to make money :) -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
I made my own twitter and oauth libraries from scratch, full unicode support, with ICS :) Never liked Indy. http://eden.fm/twitmee/ Good ! Do you made it freeware/opensource ? I only see an exe file at the link you provided. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
closed source for now since im using it for another large project, and the libraries are not complete, it's mostly just the steps to auth with twitter and send the messages. I saw someone else made an oauth for delphi already, but didnt like it, too much use of classes for any little things and overcomplicated, besides them using Indy. I don't get why ICS isnt more widely used, it's imo far more advanced and gives you a lot more control over what's happening, besides the ASync calls which I just love :) On Sun, Feb 20, 2011 at 9:03 AM, Francois PIETTE francois.pie...@skynet.bewrote: I made my own twitter and oauth libraries from scratch, full unicode support, with ICS :) Never liked Indy. http://eden.fm/twitmee/ Good ! Do you made it freeware/opensource ? I only see an exe file at the link you provided. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
I'm using it also for a plugin for this application: http://malupdater.com/ http://malupdater.com/All these posts are being sent by ICS ^^ http://twitter.com/#!/search?q=%23MalUpdater On Sun, Feb 20, 2011 at 12:45 PM, brian - hikarito...@gmail.com wrote: closed source for now since im using it for another large project, and the libraries are not complete, it's mostly just the steps to auth with twitter and send the messages. I saw someone else made an oauth for delphi already, but didnt like it, too much use of classes for any little things and overcomplicated, besides them using Indy. I don't get why ICS isnt more widely used, it's imo far more advanced and gives you a lot more control over what's happening, besides the ASync calls which I just love :) On Sun, Feb 20, 2011 at 9:03 AM, Francois PIETTE francois.pie...@skynet.be wrote: I made my own twitter and oauth libraries from scratch, full unicode support, with ICS :) Never liked Indy. http://eden.fm/twitmee/ Good ! Do you made it freeware/opensource ? I only see an exe file at the link you provided. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
I don't get why ICS isnt more widely used, Well ICS is widely used. More than one hundred thousands download so far. And about four thousands registration (That's how many postcards I've receive so far. BTW: Have you mailed yours ?). it's imo far more advanced and gives you a lot more control over what's happening, besides the ASync calls which I just love :) Spread the word ! Blog about it ! Write in Embarcadero and other forums. Take part or FaceBook and Linked-In groups. -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
closed source for now since im using it for another large project, and the libraries are not complete, it's mostly just the steps to auth with twitter and send the messages. :-( You should really consider making in freeware/opensource. You'll gain something: other people will find bugs and make enhancements. Your own applications will then be better. And you'll enter the hall of fames :-) -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
I made my own twitter and oauth libraries from scratch, full unicode support, with ICS :) Never liked Indy. http://eden.fm/twitmee/ On Fri, Feb 18, 2011 at 3:57 PM, Francois PIETTE francois.pie...@skynet.bewrote: OK, thanks for the infos. -- francois.pie...@overbyte.be http://www.overbyte.be - Original Message - From: RTT p...@sapo.pt To: ICS support mailing twsocket@elists.org Sent: Friday, February 18, 2011 3:47 PM Subject: Re: [twsocket] TTwitter component On 18-02-2011 13:52, Francois PIETTE wrote: It starts to become interesting :-) What other dependency is there ? None What is the license for that component ? Could it be added to ICS distribution or ICS usermade web page ? From what I can see, MIT License for all the code from the author of the TTwitter component. It's using also a modified OAuth.pas, to deal with the OAuth stuff, under MPL, and a LkJSON unit, to parse json, that is stated at sourceforge as being BDS. You can check for yourself http://www.lakraven.com/delphi-stuff/ttwitter/ But this project is currently beta, and it's really very incomplete and confuse. In the author site, in the comments, the author posted this, and I quote At present TTwitter only provides the means to read and post Tweets… more developments are very-much on the way. Currently I’m rewriting TTwitter to make use of a new “Social Delphi” component platform I’ve been developing… this new version of TTwitter will be releasing quite soon at the launch of the purpose-built website, along with components for other social networking websites such as Facebook etc. The new platform in-fact DOES allow you to bypass the TComponent layers and access the raw API’s directly if you wish (though I don’t expect many people will want to do that since the component layers make life so much easier) I do recommend you follow me on Twitter (@LaKraven) so you’ll be informed as soon as the new versions are available (on the new website) -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
On 18-02-2011 13:52, Francois PIETTE wrote: It starts to become interesting :-) What other dependency is there ? None What is the license for that component ? Could it be added to ICS distribution or ICS usermade web page ? From what I can see, MIT License for all the code from the author of the TTwitter component. It's using also a modified OAuth.pas, to deal with the OAuth stuff, under MPL, and a LkJSON unit, to parse json, that is stated at sourceforge as being BDS. You can check for yourself http://www.lakraven.com/delphi-stuff/ttwitter/ But this project is currently beta, and it's really very incomplete and confuse. In the author site, in the comments, the author posted this, and I quote At present TTwitter only provides the means to read and post Tweets… more developments are very-much on the way. Currently I’m rewriting TTwitter to make use of a new “Social Delphi” component platform I’ve been developing… this new version of TTwitter will be releasing quite soon at the launch of the purpose-built website, along with components for other social networking websites such as Facebook etc. The new platform in-fact DOES allow you to bypass the TComponent layers and access the raw API’s directly if you wish (though I don’t expect many people will want to do that since the component layers make life so much easier) I do recommend you follow me on Twitter (@LaKraven) so you’ll be informed as soon as the new versions are available (on the new website) -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] TTwitter component
OK, thanks for the infos. -- francois.pie...@overbyte.be http://www.overbyte.be - Original Message - From: RTT p...@sapo.pt To: ICS support mailing twsocket@elists.org Sent: Friday, February 18, 2011 3:47 PM Subject: Re: [twsocket] TTwitter component On 18-02-2011 13:52, Francois PIETTE wrote: It starts to become interesting :-) What other dependency is there ? None What is the license for that component ? Could it be added to ICS distribution or ICS usermade web page ? From what I can see, MIT License for all the code from the author of the TTwitter component. It's using also a modified OAuth.pas, to deal with the OAuth stuff, under MPL, and a LkJSON unit, to parse json, that is stated at sourceforge as being BDS. You can check for yourself http://www.lakraven.com/delphi-stuff/ttwitter/ But this project is currently beta, and it's really very incomplete and confuse. In the author site, in the comments, the author posted this, and I quote At present TTwitter only provides the means to read and post Tweets… more developments are very-much on the way. Currently I’m rewriting TTwitter to make use of a new “Social Delphi” component platform I’ve been developing… this new version of TTwitter will be releasing quite soon at the launch of the purpose-built website, along with components for other social networking websites such as Facebook etc. The new platform in-fact DOES allow you to bypass the TComponent layers and access the raw API’s directly if you wish (though I don’t expect many people will want to do that since the component layers make life so much easier) I do recommend you follow me on Twitter (@LaKraven) so you’ll be informed as soon as the new versions are available (on the new website) -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
