Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BD79710CF7 for ; Tue, 30 Jul 2013 01:53:01 +0000 (UTC) Received: (qmail 73724 invoked by uid 500); 30 Jul 2013 01:53:01 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 73704 invoked by uid 500); 30 Jul 2013 01:53:01 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 73696 invoked by uid 99); 30 Jul 2013 01:53:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jul 2013 01:53:01 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FRT_ADOBE2,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of agrieve@google.com designates 209.85.160.44 as permitted sender) Received: from [209.85.160.44] (HELO mail-pb0-f44.google.com) (209.85.160.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jul 2013 01:52:55 +0000 Received: by mail-pb0-f44.google.com with SMTP id wy7so5342692pbc.31 for ; Mon, 29 Jul 2013 18:52:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=wrmatU7LPrLrlfmthcWlUsqcracy46XSl4cXJ+jrdh8=; b=dl6hgjrE2zVM3RilK/ClKXKz5LlfMfxNA7EtBcbZuFSYoTRD/KH9fzK+YHLaYFZCoC jyC8PSZmAPUBS/AsLLyx5SGU3IPmBY3U4kMnR9yi9rGRS15GYo4XUYaZPN0fTo0qWgED /PPzwsYLuesGtMx2oXgXAYIzZs8eyNkRDTL7B8fRIZH4F9IoeKZu2h6Kd3TY3610qaRK YrFPO7uphWpikyYQKx2hxdT5VX6BKpIo5QpSGqSM6b1Uz6LUtq9f58q2UKRUSjtHhDQ2 2xyTfRKgD7gUKPjXcUWfc+krISXVpFil+K6Nf8zAi2gtF71hgonCYZvL+XF69zarwHev 4bNA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=wrmatU7LPrLrlfmthcWlUsqcracy46XSl4cXJ+jrdh8=; b=X8h6bHAXkijYfrYuKQdXG5EadnyzgZenrhQGMjbd2PXbQOKGdm50YlIGTtmzvwvtTC v7tgARPXu71Hu7Jc/fVpEIAeOKdYkuzn2XJHRqHzitNNI4a/2zJqG+VbUzTbyz85DP66 AuwbfDXLs2RgXJDlusSllRYxb5nM4hv5F5pXQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :x-gm-message-state; bh=wrmatU7LPrLrlfmthcWlUsqcracy46XSl4cXJ+jrdh8=; b=Yr4SheSkclSve6ObmTP6UL5iMQzT5mF1KK0Z+6MKG7COUXLUcNy04UfTwsqHfx0bWD K1cN4c5C4zSlAIxUB96ImPaG7YJX3/zRt4jVFrKCCE1vr5QvGgq/d0lAS6f3wyerxT/H i+8YwE7JRovsejEFnUVfx7cv26PB5BIr8IEfROfwh5w4XTYLcG1OtcDqN8YAno1AJJ+2 gAOIjOl5I6YQymweAoeWi6NUCTJPbfzJ03beNVwjWn1LuIzbrfMNftdKdp40CjfoybQL OfcsYgir+//S45Oz2kTVKGQynCm8QTV0/ZDGn2d7/tU7fUB7v7R0VQLE2TA1Nqf7sPY1 h7vA== X-Received: by 10.66.234.71 with SMTP id uc7mr71243312pac.10.1375149153993; Mon, 29 Jul 2013 18:52:33 -0700 (PDT) MIME-Version: 1.0 Sender: agrieve@google.com Received: by 10.68.28.33 with HTTP; Mon, 29 Jul 2013 18:52:13 -0700 (PDT) In-Reply-To: References: From: Andrew Grieve Date: Mon, 29 Jul 2013 21:52:13 -0400 X-Google-Sender-Auth: cxfMZQV6rphQY68baFRZtGVMeZI Message-ID: Subject: Re: List of 'issues' I have seen with latest version To: dev Content-Type: multipart/alternative; boundary=e89a8f923e78d66f0b04e2b0dc7c X-Gm-Message-State: ALoCoQk0qaCh5nQpOo3MA5tnLXyknHify0rRBAQxTS8glTH2d59XR2hnVinEnktynL9rQ07V89OuAkBEcJyIdaolR7/S8x/cYtZ4Xdb1C98y2u+345j3wEQWAjGQreDL5p9cE0lmDSi/Ht45kW0CGl08SVsBugum4dFWGVDw88sdinYdPCrrLsNwNA8lUh2/Xb+c/bGsNVpH X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f923e78d66f0b04e2b0dc7c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable The main difference between plugman & cli is that CLI provides multi-platform support and plugman doesn't. I'm not suggesting we change CLI to have platform-specific logic (neither was Tyler). I *am* suggesting that we can make the platforms aware of when they exist within a CLI world. Cordova certainly breaks more between releases than the platform IDEs... Not sure what your point there is though. There are currently key things that apps need to do that CLI doesn't support. E.g. setting entitlements for push notifications, setting app icons / launch images, setting the size of the NSUrlCache, setting allowed device orientations for iPad vs iPod. IDEs also just give really nice integration with emulators / devices ("just push play" support). Maybe the abstraction won't be perfect, but we can certainly make it through some very small tweaks (by doing the things Tyler pointed out). On Mon, Jul 29, 2013 at 7:26 PM, Brian LeRoux wrote: > I'd rather we kept our native platform abstractions in the actual > native platform code. The CLI is ignorant to the implementation > details of the native platforms so that the abstractions stay with the > code they work against. If we've learned anything these past five > years its that Eclipse, Android Studio and Xcode **will** break > between releases. > > > On Mon, Jul 29, 2013 at 6:08 PM, Anis KADRI wrote: > > Yes that is the process for now. Hopefully we'll be able to support > > IDEs in CLI as well in the future. > > > > On Mon, Jul 29, 2013 at 2:58 PM, Filip Maj wrote: > >> +1, totally agree, this was the main use case for separating our plugm= an > >> vs cli tooling in the first place I thought.. > >> > >> On 7/29/13 12:05 PM, "Brian LeRoux" wrote: > >> > >>>Woah woah, not my perception at all. If you want to work in native pro= js > >>>then use plugman directly. CLI tools are designed to avoid IDE land an= d > >>>associated pain from cat/mouse release antics. Combined usage will be > too > >>>leaky an abstraction. > >>>On Jul 29, 2013 3:02 PM, "Andrew Grieve" wrote: > >>> > >>>> On Mon, Jul 29, 2013 at 1:30 PM, Tyler Wilson > >>>> >>>> >wrote: > >>>> > >>>> > See below. > >>>> > > >>>> > On Jul 29, 2013, at 12:56 PM, Brian LeRoux wrote: > >>>> > > >>>> > > Hey Tyler, thanks for capturing this. And yup filing relevant > issues > >>>> > > very welcome! I have some responses below inline: > >>>> > > > >>>> > > > >>>> > >> You would need to create a new project to get the updated > template > >>>> > files, correct? > >>>> > > > >>>> > > This is correct. I believe we have a backlog item for implementi= ng > >>>>an > >>>> > > `upgrade` command. > >>>> > > >>>> > Great > >>>> > > > >>>> > > > >>>> > > > >>>> > >> - When initially doing a 'cordova create' and the first 'cordov= a > >>>> > platform add', it downloads the latest template files, but does no= t > >>>> display > >>>> > any progress information. If on a slow connection, it can look lik= e > it > >>>> has > >>>> > hung, and the user might cancel the operation, leaving the system > in a > >>>> > broken state. > >>>> > > > >>>> > > Yes, this is a docs issue too. If you run the command with the -= d > >>>>flag > >>>> > > you'll see detailed output. > >>>> > > >>>> > Got that now. Still think it ought to say something if it is > >>>>performing a > >>>> > possible time-consuming operation. > >>>> > > >>>> > >>>> Agree. I'd like to see -d be the default. > >>>> > >>>> > >>>> > > > >>>> > > > >>>> > >> - When doing a platform add iOS, we end up with two 'www' > folders. > >>>>One > >>>> > at the root of the project, and one within the platform/ios folder= . > In > >>>> step > >>>> > 3 of the upgrading iOS page here > >>>> > > >>>> > >>>> > http://cordova.apache.org/docs/en/3.0.0/guide_platforms_ios_upgrading.md. > >>>>html#Upgrading%20iOSitsays to copy the contents of the www folder to > the > >>>>www folder at the > >>>> > root. But the Xcode project still refers to the www folder within > the > >>>>iOS > >>>> > folder, not the one at the project root. > >>>> > > > >>>> > > This is deliberate. We copy the root www into the platform folde= r. > >>>>Our > >>>> > > goal in 4.0 is to make ./platforms just build artifacts. > >>>> > > >>>> > Okay, this was not clear to me: I just did a test with 'cordova > build' > >>>> > which - as you say - did copy from the root www to the iOS platfor= m. > >>>>But > >>>> > what about the case where the user simply creates the project, add= s > >>>>the > >>>> iOS > >>>> > platform, and then uses Xcode? You cannot edit the www in the Xcod= e > >>>> project > >>>> > since it will be overwritten the next time they do a cordova build= . > I > >>>> think > >>>> > this would be a common use-case, and I do not see an levant soluti= on > >>>>to > >>>> it. > >>>> > My initial thought is that the Xcode project should point to the > root > >>>>www > >>>> > and there are custom build options to copy then build within Xcode= . > >>>>Same > >>>> > for Android if using Eclipse with an imported platform/android=C5= =A0 > >>>> > > >>>> > >>>> Agree here too. It's on the roadmap to do exactly as you said. > >>>> > >>>> > >>>> > > >>>> > > > >>>> > > > >>>> > > > >>>> > >> - Adding plugins: I know we only have to do do the plugin add > once > >>>>per > >>>> > project, but I think is tedious. > >>>> > > > >>>> > > Plugin discovery didn't land in time for 3.0 but its there now. > You > >>>> > > can just run `cordova plugin add geolocation` to get plugins fro= m > >>>>our > >>>> > > plugin repo that is based on npm. Documentation for this is > >>>> > > forthcoming too. > >>>> > > >>>> > Nice to know. Thanks! > >>>> > >> > --e89a8f923e78d66f0b04e2b0dc7c--