Comments (18)
@linusg There are some crazy approaches, like starting a dev server inside of electron. Just being explicit so we don't endup doing crazy things. That's why we should use PR's ;)
thanks for asking
from spotifube.
@sdhutchins I think I understand what you are saying. Sorry for the confusion. I prefer and it's recommended by react people to extract components into smaller components. Right now the initial screen is doing too much. One of the refactorings I will do this week is moving code into smaller components or moving "main" stuff to "main".
from spotifube.
@sdhutchins For example, this image:
1 - Input would be a separated component
2 - The button is another
3 - The message is another
4 - The "PageInput" for example, or "Main" would be a component using all 3 before.
from spotifube.
A note for communicating with the Electron and the front-end. We should always use ipcMain and ipcRender for communication between these to layers.
from spotifube.
We should always use ipcMain and ipcRender for communication between these to layers.
Just being into electron for some days, what would be the alternative? At least the docs explicitely state using these.
from spotifube.
Anyone except me still working on anything?
from spotifube.
@linusg Yeah, hopefully, I'll open a PR today or tomorrow.
from spotifube.
Is there a preference for placement of the "download playlist" code? Would it be better to place that with the playlist input code because so far I'm doing it that way? @linusg @djalmaaraujo
from spotifube.
@sdhutchins What do you mean? I would have a button, firing a ipcMain event to the MAIN of electron and handle the download there.
from spotifube.
@linusg @sdhutchins I will spend some time this week on this project. Expect some Pr's
from spotifube.
@linusg @djalmaaraujo right now the different components of the app are split in the renderer folder and I was trying to figure out if that was a desire or not? If not, I can go ahead and open another PR with those additions. I'm just curious if there are style related desires for what things look like for the app outside of having a main
and renderer
folder.
from spotifube.
@sdhutchins I am not sure if you understand the concept of the main / renderer.
main = imagine like backend, no UI
renderer = the front-end of the app, react, UI interactions, DOM, etc.
Components will always be inside the renderer.
from spotifube.
@sdhutchins I am not sure if you understand the concept of the main / renderer.
main = imagine like backend, no UI
renderer = the front-end of the app, react, UI interactions, DOM, etc.Components will always be inside the renderer.
I understand main vs renderer. Not what I'm asking.
Again,
right now the different components of the app are split in the renderer folder and I was trying to figure out if that was a desire or not? If not, I can go ahead and open another PR with those additions. I'm just curious if there are style related desires for what things look like for the app outside of having a main and renderer folder.
Meaning other than the required style design of having main and renderer...are their style desires for components being split or would it be ok to turn playlist-input into playlist-download with some edits to that component. It wouldn't be hard to add more to it to make that component take input as well as handle downloading.
from spotifube.
I already have that written, but I wasn't sure if @djalmaaraujo @linusg you two wanted the code to be simpler or not or had a preference on that either way.
from spotifube.
For example, here is our repo.
My question was just asking about what style @linusg was going for with components and how he'd feel about me turning playlist-input
into playlist-download
instead of creating a new folder and index.js for a download class or function.
from spotifube.
If I'm not being clear, I apologize. I understand the necessary structure of the app. I'm asking specifically about what's written for playlist-input
and if there was a vision for how that would transform or maybe not.
from spotifube.
@sdhutchins I think I understand what you are saying. Sorry for the confusion. I prefer and it's recommended by react people to extract components into smaller components. Right now the initial screen is doing too much. One of the refactorings I will do this week is moving code into smaller components or moving "main" stuff to "main".
Thanks for that. I just wanted to keep those kinds of things in mind as I haven't created an electron app before, and I know it's pretty crucial to try to adhere to common practices in other programming languages even if they aren't written.
from spotifube.
Thanks! @djalmaaraujo That's very helpful. I'll try to develop in that way.
from spotifube.
Related Issues (12)
- Create some Mockups HOT 35
- Pack for all platforms
- Implement initial UI HOT 44
- new maintainer HOT 9
- Create a bridge between the CLI and this project HOT 2
- Before starting: to be discussed, defining overall common plans HOT 10
- UI design discussion HOT 22
- Choosing a license HOT 2
- 1 - Choose a folder to save the files
- 2 - Download progress
- 3 - Download completed - success
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from spotifube.