cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Higgins <br...@bryanhiggins.net>
Subject Re: cordova serve broken
Date Wed, 13 Nov 2013 16:59:47 GMT
To be fair to Josh, the semantic change was made long before he started
working on this project. He simply noticed serve was broken and sent a
patch to the list for review.


On Wed, Nov 13, 2013 at 11:19 AM, Brian LeRoux <b@brian.io> wrote:

> Thx Dick.
>
> So, Braden/Josh: did we discuss these semantics changes on list at all or
> was this just colloquially decided out off list and implemented? The latter
> is not cool. If I missed the former I apologize.
>
> I don't have a problem with this new feature per se but I don't think it
> has been thoroughly discussed (regardless), and obviously it has not been
> well tested (if at all).
>
> And I do have trouble with adding stuff to an already very large project.
> Do we need the new url scheme for app harness? If so, a landing page thing
> makes sense, I guess. Feels like we walking into territory that belongs to
> tooling like Grunt however. Could we have worked together to use the
> designer resources available from other committers to make it look better
> than an error state? Yes.
>
> Mild rant time.
>
> We have to use this list to keep everyone in the loop on the work being
> done. We can help each other create solid releases with beautiful
> experiences. Quietly introducing new semantics, untested, and a frankly
> terrible looking experience is a step backwards and worst of all it wasn't
> necessary. I am certain this was not deliberate or malicious but I do think
> it sucks.
>
> I am asking everyone here to think before you rock a large changeset, make
> smaller atomic changes that are thoroughly discussed, and give everyone
> here the opportunity to contribute to the effort. Each release should be an
> improvement on the last.
>
>
>
>
>
>
>
>
> On Wed, Nov 13, 2013 at 12:21 AM, Dick Van den Brink <
> d_vandenbrink@outlook.com> wrote:
>
> > Issue created: https://issues.apache.org/jira/browse/CB-5368
> > I tested on master and 3.2.0rc, not working in IE11, working in other
> > browsers.
> > Landing page is working in all browsers.
> >
> >
> > > From: jsoref@blackberry.com
> > > To: dev@cordova.apache.org; d_vandenbrink@outlook.com; b@brian.io;
> > timkim85@gmail.com
> > > CC: jgee@blackberry.com
> > > Subject: Re: cordova serve broken
> > > Date: Wed, 13 Nov 2013 05:39:42 +0000
> > >
> > > Andrew wrote:
> > >> Sounds issue-worthy.
> > >
> > >> I think Josh added some usage messages to serve
> > >
> > > Yes, I drove changes by our team here.
> > >
> > >> (and a landing page for /),
> > >
> > > Yep, especially this
> > >
> > >> so the next release will be more user-friendly.
> > >
> > > Speaking of which, there's a release candidate available now, please
> try
> > the following:
> > >
> > > npm install -g cordova@3.2.0-rc.1
> > >
> > >
> > > cordova create directory com.example.hello HelloWorld
> > > cd directory
> > > cordova platform add blackberry10
> > >
> > > cordova serve
> > >
> > > And then visit http://localhost:8000 in your browsers.
> > >
> > > We're doing testing of Cordova 3.2 RC this week and I'm happy to work
> on
> > things that are identified.
> > >
> > > I have OS X 10.9 and Windows 8 handy along with some VMs from
> modern.ie.
> > If there are browsers that should be tested, please let us know.
> > >
> > > The landing page isn't particularly shiny as I don't usually spend time
> > on CSS. Patches or suggestions are welcome.
> > > ---------------------------------------------------------------------
> > > This transmission (including any attachments) may contain confidential
> > information, privileged material (including material protected by the
> > solicitor-client or other applicable privileges), or constitute
> non-public
> > information. Any use of this information by anyone other than the
> intended
> > recipient is prohibited. If you have received this transmission in error,
> > please immediately reply to the sender and delete this information from
> > your system. Use, dissemination, distribution, or reproduction of this
> > transmission by unintended recipients is not authorized and may be
> > unlawful.
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message