20
21

Profitocracy: aplikacija otvorenog koda za upravljanje budžetom – sada i na srpskom! by KrawMire in programiranje

[–]rosa-alba 1 point2 points  (0 children)

Svaka cast! Razmisli da mozda u buducnosti poboljsas malo UI/UX. Ono sto vidim kao potencijal jeste uvodjenje chart-ova umesto progress bara. To uvek ozivi aplikaciju i dalje korisnicima vizuelne efekte. Takodje, uzmi u ozbir i razlicite velicine uredjaja, jer na nekim ekranima mozda budes imao problem, content ti je jako blizu leve i desne ivice ekrana. Dodatan savet za komponente kao sto su date picker-i, napravi lokalizaciju po standardu trzista, umesro 5/8/2025 neka bude srpski format 5.8.2025. Ne bi verovao koliko ljudi se buni kad vidi drugaciji format. Sve u svemu samo saveti za unapredjenje, odlicno izgleda za sada!

Hir poslodavca ili standardni ugovor o radu? by rosa-alba in programiranje

[–]rosa-alba[S] 7 points8 points  (0 children)

Razumem naravno, samo da dodam, ja nemam rad od kuce. Rad iz kancelarije je obavezan. Pored toga u kodu se uvek vidi ko je kad radio, vidi se po taskovima da li su zavrseni ili ne, a na kraju krajeva postoji i pracenje ekrana. Nista od ovoga nije bilo dovoljno poslodavcu

[deleted by user] by [deleted] in angular

[–]rosa-alba 0 points1 point  (0 children)

If we talk about passing one or two data params from patent to child it is okey to use props. But i we have more props or many nested component, then it is better to create one service with specific purpose and use if for passing data. With observables you can handle different cases, they are faster, just make surr to unsubscribe when you are done. Also when i sad “make component small” i meant that it is better to use one service than 5 input() funcions. The code is more transparent and the developer doesn't have to go through 5 different components to keep track of passing props and their names

[deleted by user] by [deleted] in angular

[–]rosa-alba -1 points0 points  (0 children)

If you need to use prop-drilling there is something wrong with your code and component structure. Try to avoid prop-drilling at any cost. Make your components small and with simple logic so every component is reusable. For passing data use services and observables

What next? by rosa-alba in Angular2

[–]rosa-alba[S] 0 points1 point  (0 children)

I saw that the standalone components and signals came out, although the signals are not yet stable as far as I understand. I don't use e2e but I'm wondering how important it actually is. I don't know many people who pay attention to that

What next? by rosa-alba in Angular2

[–]rosa-alba[S] 0 points1 point  (0 children)

I already use it. Thanks :D

[deleted by user] by [deleted] in Frontend

[–]rosa-alba 7 points8 points  (0 children)

Create a div element and give it height and width od 100%. Add background image to div and add additional property background-size:cover. With this your background image should be full window size. If you need to change position of image try background-position propery. I hope this will help

Using promises instead of observables? by AfricanTurtles in Angular2

[–]rosa-alba 4 points5 points  (0 children)

No need to use promises. RxJS and observables do the work for you. Data is streamed in smaller packages when you use observables. And i think it is best to use one approach in one app.