Comments on: Design Decisions – A REST Library

By: Gustavo Carreno

Gustavo Carreno — Tue, 14 Apr 2009 22:27:04 +0000

I’ve finally released a VERY EARLY version of the Dweetta Lib, my own version of a Twitter lib and simple client for Delphi/FreePascal.

You can find the Assembla page here: http://www.assembla.com/spaces/Dweetta

I hope the community gives a hand.

By: Scott Cooper

Scott Cooper — Sun, 12 Apr 2009 08:41:01 +0000

Hi Jamie,

I’ve worked with Delphi for 13 years. Maybe in somewhat of a tunnel-vision way. Primarily in a D7 and below – Win 32 environment, but working with a different group, and with a different type of App intrigues me enough that I’d like to offer some time to your Twitter project – if you’re interested. I have also done some Asp.Net and tinkered with REST via Rails. Shoot me an email if you’re interested.

Thanks,
Scott – We met earlier today via Twitter – I’m @CodeWhiz

By: Gustavo Carreno

Gustavo Carreno — Thu, 02 Apr 2009 14:54:35 +0000

@Jamie: Yes it will, and probably with the JSON lib I’ve sent you by mail. Let’s hope that gets us closer

http://www.progdigy.com/?page_id=6

By: jamie

jamie — Thu, 02 Apr 2009 14:51:03 +0000

@Gustavo: It’ll click together eventually ..

@rap: Apparently the UK isn’t able to access that video but I suspect I know which video you might be linking to!

@katoa: Thanks for your input, I’m a fan of these types of dual wrappers myself anyway.

By: katoa

katoa — Sun, 29 Mar 2009 18:11:18 +0000

I agree with David 100%. DISQlite3, for example, took this approach – a very thin wrapper around the native sqlite api’s, then the ‘Delphi way’ object-oriented full-featured structure. I personally have used both of these wrappers for different purposes. I think the best libraries provide both types of layers…

By: rap

rap — Sun, 29 Mar 2009 02:13:35 +0000

I pretty sure that the code will be more will be far most instructing the twitter itself

http://www.youtube.com/watch?v=PN2HAroA12w

By: Gustavo Carreno

Gustavo Carreno — Sat, 28 Mar 2009 23:52:26 +0000

@Jamie and @David: This is what I’ve been thinking about in general terms, I can’t just put my head together to get t o the specifics, AAAAAARGH

By: jamie

jamie — Sat, 28 Mar 2009 23:49:06 +0000

@David Novo: That is probably the ideal solution and it looks as if that might be the way we are heading anyway. The only problem with that, I guess, Is that you have to add the polishing touches to two classes but it would probably be worth it.

@Jim: Thanks!

By: Jim McKeeth

Jim McKeeth — Sat, 28 Mar 2009 23:03:46 +0000

Excellent write up Jamie!

By: David Novo

David Novo — Sat, 28 Mar 2009 18:45:25 +0000

Why don’t you get the best of both worlds?

Make a TAsCloseAsPossibleToTheTwitterAPI
Then make a TDelphiTwitter that contains an aggregated instance of the TAsCloseAsPossible…. The TDelphiTwitter will expose easier to use “Delphi-ified” methods, but will call the TAsCloseAsPossible to communicate with the server.

That way, if you are a twitter genius, you can just instantiate the TAsCloseAsPossible and use it directly if you like.