Re: Editing resources

I've just dropped the latest version of my AngularJS Hydra client into
GitHub:

https://github.com/dataunity/dataunity-hydra-client/blob/master/js/dataunity-hydraclient-0.1.0.js

The main code starts at line 120 (the code before this is part of an
extension mechanism to override the default behaviour).

It works very well with my API(!), but probably wont work with other APIs
just yet. I've listed the main issues on the Readme page [1]. The issues
aren't major, I was aiming to fix them before releasing the project but
I've got serious time issues at the moment.

Lots of the code is support code for things like RDF namespaces and reading
JSON-LD. The controllers are probably the first thing to look at (line 769
for the 'item' controller, with the others following). There's a very brief
overview of the methodology in the GitHub readme.

What would be a great help is if anyone has a copy of the Events demo API
with CORs headers (or a similar demo API). It would be good to have
something to test the client against other than my API, which isn't ready
for public release yet. If someone has the code for a demo API could they
chuck it up on a heroku instance (or something similar)?

Thanks,

Kev

[1] https://github.com/dataunity/dataunity-hydra-client

On 7 November 2014 17:09, <tomasz@t-code.pl> wrote:

> Hi Cedric,
>
> I do have a repository but I haven't managed to accomplish much about the
> Hydra client. Truth be told I think my approach was flawed. And I also
> spent quite some time learning how to use jsonld.js to get what I wanted
> from the Hydra-aware resource.
>
> I was planning to start from stratch anyway but by doing small steps and
> thinking about the AngularJs API first - services, directives, etc. I'm not
> aware of any other Hydra client for javascript. By the way I guess we don't
> have to be entirely tied to AngularJs.
>
> If you decide to create a repository that's fine. We could move some
> technical discussions there. However I wouldn't rush into implementation
> just yet. I know the hurdles I faced and there are challenges I expect.
> Also we must be on the same regarding what kind of user-facing API we
> really want.
>
> What do you think?
>
> Regards,
> Tom
>
> November 7 2014 4:07 PM, "Dumont Cedric" <cedric.dumont@outlook.com>
> wrote:
> > Hi Tom,
> >
> > did you put your code on Github or another repo (bitbucket...)?
> >
> > I will wait for Kev answer to see if he has sthg mature that we can
> contribute to. (or anybody
> > else)
> >
> > If not, I will start an own implementation and put it available most
> probably on github.
> >
> > I was also thinking on doing a module that could be reused (or extended,
> or configurable...)
> >
> > regards
> >
> >> Date: Fri, 7 Nov 2014 09:42:01 +0000
> >> From: tomasz@t-code.pl
> >> To: cedric.dumont@outlook.com; public-hydra@w3.org
> >> Subject: Re: Editing resources
> >>
> >> Hi Cedric
> >>
> >> I've been thinking about an AngularJs client for Hydra. I guess it
> could be an independent part
> > of a console. I intended to develop such module for use in my private
> project. As such I don't have
> > a rquirement for a 100% automatic client, but there are many areas that
> would overlap.
> > Unfortunately I got (again!) distracted by all sort of other stuff and
> private life that I haven't
> > had much progress.
> >>
> >> On the other hand I've been thinking about a number of features and the
> general API. I'm not
> > AngularJs expert either though.
> >>
> >> Regards,
> >> Tom
> >>
> >> November 7 2014 10:25 AM, "Dumont Cedric" <cedric.dumont@outlook.com>
> wrote:
> >> > Hi,
> >> >
> >> > this is my first post on this public mailing list.
> >> >
> >> > I am looking for a hydra client implemented in Angularjs and
> regarding this thread, it seems
> > that
> >> > that Kev is working on some implementation.
> >> >
> >> > My question:
> >> >
> >> > - is that console supposed to be open-sourced ? and could I use it
> for my own project ?
> >> >
> >> > - if yes : may I help in the development of this? (I am not really
> expert in angularJS, but am
> > .net
> >> > and J2EE dev)
> >> > - if not : does anyone want to start such a project with me (open
> source ?)
> >> >
> >> > Kind regards
> >> >
> >> > Dumont Cedric
> >> >> From: markus.lanthaler@gmx.net
> >> >> To: public-hydra@w3.org
> >> >> Date: Thu, 6 Nov 2014 21:12:18 +0100
> >> >> Subject: RE: Editing resources
> >> >>
> >> >> On Wednesday, November 05, 2014 7:27 PM, Kev Kirkland wrote:
> >> >>>> > version of the Hydra Client I would like the fields to be
> populated
> >> >>>> > with the data for the event (by automatically doing a GET
> request for
> >> >>>> > the resource).
> >> >>>>
> >> >>>> You could tweak the HydraConsole to, e.g., understand
> >> >>>> http://schema.org/ReplaceAction and make the UI act as you
> >> >>>> described. I'd probably merge a PR doing so if you would file one
> >> >>>> ;-P
> >> >>>
> >> >>> I don't know PHP so unfortunately, so can't supply a PR for the PHP
> >> >>> Hydra Console.
> >> >>
> >> >> The HydraConsole is mostly implemented in JavaScript. PHP is just
> used to implement a proxy
> > [1]
> >> >
> >> > to work around cross-origin restrictions and to expand/frame the
> JSON-LD. All the logic is
> >> > implemented in JavaScript (in a very ugly way using Backbone.js) [2].
> >> >>> I'll make the change in the AngularJS console I'm working on though.
> >> >>
> >> >> Cool
> >> >>
> >> >>> I haven't released the AngularJS Console just yet - there's two
> things
> >> >>> holding me up. The first issue is that it looks up the API Doc from
> a
> >> >>> static URL (rather than using the rel link in the HTTP header).
> >> >>
> >> >> Why is that? Do you have problems getting at or parsing the HTTP
> Link header?
> >> >>
> >> >>> Secondly I'd need to write a demo app which delivers Hydra JSON-LD
> >> >>> with CORs headers (the client doesn't use a proxy like the PHP
> >> >>> version). Been on my list of things to do for a while, but really
> >> >>> busy.
> >> >>
> >> >> Yeah, I should add CORS headers to the demo APIs. Are you aware of
> APItools? It's quite handy
> > for
> >> >
> >> > debugging and simply transformations as adding CORS headers.
> >> >> [1] https://github.com/lanthaler/HydraConsole/blob/master/proxy.php
> >> >> [2]
> https://github.com/lanthaler/HydraConsole/blob/master/js/hydra.js
> >> >>
> >> >> Cheers,
> >> >> Markus
> >> >>
> >> >> --
> >> >> Markus Lanthaler
> >> >> @markuslanthaler
> >> >>
> >> >>> Thanks,
> >> >>>
> >> >>> Kev
> >> >>> Thanks for the reply Markus
> >> >>>
> >> >>>> version of the Hydra Client I would like the fields to be populated
> >> >>>> with the data for the event (by automatically doing a GET request
> for
> >> >>>> the resource).
> >> >>>
> >> >>> You could tweak the HydraConsole to, e.g., understand
> >> >>> http://schema.org/ReplaceAction and make the UI act as you
> described.
> >> >>> I'd probably merge a PR doing so if you would file one ;-P I don't
> >> >>> know PHP so unfortunately, so can't supply a PR for the PHP Hydra
> >> >>> Console. I'll make the change in the AngularJS console I'm working
> on
> >> >>> though.
> >> >>>
> >> >>> I haven't released the AngularJS Console just yet - there's two
> things
> >> >>> holding me up. The first issue is that it looks up the API Doc from
> a
> >> >>> static URL (rather than using the rel link in the HTTP header).
> >> >>> Secondly I'd need to write a demo app which delivers Hydra JSON-LD
> >> >>> with CORs headers (the client doesn't use a proxy like the PHP
> >> >>> version). Been on my list of things to do for a while, but really
> >> >>> busy.
> >> >>>
> >> >>> Thanks,
> >> >>>
> >> >>> Kev
> >>
> >>
>
>
>


-- 
www.dataunity.org
twitter: @data_unity