hr0nix / blueskies Goto Github PK

What do you think? You just made a mistake and want to analyse. You pause. You then start the simulation in reverse to backtrack a bit?

Different options:

• Just run the system in negative time
• Remember the input history (a good idea anyway) and backtrack the actual user input.

Yes, here it is. We'll need second order ODE control system in order to solve this completely! And the convex hull. Was desirable anyway.

If you pause and turn while paused, the reach set will change! Think about it.
Get ready for some math :)

Should we disable that 3D zoomy thing?
Like statue of Liberty.

We need to prepare the UI for incorporation of newer features like #13 and #46 .
I propose this right panel accordion layout

• Interface and simulation settings
• wind conditions
• landing pattern settings.
  #40 completion is required to remove the legend which occupies too much space.

Or we can simply show it as a dialog on button press.

Currently it might be not so clear for not-into-optimal control people what this means.

• "Направление" -> "Направление ветра"
• Units haven't been translated
• Legend container should probably automatically grow for the russian text to fit.

Look at the margins used by other elements.

Right now, we show the reach set as a set that can be reached at 0 altitude. It can give a wrong impression that you can safely reach every point in this set, which is not true, because some of the points will require downwind landings/low turns.

Options:

1. Provide an interface control of reachset altitude (will distract the user probably)
2. Show reach set by 300m for alt > 400m and reach-by-0 for altitude < 400m.
3. Show reach-by-300m inside the reach-by-0 always. This will be slow, believe me :)

Here we have some information

https://developers.google.com/analytics/devguides/collection/analyticsjs/domains

Setting cookies on localhost

In some cases you might want to run analytics.js from a webserver running on localhost. To set analytics.js cookies, you need to disable the default cookie domain using:

ga('create', 'UA-XXXX-Y', {
'cookieDomain': 'none'
});

Or more simply:

ga('create', 'UA-XXXX-Y', 'none');

See screenshots

If the ga script is blocked by some client-side addons, some functionality breaks. For example, DZ switching.

Maybe it's possible to handle missing ga gracefully.

We should be able to create landing patterns for crosswind and (oh my god) downwind landings.

1. Is there a way to make "Got it" green and "Skip tutor" red? I think it's worth doing, currently it's reaally easy to accidentally click the wrong button.
2. Can we use the same width for the DZ selector and the DZ search (and, possibly the same font settings). It's sort of painful to look at them.
3. It's not always clear what controls is the tutorial referring to. For instance, when it's talking about the 3 buttons, its position is almost the same as when it was talking about wind settings. Some sort of arrow would certainly help, but I understand it's too much for this release, so you can ignore this.
4. "To read this tutor again, press "Restart tutor"." -> "To read this tutor again, click "restart the tutor"."
5. Can you use centered vertical alignment for github logo and "check out on github"?
6. I suggest an improvement for the text of the legend:

Right-click on any place on the map to start the simulation.

Use arrows to control the canopy: left and right to steer, up and down to use brakes.

Ugg, ugly, but still.

Something like an analog HUD-altimeter would be fantastic.

Should scroll just the column itself

The green marker is somehow located not exactly where the desired landing point is.

This a separate issue, so I broke the old one down into two.
So, how do we get winds forecasts?

Maybe even use some image.

https://developers.google.com/places/documentation/?csw=1#adding_a_place

We need to simulate the descent in real time, wrt to wall clock: in timer, calculate the time spent and move the canopy accordingly. Right now if there's increased load on the browser (i.e. controllability and reachability sets are shown), the descent is going slower.

Someone suggested https://github.com/janl/mustache.js on stackoverflow.

At the moment the tooltips and other attributes are especially annoying to localize: too much duplication.

Although enabled. Disabling and enabling helps.

Legend container should grow automatically to accomodate for text size.

At least &lat=...&lng=... should be easy to implement.

It was proposed by Dmitry Shevchenko to implement the holding area highlighting.
Might be useful for beginners.

Different winds for different altitudes.

We need to cleanup the design. Look at the right panel! Too many horizontal lines!

The landing pattern changes dramatically when the wind crosses the canopy full drive speed.

Let's consider using a smaller font and moving some elements (like language and metric/imperial selectors) to the same line.

At the moment it's not clear what's the current brake application is. I mean, all those numbers, 2.5 m/s 7 m/s. We need a good visualization.

We need to provide a convenient way to add a new DZs for the user. And by convenient I mean very convenient.

@fib0n proposed knockout
Also, http://todomvc.com/

I'm leaning towards that knockout thing, yes. Our logic is not that difficult, we just need to get rid of that update nightmare.

I doubt we'll use closurescript for this project (@fib0n strongly recommended this: http://swannodette.github.io/2013/12/17/the-future-of-javascript-mvcs/) :)

Probably after #58

It looks like there's too long of the crosswind leg for the strong wind pattern: it's difficult to get back to the wind line that way.

Your ideas on interesting places to land at.

Need to optimize that.

Language and pattern selectors are not reset upon page refresh, however the language and pattern themselves are reset (to English and Hide).

And make it easy in general to share a link to the current state of the page.

From the feedback:

Hi Boris
The wind direction is opposite to the normal terminology.
I put in a wind from 180 (south) and the simulator was acting like a 360 (north) wind.
By having the "blowing towards" direction instead of the "blowing from" direction is confusing and is not the way skydivers or pilots normally refer to wind.

From Wikipedia:
http://en.wikipedia.org/wiki/Wind_direction

Wind direction is reported by the direction from which it originates. For example, a northerly wind blows from the north to the south.[1] Wind direction is usually reported in cardinal directions or in azimuth degrees. For example, a wind coming from the south is given as 180 degrees; one from the east is 90 degrees.

Tutor code is ready, we need to create the tutor itself, i.e. the text.
Blocks #40

It's sometimes useful to go faster than real time.

Click "Show controllability set", rightclick on it (green area). Nothing happens. Simulation should start.

Should be beyond

Would be nice, wouldn't it?

We need a good introduction the first time the page is visited (and later on demand).