I discovered this:
http://developer.apple.com/iphone/library/qa/qa2010/qa1686.html
Since this was incredible useful for me and never found anywhere else, I wonder which other top secret informations are available in such "hidden" answer-documents?!
I wasn't able to find the root directory that lists all of them. Is there a way to browse all those frequently asked questions and answers, or is it a matter of great luck to stumble upon one of these?
Links to Technical Q&As and Technical Notes can be found on the left bar in the iOS Reference Library Page...
Related
I have not used either of them till yet. I looked at their websites and found their brief descriptions:
Github Gist:
Instantly share code, notes, and snippets.
Pastebin:
Pastebin is a website where you can store any text online for easy sharing. The website is mainly used by programmers to store pieces of sources code or configuration information, but anyone is more than welcome to paste any type of text. The idea behind the site is to make it more convenient for people to share large amounts of text online.
Apart from the explicit mentioning of "anyone is welcome to paste any type of text" in Pastebin's description, I see no difference in what they are used for.
I'd appreciate if someone could point me the differences between them.
Gists are way more 'advanced', since Pastebin is very simple and user-friendly.
At very least, gists are used to be shared mostly with coworkers, while pastebin is heavily being used for wide-usage or for private usage.
https://help.github.com/articles/forking-and-cloning-gists/
When using dashboard (https://melpa.org/#/dashboard) in emacs, how can I set it up so that it ignores directories or filenames matching a pattern like .gitignore ?
For example by default it shows ~/.emacs.d/elpa/*
The emacs community is friendly... but probably not as helpful as they could be. You could try filing a GitHub issue with the dashboard developer (here: https://github.com/rakanalh/emacs-dashboard/issues). If you ever did figure out a fix for your own issue, I bet the dashboard maintainer would be glad to hear about it.
Avoid plugins. Help on opensource plugins is minimal if you are not comfortable with developer jargon, politics and technical skills to understand the source code.
Just wait and see for yourselves - the emacs tag has 5.4K watchers, on average you get about <20 views per question, when do you think the question will be answered ?
Semantics aside, the suggestion is to just use the built in bookmarks feature.
https://www.gnu.org/software/emacs/manual/html_node/emacs/Bookmarks.html#Bookmarks
Is there any way to obtain, or has someone already obtained and compiled documentation from MS Technet Library for offline use?
I know of the Visual Studio Help Downloader at codeplex https://vshd.codeplex.com/ and I am looking for something similar for the Technet Library.
The Library itself has an option to select articles for export however, it is very limited in number of pages to add per click. This means you have to drill down on every subject and add it to your selection. Not very usable, besides the examples state you should be able to download as pdf or html, but I only get the html option, which is annoyingly impractical.
Ideally I would like to have the complete offline documentation for a single top-level subject (e.g. "Scripting with Windows PowerShell" at https://technet.microsoft.com/en-us/library/bb978526.aspx). If possible, including an index/TOC.
I know of the built-in Get-Help, the books available etc. but the Technet Library has more detailed information available which I'm after. Any known method of downloading this in bulk would be greatly appreciated.
All my google search results seem to either point to the built in export funcion, or people reminiscing about the old offline Technet subscription.
Ok, its not great. But its better than the above... I know this is old. But I was looking for this. This is the best I found. So Ill leave my breadcrumbs for the next fool to stumble down this road. If someone else finds better, hopefully theyll continue to pass it on.
On Github, you can download the entire Doc repo as a zip. Read it with microsoft code and a markdown extension.
Ideally, Id like to see this as a CHM (rather than a PDF).
https://github.com/PowerShell/PowerShell-Docs
I was surprised to find that this is well documented, and actually is a thing:
Taking TechNet Offline
When you start the process, it'll give you some instructions, and once you click "Start," you'll be shown the hierarchy of the entirety of that root page you linked on the left. Note the instructions in orange at the top.
I didn't go much further then this, but let us know if this worked in full, and as you expected it to. Nice feature there! I learned something myself today.
I have had mixed success with HTTrack You can give it a site a page and it will go through all links and resources recursively, saving them locally.
It requires some tuning and playing around with to get right, There might even be a newer better equivalent these days.
How exactly filling bugs for the iPhone SDK with Apple works?
I've always seen people mentioning we should fill bugs and duplicates is their way of measuring priority, but it's not clear to me:
How to actually fill the bug;
How to flag someone else's bug as a duplicate, and;
What do I need to tell people I've filled that bug and they should help me get it fixed by posting duplicates, if they're interested.
I couldn't find this process detailed anywhere - just snippets of information, so I figure you guys could help me (and all other developers fresh in Cocoa / Cocoa-touch development) by detailing it here.
Thanks!
File bugs at http://bugreport.apple.com/. After you have filed a bug at bugreporter, it helps to post it to http://openradar.me/ (not operated by Apple). It's also very useful to search against for duplicates to file against bugreporter. Not everyone uses openradar so it's not comprehensive.
The only thing in your control is actually #1, that is you can file bugs. You can do this through http://developer.apple.com/bugreporter/ for all of Apple's products including the SDK IIRC.
Your other two points are not so easy since you can only see your bugs. You will just have to trust that when Apple runs them through triage that thy properly flag duplicates. Some people do include the Radar url for their bug when positing n to the mailing lists and the like. That URL only works for Apple employees, but the hope is that if you make it easy to find your bug it might get fixed sooner.
What's the best way to get started using Popcap's "SexyApp Framework", and is it a good idea?
Wikipedia article
I'll take a (potential) Necromancer badge, even though you've (likely) already found your answer ... or went with SDL.
So, the developer.popcap.com is still active, although you won't find anything (like, say, docs) there.
Thankfully, you can still get it on popcapframework.sourceforge.net, which has all the installation guides, docs, etc.
It's been more than two years, but, hey, at least you got the answer. :)