{"action":"closed","issue":{"url":"https://api.github.com/repos/fgx/fgx.github.io/issues/34","repository_url":"https://api.github.com/repos/fgx/fgx.github.io","labels_url":"https://api.github.com/repos/fgx/fgx.github.io/issues/34/labels{/name}","comments_url":"https://api.github.com/repos/fgx/fgx.github.io/issues/34/comments","events_url":"https://api.github.com/repos/fgx/fgx.github.io/issues/34/events","html_url":"https://github.com/fgx/fgx.github.io/issues/34","id":166950393,"number":34,"title":"Is FGx Moribund? If so, what to do?","user":{"login":"theo-armour","id":547626,"avatar_url":"https://avatars.githubusercontent.com/u/547626?v=3","gravatar_id":"","url":"https://api.github.com/users/theo-armour","html_url":"https://github.com/theo-armour","followers_url":"https://api.github.com/users/theo-armour/followers","following_url":"https://api.github.com/users/theo-armour/following{/other_user}","gists_url":"https://api.github.com/users/theo-armour/gists{/gist_id}","starred_url":"https://api.github.com/users/theo-armour/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/theo-armour/subscriptions","organizations_url":"https://api.github.com/users/theo-armour/orgs","repos_url":"https://api.github.com/users/theo-armour/repos","events_url":"https://api.github.com/users/theo-armour/events{/privacy}","received_events_url":"https://api.github.com/users/theo-armour/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/fgx/fgx.github.io/labels/Discussion","name":"Discussion","color":"0e8a16"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-22T01:06:33Z","updated_at":"2016-08-07T08:25:10Z","closed_at":"2016-08-07T08:25:10Z","body":"Part 1 of a response to  #32 \r\n\r\n> > ..., FGx is nearly dead:\r\n\r\n> And until, as discussed in The Future - Dream, to me there is nothing really to promote with this yet... it > is still a WIP... we need to offer a 3D flight playback service, or something... \r\n\r\nIt seems to me that FGx currently offers actually quite a bit:\r\n\r\nhttp://fgx.github.io/fgx-aircraft-overview/r10/aircraft-overview.html\r\n\r\nhttp://fgx.github.io/fgx-globe/fgx-globe-r7/fgx-globe-r7.html\r\n* And its predecessors including http://fgx.github.io/fgx-globe/fgx-globe-r5/\r\n\r\nhttp://jaanga.github.io/fgx-plane-spotter/r4/fgx-plane-spotter-r4.html\r\n\r\nhttp://fgx.github.io/fgx-plane-spotter/r1/index.html\r\n* Click on 'First Person Controller' to fly the aircraft\r\n\r\nAnd now we have all the bits in\r\n\r\n[FGx/sandbox]( http://fgx.github.io/sandbox/index.html )\r\n\r\nWhat we don't have are any strategies for collaboration and promotion. We've never figured out ways to build upon each others skills and knowledge.\r\n\r\nEither we should consider turning off the lights at FGx or we have to start building up some discussion and strategies for making FGx useful.\r\n\r\n\r\n<hr>\r\n\r\n> This is absolutely perfect for the first time user - a quick overview, 1-by-1, just by scrolling - certainly beats the menu approach\r\n> But par contra is absolutely bad for the repeat user, who I am sure would like the simpler verbal only menu approach, that loads instantly, simply as a quick link to some sub-project you are following...\r\n\r\nYou did not look very closely at:\r\n\r\nhttps://ladybug-analysis-tools.github.io/ladybug-web/\r\n\r\nI would embed an image but I said I wouldn't. ;-)\r\n\r\nIn the top right hand corner there is a text menu under the heading of 'Contents' that enable you to jump directly to any and all of the scripts. This menu was expressly designed to give the repeat user quick access.\r\n\r\nThe interesting question here though is why would there be any repeat users? Once you've seen all the scripts, why do you need to return? How can you tell if there is anything new or of any interest?\r\n\r\nThe other dilemma is that pages like these take a long time to build.\r\n\r\nI think if we are to attract visitors we need a home page that has \r\n\r\n* 3D graphics you can interact with\r\n* Quick access to the latest happenings\r\n* And a menu system that brings the good stuff to you\r\n\r\nSo I think using the GitHub API to grab data on users and orgs at run time is an interesting route to follow as in this WIP:\r\n\r\nhttps://theo-armour.github.io/ \r\n\r\n* with mode code here: https://github.com/jaanga/jaanga.github.io/tree/master/cookbook-html/examples/github-api-rss\r\n\r\nI am still thinking about how to embed iframes with 3D as part of this.\r\n\r\nBut the main thing is finding ways informing visitors about WIP without users actually having to do anything.\r\n\r\nSo part of the answer to the first part of this message is:\r\n\r\nThe code you are having fun writing should auto-magically do the marketing and promoting for you.\r\n\r\nAm I being understandable here?\r\n\r\n ;-)\r\n\r\n\r\n\r\n"}}
{"actor":{"display_login":"theo-armour"}}