Looks awesome Ray, thanks a lot for taking this on! I really like the SAP architecture section, I think that is probably one of the biggest challenges new developers will face. I think we should include some links to more in-depth discussions about SAP though, so I will try to add some today. (I know that Carlos was working on http://spajs.io - it looks dead but for example the architecture page looks pretty good: http://spajs.io/pages/app-arch/index.html)
Should we add a section about version control? I see that question asked from time to time: "What should I be checking in?", this could also be expanded to tips for working on a team (what happens when one person uses OSX and the other Windows) - although that is a more advanced use case. Maybe we can change the "Handling Upgrades" section to "Handling Source Code and Cordova Upgrades." I added a note at the top that the document isn't prescriptive - echoing Michael Brooks' thoughts in the origional JIRA item (CB-677). I like it a lot so far, great job! On Wed, Apr 30, 2014 at 5:40 PM, Andrew Grieve <[email protected]> wrote: > On Wed, Apr 30, 2014 at 5:28 PM, Josh Soref <[email protected]> wrote: > > > Ray Camden wrote: > > > I had 3 hours here at the airport so I took at stab at writing content > > > for the Next Steps document. You can find (and edit) the document here: > > > > > > > > > https://docs.google.com/document/d/1uJ5qXqQxK2oh1eZPgMdYuhK2rQTB7QMHXUHbkc > > >omWgk/edit# > > > > Personally, I favor ether pads / pirate pads. > > > > > The main thing missing now (imo) is the Upgrade section. > > > I think with that added - this is in a good place (at least initially). > > > > > > Thoughts, opinions, etc? > > > > I like it. > > > > > Any volunteers ready to write out the upgrade section? > > > > I don't want to set up a Google account at work, but > > > FYI - you don't need an account to edit a doc that's made "editable via > those with the link" (as this one is). > > > 1. Please don't mention WebSQL. > > 2. The offline/online event is not a great indicator, it's a hint, but it > > can be misleading. People need to try a connection (XHR) to their > > destination, if it works, great, if it doesn't that's it. If I'm in a > > captive portal, or if I'm in an office, I can easily not have access to > > your backend, even though I do have some form of "network access". > > 3. For Debugging, on BlackBerry 10, you get web inspector out of the box. > > > https://developer.blackberry.com/html5/documentation/v2_0/enabling_web_insp > > ector.html > > > https://developer.blackberry.com/html5/documentation/v2_0/debugging_using_w > > eb_inspector.html > > > > 4. I think we decided to favor stack overflow over google groups > > 5. s/you simulator the accelerometer to test shake events/you simulate > the > > accelerometer to test shake events/ > > — this last one means you should introduce the document to WinWord and > ask > > it for an opinion :). > > > > >
