Giter VIP home page Giter VIP logo

plate-map's People

Contributors

bhalbert avatar bwlang avatar dependabot[bot] avatar ekappotis avatar gorj-tessella avatar halb-tessella avatar jakemiller13 avatar jossiemathews avatar jperfetto avatar lev1ty avatar lubwen avatar shevtessella avatar zahen avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

plate-map's Issues

consider removing es6 code

it will need to be transpiled which complicates ebase's asset pipeline with a bunch of immature tools.

Required fields don't work well

warning about requiring 100% completion does not clear the save button - can't try again.
it's not clear which fields are required

image

Reconciling gem-plate-map and master.

The gem-plate-map branch is being actively developed, however all changes are applicable to master. The problem is that the two branches have different hierarchies.

We need to decide if both branches should be maintained, or only the gem version. Alternatively, we could have a separate project for the gem version, but then things will need to be updated twice.

Product/Lot picker

Allow user to select Product per well, then only display appropriate Lots

no longer available on npm?

When trying to install by running npm install plate-map --save with node version 12.18.3 and npm version 6.14.7, I get the following:

http fetch GET 200 https://registry.npmjs.org/plate-map 14ms (from cache)
silly fetchPackageMetaData error for plate-map@latest No valid versions available for plate-map

same after cleaning the cache:
http fetch GET 200 https://registry.npmjs.org/plate-map 170ms

prepend is adding HTML elements multiple times

Example:
bottom-table.js:25-27 :

let singleField = this._createElement("<th></th>")
  .text("Group");
row.prepend(singleField);

When multiple JavaScript files get loaded in (example: CoreSubmission is rendering other forms within itself), this line gets repeated and the field as prepended multiple times. Instead, we want to replace the field. Use html instead of prepend

Ref: https://stackoverflow.com/questions/26268382/rails-4-ajax-rendering-partial-multiple-times-on-same-page-each-time-submit-is-h

Any plan on releasing to npm ?

In the readme you mention this project

is designed to be easily utilized in the context of a larger scientific software application

Composing third-party code libraries in large (in fact, any) application usually comes with some sort of dependency (package) manager.

Any plans on releasing to npm maybe ?

Clean/responsive layout and css

The current implementation makes extensive use of elements with fixed heights and widths, float tags, and other css positioning behaviors that are not adequately responsive to the size of the user interface. This should be cleaned up.

In particular the following specific items must be addressed:

  • If more than 5 or 6 fields are on a tab, scroll bars are automatically triggered. The vertical scrollbar may be unavoidable, but the horizontal scrollbar is also triggered because there is insufficient space for vertical scrollbar when triggered. There are two possible solutions:
    • Make the field widths adapt to their container, and shrink when the scrollbar is triggered
    • Less preferentially, leave enough room for scrollbar to activate. The problem is scrollbar width varies.
  • Allow main interface to expand to fit page, mainly for benefit of bottom table?
  • Unit dropdown should be to right of input field, not on top of it.
  • Use table to align fields?

npm run start crashes on server.dev task due to gulpfile.js path bug

PATH.source does not define app, rather it defines css and js directly. npm ci; npm run start results in crash due to missing property app.

gulp.task('server.dev', async () => {
    browserSync.init({server: PATH.destination.dev.root});
    gulp.watch(PATH.source.app.css.concat(PATH.source.app.js), gulp.series('build.dev', browserSync.reload));
});
[23:02:35] TypeError: Cannot read property 'css' of undefined
    at /Users/lev1ty/Documents/031521/plate-map/gulpfile.js:167:32
    at taskWrapper (/Users/lev1ty/Documents/031521/plate-map/node_modules/undertaker/lib/set-task.js:13:15)
    at bound (domain.js:415:14)
    at runBound (domain.js:428:12)
    at asyncRunner (/Users/lev1ty/Documents/031521/plate-map/node_modules/async-done/index.js:55:18)
    at processTicksAndRejections (internal/process/task_queues.js:82:9)
[23:02:35] 'serve.dev' errored after 167 ms

Add warning for copying from multiple wells

When you select multiple wells with different conditions and copy/paste them, it either pastes the same conditions for every well, or leaves fields that vary blank (I've seen both behaviors).

I don't think a user would expect this, so unless this is changed, I think there should be a warning message when you try to do this saying something like "Warning: Attempting to copy multiple wells will only copy one set of conditions."

How hard would it be to make this work for 384-well plate maps?

I am wondering how hard it is to make this work for 384-well plate maps. I adopted the code for a 96-well plate maps project and it worked very well. We might need to work with 384-well plate maps in the future so I am wondering about this...

Thanks to everyone for this wonderful code repo!

Remove Select2v4.0.6rc1 dropdown workaround when possible

As of Select2 v4.0.6rc1 (and previous v4 versions) there is odd behavior around clicking the "unselect" x button. Instead of just removing the item in a multiselect, or clearing the selection of a select, it also opens the dropdown. This behavior was not present in 3.5.3, and has been documented since 2015 (select2/select2#3320). Despite being raised many times along with some pull requests, it has not been addressed and given the rate of work on select2 may not be for some time. While annoying, it is not a dealbreaker and hopefully will be addressed at some point. Currently the code has a workaround.

Use Select2 v4

Select2 v3.5 hasn't been updated in 4 years and does not support modern javascript usage via import.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.