Ben Bucksch wrote on 30.11.2015 18:57:
Richard Newman wrote on 30.11.2015 18:40:
There isn't much documentation, and certainly no architecture docs.
And my apologies for that; it's been on my list for a little while
(and I might still get to it), but this quarter hasn't really gone as
planned.
Giri, if there's any subject, or any perspective, in particular that
you're looking to understand, it'll help target those docs when
they're written.
Generally, when I start to look at a project, the most important are
some architecture documents that describes the
1) overall execution flow
2) overall data flow (if not identical)
3) what each class is for, and how they interact.
4) any important overall design choices you've made (nothing arcane or
any details).
Usually, the question to answer is: I want to do ABC, so which code is
the right place? A document like this usually helps a great deal to
locate the right class and function.
Keep it high-level, though. The most interesting flows are:
* Startup, up to first page launch
* Page change/load
* Important (frequently used) callbacks from WebKit
_______________________________________________
mobile-firefox-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/mobile-firefox-dev
