The Map

[Rob McBroom]

With renewed motivation, and nothing pretty to look at from a train’s
observation deck, here’s this evening’s work:

https://github.com/quicksilver/Quicksilver/blob/themap/The_Map.md

I plan to rebase and force-push that branch a few times before merging,
so don’t get attached, but I wanted to share a preview.

Let me know if you have any ideas for what should go in there.

--
Rob McBroom
http://www.skurfer.com/

[Patrick Robertson]

Looks good! I think it still needs to be more accessible to first time devs. I’m not really sure how this could be done, but maybe some kind of walkthrough of ‘how to find the code you are interested in’ kind of thing.
I remember when I first started developing I had to just use “Find” and look around for anything that might sound vaguely like what I’m trying to do, often with no success.

Perhaps if we’re going to add details about ‘important classes’ then we could also add it to the classes themselves using doxygen type strings, and get that pull request merged…? ;-)

For ‘the code for some action’. I remember neurolepsy at some point *did* make a program (written in lisp) that would match up identifiers with names. I can’t remember where it is but that might be a useful resource to keep in a repo.

Should this be a separate ‘development’ repo - that goes with the Plugin dev ref, perhaps an example plugin, and also some things to do with developing the main QS?

> --
> You received this message because you are subscribed to the Google Groups "Quicksilver - Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to quicksilver---deve...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Rob McBroom]

On 9 Aug 2015, at 13:48, Patrick Robertson wrote:

> I think it still needs to be more accessible to first time devs.

Me, too.

> I’m not really sure how this could be done,

Me either. :-)

> but maybe some kind of walkthrough of ‘how to find the code you are
> interested in’ kind of thing.

That’s what the “Where is…” section is meant to be. Maybe you
couldn’t tell it was a section, since it’s only has one thing in it
right now. Any ideas for other common things you’d look for? Just give
me a list and I’ll write up the details.

> Perhaps if we’re going to add details about ‘important classes’
> then we could also add it to the classes themselves using doxygen type
> strings, and get that pull request merged…? ;-)

Eventually.

> For ‘the code for some action’. I remember neurolepsy at some
> point *did* make a program (written in lisp) that would match up
> identifiers with names. I can’t remember where it is but that might
> be a useful resource to keep in a repo.

If we can find it. But it’s not that hard to do manually, especially
with nice instructions.

> Should this be a separate ‘development’ repo - that goes with the
> Plugin dev ref, perhaps an example plugin, and also some things to do
> with developing the main QS?

I don’t think so. I like having it close to the code itself. Maybe we
can revisit that if it grows.