DevTools/RoadmapDec2011: Difference between revisions

← Older edit

DevTools/RoadmapDec2011 (view source)

Revision as of 23:02, 19 April 2018

1,184 bytes added , 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 7, 2011
+|updated=December 14, 2011
 |status=Draft
-|description=We want the web to be ''easier to develop for than proprietary platforms''. Mozilla can't do that alone, but we want to help developers as much as possible 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 7, 2012
+Kevin Dangoor [mailto:kdangoor@mozilla.com kdangoor@mozilla.com] December 14, 2011
+'''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)
-Mozilla can't do that alone, but we want to help developers as much as possible by making Firefox ''the best dynamic environment for building modern web applications''.
+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 25: / Line 40: @@
 The tools they have access to should support all of the common tasks well and provide places for add-ons to handle the less common tasks.
-What are the common tasks today?
+What are the common tasks today ([[#1|1]])?
-* Looking at how other sites implement their layouts in CSS
 * Manipulating CSS styles to get the desired look and often saving the end result to source files
 * Tweaking HTML in support of CSS work
 * Experimenting with JavaScript
+* Looking at how other sites implement their layouts in CSS
 * Making sure that their code will work across the browsers they need to support
 * Inspection of cookies, localStorage, app cache and other page resources
@@ Line 51: / Line 66: @@
 * things that they didn't realize they could do in the browser or that the browser could do for them
-We will assess these on a case-by-case basis and try to provide the features that will delight developers the most.
+We will assess these on a case-by-case basis and try to provide the features that will delight developers the most. The focus for 2012, however, is on shipping great tools for the common tasks.
-==Supporting Open Web Standards via Tools==
+==New and Evolving 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.
+Our biggest news in 2012 is going to be the addition of new tools for page styling, debugging and visualizing how web sites interact with the server. These tools join the Web Console and Scratchpad that were introduced in 2011. Together, these features touch on the most common needs of web developers.
-Among the many user interface challenges that we face, we want our tools to:
+As soon as a feature is "useful", we'll get it out to web developers. But, that's not the end of the story. The Mozilla community will continue to iterate on these tools with improvements at each release.
-# provide support for and encourage users to develop for the latest standards supported by modern browsers
+Examples of improvements that will show up over the course of the year:
-# 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.
+* Integrated user interface with a command line that provides quick access to features
+* HTML document manipulation
+* autocompletion of CSS properties and values
+* a web developer-oriented color picker
+* a 3D view of web page structure
+* features that help users spot errors in their code more quickly
+* Scratchpad improvements that make it quicker to navigate and run JavaScript
+* ability for the user to view the changes they made using the tools, to help them modify their source code
-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.
+Though we're introducing many new tools in 2012, by the end of 2012 most will have moved well beyond a "1.0" state.
 ==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.
@@ Line 118: / Line 139: @@
 * Tooling to assist with application performance issues
+<div id="1">This list of common tasks is extrapolated from user studies (7) and a survey we commissioned (600 web developers). If you think there are other common things that web developers do or want to do that are not covered by this collection of tasks, let me know!</div>
 [[Category:Roadmaps]]