DevTools/RoadmapDec2011: Difference between revisions

← Older edit

DevTools/RoadmapDec2011 (view source)

Revision as of 23:02, 19 April 2018

526 bytes removed , 19 April 2018

m

Mark as outdated

Asa

Confirmed users, Bureaucrats and Sysops emeriti

2,974

edits

@@ Line 1: / Line 1: @@
+{{outdated}}
 <section begin=summary />{{RoadmapSummary
 |icon=Devtoolsicon.png
@@ Line 4: / Line 6: @@
 |pagetitle=Developer Tools 2012 Roadmap
 |owner=Kevin Dangoor
-|updated=December 8, 2011
+|updated=December 14, 2011
 |status=Draft
-|description=We want the web to be ''easier to develop for than proprietary platforms''. One way in which Mozilla helps keep the web out in front is by making Firefox ''the best dynamic environment for building modern web applications''. In 2012, we'll build on the momentum started in 2011 to deliver a useful and easy-to-use suite of tools.
+|description=The web must be ''easier to develop for than proprietary platforms''. One way in which Mozilla helps keep the web out in front is by making Firefox ''the best dynamic environment for building modern web applications''. In 2012, we'll build on the momentum started in 2011 to deliver a useful and easy-to-use suite of tools.
 }}<section end=summary />
 =Developer Tools 2012=
-Kevin Dangoor [mailto:kdangoor@mozilla.com kdangoor@mozilla.com] December 13, 2012
+Kevin Dangoor [mailto:kdangoor@mozilla.com kdangoor@mozilla.com] December 14, 2011
-'''This is a draft. comments welcome! The best place for discussion is on [https://lists.mozilla.org/listinfo/dev-apps-firefox the dev-apps-firefox mailing list]'''
+'''comments welcome! The best place for discussion is on [https://lists.mozilla.org/listinfo/dev-apps-firefox the dev-apps-firefox mailing list]'''
 ==Vision==
-We want the web to be ''easier to develop for than proprietary platforms''.
+The web must be ''easier to develop for than proprietary platforms''.
 One way in which Mozilla helps keep the web out in front is by making Firefox ''the best dynamic environment for building modern web applications''.
+==Themes==
+The details are in the sections that follow this one but if you want just the high level view of 2012 for developer tools, this is it:
+# Bundled tools for the most common tasks (page styling, JavaScript debugging, viewing details of network requests and page resources)
+That is the most important thing we are doing, because everything else we want to build in 2012 and beyond relies on the basics being there and being solid. Beyond delivering on great new tools, we will also seek to:
+# Create a coherent tools plan for add-ons, apps, mobile (working with the other teams in those areas)
+# Continue to engage web developers in building the best tools for Firefox
 ==Bundled Tools for the Most Common Tasks==
@@ Line 73: / Line 86: @@
 Though we're introducing many new tools in 2012, by the end of 2012 most will have moved well beyond a "1.0" state.
-==Supporting Open Web Standards via Tools==
-Ideally, every person using web sites and applications is using a modern browser with support for the latest standards. Of course, even this ideal scenario falls short of the ideal: what are the “latest standards”? The “HTML5” standard is still evolving and there has been considerable churn in areas like Web Sockets and IndexedDB vs. Web SQL Database.
-Among the many user interface challenges that we face, we want our tools to:
-# provide support for and encourage users to develop for the latest standards supported by modern browsers
-# assist users in making good tradeoffs when they need to support older browsers
-Most web developers are given constraints concerning which browsers they must support, with some developers saddled with a requirement to support a decade-old browser. If we can help developers both provide support for the browsers they are required to support ''and'' take advantage of newer browser features, we will be making the web a better place.
-This won’t be easy, and I won’t even dive into specifics on how to do this here. I’m writing this as a guideline that we can apply and one more thing to think about as we design new tools.
 ==Apps and Add-ons==
-In 2012, Mozilla is making a big push into Apps. "Apps" are standard web technology, but with enough supporting technology to make them integrated better into the user's computing environments (desktops, smartphones and tablets).
+In 2012, Mozilla is making a big push into [https://apps.mozillalabs.com/ Apps]. "Apps" are standard web technology, but with enough supporting technology to make them integrated better into the user's computing environments (desktops, smartphones and tablets).
 The tools that we build for web developers should work easily for Apps, but opportunities may present themselves for helping Apps developers even more.