Blogs, Screencasts, etc on Browser Developer Tools

[Claus Reinke]

Next to tool implementation and work coordination, tool
usage information and especially tool feature comparisons
make for useful information that should be of interest to
readers of this list. If you find such resources, and consider
them helpful, please share titles/links here.

Here is an example (which I had hoped the author would post
himself), a comparative overview of some browser developer
tools features (further installments planned):

25 Secrets of the Browser Developer Tools
http://www.andismith.com/blog/2011/11/25-dev-tool-secrets/

The author provides links to documentation for each tool,
and -in the comments- also recommends this

Beginner Guide to Page and Script Debugging with Chrome
http://www.codeproject.com/KB/trace/BeginChromeDebug.aspx

I would also encourage the teams working on browser developer
tools to mention their tool updates, new features and how-to-use
screencasts here.

And if you know a browser team who somehow has not heard
about our list yet, please let them know about this mailing list
as a way to reach not only their own current users but specifically
everyone interested in or working on JS tools!-) We want to make
this the central place for JS tool information.

Also, a question: I am tempted to try adding blogs, screencasts,
and talks about developer tools to our js-tools resources,

http://clausreinke.github.com/js-tools/resources.html

but a lot of this information is either short-lived (focusing on
currently new features, current issues) or is produced and
already collected by the tool developer teams. Would you like
to see such items included in our resource listing, or do these
things get out of date too quickly?

Claus
http://clausreinke.github.com/

[Paul Irish]

Also, a question: I am tempted to try adding blogs, screencasts,
and talks about developer tools to our js-tools resources,
http://clausreinke.github.com/js-tools/resources.html

but a lot of this information is either short-lived (focusing on currently new features, current issues) or is produced and already collected by the tool developer teams. Would you like to see such items included in our resource listing, or do these things get out of date too quickly?

Claus, I'd love to see this document track those things.. 

As I do things for Google Chrome's developer tools, I will try to keep the group updated when we publish new stuff out there. 

_

Paul Irish

Chrome Developer Advocate

[John Arthorne]

How about using a blog aggregator (planet) to pull together blogs related to JS tooling efforts? Personally I like subscribing to planets because I get all the updates in a single feed, and I find out about blogs I wouldn't otherwise stumble across. Static information pages are fine too, but they tend to get stale. Also as a consumer you aren't notified of changes, so people tend to visit the page once or twice and then forget about it.

John

[Axel Rauschmayer]

@John: Another possibility – a Twitter hashtag #jstools, then things
are decentralized.

[Steven Roussey]

There are some Firebug screencasts (http://getfirebug.com/screencasts), though it looks like we should add something new there. I have a screencast of Illuminations projecting design patterns from a JS framework into Firebug (http://www.illuminations-for-developers.com/about/), though it really needs some audio to explain what you are seeing for those that aren't used to component hierarchies or MVC.

Steven Roussey

[Jan 'Honza' Odvarko]

On Monday, November 28, 2011 9:19:23 PM UTC+1, Steven Roussey wrote:

There are some Firebug screencasts (http://getfirebug.com/screencasts), though it looks like we should add something new there.

Yes, please!

We have a bug report here:
http://code.google.com/p/fbug/issues/detail?id=4508

And we are looking for native English speaker who could do it. If it helps, I can provide list of things (screenplay) that could be in the screencast.

Honza
 

[Claus Reinke]

> How about using a blog aggregator (planet) to pull together blogs related
> to JS tooling efforts? Personally I like subscribing to planets because I
> get all the updates in a single feed, and I find out about blogs I
> wouldn't
> otherwise stumble across. Static information pages are fine too, but they
> tend to get stale. Also as a consumer you aren't notified of changes, so
> people tend to visit the page once or twice and then forget about it.

Hi John,

I don't have the resources for a planet/aggregator at the moment,
but perhaps you or someone else want to go for that?

Personally, I have found planets useful intermediate stages in the past,
but tend to need more control over my feed selection quickly (planets
are intentionally open to off-topic posts). I want to learn about new
blogs, but not subscribe automatically.

If people are willing to make their blogs filterable for posts relevant
to js-tools (a js-tools category/tag), or if the author guarantees that
the blog in question (or an existing tag for that blog) will be mostly
relevant to js-tools, I'll be happy to collect links to such blogs.

Otherwise, linking to relevant individual posts should do the trick,
shouldn't it? You can still decide to subscribe to the whole blog.

I should have made it more explicit that our resources page is far
from static!-) It is the first part of a github companion repo for this
list

http://clausreinke.github.com/js-tools/

which uses github pages to present web pages for the github repo,
so if you are on github, you can just watch the repo for updates

https://github.com/clausreinke/js-tools/tree/gh-pages

and if you are not on github, you can follow the commit feed
(just make sure you watch the gh-pages branch)

https://github.com/clausreinke/js-tools/commits/gh-pages.atom

or watch the commit history, with diffs

https://github.com/clausreinke/js-tools/commits/gh-pages

More interestingly, you can submit patches/pull-requests, and
if I should ever disappear, someone can fork and continue, so the
info we collect need not be lost or get stale!-)

Claus
http://clausreinke.github.com/

[Claus Reinke]

> @John: Another possibility � a Twitter hashtag #jstools, then things
> are decentralized.

Agreeing on a Twitter hashtag #jstools would be useful.

Just remember that tweets are not archived, and that this list
exists to have more in-depth discussions than the tweet format
allows. With an archive that can be searched later, so information
doesn't get lost.

Even if a discussion happens to take place entirely on Twitter,
but results in useful js-tools-related information, or if there are
links to share, it would be great if people could update this list
with a summary. And don't just post links, please, there is room
here to add a sentence on what the links are about!-)

We want to work towards a state in which this list is thought
of as the obvious place for js-tools-related information, in
terms of both publishing and looking for such info.

Claus
http://clausreinke.github.com/

[John J Barton]

On Wed, Nov 30, 2011 at 10:21 AM, Claus Reinke <claus....@talk21.com> wrote:
>> How about using a blog aggregator (planet) to pull together blogs related
>> to JS tooling efforts? Personally I like subscribing to planets because I
>> get all the updates in a single feed, and I find out about blogs I
>> wouldn't
>> otherwise stumble across. Static information pages are fine too, but they
>> tend to get stale. Also as a consumer you aren't notified of changes, so
>> people tend to visit the page once or twice and then forget about it.

> I should have made it more explicit that our resources page is far

> from static!-) It is the first part of a github companion repo for this
> list
>
>   http://clausreinke.github.com/js-tools/

I guess you meant to link the source:
https://github.com/clausreinke/js-tools

From the source you can get to the page above but not vice-versa.

BTW you can change the default branch on github using the "admin" button.

jjb

[Claus Reinke]

>> I should have made it more explicit that our resources page is far
>> from static!-) It is the first part of a github companion repo for this
>> list
>>
>> http://clausreinke.github.com/js-tools/
>
> I guess you meant to link the source:
> https://github.com/clausreinke/js-tools

nope:-) I'm trying to establish a single entry page for links
to this group, which is why that first link has a little intro
(useful when you can only post an url, as in a tweet) and
links to all other js-tools pages.

> From the source you can get to the page above but not vice-versa.

That entry page links to all of Google group, Github repo/branch,
and resource listing. All of those pages link back to the entry page
(actually, the resource listing doesn't, yet - todo) - they only have
(prominent) space for a single link each.

> BTW you can change the default branch on github using the "admin" button.

Thanks, didn't know that!

Claus
http://clausreinke.github.com

[John J Barton]

On Fri, Dec 2, 2011 at 4:47 PM, Claus Reinke <claus....@talk21.com> wrote:
>>> I should have made it more explicit that our resources page is far
>>> from static!-) It is the first part of a github companion repo for this
>>> list
>>>
>>>  http://clausreinke.github.com/js-tools/
>>
>>
>> I guess you meant to link the source:
>>  https://github.com/clausreinke/js-tools
>
>
> nope:-) I'm trying to establish a single entry page for links
> to this group, which is why that first link has a little intro
> (useful when you can only post an url, as in a tweet) and
> links to all other js-tools pages.
>>
>> From the source you can get to the page above but not vice-versa.
>
>
> That entry page links to all of Google group, Github repo/branch,
> and resource listing. All of those pages link back to the entry page
> (actually, the resource listing doesn't, yet - todo) - they only have
> (prominent) space for a single link each.

Well this part of the page is incorrect:
--------
There is a companion github repo for the group at

http://clausreinke.github.com/js-tools/

^^^^^^^^^^^^^^^^^ not a repo ^^^^^^^^^^^^

The repo has a longer description of why I think this group
is needed, and it holds a list of tool resources that we hope
to grow as Javascript tool developers start using js-tools
as a place to announce their tools.
----------

[John Arthorne]

On Wed, Nov 30, 2011 at 1:21 PM, Claus Reinke <claus....@talk21.com> wrote:

I don't have the resources for a planet/aggregator at the moment,
but perhaps you or someone else want to go for that?

I'll try out the idea of listening to your Git Hub feed for now and see how that goes. I guess an advantage of this approach is that it can be used for non-blog content, or for links to individual posts on a blog that is not otherwise specifically about JavaScript tools.
 

If people are willing to make their blogs filterable for posts relevant
to js-tools (a js-tools category/tag), or if the author guarantees that
the blog in question (or an existing tag for that blog) will be mostly
relevant to js-tools, I'll be happy to collect links to such blogs.

 

I maintain a blog related to the Orion browser-based tools project. I'll try to remember adding the js-tools tag for posts that talk about the JavaScript tooling for Orion in particular (or follow the whole blog to hear about other generic IDE features, HTML/CSS tooling, etc).

http://planetorion.org/news/tag/js-tools/

John

[Ariya Hidayat]

> If people are willing to make their blogs filterable for posts relevant
> to js-tools (a js-tools category/tag), or if the author guarantees that
> the blog in question (or an existing tag for that blog) will be mostly
> relevant to js-tools, I'll be happy to collect links to such blogs.

Here is mine (mostly related to PhantomJS, and in future also
Esprima), in case someone is interested in:

http://ariya.ofilabs.com/tag/jstools

Thank you!

Best regards,

--
Ariya Hidayat, http://ariya.ofilabs.com