phetsims / build-a-molecule Goto Github PK

Breaking apart H2O2 with a slice should never cause an O2 collection box to flash.

Those were really the only touch issues on my galaxy s3.

For Chinese / Korean / Japanese, this may be beneficial.

Should they just be larger to be easier to touch on smaller screens? Do we want something radically different like a '3D view' box where dragging in a molecule will show it in 3D?

Probably should leave a brief visual trail also?

Seems potentially linked to an order issue or possibly require.js. Seems to happen occasionally when opening a non-cached version.

Probably only in the third tab?

As seen on iPad.

Reproducible every time, especially when alt-tabbing in-out.

Win 7 64bit.
IE 10.0.9200.16721 update versions 10.0.10

Might be best to just do the background / shapes in Scenery.

Almost all of the WebGL code has already been made for the Molecule Shapes demo. Build from that for the start, but also keep three.js in mind.

Use Constants.has3d flag to determine whether to initialize.

We also need a good design for how this works (currently it shows one at a time, we'll want to decide how to close this to get back, what touch areas are used to rotate the molecule, and how the space-fill/ball-and-stick view switch should be displayed).

See CCl3, BF3, other examples. BF3 is where the hydrogen 'spheres' are entirely inside of the boron. CCl3 shows a more complicated intersection example.

Do we need differences for Van der Waals / covalent / ionic? Jmol may be handling these for us?

This breaks the scissors cursors on IE.

This causes the text to overshoot the button UI, and it looks ugly (gray is shaded over where the Text bounds thinks it exists):

Hit all the standard optimizations, none are done as of right now.

It's very slow, sometimes ~20 seconds on the iPad. This can consist of:

• Delay reading / computing all structures initially, just the ones needed for display.
• More compact way of storing molecule data, or pre-compress

Will cross-post to Joist. Here's the screenshot:

See screenshot.

See http://stackoverflow.com/questions/8720071/how-do-i-force-the-mouse-cursor-to-change-without-a-mouse-movement-in-javascript
which references https://code.google.com/p/chromium/issues/detail?id=26723 and https://code.google.com/p/chromium/issues/detail?id=20717

(before code review)

Model operations are slow when there are many atoms out, in addition to other operations.

Dragging atoms after slicing seems to be too slow.

After thinking about this, I believe it should match the 3D view's look precisely, but at the ideal orientation.

To test, pull out a bunch of molecules on the 3rd screen. Then drag around a molecule. It's fast when the bounding box of the molecules isn't changing, and slow when it is (even though we are using SVG).

Maybe a no-fill no-stroke rectangle can speed up performance in this case?

Decide between limiting the distance (and then cutting then), or potentially a fade effect (which might have lower performance).