BenasP / AxmlApp

Test project for learning AXML
1 stars 0 forks source link

Server: remove unnecessary UI #9

Open BenasP opened 7 years ago

BenasP commented 7 years ago

Remove everything that is not necessary for controllers to work properly

SorrowMmussy commented 7 years ago

Bendri klausimai:

1.Ar tai per ka mes darome yra xamarin pagrindu? 2.Ar yra kazkokiu tutorialu kuriu pagalba butu galima mokintis/suzinoti ka kaip daro pati programa? 3.Kur pasiziureti, kokioje programoje koks kodas ir kaip naudojamas? 4.Kaip ismokti lengviausiai visus zingsniukus(step by step) programos naudojimosi instrukcijomis appso kurimui? 5.Nuo ko pradeti, gavus uzduoti? (pasalinti nereikalinga UI) 6.Kur rasti kokiose sekcijose programos UI yra talpinama? 7.Ar UI sekcijoje yra talpinama tik tai kas yra UI, ar kazkas daugiau, ir ar atskirti tai tik kodu?

Sunkioji klausimu dalis:

8.Programos dalyje Server.Tests mes testuojame savo parasyta programos koda, kaip pati testavima atlikti, ka kompiliuoti, kas turi buti rodoma? 9.Pacio testu rasymas, kaip testas turetu atrodyti? Kokia jo vizualizacija? 10.Pasirasius pati testa, naikinti palaipsniui UI, ar visa teksta su UI iskart? Kas buvo naudota sukurti appso sablona? Kur galima tokiu sablonu tutorialus atrasti? 11.Kaip efektyviausiai atlikti toki darba? Jei kodas vis dar atrodo ganetinai svetimai, kaip susikomentuoti jo nesuprantamas sekcijas, kur rasti tokia informacija (kokiu keyword ieskoti?) 12.Kaip reikia isnaudoti teksto koregavimo programas kaip Resharper ar CodeFactor savo naudai rasant appsu kurima?

BenasP commented 7 years ago

1) Server side - no, App project is basically yes. 2) There is a lot of tutorials, but this is a very wide variety of theory and maybe you have something specific? if no then I will find few tutorials for starters. 3) What do you mean by this? what code you want to view? 4) I say practice :D 5) Analysis and evaluate what is needed to do. When you have a good view where is everything then start removing. 6) Most of the times it has some keyword. This time everything is Views folders. But in some cases it could be extracted or duplicated to other places. So I think the best way is to check every file 7) UI you mean Views? If yes, then my answer it should contain only information/code related to UI, but no one forbids to add something not related to the UI, of course it will be violation of the program design patterns. 8) we will talk about this during the meeting 9) https://msdn.microsoft.com/en-us/library/hh694602.aspx 10) I never advice to apply big band principle. I advice to remove small parts related to the UI and the commit. 11) You can ask me for official keywords for some parts and then it will be easier for you to find information. 12) Resharper - https://www.jetbrains.com/resharper/features/ CF - view system for reported errors and try to fix them if possible

BenasP commented 7 years ago

Next time try to write your questions/answers in English for professional reasons

SorrowMmussy commented 7 years ago

In question nr. 3 , i was referring to basic app breakdown. For example we have folders - App/Server. Each folder consists of more folders inside of it - objects? How to know witch folder is responsible for what doing in the app itself? Really curious to learn what part of witch code is where. We covered most of it, in our previous session, interested to know, where could i find more info in depth of each object.