The scripts + plugman workflow works fine. If it didn't, CLI wouldn't either :-}
I also agree that one workflow is better than two. It could be one workflow once we figure out a way to allow people to import their projects into their IDEs and/or work on a specific platform without worrying about their native/js code being destroyed at build time. On Tue, Jul 16, 2013 at 1:47 PM, Andrew Grieve <agri...@chromium.org> wrote: > Agree that the core + the plugins are as solid as ever, it's really just > the new workflow (CLI) that has rough edges. > Agree that a blog post should be the mechanism for delivering the message. > I haven't tried the create scripts + plugman workflow, but hopefully that > does work well. > > I am worried about us having two different documented workflows though (CLI > vs non-CLI). Seems like a lot of documentation to write and that it could > end up sounding confusing (when should one be used over the other, what are > the goods & bads of either). > > We do have our own blog now (yay). Any volunteers for drafting the release > announcement for it so that we have a bit of time to mull over the message > we're sending? For blog posts, I think a vote should be had before anything > goes live, maybe in the form of "Ship it" reviewboard reviews? > > > On Tue, Jul 16, 2013 at 4:36 PM, Anis KADRI <anis.ka...@gmail.com> wrote: > > > On Tue, Jul 16, 2013 at 10:38 AM, Andrew Grieve <agri...@chromium.org > > >wrote: > > > > > One prime example of something that I think people will get tripped up > by > > > is that when you use Xcode or Eclipse, your changes will be often blown > > > away by "cordova prepare". I think we should explore solutions to this > > > (e.g. in Xcode, have the project reference the root www/ and merges/ > > > instead of the derived one). Another thing we could do is rename www -> > > > derived_www/. > > > > > > > We've known this all along. That is precisely why I wanted the ability to > > manage projects and plugins outside of Cordova-CLI. That is also why > > plugman can also be used as a standalone tool. People are still able to > use > > the platform provided create/build/emulate scripts. If you don't use CLI, > > you're still able to load your project in XCode/Eclipse/Android Studio > > etc... > > > > I think both options should be offered for as long as possible. Some > people > > like the command-line some people don't. > > > > As far as beta vs final, I think that as long as we're comfortable with > our > > "exec" bridge and our plugin management it should be a final release. > Every > > other issue can be managed separately in the plugin land as Brian > > mentioned. This is a major architectural change and I don't expect most > > developers will upgrade right away unless they're early adopters. > Labeling > > it beta or final won't change that fact I think. > > > > The important thing is to document everything related to 3.0 as much as > > possible. > > >
