You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Shazron <sh...@gmail.com> on 2013/10/09 16:23:15 UTC
[iOS] Moving setting of UIWebView properties to its own plugin from
the core
See: https://issues.apache.org/jira/browse/CB-5026
Pros:
- if iOS >= 8 adds more properties, and people want to stick to Cordova 3.A
and we only support it in 3.B or 4.x, they only have to update a plugin and
not the whole core.
Cons:
- if they rely on these settings, they will lose them when they upgrade if
they don't install a plugin, this won't be any different when they moved
from 2.x to 3.x
- Yet Another Repo?
Re: [iOS] Moving setting of UIWebView properties to its own plugin from the core
Posted by James Jong <wj...@gmail.com>.
In favor of moving it to a plugin but keeping it in cordova-ios (same as CDVLocalStorage). We can always move it out later.
-James Jong
On Oct 9, 2013, at 12:55 PM, Shazron <sh...@gmail.com> wrote:
> If we do that, might as well pluginize (well its already a plugin) the
> CDVLocalStorage stuff as well into that process. But! The difference in the
> CDVLocalStorage plugin is, it has to be loaded/run before the UIWebView is
> created, so I don't think it would work (unless we have another feature
> param attribute, or something)
>
>
> On Wed, Oct 9, 2013 at 9:47 AM, Andrew Grieve <ag...@chromium.org> wrote:
>
>> I think pluginerizing the settings is a good idea. A nice-to-have here
>> would be to have the plugin installed by default for new projects. Maybe we
>> can ship a version of the plugin with platforms, and then allow it to be
>> upgraded via the registry?
>>
>>
>> On Wed, Oct 9, 2013 at 11:43 AM, Brian LeRoux <b...@brian.io> wrote:
>>
>>> I am all in favor of distilling platforms down to the very essence and
>>> 'plugin all the things'. Way easier for issue tracking, maintenance, and
>>> upgrading.
>>>
>>>
>>> On Wed, Oct 9, 2013 at 7:23 AM, Shazron <sh...@gmail.com> wrote:
>>>
>>>> See: https://issues.apache.org/jira/browse/CB-5026
>>>>
>>>>
>>>> Pros:
>>>> - if iOS >= 8 adds more properties, and people want to stick to Cordova
>>> 3.A
>>>> and we only support it in 3.B or 4.x, they only have to update a plugin
>>> and
>>>> not the whole core.
>>>>
>>>> Cons:
>>>> - if they rely on these settings, they will lose them when they upgrade
>>> if
>>>> they don't install a plugin, this won't be any different when they
>> moved
>>>> from 2.x to 3.x
>>>> - Yet Another Repo?
>>>>
>>>
>>
Re: [iOS] Moving setting of UIWebView properties to its own plugin
from the core
Posted by Shazron <sh...@gmail.com>.
If we do that, might as well pluginize (well its already a plugin) the
CDVLocalStorage stuff as well into that process. But! The difference in the
CDVLocalStorage plugin is, it has to be loaded/run before the UIWebView is
created, so I don't think it would work (unless we have another feature
param attribute, or something)
On Wed, Oct 9, 2013 at 9:47 AM, Andrew Grieve <ag...@chromium.org> wrote:
> I think pluginerizing the settings is a good idea. A nice-to-have here
> would be to have the plugin installed by default for new projects. Maybe we
> can ship a version of the plugin with platforms, and then allow it to be
> upgraded via the registry?
>
>
> On Wed, Oct 9, 2013 at 11:43 AM, Brian LeRoux <b...@brian.io> wrote:
>
> > I am all in favor of distilling platforms down to the very essence and
> > 'plugin all the things'. Way easier for issue tracking, maintenance, and
> > upgrading.
> >
> >
> > On Wed, Oct 9, 2013 at 7:23 AM, Shazron <sh...@gmail.com> wrote:
> >
> > > See: https://issues.apache.org/jira/browse/CB-5026
> > >
> > >
> > > Pros:
> > > - if iOS >= 8 adds more properties, and people want to stick to Cordova
> > 3.A
> > > and we only support it in 3.B or 4.x, they only have to update a plugin
> > and
> > > not the whole core.
> > >
> > > Cons:
> > > - if they rely on these settings, they will lose them when they upgrade
> > if
> > > they don't install a plugin, this won't be any different when they
> moved
> > > from 2.x to 3.x
> > > - Yet Another Repo?
> > >
> >
>
Re: [iOS] Moving setting of UIWebView properties to its own plugin
from the core
Posted by Michal Mocny <mm...@chromium.org>.
Or support optional-plugin-dependencies for platforms for 3.2? This has
come up before for the console plugin for ios..
On Wed, Oct 9, 2013 at 12:47 PM, Andrew Grieve <ag...@chromium.org> wrote:
> I think pluginerizing the settings is a good idea. A nice-to-have here
> would be to have the plugin installed by default for new projects. Maybe we
> can ship a version of the plugin with platforms, and then allow it to be
> upgraded via the registry?
>
>
> On Wed, Oct 9, 2013 at 11:43 AM, Brian LeRoux <b...@brian.io> wrote:
>
> > I am all in favor of distilling platforms down to the very essence and
> > 'plugin all the things'. Way easier for issue tracking, maintenance, and
> > upgrading.
> >
> >
> > On Wed, Oct 9, 2013 at 7:23 AM, Shazron <sh...@gmail.com> wrote:
> >
> > > See: https://issues.apache.org/jira/browse/CB-5026
> > >
> > >
> > > Pros:
> > > - if iOS >= 8 adds more properties, and people want to stick to Cordova
> > 3.A
> > > and we only support it in 3.B or 4.x, they only have to update a plugin
> > and
> > > not the whole core.
> > >
> > > Cons:
> > > - if they rely on these settings, they will lose them when they upgrade
> > if
> > > they don't install a plugin, this won't be any different when they
> moved
> > > from 2.x to 3.x
> > > - Yet Another Repo?
> > >
> >
>
Re: [iOS] Moving setting of UIWebView properties to its own plugin
from the core
Posted by Andrew Grieve <ag...@chromium.org>.
I think pluginerizing the settings is a good idea. A nice-to-have here
would be to have the plugin installed by default for new projects. Maybe we
can ship a version of the plugin with platforms, and then allow it to be
upgraded via the registry?
On Wed, Oct 9, 2013 at 11:43 AM, Brian LeRoux <b...@brian.io> wrote:
> I am all in favor of distilling platforms down to the very essence and
> 'plugin all the things'. Way easier for issue tracking, maintenance, and
> upgrading.
>
>
> On Wed, Oct 9, 2013 at 7:23 AM, Shazron <sh...@gmail.com> wrote:
>
> > See: https://issues.apache.org/jira/browse/CB-5026
> >
> >
> > Pros:
> > - if iOS >= 8 adds more properties, and people want to stick to Cordova
> 3.A
> > and we only support it in 3.B or 4.x, they only have to update a plugin
> and
> > not the whole core.
> >
> > Cons:
> > - if they rely on these settings, they will lose them when they upgrade
> if
> > they don't install a plugin, this won't be any different when they moved
> > from 2.x to 3.x
> > - Yet Another Repo?
> >
>
Re: [iOS] Moving setting of UIWebView properties to its own plugin
from the core
Posted by Brian LeRoux <b...@brian.io>.
I am all in favor of distilling platforms down to the very essence and
'plugin all the things'. Way easier for issue tracking, maintenance, and
upgrading.
On Wed, Oct 9, 2013 at 7:23 AM, Shazron <sh...@gmail.com> wrote:
> See: https://issues.apache.org/jira/browse/CB-5026
>
>
> Pros:
> - if iOS >= 8 adds more properties, and people want to stick to Cordova 3.A
> and we only support it in 3.B or 4.x, they only have to update a plugin and
> not the whole core.
>
> Cons:
> - if they rely on these settings, they will lose them when they upgrade if
> they don't install a plugin, this won't be any different when they moved
> from 2.x to 3.x
> - Yet Another Repo?
>