balala wrote: ↑June 14th, 2020, 6:31 pm
include all resources into the @Resources folder
There wasn't a single doubt in my mind that a statement along the lines of this would appear. And while that may make sense to some, for me though (and maybe for others), it flies in the face of convention. @Resources makes sense for suite wide (reused) assets. Single use assets kept with the relevant section. Not unlike how we maintained websites back in the late 90's.
As for Layout, well, far be it for me to impose rules or suggestions about how to arrange meters. I just put in a suggestion, "Here's how I lay them out, and why". I also put them on the far top right edge of my screen. Does layout include screen co-ordinates? What if my positioning is off-screen for the next person.
balala wrote: ↑June 14th, 2020, 6:31 pm
For instance if the user would click Clock onto Intro, the appropriate skin (basix\RingClock\RingClock.ini) should be loaded / unloaded
Except under certain circumstances, I would have thought any Introductory screen would be single use, and that generally the skin manager would be used to fetch other skins from a specific suite. If, for instance, I had a suite of clocks, then I might switch to an Intro if it acted like a menu to select a different clock face.
jsmorley wrote: ↑June 14th, 2020, 6:45 pmQuitter...
I think he has a point.
However…
balala wrote: ↑June 14th, 2020, 6:31 pm
modification so now I have to rewrite my code again
That is an obvious problem. But I would have thought that XML/JSON data feeds would be more stable than using Regex to scrape a page. That would seem to be the best line of attack.
Of course, I could be wrong too… This is all new to me.