There were plans to make the jsdo opene source. Any idea whan that could become real? Could motivate prospects to step in.
Reply by agent_008_nlThanks for your reactions. The CDO is new to me. If I understand the links correctly CDO is no more than a rebranding of JSDO? In that case I find JSDO a less cloudy /clearer name I must say, but there will be marketing reasons. Further more the JSDO is positioned as "an implementation of the CDO for a JavaScript" (why "implementation"?) "available for a browser or hybrid mobile client running against a Progress OpenEdge® server" (clouddataobject.github.io/CDO). This is confusing for me also. Bill Wood assured I am not bound to the progress appserver when I use the jsdo community.progress.com/.../55518.aspx. I trusted that this is so, at least when I do not use the built in ablFilter community.progress.com/.../57662.aspx.
Regards, Stefan.
Stop receiving emails on this subject.Flag this post as spam/abuse.
The Cloud Data Object and JSDO are now available on GitHub.
You can access it using clouddataobject.github.io/CDO
- Check out all of the links to see the repos in GitHub
- Any missing items will be deployed by EOD Saturday
The AppBuilder mobile template is available in both the Telerik Platform and on GitHub so users can easily create Mobile Apps that work with an OE server.
Just saw a post from Edsel today... community.progress.com/.../18212.aspx
I agree the headline should have been JSDO open sourced but it's there in the post - github.com/.../lib
Just saw a post from Edsel today... community.progress.com/.../18212.aspx
I agree the headline should have been JSDO open sourced but it's there in the post - github.com/.../lib
The Cloud Data Object and JSDO are now available on GitHub.
You can access it using clouddataobject.github.io/CDO
- Check out all of the links to see the repos in GitHub
- Any missing items will be deployed by EOD Saturday
The AppBuilder mobile template is available in both the Telerik Platform and on GitHub so users can easily create Mobile Apps that work with an OE server.
Thanks for your reactions. The CDO is new to me. If I understand the links correctly CDO is no more than a rebranding of JSDO? In that case I find JSDO a less cloudy /clearer name I must say, but there will be marketing reasons. Further more the JSDO is positioned as "an implementation of the CDO for a JavaScript" (why "implementation"?) "available for a browser or hybrid mobile client running against a Progress OpenEdge® server" (clouddataobject.github.io/CDO). This is confusing for me also. Bill Wood assured I am not bound to the progress appserver when I use the jsdo community.progress.com/.../55518.aspx. I trusted that this is so, at least when I do not use the built in ablFilter community.progress.com/.../57662.aspx.
Regards, Stefan.
Reply by agent_008_nlThanks for your reactions. The CDO is new to me. If I understand the links correctly CDO is no more than a rebranding of JSDO? In that case I find JSDO a less cloudy /clearer name I must say, but there will be marketing reasons. Further more the JSDO is positioned as "an implementation of the CDO for a JavaScript" (why "implementation"?) "available for a browser or hybrid mobile client running against a Progress OpenEdge® server" (clouddataobject.github.io/CDO). This is confusing for me also. Bill Wood assured I am not bound to the progress appserver when I use the jsdo community.progress.com/.../55518.aspx. I trusted that this is so, at least when I do not use the built in ablFilter community.progress.com/.../57662.aspx.
Regards, Stefan.
Stop receiving emails on this subject.Flag this post as spam/abuse.
Shelley, this means that eventually switching to odata as standard is now definitively ruled out? There are a bunch of vendors that can use odata (including kendo) and PSC (through Data Direct) is part of the committee defining the standard... what is the reason for yet another REST 'standard'?
Reply by Marian EduShelley, this means that eventually switching to odata as standard is now definitively ruled out? There are a bunch of vendors that can use odata (including kendo) and PSC (through Data Direct) is part of the committee defining the standard... what is the reason for yet another REST 'standard'?
Stop receiving emails on this subject.Flag this post as spam/abuse.