You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ripple.apache.org by Hadrien TULIPE <ha...@gmail.com> on 2013/09/19 23:39:15 UTC
Support of Cordova 3.0.0
Hi there,
I understood that help could be welcome for cordova 3 support.
I'd like to know if there is anything I can do to help you with that I
never worked on Chrome extensions but I'm quite used to Javascript/HTML
stuff.
Let me know. For the record I'm at GMT+2
Cheers
Re: Support of Cordova 3.0.0
Posted by Gord Tanner <gt...@gmail.com>.
So I added support for running `ripple emulate` on a cordova 3.0 directory
[1]. There is still some work to do on it as right now it assumes that
they have an android platform.
Todo on it:
- handle different platforms (preparing and navigating to correct hosting
folder)
- handle selection of platfom based on query string
- open browser
- Double check existing API support (MobileSpec review)
We should ensure that our test count for Cordova's mobile spec [2] stays
the roughly the same between Cordova 2.X and Cordova 3.X. Any more tests
that we can pass during this review is awesome.
- Using the correct platform javascript / resources based on the selected
device (would be nice).
I will be handling this with my work mentioned above.
Things are starting to get close!
[1] -
https://git-wip-us.apache.org/repos/asf?p=incubator-ripple.git;a=commitdiff;h=af934027bc2ec7f7761f8c25fc1765934fafb6a5
[2] - https://github.com/apache/cordova-mobile-spec
On Tue, Oct 1, 2013 at 3:49 PM, Hadrien TULIPE <ha...@gmail.com>wrote:
> AFAIK there are no differences for config.xml between 2.x and 3.x and the
> current piece of code can be reused as is. I won't swear it though, I saw
> that you added a whitelist attribute to widgetInfo object.
>
> Another thing, I tried config.xml validation on two projects: one created
> with cordova-cli and another created with phonegap-cli. While the phonegap
> project validated successfully the cordova one failed. This is due to
> spec/config.js that requires a phonegap namespace (called 'gap'). What
> about pure cordova projects?
>
> Going back to config.xml support, I don't see much more that can be done.
> Please correct me if I'm mistaken. Otherwise I can start on semthin else, I
> saw two items in your previous TODO list:
>
> - Double check existing API support (MobileSpec review)
> - Using the correct platform javascript / resources based on the selected
> device (would be nice)
>
> Could you give me some more details on those two?
>
> Regards
>
> Hadrien Tulipe
>
>
> 2013/9/30 Hadrien TULIPE <ha...@gmail.com>
>
>> Hi Gord, I had little time this week for myself and I had to clean
>> install my linux distro. I only had the time to look into the code. Please
>> go ahead with the ripple command line stuff. I'm hopping to dig into the
>> code this afternoon, I will see about the config.xml parser.
>>
>> Cheers
>>
>> Hadrien Tulipe
>>
>>
>> 2013/9/30 Gord Tanner <gt...@gmail.com>
>>
>>> Hey Hadrien,
>>>
>>> I was thinking of starting the ripple emulate support for cordova 3.0
>>> project directories this week, did you start that yet?
>>>
>>> I am going to take a look into it starting tomorrow night.
>>>
>>> Gord
>>>
>>>
>>> On Sun, Sep 22, 2013 at 12:51 AM, Gord Tanner <gt...@gmail.com> wrote:
>>>
>>>> Sounds awesome.
>>>>
>>>> I hacked a bit more on the InAppBrowser. I stubbed in a route for
>>>> using our proxy code and setting the iframe to
>>>> localhost:4400/ripple/browser [1]. Had some unexpected issues with
>>>> navigation and such (which makes sense now that I have coded it). I should
>>>> have this cleaned up soon though with or without the iframe.
>>>>
>>>> Gord
>>>>
>>>> [1] -
>>>> https://github.com/apache/incubator-ripple/commit/f7881559a06fb104a33d6551d49fda3ec6eaec35
>>>>
>>>>
>>>> On Sat, Sep 21, 2013 at 5:39 AM, Hadrien TULIPE <
>>>> hadrientulipe@gmail.com> wrote:
>>>>
>>>>> I will start with xml parsing/validation and check the ripple emulate
>>>>> command issue
>>>>>
>>>>> Hadrien Tulipe
>>>>>
>>>>>
>>>>> 2013/9/20 Raymond Camden <ra...@gmail.com>
>>>>>
>>>>> > I thought it was the default to go through the Ripple proxy? From
>>>>> what I
>>>>> > remember, you had to tell it specifically when you didn't want to
>>>>> use it.
>>>>> >
>>>>> >
>>>>> > On Thu, Sep 19, 2013 at 9:29 PM, Gord Tanner <gt...@gmail.com>
>>>>> wrote:
>>>>> >
>>>>> >> So for InAppBrowser I am getting blocked by CORS and web security.
>>>>> I can
>>>>> >> emulate this with just a simple overlay that will invoke any
>>>>> callbacks
>>>>> >> that
>>>>> >> are registered and show the developer the arguments that were used
>>>>> to show
>>>>> >> it.
>>>>> >>
>>>>> >> It is kinda a cop out for now but will get us moving on quickly
>>>>> adding
>>>>> >> cordova 3.0 support.
>>>>> >>
>>>>> >> I am wondering if we could use the proxy code to add a route to the
>>>>> ripple
>>>>> >> server for the InAppBrowser. I am not familiar with this code but
>>>>> it
>>>>> >> seems
>>>>> >> doable, thoughts Brent?
>>>>> >>
>>>>> >> Would be cool to just set the iFrames URL to:
>>>>> >>
>>>>> >> http://localhost:4400/ripple/inappbrowser?url=
>>>>> <user_url_encoded_here>
>>>>> >>
>>>>> >> That would be epic.
>>>>> >>
>>>>> >>
>>>>> >> On Thu, Sep 19, 2013 at 8:40 PM, Gord Tanner <gt...@gmail.com>
>>>>> wrote:
>>>>> >>
>>>>> >> > So thought I would put a good list of the tasks that need to be
>>>>> done for
>>>>> >> > cordova 3.0 support. Work is being done in the cordova-3.0
>>>>> branch [1]
>>>>> >> >
>>>>> >> > Areas of work:
>>>>> >> >
>>>>> >> > - Double check existing API support (MobileSpec review)
>>>>> >> > - InAppBrowser support
>>>>> >> > - Calling 'ripple emulate' in a cordova folder should work
>>>>> (without
>>>>> >> > needing to navigate to the www folder.
>>>>> >> > - Using the correct platform javascript / resources based on the
>>>>> >> selected
>>>>> >> > device (would be nice)
>>>>> >> > - Review cordova 3.0 config.xml parsing / validation.
>>>>> >> >
>>>>> >> > I am sure there is more but that will get us started.
>>>>> >> >
>>>>> >> > I am going to start on InAppBrowser support. I am going to try to
>>>>> >> handle
>>>>> >> > this with overlays and an iframe. I have a good feeling I will
>>>>> be able
>>>>> >> to
>>>>> >> > get something cool emulated.
>>>>> >> >
>>>>> >> >
>>>>> >> > [1] - https://github.com/apache/incubator-ripple/tree/cordova-3.0
>>>>> >> >
>>>>> >> >
>>>>> >> > On Thu, Sep 19, 2013 at 5:39 PM, Hadrien TULIPE <
>>>>> >> > hadrientulipe+dev@gmail.com> wrote:
>>>>> >> >
>>>>> >> >> Hi there,
>>>>> >> >>
>>>>> >> >> I understood that help could be welcome for cordova 3 support.
>>>>> >> >> I'd like to know if there is anything I can do to help you with
>>>>> that I
>>>>> >> >> never worked on Chrome extensions but I'm quite used to
>>>>> Javascript/HTML
>>>>> >> >> stuff.
>>>>> >> >>
>>>>> >> >> Let me know. For the record I'm at GMT+2
>>>>> >> >>
>>>>> >> >> Cheers
>>>>> >> >>
>>>>> >> >
>>>>> >> >
>>>>> >>
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> >
>>>>> ===========================================================================
>>>>> > Raymond Camden, Adobe Developer Evangelist
>>>>> >
>>>>> > Email : raymondcamden@gmail.com
>>>>> > Blog : www.raymondcamden.com
>>>>> > Twitter: cfjedimaster
>>>>> >
>>>>>
>>>>
>>>>
>>>
>>
>
Re: Support of Cordova 3.0.0
Posted by Hadrien TULIPE <ha...@gmail.com>.
AFAIK there are no differences for config.xml between 2.x and 3.x and the
current piece of code can be reused as is. I won't swear it though, I saw
that you added a whitelist attribute to widgetInfo object.
Another thing, I tried config.xml validation on two projects: one created
with cordova-cli and another created with phonegap-cli. While the phonegap
project validated successfully the cordova one failed. This is due to
spec/config.js that requires a phonegap namespace (called 'gap'). What
about pure cordova projects?
Going back to config.xml support, I don't see much more that can be done.
Please correct me if I'm mistaken. Otherwise I can start on semthin else, I
saw two items in your previous TODO list:
- Double check existing API support (MobileSpec review)
- Using the correct platform javascript / resources based on the selected
device (would be nice)
Could you give me some more details on those two?
Regards
Hadrien Tulipe
2013/9/30 Hadrien TULIPE <ha...@gmail.com>
> Hi Gord, I had little time this week for myself and I had to clean install
> my linux distro. I only had the time to look into the code. Please go ahead
> with the ripple command line stuff. I'm hopping to dig into the code this
> afternoon, I will see about the config.xml parser.
>
> Cheers
>
> Hadrien Tulipe
>
>
> 2013/9/30 Gord Tanner <gt...@gmail.com>
>
>> Hey Hadrien,
>>
>> I was thinking of starting the ripple emulate support for cordova 3.0
>> project directories this week, did you start that yet?
>>
>> I am going to take a look into it starting tomorrow night.
>>
>> Gord
>>
>>
>> On Sun, Sep 22, 2013 at 12:51 AM, Gord Tanner <gt...@gmail.com> wrote:
>>
>>> Sounds awesome.
>>>
>>> I hacked a bit more on the InAppBrowser. I stubbed in a route for using
>>> our proxy code and setting the iframe to localhost:4400/ripple/browser [1].
>>> Had some unexpected issues with navigation and such (which makes sense now
>>> that I have coded it). I should have this cleaned up soon though with or
>>> without the iframe.
>>>
>>> Gord
>>>
>>> [1] -
>>> https://github.com/apache/incubator-ripple/commit/f7881559a06fb104a33d6551d49fda3ec6eaec35
>>>
>>>
>>> On Sat, Sep 21, 2013 at 5:39 AM, Hadrien TULIPE <hadrientulipe@gmail.com
>>> > wrote:
>>>
>>>> I will start with xml parsing/validation and check the ripple emulate
>>>> command issue
>>>>
>>>> Hadrien Tulipe
>>>>
>>>>
>>>> 2013/9/20 Raymond Camden <ra...@gmail.com>
>>>>
>>>> > I thought it was the default to go through the Ripple proxy? From
>>>> what I
>>>> > remember, you had to tell it specifically when you didn't want to use
>>>> it.
>>>> >
>>>> >
>>>> > On Thu, Sep 19, 2013 at 9:29 PM, Gord Tanner <gt...@gmail.com>
>>>> wrote:
>>>> >
>>>> >> So for InAppBrowser I am getting blocked by CORS and web security.
>>>> I can
>>>> >> emulate this with just a simple overlay that will invoke any
>>>> callbacks
>>>> >> that
>>>> >> are registered and show the developer the arguments that were used
>>>> to show
>>>> >> it.
>>>> >>
>>>> >> It is kinda a cop out for now but will get us moving on quickly
>>>> adding
>>>> >> cordova 3.0 support.
>>>> >>
>>>> >> I am wondering if we could use the proxy code to add a route to the
>>>> ripple
>>>> >> server for the InAppBrowser. I am not familiar with this code but it
>>>> >> seems
>>>> >> doable, thoughts Brent?
>>>> >>
>>>> >> Would be cool to just set the iFrames URL to:
>>>> >>
>>>> >> http://localhost:4400/ripple/inappbrowser?url=
>>>> <user_url_encoded_here>
>>>> >>
>>>> >> That would be epic.
>>>> >>
>>>> >>
>>>> >> On Thu, Sep 19, 2013 at 8:40 PM, Gord Tanner <gt...@gmail.com>
>>>> wrote:
>>>> >>
>>>> >> > So thought I would put a good list of the tasks that need to be
>>>> done for
>>>> >> > cordova 3.0 support. Work is being done in the cordova-3.0 branch
>>>> [1]
>>>> >> >
>>>> >> > Areas of work:
>>>> >> >
>>>> >> > - Double check existing API support (MobileSpec review)
>>>> >> > - InAppBrowser support
>>>> >> > - Calling 'ripple emulate' in a cordova folder should work (without
>>>> >> > needing to navigate to the www folder.
>>>> >> > - Using the correct platform javascript / resources based on the
>>>> >> selected
>>>> >> > device (would be nice)
>>>> >> > - Review cordova 3.0 config.xml parsing / validation.
>>>> >> >
>>>> >> > I am sure there is more but that will get us started.
>>>> >> >
>>>> >> > I am going to start on InAppBrowser support. I am going to try to
>>>> >> handle
>>>> >> > this with overlays and an iframe. I have a good feeling I will be
>>>> able
>>>> >> to
>>>> >> > get something cool emulated.
>>>> >> >
>>>> >> >
>>>> >> > [1] - https://github.com/apache/incubator-ripple/tree/cordova-3.0
>>>> >> >
>>>> >> >
>>>> >> > On Thu, Sep 19, 2013 at 5:39 PM, Hadrien TULIPE <
>>>> >> > hadrientulipe+dev@gmail.com> wrote:
>>>> >> >
>>>> >> >> Hi there,
>>>> >> >>
>>>> >> >> I understood that help could be welcome for cordova 3 support.
>>>> >> >> I'd like to know if there is anything I can do to help you with
>>>> that I
>>>> >> >> never worked on Chrome extensions but I'm quite used to
>>>> Javascript/HTML
>>>> >> >> stuff.
>>>> >> >>
>>>> >> >> Let me know. For the record I'm at GMT+2
>>>> >> >>
>>>> >> >> Cheers
>>>> >> >>
>>>> >> >
>>>> >> >
>>>> >>
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> >
>>>> ===========================================================================
>>>> > Raymond Camden, Adobe Developer Evangelist
>>>> >
>>>> > Email : raymondcamden@gmail.com
>>>> > Blog : www.raymondcamden.com
>>>> > Twitter: cfjedimaster
>>>> >
>>>>
>>>
>>>
>>
>
Re: Support of Cordova 3.0.0
Posted by Hadrien TULIPE <ha...@gmail.com>.
Hi Gord, I had little time this week for myself and I had to clean install
my linux distro. I only had the time to look into the code. Please go ahead
with the ripple command line stuff. I'm hopping to dig into the code this
afternoon, I will see about the config.xml parser.
Cheers
Hadrien Tulipe
2013/9/30 Gord Tanner <gt...@gmail.com>
> Hey Hadrien,
>
> I was thinking of starting the ripple emulate support for cordova 3.0
> project directories this week, did you start that yet?
>
> I am going to take a look into it starting tomorrow night.
>
> Gord
>
>
> On Sun, Sep 22, 2013 at 12:51 AM, Gord Tanner <gt...@gmail.com> wrote:
>
>> Sounds awesome.
>>
>> I hacked a bit more on the InAppBrowser. I stubbed in a route for using
>> our proxy code and setting the iframe to localhost:4400/ripple/browser [1].
>> Had some unexpected issues with navigation and such (which makes sense now
>> that I have coded it). I should have this cleaned up soon though with or
>> without the iframe.
>>
>> Gord
>>
>> [1] -
>> https://github.com/apache/incubator-ripple/commit/f7881559a06fb104a33d6551d49fda3ec6eaec35
>>
>>
>> On Sat, Sep 21, 2013 at 5:39 AM, Hadrien TULIPE <ha...@gmail.com>wrote:
>>
>>> I will start with xml parsing/validation and check the ripple emulate
>>> command issue
>>>
>>> Hadrien Tulipe
>>>
>>>
>>> 2013/9/20 Raymond Camden <ra...@gmail.com>
>>>
>>> > I thought it was the default to go through the Ripple proxy? From what
>>> I
>>> > remember, you had to tell it specifically when you didn't want to use
>>> it.
>>> >
>>> >
>>> > On Thu, Sep 19, 2013 at 9:29 PM, Gord Tanner <gt...@gmail.com>
>>> wrote:
>>> >
>>> >> So for InAppBrowser I am getting blocked by CORS and web security. I
>>> can
>>> >> emulate this with just a simple overlay that will invoke any callbacks
>>> >> that
>>> >> are registered and show the developer the arguments that were used to
>>> show
>>> >> it.
>>> >>
>>> >> It is kinda a cop out for now but will get us moving on quickly adding
>>> >> cordova 3.0 support.
>>> >>
>>> >> I am wondering if we could use the proxy code to add a route to the
>>> ripple
>>> >> server for the InAppBrowser. I am not familiar with this code but it
>>> >> seems
>>> >> doable, thoughts Brent?
>>> >>
>>> >> Would be cool to just set the iFrames URL to:
>>> >>
>>> >> http://localhost:4400/ripple/inappbrowser?url=<user_url_encoded_here>
>>> >>
>>> >> That would be epic.
>>> >>
>>> >>
>>> >> On Thu, Sep 19, 2013 at 8:40 PM, Gord Tanner <gt...@gmail.com>
>>> wrote:
>>> >>
>>> >> > So thought I would put a good list of the tasks that need to be
>>> done for
>>> >> > cordova 3.0 support. Work is being done in the cordova-3.0 branch
>>> [1]
>>> >> >
>>> >> > Areas of work:
>>> >> >
>>> >> > - Double check existing API support (MobileSpec review)
>>> >> > - InAppBrowser support
>>> >> > - Calling 'ripple emulate' in a cordova folder should work (without
>>> >> > needing to navigate to the www folder.
>>> >> > - Using the correct platform javascript / resources based on the
>>> >> selected
>>> >> > device (would be nice)
>>> >> > - Review cordova 3.0 config.xml parsing / validation.
>>> >> >
>>> >> > I am sure there is more but that will get us started.
>>> >> >
>>> >> > I am going to start on InAppBrowser support. I am going to try to
>>> >> handle
>>> >> > this with overlays and an iframe. I have a good feeling I will be
>>> able
>>> >> to
>>> >> > get something cool emulated.
>>> >> >
>>> >> >
>>> >> > [1] - https://github.com/apache/incubator-ripple/tree/cordova-3.0
>>> >> >
>>> >> >
>>> >> > On Thu, Sep 19, 2013 at 5:39 PM, Hadrien TULIPE <
>>> >> > hadrientulipe+dev@gmail.com> wrote:
>>> >> >
>>> >> >> Hi there,
>>> >> >>
>>> >> >> I understood that help could be welcome for cordova 3 support.
>>> >> >> I'd like to know if there is anything I can do to help you with
>>> that I
>>> >> >> never worked on Chrome extensions but I'm quite used to
>>> Javascript/HTML
>>> >> >> stuff.
>>> >> >>
>>> >> >> Let me know. For the record I'm at GMT+2
>>> >> >>
>>> >> >> Cheers
>>> >> >>
>>> >> >
>>> >> >
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> ===========================================================================
>>> > Raymond Camden, Adobe Developer Evangelist
>>> >
>>> > Email : raymondcamden@gmail.com
>>> > Blog : www.raymondcamden.com
>>> > Twitter: cfjedimaster
>>> >
>>>
>>
>>
>
Re: Support of Cordova 3.0.0
Posted by Gord Tanner <gt...@gmail.com>.
Hey Hadrien,
I was thinking of starting the ripple emulate support for cordova 3.0
project directories this week, did you start that yet?
I am going to take a look into it starting tomorrow night.
Gord
On Sun, Sep 22, 2013 at 12:51 AM, Gord Tanner <gt...@gmail.com> wrote:
> Sounds awesome.
>
> I hacked a bit more on the InAppBrowser. I stubbed in a route for using
> our proxy code and setting the iframe to localhost:4400/ripple/browser [1].
> Had some unexpected issues with navigation and such (which makes sense now
> that I have coded it). I should have this cleaned up soon though with or
> without the iframe.
>
> Gord
>
> [1] -
> https://github.com/apache/incubator-ripple/commit/f7881559a06fb104a33d6551d49fda3ec6eaec35
>
>
> On Sat, Sep 21, 2013 at 5:39 AM, Hadrien TULIPE <ha...@gmail.com>wrote:
>
>> I will start with xml parsing/validation and check the ripple emulate
>> command issue
>>
>> Hadrien Tulipe
>>
>>
>> 2013/9/20 Raymond Camden <ra...@gmail.com>
>>
>> > I thought it was the default to go through the Ripple proxy? From what I
>> > remember, you had to tell it specifically when you didn't want to use
>> it.
>> >
>> >
>> > On Thu, Sep 19, 2013 at 9:29 PM, Gord Tanner <gt...@gmail.com> wrote:
>> >
>> >> So for InAppBrowser I am getting blocked by CORS and web security. I
>> can
>> >> emulate this with just a simple overlay that will invoke any callbacks
>> >> that
>> >> are registered and show the developer the arguments that were used to
>> show
>> >> it.
>> >>
>> >> It is kinda a cop out for now but will get us moving on quickly adding
>> >> cordova 3.0 support.
>> >>
>> >> I am wondering if we could use the proxy code to add a route to the
>> ripple
>> >> server for the InAppBrowser. I am not familiar with this code but it
>> >> seems
>> >> doable, thoughts Brent?
>> >>
>> >> Would be cool to just set the iFrames URL to:
>> >>
>> >> http://localhost:4400/ripple/inappbrowser?url=<user_url_encoded_here>
>> >>
>> >> That would be epic.
>> >>
>> >>
>> >> On Thu, Sep 19, 2013 at 8:40 PM, Gord Tanner <gt...@gmail.com>
>> wrote:
>> >>
>> >> > So thought I would put a good list of the tasks that need to be done
>> for
>> >> > cordova 3.0 support. Work is being done in the cordova-3.0 branch
>> [1]
>> >> >
>> >> > Areas of work:
>> >> >
>> >> > - Double check existing API support (MobileSpec review)
>> >> > - InAppBrowser support
>> >> > - Calling 'ripple emulate' in a cordova folder should work (without
>> >> > needing to navigate to the www folder.
>> >> > - Using the correct platform javascript / resources based on the
>> >> selected
>> >> > device (would be nice)
>> >> > - Review cordova 3.0 config.xml parsing / validation.
>> >> >
>> >> > I am sure there is more but that will get us started.
>> >> >
>> >> > I am going to start on InAppBrowser support. I am going to try to
>> >> handle
>> >> > this with overlays and an iframe. I have a good feeling I will be
>> able
>> >> to
>> >> > get something cool emulated.
>> >> >
>> >> >
>> >> > [1] - https://github.com/apache/incubator-ripple/tree/cordova-3.0
>> >> >
>> >> >
>> >> > On Thu, Sep 19, 2013 at 5:39 PM, Hadrien TULIPE <
>> >> > hadrientulipe+dev@gmail.com> wrote:
>> >> >
>> >> >> Hi there,
>> >> >>
>> >> >> I understood that help could be welcome for cordova 3 support.
>> >> >> I'd like to know if there is anything I can do to help you with
>> that I
>> >> >> never worked on Chrome extensions but I'm quite used to
>> Javascript/HTML
>> >> >> stuff.
>> >> >>
>> >> >> Let me know. For the record I'm at GMT+2
>> >> >>
>> >> >> Cheers
>> >> >>
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> >
>> ===========================================================================
>> > Raymond Camden, Adobe Developer Evangelist
>> >
>> > Email : raymondcamden@gmail.com
>> > Blog : www.raymondcamden.com
>> > Twitter: cfjedimaster
>> >
>>
>
>
Re: Support of Cordova 3.0.0
Posted by Gord Tanner <gt...@gmail.com>.
Sounds awesome.
I hacked a bit more on the InAppBrowser. I stubbed in a route for using
our proxy code and setting the iframe to localhost:4400/ripple/browser [1].
Had some unexpected issues with navigation and such (which makes sense now
that I have coded it). I should have this cleaned up soon though with or
without the iframe.
Gord
[1] -
https://github.com/apache/incubator-ripple/commit/f7881559a06fb104a33d6551d49fda3ec6eaec35
On Sat, Sep 21, 2013 at 5:39 AM, Hadrien TULIPE <ha...@gmail.com>wrote:
> I will start with xml parsing/validation and check the ripple emulate
> command issue
>
> Hadrien Tulipe
>
>
> 2013/9/20 Raymond Camden <ra...@gmail.com>
>
> > I thought it was the default to go through the Ripple proxy? From what I
> > remember, you had to tell it specifically when you didn't want to use it.
> >
> >
> > On Thu, Sep 19, 2013 at 9:29 PM, Gord Tanner <gt...@gmail.com> wrote:
> >
> >> So for InAppBrowser I am getting blocked by CORS and web security. I
> can
> >> emulate this with just a simple overlay that will invoke any callbacks
> >> that
> >> are registered and show the developer the arguments that were used to
> show
> >> it.
> >>
> >> It is kinda a cop out for now but will get us moving on quickly adding
> >> cordova 3.0 support.
> >>
> >> I am wondering if we could use the proxy code to add a route to the
> ripple
> >> server for the InAppBrowser. I am not familiar with this code but it
> >> seems
> >> doable, thoughts Brent?
> >>
> >> Would be cool to just set the iFrames URL to:
> >>
> >> http://localhost:4400/ripple/inappbrowser?url=<user_url_encoded_here>
> >>
> >> That would be epic.
> >>
> >>
> >> On Thu, Sep 19, 2013 at 8:40 PM, Gord Tanner <gt...@gmail.com> wrote:
> >>
> >> > So thought I would put a good list of the tasks that need to be done
> for
> >> > cordova 3.0 support. Work is being done in the cordova-3.0 branch [1]
> >> >
> >> > Areas of work:
> >> >
> >> > - Double check existing API support (MobileSpec review)
> >> > - InAppBrowser support
> >> > - Calling 'ripple emulate' in a cordova folder should work (without
> >> > needing to navigate to the www folder.
> >> > - Using the correct platform javascript / resources based on the
> >> selected
> >> > device (would be nice)
> >> > - Review cordova 3.0 config.xml parsing / validation.
> >> >
> >> > I am sure there is more but that will get us started.
> >> >
> >> > I am going to start on InAppBrowser support. I am going to try to
> >> handle
> >> > this with overlays and an iframe. I have a good feeling I will be
> able
> >> to
> >> > get something cool emulated.
> >> >
> >> >
> >> > [1] - https://github.com/apache/incubator-ripple/tree/cordova-3.0
> >> >
> >> >
> >> > On Thu, Sep 19, 2013 at 5:39 PM, Hadrien TULIPE <
> >> > hadrientulipe+dev@gmail.com> wrote:
> >> >
> >> >> Hi there,
> >> >>
> >> >> I understood that help could be welcome for cordova 3 support.
> >> >> I'd like to know if there is anything I can do to help you with that
> I
> >> >> never worked on Chrome extensions but I'm quite used to
> Javascript/HTML
> >> >> stuff.
> >> >>
> >> >> Let me know. For the record I'm at GMT+2
> >> >>
> >> >> Cheers
> >> >>
> >> >
> >> >
> >>
> >
> >
> >
> > --
> >
> ===========================================================================
> > Raymond Camden, Adobe Developer Evangelist
> >
> > Email : raymondcamden@gmail.com
> > Blog : www.raymondcamden.com
> > Twitter: cfjedimaster
> >
>
Re: Support of Cordova 3.0.0
Posted by Hadrien TULIPE <ha...@gmail.com>.
I will start with xml parsing/validation and check the ripple emulate
command issue
Hadrien Tulipe
2013/9/20 Raymond Camden <ra...@gmail.com>
> I thought it was the default to go through the Ripple proxy? From what I
> remember, you had to tell it specifically when you didn't want to use it.
>
>
> On Thu, Sep 19, 2013 at 9:29 PM, Gord Tanner <gt...@gmail.com> wrote:
>
>> So for InAppBrowser I am getting blocked by CORS and web security. I can
>> emulate this with just a simple overlay that will invoke any callbacks
>> that
>> are registered and show the developer the arguments that were used to show
>> it.
>>
>> It is kinda a cop out for now but will get us moving on quickly adding
>> cordova 3.0 support.
>>
>> I am wondering if we could use the proxy code to add a route to the ripple
>> server for the InAppBrowser. I am not familiar with this code but it
>> seems
>> doable, thoughts Brent?
>>
>> Would be cool to just set the iFrames URL to:
>>
>> http://localhost:4400/ripple/inappbrowser?url=<user_url_encoded_here>
>>
>> That would be epic.
>>
>>
>> On Thu, Sep 19, 2013 at 8:40 PM, Gord Tanner <gt...@gmail.com> wrote:
>>
>> > So thought I would put a good list of the tasks that need to be done for
>> > cordova 3.0 support. Work is being done in the cordova-3.0 branch [1]
>> >
>> > Areas of work:
>> >
>> > - Double check existing API support (MobileSpec review)
>> > - InAppBrowser support
>> > - Calling 'ripple emulate' in a cordova folder should work (without
>> > needing to navigate to the www folder.
>> > - Using the correct platform javascript / resources based on the
>> selected
>> > device (would be nice)
>> > - Review cordova 3.0 config.xml parsing / validation.
>> >
>> > I am sure there is more but that will get us started.
>> >
>> > I am going to start on InAppBrowser support. I am going to try to
>> handle
>> > this with overlays and an iframe. I have a good feeling I will be able
>> to
>> > get something cool emulated.
>> >
>> >
>> > [1] - https://github.com/apache/incubator-ripple/tree/cordova-3.0
>> >
>> >
>> > On Thu, Sep 19, 2013 at 5:39 PM, Hadrien TULIPE <
>> > hadrientulipe+dev@gmail.com> wrote:
>> >
>> >> Hi there,
>> >>
>> >> I understood that help could be welcome for cordova 3 support.
>> >> I'd like to know if there is anything I can do to help you with that I
>> >> never worked on Chrome extensions but I'm quite used to Javascript/HTML
>> >> stuff.
>> >>
>> >> Let me know. For the record I'm at GMT+2
>> >>
>> >> Cheers
>> >>
>> >
>> >
>>
>
>
>
> --
> ===========================================================================
> Raymond Camden, Adobe Developer Evangelist
>
> Email : raymondcamden@gmail.com
> Blog : www.raymondcamden.com
> Twitter: cfjedimaster
>
Re: Support of Cordova 3.0.0
Posted by Gord Tanner <gt...@gmail.com>.
That is still doing an XHR call. I am attempting to inject the following
into the DOM:
<iframe src="http://someotherserver.com"></iframe>
which is giving me the CORS issue.
Ripple overrides the XMLHttpRequest object from under you which allows us
to fake the request by going to our proxy, we can't do that for injected
DOM content.
On Thu, Sep 19, 2013 at 11:06 PM, Raymond Camden <ra...@gmail.com>wrote:
> Err, right. In the past, Ripple handed them just fine. I could
>
> $.get("http://someotherserver.com")
>
> and even w/o CORS, it worked fine. That's one of the many reasons I liked
> Ripple. ;)
>
> Unless I'm misunderstanding you.
>
>
> On Thu, Sep 19, 2013 at 10:04 PM, Gord Tanner <gt...@gmail.com> wrote:
>
> > That is for XHR calls, not for resources.
> >
> >
> > On Thu, Sep 19, 2013 at 10:41 PM, Raymond Camden <
> raymondcamden@gmail.com
> > >wrote:
> >
> > > I thought it was the default to go through the Ripple proxy? From what
> I
> > > remember, you had to tell it specifically when you didn't want to use
> it.
> > >
> > >
> > > On Thu, Sep 19, 2013 at 9:29 PM, Gord Tanner <gt...@gmail.com>
> wrote:
> > >
> > > > So for InAppBrowser I am getting blocked by CORS and web security. I
> > can
> > > > emulate this with just a simple overlay that will invoke any
> callbacks
> > > that
> > > > are registered and show the developer the arguments that were used to
> > > show
> > > > it.
> > > >
> > > > It is kinda a cop out for now but will get us moving on quickly
> adding
> > > > cordova 3.0 support.
> > > >
> > > > I am wondering if we could use the proxy code to add a route to the
> > > ripple
> > > > server for the InAppBrowser. I am not familiar with this code but it
> > > seems
> > > > doable, thoughts Brent?
> > > >
> > > > Would be cool to just set the iFrames URL to:
> > > >
> > > > http://localhost:4400/ripple/inappbrowser?url=
> <user_url_encoded_here>
> > > >
> > > > That would be epic.
> > > >
> > > >
> > > > On Thu, Sep 19, 2013 at 8:40 PM, Gord Tanner <gt...@gmail.com>
> > wrote:
> > > >
> > > > > So thought I would put a good list of the tasks that need to be
> done
> > > for
> > > > > cordova 3.0 support. Work is being done in the cordova-3.0 branch
> > [1]
> > > > >
> > > > > Areas of work:
> > > > >
> > > > > - Double check existing API support (MobileSpec review)
> > > > > - InAppBrowser support
> > > > > - Calling 'ripple emulate' in a cordova folder should work (without
> > > > > needing to navigate to the www folder.
> > > > > - Using the correct platform javascript / resources based on the
> > > selected
> > > > > device (would be nice)
> > > > > - Review cordova 3.0 config.xml parsing / validation.
> > > > >
> > > > > I am sure there is more but that will get us started.
> > > > >
> > > > > I am going to start on InAppBrowser support. I am going to try to
> > > handle
> > > > > this with overlays and an iframe. I have a good feeling I will be
> > able
> > > > to
> > > > > get something cool emulated.
> > > > >
> > > > >
> > > > > [1] - https://github.com/apache/incubator-ripple/tree/cordova-3.0
> > > > >
> > > > >
> > > > > On Thu, Sep 19, 2013 at 5:39 PM, Hadrien TULIPE <
> > > > > hadrientulipe+dev@gmail.com> wrote:
> > > > >
> > > > >> Hi there,
> > > > >>
> > > > >> I understood that help could be welcome for cordova 3 support.
> > > > >> I'd like to know if there is anything I can do to help you with
> > that I
> > > > >> never worked on Chrome extensions but I'm quite used to
> > > Javascript/HTML
> > > > >> stuff.
> > > > >>
> > > > >> Let me know. For the record I'm at GMT+2
> > > > >>
> > > > >> Cheers
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > >
> >
> ===========================================================================
> > > Raymond Camden, Adobe Developer Evangelist
> > >
> > > Email : raymondcamden@gmail.com
> > > Blog : www.raymondcamden.com
> > > Twitter: cfjedimaster
> > >
> >
>
>
>
> --
> ===========================================================================
> Raymond Camden, Adobe Developer Evangelist
>
> Email : raymondcamden@gmail.com
> Blog : www.raymondcamden.com
> Twitter: cfjedimaster
>
Re: Support of Cordova 3.0.0
Posted by Raymond Camden <ra...@gmail.com>.
Err, right. In the past, Ripple handed them just fine. I could
$.get("http://someotherserver.com")
and even w/o CORS, it worked fine. That's one of the many reasons I liked
Ripple. ;)
Unless I'm misunderstanding you.
On Thu, Sep 19, 2013 at 10:04 PM, Gord Tanner <gt...@gmail.com> wrote:
> That is for XHR calls, not for resources.
>
>
> On Thu, Sep 19, 2013 at 10:41 PM, Raymond Camden <raymondcamden@gmail.com
> >wrote:
>
> > I thought it was the default to go through the Ripple proxy? From what I
> > remember, you had to tell it specifically when you didn't want to use it.
> >
> >
> > On Thu, Sep 19, 2013 at 9:29 PM, Gord Tanner <gt...@gmail.com> wrote:
> >
> > > So for InAppBrowser I am getting blocked by CORS and web security. I
> can
> > > emulate this with just a simple overlay that will invoke any callbacks
> > that
> > > are registered and show the developer the arguments that were used to
> > show
> > > it.
> > >
> > > It is kinda a cop out for now but will get us moving on quickly adding
> > > cordova 3.0 support.
> > >
> > > I am wondering if we could use the proxy code to add a route to the
> > ripple
> > > server for the InAppBrowser. I am not familiar with this code but it
> > seems
> > > doable, thoughts Brent?
> > >
> > > Would be cool to just set the iFrames URL to:
> > >
> > > http://localhost:4400/ripple/inappbrowser?url=<user_url_encoded_here>
> > >
> > > That would be epic.
> > >
> > >
> > > On Thu, Sep 19, 2013 at 8:40 PM, Gord Tanner <gt...@gmail.com>
> wrote:
> > >
> > > > So thought I would put a good list of the tasks that need to be done
> > for
> > > > cordova 3.0 support. Work is being done in the cordova-3.0 branch
> [1]
> > > >
> > > > Areas of work:
> > > >
> > > > - Double check existing API support (MobileSpec review)
> > > > - InAppBrowser support
> > > > - Calling 'ripple emulate' in a cordova folder should work (without
> > > > needing to navigate to the www folder.
> > > > - Using the correct platform javascript / resources based on the
> > selected
> > > > device (would be nice)
> > > > - Review cordova 3.0 config.xml parsing / validation.
> > > >
> > > > I am sure there is more but that will get us started.
> > > >
> > > > I am going to start on InAppBrowser support. I am going to try to
> > handle
> > > > this with overlays and an iframe. I have a good feeling I will be
> able
> > > to
> > > > get something cool emulated.
> > > >
> > > >
> > > > [1] - https://github.com/apache/incubator-ripple/tree/cordova-3.0
> > > >
> > > >
> > > > On Thu, Sep 19, 2013 at 5:39 PM, Hadrien TULIPE <
> > > > hadrientulipe+dev@gmail.com> wrote:
> > > >
> > > >> Hi there,
> > > >>
> > > >> I understood that help could be welcome for cordova 3 support.
> > > >> I'd like to know if there is anything I can do to help you with
> that I
> > > >> never worked on Chrome extensions but I'm quite used to
> > Javascript/HTML
> > > >> stuff.
> > > >>
> > > >> Let me know. For the record I'm at GMT+2
> > > >>
> > > >> Cheers
> > > >>
> > > >
> > > >
> > >
> >
> >
> >
> > --
> >
> ===========================================================================
> > Raymond Camden, Adobe Developer Evangelist
> >
> > Email : raymondcamden@gmail.com
> > Blog : www.raymondcamden.com
> > Twitter: cfjedimaster
> >
>
--
===========================================================================
Raymond Camden, Adobe Developer Evangelist
Email : raymondcamden@gmail.com
Blog : www.raymondcamden.com
Twitter: cfjedimaster
Re: Support of Cordova 3.0.0
Posted by Gord Tanner <gt...@gmail.com>.
That is for XHR calls, not for resources.
On Thu, Sep 19, 2013 at 10:41 PM, Raymond Camden <ra...@gmail.com>wrote:
> I thought it was the default to go through the Ripple proxy? From what I
> remember, you had to tell it specifically when you didn't want to use it.
>
>
> On Thu, Sep 19, 2013 at 9:29 PM, Gord Tanner <gt...@gmail.com> wrote:
>
> > So for InAppBrowser I am getting blocked by CORS and web security. I can
> > emulate this with just a simple overlay that will invoke any callbacks
> that
> > are registered and show the developer the arguments that were used to
> show
> > it.
> >
> > It is kinda a cop out for now but will get us moving on quickly adding
> > cordova 3.0 support.
> >
> > I am wondering if we could use the proxy code to add a route to the
> ripple
> > server for the InAppBrowser. I am not familiar with this code but it
> seems
> > doable, thoughts Brent?
> >
> > Would be cool to just set the iFrames URL to:
> >
> > http://localhost:4400/ripple/inappbrowser?url=<user_url_encoded_here>
> >
> > That would be epic.
> >
> >
> > On Thu, Sep 19, 2013 at 8:40 PM, Gord Tanner <gt...@gmail.com> wrote:
> >
> > > So thought I would put a good list of the tasks that need to be done
> for
> > > cordova 3.0 support. Work is being done in the cordova-3.0 branch [1]
> > >
> > > Areas of work:
> > >
> > > - Double check existing API support (MobileSpec review)
> > > - InAppBrowser support
> > > - Calling 'ripple emulate' in a cordova folder should work (without
> > > needing to navigate to the www folder.
> > > - Using the correct platform javascript / resources based on the
> selected
> > > device (would be nice)
> > > - Review cordova 3.0 config.xml parsing / validation.
> > >
> > > I am sure there is more but that will get us started.
> > >
> > > I am going to start on InAppBrowser support. I am going to try to
> handle
> > > this with overlays and an iframe. I have a good feeling I will be able
> > to
> > > get something cool emulated.
> > >
> > >
> > > [1] - https://github.com/apache/incubator-ripple/tree/cordova-3.0
> > >
> > >
> > > On Thu, Sep 19, 2013 at 5:39 PM, Hadrien TULIPE <
> > > hadrientulipe+dev@gmail.com> wrote:
> > >
> > >> Hi there,
> > >>
> > >> I understood that help could be welcome for cordova 3 support.
> > >> I'd like to know if there is anything I can do to help you with that I
> > >> never worked on Chrome extensions but I'm quite used to
> Javascript/HTML
> > >> stuff.
> > >>
> > >> Let me know. For the record I'm at GMT+2
> > >>
> > >> Cheers
> > >>
> > >
> > >
> >
>
>
>
> --
> ===========================================================================
> Raymond Camden, Adobe Developer Evangelist
>
> Email : raymondcamden@gmail.com
> Blog : www.raymondcamden.com
> Twitter: cfjedimaster
>
Re: Support of Cordova 3.0.0
Posted by Raymond Camden <ra...@gmail.com>.
I thought it was the default to go through the Ripple proxy? From what I
remember, you had to tell it specifically when you didn't want to use it.
On Thu, Sep 19, 2013 at 9:29 PM, Gord Tanner <gt...@gmail.com> wrote:
> So for InAppBrowser I am getting blocked by CORS and web security. I can
> emulate this with just a simple overlay that will invoke any callbacks that
> are registered and show the developer the arguments that were used to show
> it.
>
> It is kinda a cop out for now but will get us moving on quickly adding
> cordova 3.0 support.
>
> I am wondering if we could use the proxy code to add a route to the ripple
> server for the InAppBrowser. I am not familiar with this code but it seems
> doable, thoughts Brent?
>
> Would be cool to just set the iFrames URL to:
>
> http://localhost:4400/ripple/inappbrowser?url=<user_url_encoded_here>
>
> That would be epic.
>
>
> On Thu, Sep 19, 2013 at 8:40 PM, Gord Tanner <gt...@gmail.com> wrote:
>
> > So thought I would put a good list of the tasks that need to be done for
> > cordova 3.0 support. Work is being done in the cordova-3.0 branch [1]
> >
> > Areas of work:
> >
> > - Double check existing API support (MobileSpec review)
> > - InAppBrowser support
> > - Calling 'ripple emulate' in a cordova folder should work (without
> > needing to navigate to the www folder.
> > - Using the correct platform javascript / resources based on the selected
> > device (would be nice)
> > - Review cordova 3.0 config.xml parsing / validation.
> >
> > I am sure there is more but that will get us started.
> >
> > I am going to start on InAppBrowser support. I am going to try to handle
> > this with overlays and an iframe. I have a good feeling I will be able
> to
> > get something cool emulated.
> >
> >
> > [1] - https://github.com/apache/incubator-ripple/tree/cordova-3.0
> >
> >
> > On Thu, Sep 19, 2013 at 5:39 PM, Hadrien TULIPE <
> > hadrientulipe+dev@gmail.com> wrote:
> >
> >> Hi there,
> >>
> >> I understood that help could be welcome for cordova 3 support.
> >> I'd like to know if there is anything I can do to help you with that I
> >> never worked on Chrome extensions but I'm quite used to Javascript/HTML
> >> stuff.
> >>
> >> Let me know. For the record I'm at GMT+2
> >>
> >> Cheers
> >>
> >
> >
>
--
===========================================================================
Raymond Camden, Adobe Developer Evangelist
Email : raymondcamden@gmail.com
Blog : www.raymondcamden.com
Twitter: cfjedimaster
Re: Support of Cordova 3.0.0
Posted by Gord Tanner <gt...@gmail.com>.
So for InAppBrowser I am getting blocked by CORS and web security. I can
emulate this with just a simple overlay that will invoke any callbacks that
are registered and show the developer the arguments that were used to show
it.
It is kinda a cop out for now but will get us moving on quickly adding
cordova 3.0 support.
I am wondering if we could use the proxy code to add a route to the ripple
server for the InAppBrowser. I am not familiar with this code but it seems
doable, thoughts Brent?
Would be cool to just set the iFrames URL to:
http://localhost:4400/ripple/inappbrowser?url=<user_url_encoded_here>
That would be epic.
On Thu, Sep 19, 2013 at 8:40 PM, Gord Tanner <gt...@gmail.com> wrote:
> So thought I would put a good list of the tasks that need to be done for
> cordova 3.0 support. Work is being done in the cordova-3.0 branch [1]
>
> Areas of work:
>
> - Double check existing API support (MobileSpec review)
> - InAppBrowser support
> - Calling 'ripple emulate' in a cordova folder should work (without
> needing to navigate to the www folder.
> - Using the correct platform javascript / resources based on the selected
> device (would be nice)
> - Review cordova 3.0 config.xml parsing / validation.
>
> I am sure there is more but that will get us started.
>
> I am going to start on InAppBrowser support. I am going to try to handle
> this with overlays and an iframe. I have a good feeling I will be able to
> get something cool emulated.
>
>
> [1] - https://github.com/apache/incubator-ripple/tree/cordova-3.0
>
>
> On Thu, Sep 19, 2013 at 5:39 PM, Hadrien TULIPE <
> hadrientulipe+dev@gmail.com> wrote:
>
>> Hi there,
>>
>> I understood that help could be welcome for cordova 3 support.
>> I'd like to know if there is anything I can do to help you with that I
>> never worked on Chrome extensions but I'm quite used to Javascript/HTML
>> stuff.
>>
>> Let me know. For the record I'm at GMT+2
>>
>> Cheers
>>
>
>
Re: Support of Cordova 3.0.0
Posted by Gord Tanner <gt...@gmail.com>.
So thought I would put a good list of the tasks that need to be done for
cordova 3.0 support. Work is being done in the cordova-3.0 branch [1]
Areas of work:
- Double check existing API support (MobileSpec review)
- InAppBrowser support
- Calling 'ripple emulate' in a cordova folder should work (without needing
to navigate to the www folder.
- Using the correct platform javascript / resources based on the selected
device (would be nice)
- Review cordova 3.0 config.xml parsing / validation.
I am sure there is more but that will get us started.
I am going to start on InAppBrowser support. I am going to try to handle
this with overlays and an iframe. I have a good feeling I will be able to
get something cool emulated.
[1] - https://github.com/apache/incubator-ripple/tree/cordova-3.0
On Thu, Sep 19, 2013 at 5:39 PM, Hadrien TULIPE <hadrientulipe+dev@gmail.com
> wrote:
> Hi there,
>
> I understood that help could be welcome for cordova 3 support.
> I'd like to know if there is anything I can do to help you with that I
> never worked on Chrome extensions but I'm quite used to Javascript/HTML
> stuff.
>
> Let me know. For the record I'm at GMT+2
>
> Cheers
>