Hey all,
I'm working on a Clojurescript wrapper of Facebook's JS SDK, using
Prismatic's schema for documentation / types. Here's the code:
https://gist.github.com/sritchie/b517d67f9507aca36399
If anyone here's interested I'd be happy to put a little library up on
github with this and the res
t;> (filter #(p/has-edge? g % n) (p/nodes g
>>>>
>>>> E.g., implementations of Loom's API need to provide two implementations
>>>> of neighbors and need to implement add-nodes* instead of only add-node*.
>>>> This may not be much more work to d
ilter #(p/has-edge? g % n) (p/nodes g
>>>
>>> E.g., implementations of Loom's API need to provide two implementations
>>> of neighbors and need to implement add-nodes* instead of only add-node*.
>>> This may not be much more work to do. However, the
Loom is a great project, has the
>> same goals and, in terms of functionality, is way ahead of my efforts.
>>
>> Said all that, I definitely don't want there to be two competing graph
>> APIs. That would be counterproductive. I see the following possible
>> solu
t;>
>> On Monday, June 17, 2013 1:14:34 PM UTC-7, dgrnbrg wrote:
>>>
>>> I think that there's already a project working on this called Loom. The
>>> furthest-developed fork is here: https://github.com/aysylu/loom which
>>> appears to have protocols
great project, has the
> same goals and, in terms of functionality, is way ahead of my efforts.
>
> Said all that, I definitely don't want there to be two competing graph
> APIs. That would be counterproductive. I see the following possible
> solutions:
>
> 1. I keep the
gt;
> Please, don't get me wrong. I think that Loom is a great project, has the
> same goals and, in terms of functionality, is way ahead of my efforts.
>
> Said all that, I definitely don't want there to be two competing graph
> APIs. That would be counterproductive. I se
ing graph
APIs. That would be counterproductive. I see the following possible
solutions:
1. I keep the code to myself and let loom be the sole graph API.
2. We transfer the advantages of my proposal to Loom and change its API. Do
you know of any implementations of the API outside Loom itself? If there
are
ualization support, and implementations
> of several algorithms.
>
> Maybe there's a way to incorporate these projects?
>
> On Monday, June 17, 2013 3:38:45 PM UTC-4, Stephen Kockentiedt wrote:
>>
>> Hello,
>>
>> I want to create a graph API similar
gt;
> On Monday, June 17, 2013 3:38:45 PM UTC-4, Stephen Kockentiedt wrote:
>>
>> Hello,
>>
>> I want to create a graph API similar to what core.matrix is for matrices.
>> I have created some protocols which every graph implementation has to
>> satisfy and a prototy
veral algorithms.
Maybe there's a way to incorporate these projects?
On Monday, June 17, 2013 3:38:45 PM UTC-4, Stephen Kockentiedt wrote:
>
> Hello,
>
> I want to create a graph API similar to what core.matrix is for matrices.
> I have created some protocols which every gr
Hello,
I want to create a graph API similar to what core.matrix is for matrices. I
have created some protocols which every graph implementation has to satisfy
and a prototype implementation. Now I want your feedback on these
protocols. Which functions do you want to see which aren't
Dear Max,
thank you very much for explanation :)
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To
Hi Bojan,
there has been a global change within the Facebook Graph API, it
doesn't sent a referer in the headers of the authentication callback
request anymore.
A middleware function of clj-facebook-graph has relied upon this
referer. I have fixed this issue in version 0.1.3-SNAPSHOT, but no
I got latest version of your framework from Github and it works OK.
I am not sure if this is related to new settings in Facebook App page (I put
most of them to Disabled now) or some global change.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
T
Dear Max,
have there been some changes around Facebook authentication, because now it
seems as token that is returned is not valid?
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note tha
Dear Max,
this works like a charm.
Thank you very much for real fast response.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be pa
Hi Bojan,
I've added a basic support to post something against the Facebook
Graph API. The documentation for this new feature can be found under
https://github.com/maxweber/clj-facebook-graph
Best regards
Max
On 9 Mai, 20:22, Bojan Jovičić wrote:
> Hi Max,
> I have started investi
Hi Max,
I have started investigating this, and it works very nice.
I am a noob in Clojure/Java and I have a question about posting to FB using
your library. I tried something like this:
*(def auth-token (facebook-auth-by-name))
(def auth-name (first (keys auth-token)))
(with-facebook-auth-by-na
Hi Max,
I'm already using your library for a university project, and it's very
well written.
Good job!
Best,
Alfredo
On Apr 8, 12:16 pm, Max Weber wrote:
> Hello everyone,
>
> I like to introduce you to clj-facebook-graph, it is a Clojure client
> for the Facebook Graph
Hello everyone,
I like to introduce you to clj-facebook-graph, it is a Clojure client
for the Facebook Graph API and it is based on clj-http and Ring. I
have written a blog post about how to leverage clj-facebook-graph to
query the Facebook Graph API:
http://max-weber.tumblr.com/post/4183433816
21 matches
Mail list logo
