Missing OAuthConsumer files and out-of-the-box Demo experience about mgtwitterengine HOT 9 OPEN

You can use my fork of OAuthConsumer ( http://github.com/ctshryock/oauthconsumer ) I recently merged it with another fork that is apparently gone now that had some adjustments specifically for the desktop. My app is desktop only so I had to look around for fixes too.

As far as missing files (in OAuthConsumer); I haven't ran into that; my fork has OACall and OAProblem.

I also plan to update the readme in my fork with notice that it's gear for the desktop and maybe some usage guides.

Patches welcome

from mgtwitterengine.

I guess the missing OAToken_KeychainExtentions.h/m files aren't that important in the grand scheme of things?

I see they where removed as the iPhone version doesn't need them but they are still listed in the MGTwitterEngine project.

Not clear on whether better to use your fork or amazingsyco's

from mgtwitterengine.

You should include the OAuthConsumer code in this project, or at least specify where to go to get the code. I would never in my life have known where to go if not for this issue being posted.

from mgtwitterengine.

It's mentioned in the Wiki under "Migrating from Basic Auth to OAuth/XAuth". Though you have a point, there are other dependancies like yajl and TouchJSON that are in the xcodeproj file but not in the source, and people new to the engine might now know what's going on there.

I've created a separate ticket for creating a "getting started" wiki page. Hopefully that will help people in the future

from mgtwitterengine.

The one mentioned in the wiki seems to be the correct one (complete with the "Crytpo" typo). This is a pretty nasty setup for anybody starting off here, specially since there are quite a few "oauthconsumer" projects out there. Having a link to the correct one buried under the wrong wiki title (I'm not migrating from Basic Auth, but starting from scratch in OAuth) definitely does not help.

I don't think the external code should be included with the project, but links to the resources should be placed in an obvious location in the project page, and in the README file on the project. Currently the README file mentions absolutely nothing about external libraries.

from mgtwitterengine.

I put together a wiki page with the balance of what I figured out getting MGTE up and running. Feedback welcome.

from mgtwitterengine.

Still lots of dependencies missing in the project. I remember going down this path before, but it was months/years ago. Wish I remember how do to this. First, there is a OAToken.h file missing (then 530 other errors)

from mgtwitterengine.

Having same problems compiling/adding files/resolving dependencies as above. Can anyone provide a proper project set with the latest versions that resolves all the typos/builds/includes? I've spent more than all morning on this and cannot get it to build. Yajl #include's are sometimes "" vs. <>? ...and being new to UNIX environments, using cmake and build steps are not familiar either (cf. Wiki by @irons). Looks like a great Engine in Objective-C, but not getting past the build stages at a much lower level. A functional project tree buildable as-is would be extremely helpful to use these tools.

from mgtwitterengine.

My fork my help you: https://github.com/ctshryock/mgtwitterengine

from mgtwitterengine.