Hey everyone. I’ve been lurking around here for a few weeks. I created a package, mark-ring (mostly by cannibalizing code from another package), and I’ve been messing around with the “hackable” features of Atom.
So far, I’m really impressed. I found it pretty easy to dive right in, but now I’m at a stopping point. I really want to start working on things people want, but I’m finding out that getting the information I’d like is a little overwhelming. The API documentation is okay for what’s there, but the undocumented features of even the little things are really making this much more difficult.
Here are a few examples:
apmfor instance. I tried publishing a new version of my package earlier, but I messed up the README after I’d moved to version 2.0.0. I had no idea how to add and publish the small change to stay at 2.0.0.
- What is
dev-mode? I’ve tried to figure it out. I spent about an hour yesterday trying to figure out what it was exactly, but I didn’t come up with a definitive answer. What does it change, other than loading packages in the developer folder? That wasn’t even documented.
- How does the View system work?
Pretty much every critique laid out in this thread is still valid. I know the API freeze is on, and that getting the documentation up to snuff is on the list now, but it’s been 7-ish months now. The biggest quote from that thread, to me, is:
I found the documentation to be enough to simply set up a package in the first place, but no help in building one. The API reference has good explanations for some classes, but not for others.
So my question to you is, do you have any simple ideas for things that I could use to get acquainted with the architecture more quickly (or in smaller chunks)?
I don’t come from a web-dev background either, so a little information about how much node.js, jQuery, etc. I’d need to know to be effective would be much appreciated as well.
If I came off as confrontational, please don’t take my comments the wrong way. I really do find hacking away to be very enjoyable, and I look forward to Atom’s future. Even with my limited knowledge, I’ve produced something which I never did with Vim or Emacs.