I am finally getting some time to work on the LCARS skin that I already promised a few times, a while ago.
it is coming along nicely but i need some info from those who are interested.
the LCARS skin needs a background. I did try to avoid that, but i couldnt.
and that makes it difficult to create it for several screensizes.
i will try to create as many as needed. if i start searching for screensizes i get crazy from the amount of sizes that there are.
So my question on you guys: What screensize would you need?
my tablet = 1024x600 so that one i got.
the picture on the top right is an image widget. so scalable and movable.
light with brightness and input_slider are also usable (will be shown in a short while. @aimc has promised to make this skin a included skin as soon as i am finished with it.
so please give me your input what would it a workable dashboard for YOU!
oke i hoped for some response, but i am sure not everyone is seeing it
i am going to call all people i think that might be interested.
but even if your not, please give me an idea of which screensize would be interesting for you so i can make it as general as possible, but still managable.
for your 1280x800 you can use the 1280x768
and i added the 2560x1600 to the list off resolution that i have calculated.
there is only 1 setting i cant test there but you can test that for me
i am uploading and creating the skin online at this moment and probably will need another hour or so to complete.
Very nice, would be nice if also the regular resolution of LCDs of 1920x1080 would also be supported. For multimonitor setups to have this kind of dashboard permanently set up on one monitor for example :).
For some reason my Nexus 7 2013 scales everything to 960x600, so I’d like that resolution. (or if someone can tell me how to get the nexus to display it’s native resolution (ie, 1920x1200) that would be great too )
how the skin is setup right now i can offer you the settings for a screenwidth from 960, but that would scale the screenheight to 560, so you would have a small bar beneath the skin.
you could set the resolution from the background to 960x600 to solve that but then you also need to put in an extra row and that might solve it.
could be that you also need to change fontsizes to get a decent result.
im not gonna put up those settings in the readme yet, but here are the settings you could try:
in variables.yaml set screenwidth: 1024 to 960
in dashboard.css change background-size: 1024px; to “960p 600px”
in the dashboard use the settings:
widget_dimensions: [112, 22]
widget_margins: [5, 2]
and you might need to change
stardate:
container_style: "top: 6px" #6px for 1024, 18px for 1280, 28px for 1600
to get the stardate at the right position after you have put in an extra line in the layout.
Might be being a bit particular here, but is the calculation for the Stardate correct? According to TrekGude.com, today’s Stardate is 71359.2, whereas the Stardate sensor in Home Assistant is showing that today’s Stardate is 11789.2. Not too sure how it’s being calculated, but on TrekGuide’s website, it has a calculator to help calculate Stardates. Here’s the source code for that particular calculator (it’s JavaScript):
i have been searching and searching when i started this.
all stardates that you can find out there are invented and not based on star trek directly.
i came accross a very good site that analysed the various used formulas and the actual dates in the series.
based on that information i also “invented” my own stardate.
with this formula i have tried to come as close to what the stardates in the series are.
according to what i have found this should be the first century.
thats why it starts with 1.
a stardate starting with a 7 would be way after any stardate that is used in all the series. and we are BEFORE the series.
it should be a like XXXXX.X so thats what they have in common.
i took the amount of days between 2000 and 2100 and recalculate them to get XXXX.X
that means that in a bit more then 83 years this stardate will go into its second century without a leap.
that makes that this dashboards stardate will continu to run for the next 1000 years.
so i guess i have to be there to correct the formula when the next millenium is there
i read the site you mentioned after i wrote my last reaction and this comes actually close to my approach.
Since the Stardate systems used in various Star Trek episodes are meant to measure time in the Twenty-third and Twenty-fourth Centuries, the same Stardate system cannot be used to express contemporary dates (i.e., in the Twentieth and Twenty-first Centuries).
However, for those who would like to create Stardates to represent contemporary dates, there are three methods that can be used:
Represent the current date in YYMM.DD format, where “YY” is the current year minus 1900, MM is the current month (01-12), and DD is the current day of the month (01-31).
For example, September 08, 1966, would be written as “Stardate 6609.08” in the YYMM.DD format. Another digit must be added for years after 1999, such that September 11, 2001, would be written as “Stardate 10109.11” in the YYMM.DD format. This system can be used to express any year after 1900 in Stardate format.
This system also roughly corresponds to the Stardates used in the first six Star Trek motion pictures, such that if a new movie were made today in The Original Series continuity, then its Stardate would be close to the YYMM.DD format.
like they say, there is no real stardate and in my opinion it makes no sense to use the other options they gave, because then we would be way ahead of the 2400 century.
but we could call this the prefederation stardate
on Tuesday, April 25, 2265, at 00:00 hours we could start using the new formula and call that first federation stardate and on on Friday, July 5, 2318, around noon we need another reset and formula change to second federation stardate.
I just installed home assistant and have a few automated tasks now for a couple of items. I’m really looking forward to installing LCARS on my main monitor which is a 24" Dell touch screen at 1080p.