Part Information/Selection Page

[mhayward12]

Implement a parts page that allows for users to filter parts through an advanced search bar. They will be able to filter by location, battery, voltage, and flags.

[shbenzer]

Should ideally contain:

• navigation bar (ability to add filters)
• list of all parts
• search function
• ability to select a part and view more information on it

[josemvidal]

For the PoC, only type of filter is needed.

[shbenzer]

due to almost every row in provided mock data being the same, filtering will likely be unavailable for POC and it is questionable if necessary for Beta

[shbenzer]

@josemvidal @ICanNomNoms Any chance you guys wanna take a look at my ListOfParts.vue file? I'll give you a starbucks giftcard if you can figure it out

[josemvidal]

Sorry, I have not used Vue.

[shbenzer]

eh, worth a shot. Know anybody that has? @josemvidal

[josemvidal]

Nope. A quick github search shows @SCCapstone/ezbag is the only group currently using vue this year (at least, from the commits history).

[shbenzer]

Am I allowed to contact 'Cognito Forms'? They are a company in the Vista that I know works with Vue @josemvidal

[josemvidal]

Yes, of course. You can also try online forums for vue. Most frameworks will have at least one online place where beginners can go to ask questions.

[shbenzer]

@josemvidal Cool! I've already tried StackOverflow and the Vue.js official forum... no luck

[shbenzer]

Update: trashed php method, found new one
Good news: Built a REST API that displays data from a sql table
Bad news: Integration into the web app has hit a snag, and I can't really figure out why

[shbenzer]

Idea: Skip integration and write script to just read the data from one of the pages the api spits out.
Pros: Possibly easier
Cons: eliminates ability to use crud functionality on mysql database from webapp, any changes would be both local and temporary.

Thoughts? @josemvidal

While I think it would be too limiting for the final release next semester, would it be good enough for poc?

[josemvidal]

The goal of the PoC (any proof of concept) is to prove to yourself that you can integrate all the libraries+APIs+whatevers that you plan to use into one deployable working app. That is, prove to yourself that it will work. There are no show-stopper issues that will prevent all further development ("we need library X to work, but it won't, we are dead").

If you drop a library, that goes against the idea of a proof of concept.

Have you tried just downloading and running an example that does what you want? This is lots of example code in github/etc. showing how to do X. You find one that does what you want, download and run it locally to convince yourself that it actually works, then you look at their code to see what it is they are doing differently from your code.

Examples like Vue.js + Node.js + Express + MySQL example: Build a full-stack CRUD Application - BezKoder

[shbenzer]

Yeah. that’s fair. I’ve actually adapted what I have now from that example