Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of purplecabbage@gmail.com
 designates 209.85.128.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADVgkyOFwqSOscezT2N7X40P1CoQU6Mn33_Z1_68qq01xL7z5w@mail.gmail.com>
References: <20140217163404.6606994.39682.12147@blackberry.com>
	<CAKP6k2vGAz4cJEjKPb1-RZkZLubcPj_hguZDbvZjhuE3485z8Q@mail.gmail.com>
	<CADVgkyOFwqSOscezT2N7X40P1CoQU6Mn33_Z1_68qq01xL7z5w@mail.gmail.com>
Date: Mon, 17 Feb 2014 11:33:10 -0800
Message-ID: 
 <CAKP6k2usq99rKoeKKYruLkoyocmfP9PSMO9e0DAA0iVoTV_Vww@mail.gmail.com>
Subject: Re: XML Namespaces
From: Jesse <purplecabbage@gmail.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=20cf307f3bf0da3f7904f29f3953

--20cf307f3bf0da3f7904f29f3953
Content-Type: text/plain; charset=ISO-8859-1

The config.xml file is currently read at launch on all platforms to decide
what the start-page is, any preferences that exist, and what features are
allowed.
This has deeper implications than just cli projects.

@purplecabbage
risingj.com


On Mon, Feb 17, 2014 at 11:26 AM, Brian LeRoux <b@brian.io> wrote:

> this is at the project level (cli projects) not the platform level so I
> think we're ok
>
> that said, this whole discussion reeks of bikeshed
>
>
> On Mon, Feb 17, 2014 at 11:17 AM, Jesse <purplecabbage@gmail.com> wrote:
>
> > FYI. Windows Phone SDK and Windows 8 'native' .net SDKs do NOT provide a
> > library to parse generic json objects, while reading XML is trivial.
> > I could easily add the 6MB JSON.net [1] library to support this, but I
> have
> > avoided every dependency I could in getting to this point, so I would
> > rather not. I would likely have to write ~400 LOC to use the
> > DataContractJsonSerializer to parse the file, which isn't a huge deal,
> but
> > should be considered. I always strive to write as little code as
> possible.
> >
> > Please keep in mind the 'native' implications of making the move to .json
> > only, and not just the convenience of inspecting, authoring, and
> modifying
> > the config file.
> >
> >
> >
> > [1] http://james.newtonking.com/json
> > [2]
> >
> >
> http://msdn.microsoft.com/en-us/library/system.runtime.serialization.json.datacontractjsonserializer(v=vs.110).aspx
> >
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Mon, Feb 17, 2014 at 8:34 AM, Josh Soref <jsoref@blackberry.com>
> wrote:
> >
> > > Jonathan wrote:
> > > > It fits more naturally with some 'native' tools (e.g. android &
> windows
> > > 8).
> > > > IDE's have better support for it.
> > >
> > > This is changing
> > >
> >
> http://blogs.msdn.com/b/visualstudioalm/archive/2014/02/06/json-debugger-visualizer-in-visual-studio-2013.aspx
> > >
> > > > If you're developing only with css,js,html -> json makes more sense
> > >
> > > > If you're developing using native tools (plugman flow) -> xml makes
> > more
> > > sense
> > >
> > > Tools evolve. I don't see this as a particularly strong argument.
> >
>

--20cf307f3bf0da3f7904f29f3953--