What I like about Apple's Developer documentation over MSDN
-
I may be a little old fashioned, I prefer to print and read documentation. Not all the documents, for example I don't print reference documentation such as class references. But when it comes to overview of a technology, I find it really hard to read it on screen and that is where MSDN fails. It is very difficult to print documentation about a topic and all its sub topics. It can be done from the document explorer but it has many defects. For example, some sections don't appear as they are hidden in the original HTML. The nice thing about Apple's documentation is that they provide a pdf form for all their developer documents. I print out the overview docs. As a side, the quality of the docs is also good. It has less of marketing stuff and is almost always direct and to the point. Am I the only exception here? Does no one else likes to print the docs?
Proud to be a CPHog user
my favorite aspect of MSDN is the way google is the best method for searching it :)
Einstein argued that there must be simplified explanations of nature, because God is not capricious or arbitrary. No such faith comforts the software engineer. -Fred Brooks
-
I may be a little old fashioned, I prefer to print and read documentation. Not all the documents, for example I don't print reference documentation such as class references. But when it comes to overview of a technology, I find it really hard to read it on screen and that is where MSDN fails. It is very difficult to print documentation about a topic and all its sub topics. It can be done from the document explorer but it has many defects. For example, some sections don't appear as they are hidden in the original HTML. The nice thing about Apple's documentation is that they provide a pdf form for all their developer documents. I print out the overview docs. As a side, the quality of the docs is also good. It has less of marketing stuff and is almost always direct and to the point. Am I the only exception here? Does no one else likes to print the docs?
Proud to be a CPHog user
Agreed. Sometimes it is too difficult to switch between windows to read some esoteric knowledge then back again to apply etc. Having it in your hand allows for more contemplation as you attempt the new/difficult/impossible!
------------------------------------ We hang the petty thieves and appoint the great ones to public office. - Aesop
-
my favorite aspect of MSDN is the way google is the best method for searching it :)
Einstein argued that there must be simplified explanations of nature, because God is not capricious or arbitrary. No such faith comforts the software engineer. -Fred Brooks
Wikipedia also shares this feature.
-
I may be a little old fashioned, I prefer to print and read documentation. Not all the documents, for example I don't print reference documentation such as class references. But when it comes to overview of a technology, I find it really hard to read it on screen and that is where MSDN fails. It is very difficult to print documentation about a topic and all its sub topics. It can be done from the document explorer but it has many defects. For example, some sections don't appear as they are hidden in the original HTML. The nice thing about Apple's documentation is that they provide a pdf form for all their developer documents. I print out the overview docs. As a side, the quality of the docs is also good. It has less of marketing stuff and is almost always direct and to the point. Am I the only exception here? Does no one else likes to print the docs?
Proud to be a CPHog user
-
Agreed. Sometimes it is too difficult to switch between windows to read some esoteric knowledge then back again to apply etc. Having it in your hand allows for more contemplation as you attempt the new/difficult/impossible!
------------------------------------ We hang the petty thieves and appoint the great ones to public office. - Aesop
Dalek Dave wrote:
Sometimes it is too difficult to switch between windows to read some esoteric knowledge then back again to apply
That's beyond dispute, I think. But why don't you use an additional display? Regards Thomas
_Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Programmer - an organism that turns coffee into software._
-
Dalek Dave wrote:
Sometimes it is too difficult to switch between windows to read some esoteric knowledge then back again to apply
That's beyond dispute, I think. But why don't you use an additional display? Regards Thomas
_Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Programmer - an organism that turns coffee into software._
I hadn't thought of it, but now that I have, I don't think I would like to lose the room on my desk. Also, There is something comforting about a book or sheaf of papers that a screen lacks.
------------------------------------ We hang the petty thieves and appoint the great ones to public office. - Aesop
-
I hadn't thought of it, but now that I have, I don't think I would like to lose the room on my desk. Also, There is something comforting about a book or sheaf of papers that a screen lacks.
------------------------------------ We hang the petty thieves and appoint the great ones to public office. - Aesop
Dalek Dave wrote:
There is something comforting about a book or sheaf of papers that a screen lacks.
It surely is - until your desk spills over from things you usually read only once in your lifetime. :) Regards Thomas
_Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Programmer - an organism that turns coffee into software._
-
Dalek Dave wrote:
There is something comforting about a book or sheaf of papers that a screen lacks.
It surely is - until your desk spills over from things you usually read only once in your lifetime. :) Regards Thomas
_Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Programmer - an organism that turns coffee into software._
-
That just means you need a bigger desk.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
:laugh:
www.thomas-weller.de Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Programmer - an organism that turns coffee into software. -
:laugh:
www.thomas-weller.de Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Programmer - an organism that turns coffee into software.You only think I'm joking. My work desk consumes ~21' of linear wall space (includes two corners). It houses 2 computers and 3 monitors with loads of space. My homedesk is only 10' with one corner. With two monitors, one 15" laptop, one 10" laptop, and a printer I'm desperately in need of more space. The only thing holding me back is the cost. Plywood and sawhorses is too tacky for my taste and almost anything larger commercially available is office type furniture, the cheaper sorts are cubical gray, the more expensive ones management fake wood.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
-
I may be a little old fashioned, I prefer to print and read documentation. Not all the documents, for example I don't print reference documentation such as class references. But when it comes to overview of a technology, I find it really hard to read it on screen and that is where MSDN fails. It is very difficult to print documentation about a topic and all its sub topics. It can be done from the document explorer but it has many defects. For example, some sections don't appear as they are hidden in the original HTML. The nice thing about Apple's documentation is that they provide a pdf form for all their developer documents. I print out the overview docs. As a side, the quality of the docs is also good. It has less of marketing stuff and is almost always direct and to the point. Am I the only exception here? Does no one else likes to print the docs?
Proud to be a CPHog user
I used to like printing things back in the 20th century until I realized every cleanup of my office involved throwing out a huge pile of paper that I never actually read. No I far prefer online sources of information over printed or even books.
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
-
my favorite aspect of MSDN is the way google is the best method for searching it :)
Einstein argued that there must be simplified explanations of nature, because God is not capricious or arbitrary. No such faith comforts the software engineer. -Fred Brooks
Really... Google is great for searching MSDN
-
I used to like printing things back in the 20th century until I realized every cleanup of my office involved throwing out a huge pile of paper that I never actually read. No I far prefer online sources of information over printed or even books.
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
John C wrote:
involved throwing out a huge pile of paper that I never actually read
Have so been there and done that :)
Rocky <>< Recent Blog Post: Keep on your toes – Process Monitor V2.02 Thinking about Silverlight? www.SilverlightCity.com
-
I may be a little old fashioned, I prefer to print and read documentation. Not all the documents, for example I don't print reference documentation such as class references. But when it comes to overview of a technology, I find it really hard to read it on screen and that is where MSDN fails. It is very difficult to print documentation about a topic and all its sub topics. It can be done from the document explorer but it has many defects. For example, some sections don't appear as they are hidden in the original HTML. The nice thing about Apple's documentation is that they provide a pdf form for all their developer documents. I print out the overview docs. As a side, the quality of the docs is also good. It has less of marketing stuff and is almost always direct and to the point. Am I the only exception here? Does no one else likes to print the docs?
Proud to be a CPHog user
Curious though, if it is in PDFs does that mean you have no context sensitive search abilites when developing? About the only time I see MSDN documentation is when I hit F1 and then "Try" to find what I am looking for (was much better in the past getting where I needed to go). I seldom if ever just bring up MSDN documnetation to simply read through it. If I need that kind of an overview, I usually do a quick search for video screencast or tutorials on the topic. In today's world there is so much more information out there to be had with a few clicks. Of course, since the .Net Microsoft development world is so huge, there are problably more people pumping this out than with other platoforms. My eyes do too much reading already, a quick video sure makes life easy ;)
Rocky <>< Recent Blog Post: Keep on your toes – Process Monitor V2.02 Thinking about Silverlight? www.SilverlightCity.com
-
Curious though, if it is in PDFs does that mean you have no context sensitive search abilites when developing? About the only time I see MSDN documentation is when I hit F1 and then "Try" to find what I am looking for (was much better in the past getting where I needed to go). I seldom if ever just bring up MSDN documnetation to simply read through it. If I need that kind of an overview, I usually do a quick search for video screencast or tutorials on the topic. In today's world there is so much more information out there to be had with a few clicks. Of course, since the .Net Microsoft development world is so huge, there are problably more people pumping this out than with other platoforms. My eyes do too much reading already, a quick video sure makes life easy ;)
Rocky <>< Recent Blog Post: Keep on your toes – Process Monitor V2.02 Thinking about Silverlight? www.SilverlightCity.com
No, you do have context sensitive help, but it's not as nice as VS. In VS you can just highlight some code and hit F1, and get to the right Docs (or at least in VC6 that's how ti works, the new ones it seems like it's a crapshoot). Whereas in Xcode you have to either go the menu item (the keyboard shortcut doesn't always work) and pray. Sometimes you get to where you want, other times, not so much. This is, of course, a huge improvement over what used to exist, which is NO context sensitive help.
¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog
-
No, you do have context sensitive help, but it's not as nice as VS. In VS you can just highlight some code and hit F1, and get to the right Docs (or at least in VC6 that's how ti works, the new ones it seems like it's a crapshoot). Whereas in Xcode you have to either go the menu item (the keyboard shortcut doesn't always work) and pray. Sometimes you get to where you want, other times, not so much. This is, of course, a huge improvement over what used to exist, which is NO context sensitive help.
¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog
Well the Research assistant works great lot of times. I have never found any trouble finding anything in XCode help. I only recently started playing with it again after a gap of 3+ months.
Proud to be a CPHog user
-
Curious though, if it is in PDFs does that mean you have no context sensitive search abilites when developing? About the only time I see MSDN documentation is when I hit F1 and then "Try" to find what I am looking for (was much better in the past getting where I needed to go). I seldom if ever just bring up MSDN documnetation to simply read through it. If I need that kind of an overview, I usually do a quick search for video screencast or tutorials on the topic. In today's world there is so much more information out there to be had with a few clicks. Of course, since the .Net Microsoft development world is so huge, there are problably more people pumping this out than with other platoforms. My eyes do too much reading already, a quick video sure makes life easy ;)
Rocky <>< Recent Blog Post: Keep on your toes – Process Monitor V2.02 Thinking about Silverlight? www.SilverlightCity.com
Rocky Moore wrote:
Curious though, if it is in PDFs does that mean you have no context sensitive search abilites when developing?
No it is PDF as well as HTML.
Rocky Moore wrote:
I usually do a quick search for video screencast
Yes I don't have enough patience unfortunately to watch a video. One thing which I liked greatly was ASP.NET Quickstarts, that helped me a lot when .NET came out to quickly grasp ASP.NET. With printed docs the beauty is flexibility. You can read it anywhere. When you are waiting for food to come in a restaurant, when you take your daughter to swimming lessons, when you are flying on a plane or waiting at an airport and so on.
Proud to be a CPHog user
-
my favorite aspect of MSDN is the way google is the best method for searching it :)
Einstein argued that there must be simplified explanations of nature, because God is not capricious or arbitrary. No such faith comforts the software engineer. -Fred Brooks
:laugh: Yeah. I spent the weekend searching for relatively trivial help in C# using MSDN Search. I even used their filter and specifically selected C#, and removed all Office references in the search parameters. Every link returned was for Office, or FoxPro, and only a couple mentioned C# in any way. Google, on the other hand, always returned something relevant on the first page, and most often the third party references were far better than the hits returned from the MSDN content. Maybe Microsoft should outsource MSDN to Google. :-D
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
Agreed. Sometimes it is too difficult to switch between windows to read some esoteric knowledge then back again to apply etc. Having it in your hand allows for more contemplation as you attempt the new/difficult/impossible!
------------------------------------ We hang the petty thieves and appoint the great ones to public office. - Aesop