StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14853444
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-13T12:19:58.820
FavoriteCount
0
LastActivityDate
2013-02-13T12:19:58.820
LastEditDate
LastEditorUserId
0
OwnerUserId
2068211
ParentId
13522246
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
I agree with the points other folks have said so far; its very easy to split things up into separate modules and have the modules depend on each other with regular AngularJS stuff. Then your JS code can be split into whatever files and directory trees you prefer. Just thought I'd mention what we're doing in the open source <a href="http://hawt.io/" rel="nofollow">hawtio</a> project which is based on AngularJS. We've taken modularity to a bit of an extreme :) hawtio uses <a href="http://hawt.io/developers/plugins.html" rel="nofollow">plugins</a> which can be discovered at runtime in the running server (e.g. deploy and undeploy UI functions at runtime). So based on some REST query or JMX detection we can dynamically and or remove plugins. e.g. here are all our <a href="https://github.com/hawtio/hawtio/tree/master/hawtio-web/src/main/webapp/app/" rel="nofollow">current default plugins</a> In terms of layout, each plugin has its own directories for code (js), html partials (html) and anything else (e.g. css / img directories) which makes it easy to keep things nice and modular. e.g. here's the <a href="https://github.com/hawtio/hawtio/tree/master/hawtio-web/src/main/webapp/app/camel" rel="nofollow">camel plugin</a> which has its own html, js and img folders. Then a specific plugin defines its own AngularJS module, directives, filters and which can then depend on other modules. We've not come up with terribly many helpful <a href="https://github.com/hawtio/hawtio/blob/master/doc/CodingConventions.md" rel="nofollow">naming conventions</a> for the source files so far though :). We find writing a file per controller seems simplest; but other than the fooPlugin.ts file and the helpers.ts file (for general module specific helper functions) we've not yet found any other meaningful naming conventions so far.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORecommended scalable AngularJS project structure?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJames Strachan
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.