He’s gonna live a long life. Until we know pi.
He’s gonna live a long life. Until we know pi.
I really like Calendar Versioning CalVer.
Gives so much more meaning to version numbers. Immediately obvious how old, and from when.
Nobody knows when Firefox 97 released. If it were 22.2
you’d know it’s from February 2022.
It doesn’t conflict with semver either. You can use y.M.<release>
. (I would prefer using yy.MM.
but leading 0 is not semver.)
In my Firefox I get a NS_BINDING_ABORTED
error on the Google Fonts font request.
And they didn’t specify a font fallback, only their external web font. It would have worked if they had added monospace
as a fallback.
Ignoring secondary email addresses, what was my primary [onlineaccount] E-Mail address has changed four times.
Nested CSS obscures complexity
An interesting point. Something I will take with me for observation and consideration.
Maybe sometimes it’s worth despite it and other times not.
extending the list
Seems like a valid formalization.
I think a or a few counter-examples would go a long way though.
The “rectangle” probably isn’t supposed to be this messy?
Are you saying “don’t use a synthetic key, you ain’t gonna need it”?
People regularly change email addresses. Listing that as an example is a particularly bad example in my opinion.
many2one: so in this relationship you will have more than one record in one table which matches to only one record in another table. something like A <-- B. where (<–) is foreign key relationship. so B will have a column which will be mapped to more than one record of A.
no, the other way around
When B has a foreign key to A, many B records may relate to one A record. That’s the many2one part.
The fact that different B records can point to different A records is irrelevant to that.
one2many: same as many2one but instead now the foreign key constrain will look something like A --> B.
It’s the same, mirrored. Or mirrored interpretation / representation to be more specific. (No logical change.)
If you had B --> A for many2one, then the foreign key relationship is still B --> A. But if you want to represent it from A perspective, you can say one2many - even though A does not hold the foreign keys.
In relational database schemata, using foreign keys on a column means the definition order is always one to one, and only through querying for the shared id will you identify the many.
many2many: this one is interesting because this relationship doesn’t make use of foreign key directly. to have this relationship between A and B you have to make a third database something like AB_rel. AB_rel will hold values of primary key of A and also primary key of B. so that way we can map those two using AB_rel table.
Notably, we still make use of foreign keys. But because one record does not necessarily have only one FK value we don’t store it in a column but have to save it in a separate table.
This association table AB_rel will then hold the foreign keys to both sides.
Ask your profs or other applicable personnel for offered final year projects, suggestions, and previous years projects. You can also check software dev companies which may offer such projects as job openings. That’ll give you more of an overview of current common projects, and some ideas of what you could do.
Did you stop programming altogether? /s
I think you can potentially get stuck with worse when you stop Java.
For a desktop app I would go with none of those.
If cross platform is the goal, the more important question, and independent of the programming language, is which GUI framework you will use.
Your best bet, at least if you are looking for a stable GUI framework, the best candidate may be C++ and Qt. But that’s a hassle in its own right - both C++ and Qt.
TypeScript will have some solutions for you, with web rendering as a desktop app. Golang will have Qt bindings or other more experimental/not thoroughly established+popular GUI frameworks.
My personal favorite ecosystem is .NET. It has an official cross-platform UI project MAUI, but without an official Linux target. Community extensions probably exist. Personally, I dislike the way the UI is declared and bound though (XAML).
My current interest, which I have not explored or validate yet, is using .NET but then host a web or Blazor app in it with Webview2. .NET supports cross-boundary programming, crossing web+managed/native development, and crossing web(HTML+JS)+managed.
Most of the time GUI and the framework technology is a hassle. Your question is too broad and unspecific, so there’s not a good answer.
If it’s not a “serious” project that you depend on [for your livelihood], pick and start with whatever [looks good or interesting] and go from there. If it is a “serious project” do a bit more GUI framework exploration and assessment, and pick and commit to something. If it’s a big commitment or risk, do prototyping with your candidates for verification and assessment - beyond the most simple examples, and for your specific usage.
deleted by creator
We’re so agile the sprint became a time-block framework rather than a lock-down of tickets that we certainly will finish. (In part because stuff comes up within sprint.)
In highlighting the need to understand the requirements before development begins, the research charts a path between Agile purists and Waterfall advocates. ®
Random trademark symbol. What’s the registered trademark here? The dot? “advocates”?
Sounds to me like the AI was programming using you instead of the other way around.
Did you copy and paste back and forth without learning or understanding anything? Or did you read and assess the results, and try to understand errors and issues?
no no no, this is the wrong way around
because sales and marketing sell it before it even exists
What conclusion did you come to?