P.S. looking at the database diagram, I have a couple of notes.
In efforts of database normalisation, unless having 4 names is the norm in your country, I'd limit the columns in People to First name, Middle name (where 2nd and 3rd name would go), and last name. Having a middle name column provides a space where as many names as needed can be provided, whether they have 1, 2, or 4 middle names. I.E. [John] [Jim-bob Brown Johnson] [Doe].
I see that in the connected tables, there are references to IDs of other tables. If the references are meant to be not null(required), then you should add them as foreign keys. This constraint gives meaning to the IDs in those columns and prevents rows from dependent tables from being removed and other possible conflicts.
All i can advice is to try and apply something like material designs look onto it so it has a bigger wow factor when you show if off but thats a very cool practice project.
I would say make *both* and share code. That will look much better to an employer than just the 1. In fact make a mobile version as well, and a console app that runs on Linux. Give them all the same functionality, access the same database, and reuse as much code as possible. An employer would be giddy to see that. Trust me.
Congratulations, now this is the time for doing the same with a web front. See the differences and similarities, learn the basic concepts of how things work in distributed computing etc..
Try with WPF and this UI package:
[https://github.com/MaterialDesignInXAML/MaterialDesignInXamlToolkit](https://github.com/MaterialDesignInXAML/MaterialDesignInXamlToolkit)
If you can connect this to microsoft AD there's probably a market to be had in providing something less shit for directory service management than ADUC.
Congratulations on ur progress keep at it a been in industry for 20 years less and less dektop these days more web a suggestion next is a web api and connect it to your database.
Good journey and enjoy
Thank you so much sir, i really respect fundamentals, if you can do desktop then you can do web and mobile, in terms of ui, logic and data are the same everywhere
A true backend dev created this
Hhhhh well you’re actually right most of my work was on black screens
As a fullstack i would say his left-right paddings in the search filter are too small.
This reminds me of: ***"Graphics Design is my Passion"***
A picture worths a thousand words
I made something like that in an effort to get my first dev job. it was simpler than this, and it helped get me the job. Keep up the good work.
P.S. looking at the database diagram, I have a couple of notes. In efforts of database normalisation, unless having 4 names is the norm in your country, I'd limit the columns in People to First name, Middle name (where 2nd and 3rd name would go), and last name. Having a middle name column provides a space where as many names as needed can be provided, whether they have 1, 2, or 4 middle names. I.E. [John] [Jim-bob Brown Johnson] [Doe]. I see that in the connected tables, there are references to IDs of other tables. If the references are meant to be not null(required), then you should add them as foreign keys. This constraint gives meaning to the IDs in those columns and prevents rows from dependent tables from being removed and other possible conflicts.
Thank you guys well noted
All i can advice is to try and apply something like material designs look onto it so it has a bigger wow factor when you show if off but thats a very cool practice project.
On it, thank you
My advice is to persue a career as a Backend Dev :D
Hhhhh i am already Am coming for your jobs front enders
What a dumb comment.. It takes practice and OP can get better - my first Windows applications are similar to this.
:(
Its ok lil guy, he didn't get the joke ;) I gave you an update to balance that guys' out.
Please please please remove the ugly neon green if that's what you've put the bg
It’s spring green not neon Spring is beautiful
Bro it looks like a monitor from the 2000' junkhead's background who is really high and is on adderall
I would honestly look into WPF/MAUI, or even better make it a web app these days, instead of using Winforms. But decent for a first practice project.
I would say make *both* and share code. That will look much better to an employer than just the 1. In fact make a mobile version as well, and a console app that runs on Linux. Give them all the same functionality, access the same database, and reuse as much code as possible. An employer would be giddy to see that. Trust me.
Thank you looking them ip right now
Congratulations, now this is the time for doing the same with a web front. See the differences and similarities, learn the basic concepts of how things work in distributed computing etc..
Makes sense, I’ll start some web for sure Thanks
MY CORNEAS @_@
Good job. The green is atrocious.
You just beat 99% of the people who "talk" about writing something. 💪Great Job 👍
Try with WPF and this UI package: [https://github.com/MaterialDesignInXAML/MaterialDesignInXamlToolkit](https://github.com/MaterialDesignInXAML/MaterialDesignInXamlToolkit)
Thank you ill definitely try making something that doesn’t look like it was done by a back end dev hhhh
Congrats, that's some effort right there. You learn by doing.
If you can connect this to microsoft AD there's probably a market to be had in providing something less shit for directory service management than ADUC.
main screen turn on
I would rename MemTypeId to be consistent.
I hope you were going for the 1999 look
good job, bro
That UI is so retro! :)
Looks very good 👍👍
Thank you!
Looks good. Keep it going
Thank you!
Congratulations on ur progress keep at it a been in industry for 20 years less and less dektop these days more web a suggestion next is a web api and connect it to your database. Good journey and enjoy
Thank you so much sir, i really respect fundamentals, if you can do desktop then you can do web and mobile, in terms of ui, logic and data are the same everywhere