Skip to content

DM-7406: Create Light curve skeleton app #157

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 30, 2016
Merged

DM-7406: Create Light curve skeleton app #157

merged 2 commits into from
Aug 30, 2016

Conversation

loitly
Copy link
Contributor

@loitly loitly commented Aug 27, 2016

  • introduce template into firefly entry point.
  • create light curve as a template.
  • create viewer, controller, and results component for light curve.
    • these components are place holders and are not fully implemented.
  • create upload form for use during development.

To view light curver viewer use lc.html: ie. http://localhost:8080/firefly/lc.html
Upload a table to see the results.

 - introduce template into firefly entry point.
 - create light curve as a template.
 - create viewer, controller, and results component for light curve.
   - these components are place holders and are not fully implemented.
 - create upload form for use during development.
@ejoliet
Copy link
Contributor

ejoliet commented Aug 27, 2016

Looks great!!! Nice starter page! I've uploaded a file and checked that everything was ok.
LC layout and skeleton is good. Review done.

<script>
window.firefly = {
app: {
template: 'LightCurveViewer',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The triview is the default template? I think we should probably specify it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, FireflyViewer is the default. It's documented via jsdoc in FFEntryPoint.app.

@robyww
Copy link
Contributor

robyww commented Aug 30, 2016

Is LayoutCntlr more general than just the tri-view? I know it is required for expanded but it is not clear if is for others. Maybe I don't understand it well enough. I am having trouble which what goes in LayoutCntlr.

Yes. LayoutCntlr contains the common layout states like, dropdown, expanded, standard. It may also carry additional states specific to the component, like images. This is how saga or action listener can dynamically change the layout.

@robyww
Copy link
Contributor

robyww commented Aug 30, 2016

should the triview stuff be moved to templates/tri-view?

Yes, I plan to move FireflyViewer and its related parts into templates as a separate refactoring task once templates is accepted.

@robyww
Copy link
Contributor

robyww commented Aug 30, 2016

Conclusions:

  • The structure looks good. It provides both flexibility and simplicity.
  • I think we might want to have everything about a templates together: constant and code. Maybe we import a template object that has the constant and the React Element?
  • I think I need to further separate the saga from the TriViewImageSection and rename it.
  • I need to understand LayoutCntrl better, I have used with out enough understanding.

I think the only thing you should change for this ticket is the template organization (tri-view in templates directory), other stuff we can iterate on).

This is really good path forward.
Review Complete.

 - move FireflyViewer related code into templates
 - create template mappings object in FFEntryPoint.js
@loitly loitly merged commit 4e08701 into dev Aug 30, 2016
@loitly loitly deleted the DM-7159_lc_frame branch August 30, 2016 23:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants