esposem / ualac Goto Github PK

Here we discuss about the design our app will have

Currently, about CMS template, me and @jfida are working on the creation of the dashboard by using the AtelierBeats from the assignment 7. However, including the components from the old template done with firebase to the AtelierBeats is quite hard and we are not able to show the components. The components are loaded and present in the Dom, but are not displayed, we don't know why. No error is displayed.
@gyammy is working on a polymer component that will allow the swap between the different views : simple, long one, and "pittogrammi".

I have taken contacts with the student from SUPSI and the bad news is that their work was more theoretical than practical and I still don't know if a concrete file exists, in any case I can manage to meet him to discuss their analysis together and produce a sort of document with the main point.

Here we discuss about polymer, any useful libraries and stuff related to it

After Milestone presentation 1 the feedbacks are:

• clarify requirements and see if the stakeholders are ok with them (see #4 Requirements)
• create a prototype of our idea
• create an architecture design (see #7 Architectural Design)
• be more clear in the presentation about user experience and Polymer functionalities
• start developing model for a single targeted kind of user (probably blind)
• decide which screen reader/other kind of application use (see #5 Testing Tools)

@esposem please update this issue.

We should prepare also the presentation for Milestone 3. Soon somebody will upload the main points to cover and a scratch

• Creation of various web components that are flexible, adaptable, scalable and ready to use;
• Creation of a Dashboard were we can show our work;
• We should take in account that we don't know where our web components will be used;

While waiting for feedback, what we need to do is :

• login
• image preview without uploading the image
• list image uploaded
• download the file to export
• decide what to do with the menu component button
• sleep (maybe)

As professor Pautasso also suggested, we need to install tools like a screen reader that a possible user will use.
I think a good one could be ChromeVox: https://chrome.google.com/webstore/detail/chromevox/kgejglhpjiefppelpmljglcjbhoiplfn?hl=en