Skip to content
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

PLANNING ISSUE : Spectral Workbench Capture #92

Closed
5 tasks done
sidntrivedi012 opened this issue May 11, 2019 · 18 comments
Closed
5 tasks done

PLANNING ISSUE : Spectral Workbench Capture #92

sidntrivedi012 opened this issue May 11, 2019 · 18 comments
Assignees

Comments

@sidntrivedi012
Copy link
Member

sidntrivedi012 commented May 11, 2019

Planning issue for the roadmap to completing the Spectral Workbench Capture project.

The major tasks to be implemented are as follow:

  • Refactoring and Integration
  • Testing
  • Consolidation and Testing of API for search, matching, etc.
  • Making an npm module
  • Development of React app around basic ui modules .

However, I will also be dividing these major tasks into subtasks in order to make the tracking of progress easy.

@jywarren @harshithpabbati Please have a look at this and suggest as to what more should I add and how to start the work further. 🙂

@welcome
Copy link

welcome bot commented May 11, 2019

Thanks for opening your first issue here! Please follow the issue template to help us help you 👍🎉😄
If you have screenshots to share demonstrating the issue, that's really helpful! 📸 You can make a gif too!

@SidharthBansal
Copy link
Member

Thanks @sidntrivedi012 for opening up a planning issue. It will be great if you can break this issues so that we can introduce modularity and fix things in baby steps.

@SidharthBansal
Copy link
Member

Please add appropriate labels like gsoc etc.

@sidntrivedi012
Copy link
Member Author

@SidharthBansal I think I don't have the access to add labels. The option to add labels is not popping up.

@harshithpabbati
Copy link

Mmm wait let @jywarren add you to the collaborator. So that you will have access to add labels.

@sidntrivedi012
Copy link
Member Author

Sure. @harshithpabbati 👍

@Dhiraj240
Copy link
Member

@sidntrivedi012 Have you thought of sub-dividing the above tasks? The coding period is near and as per your proposal work on dividing "Refactoring and Integration" task, so that you can start efficiently.

@jywarren
Copy link
Member

I've added you all as collaborators! And, I hope this makes sense but I protected the main branch. Let's be sure to get reviews from me for at least the first few merges to main as we get used to the workflow. Sound good? Thanks all!

@jywarren
Copy link
Member

also noting publiclab/plots2#5794 as we get organized!

@starkblaze01
Copy link
Member

I've added you all as collaborators! And, I hope this makes sense but I protected the main branch. Let's be sure to get reviews from me for at least the first few merges to main as we get used to the workflow. Sound good? Thanks all!

Yeah sure @jywarren .
And, I guess Cross Domain Session in production is working fine with SWB PR being merged?

@jywarren
Copy link
Member

jywarren commented Jun 17, 2019

I wanted to note that we could do some more granular task listing here. Maybe:

  • resolving basic bugs with current local capture (starting with Error in capture demo #95)
  • publishing gh-pages demo of capture working!
  • starting a new branch where the /examples/capture/capture.js code is compiled in https://github.com/publiclab/spectral-workbench.js/tree/main/src, in a file called SpectralWorkbench.Capture.js, and saved to /dist/ alongside other compiled files
  • pointing the demo at the new /dist/ compiled code
  • ensuring it works in gh-pages
  • starting to chop up the code in SpectralWorkbench.Capture.js into sub-files, using the require() method (I recommend this post! https://ponyfoo.com/articles/modular-design-thinking) starting with just one sub-file and confirming that the demo works
  • repeating to logically break up the big file into smaller chunks, like has been done with existing code! Aim for <100 lines per file and "one purpose per file" roughly

This is a good bit! What do you think???

@sidntrivedi012
Copy link
Member Author

Sure @jywarren. This will be really helpful. Thanks a ton. 🎉

@starkblaze01
Copy link
Member

I wanted to note that we could do some more granular task listing here. Maybe:

  • resolving basic bugs with current local capture (starting with Error in capture demo #95)
  • publishing gh-pages demo of capture working!
  • starting a new branch where the /examples/capture/capture.js code is compiled in https://github.com/publiclab/spectral-workbench.js/tree/main/src, in a file called SpectralWorkbench.Capture.js, and saved to /dist/ alongside other compiled files
  • pointing the demo at the new /dist/ compiled code
  • ensuring it works in gh-pages
  • starting to chop up the code in SpectralWorkbench.Capture.js into sub-files, using the require() method (I recommend this post! https://ponyfoo.com/articles/modular-design-thinking) starting with just one sub-file and confirming that the demo works
  • repeating to logically break up the big file into smaller chunks, like has been done with existing code! Aim for <100 lines per file and "one purpose per file" roughly

This is a good bit! What do you think???

Sounds great @jywarren ,
Also, @sidntrivedi012 make sure to create small modules one by one according to functionality and replace it by exporting in the file, and after testing the module move on to next function to make it easy to trace back for any errors while implementing.

@sidntrivedi012
Copy link
Member Author

Ok @starkblaze01 . 👍

@jywarren
Copy link
Member

This is looking great in the gh-pages demo! https://publiclab.github.io/spectral-workbench.js/examples/capture/

image

Seems like the download button isn't working, however?

@sidntrivedi012
Copy link
Member Author

@jywarren Should I open an issue for it and try solving it?

@sidntrivedi012
Copy link
Member Author

sidntrivedi012 commented Jul 19, 2019

@jywarren Also, I need help for solving #75. I am facing an error when using the infragram code in capture's html file. I have mentioned the error here - #103 as well on the gitter channel. Please take a look. Thanks 🙂

@jywarren
Copy link
Member

jywarren commented Oct 5, 2021

Closing this one out! Thanks all!

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

No branches or pull requests

6 participants