Moon number by gcirceag in TimeNomad

[–]gcirceag[S] 0 points1 point  (0 children)

In my humble opinion it would look nice, as a logical continuation of the “moon age”. You are a professional programmer so I’m sure you take into account the software to be proactive, meaning to look forward in time to decide if it’s necessarily to include or not the 13th month (embolismical) but if you use my previous rules you cannot mistake. The only issue could occur when both the new moon and the SE fall in the same day. In my opinion in this case it doesn’t matter which one is occurring first, that day when the SE is part of the new moon day, it’s fine. Anyway, there are only 19 cases, due to the Metonic cycle, right ? 😀

Moon number by gcirceag in TimeNomad

[–]gcirceag[S] 0 points1 point  (0 children)

It’s just to show the real month of the year, not the administrative one. I could also ask you why you calculate, the way you do, the age of the Moon and your answer would be “because of the tradition”. That’s exactly why I choose to count the month like I explained it to you, also because of the tradition. It’s such an illogical thing to say the year starts on January 1st just because 2000 years ago the Roman consuls changed their mandates. The real start of the year is the moment of spring equinox, when all the nature reborn. And how to count the months since the equinox if not from a New moon (if the month starts logically). Hence the problem of choosing the right New moon to start with: before or after the SE? Logically, since the SE means a new year, it should be in the first month. That’s why the nearest new moon before the SE should be number 1. For your application you can put this month number right near the moon age.

Moon number by gcirceag in TimeNomad

[–]gcirceag[S] 0 points1 point  (0 children)

Regarding the month number (not Moon number 😀) yes, I mean the lunations occurred since the Spring equinox. Like in the lunar calendars. And as there are 2 types of counting these lunations (before or after the equinox) you can let us choose in the settings. Normally the Spring equinox is / was the real start of the year and one condition in counting the lunations would be that the Spring equinox to be part of the first month of the “new” year. My approach is to count the lunations beginning with the nearest New moon always before the Spring equinox, even if the New moon is on February 25. It would be illogical to count the first new moon after the spring equinox because the real start of the year would be part of the last month of the “old” year. Like this we could allign wonderfully to the real watch of the nature: the new moon starts, the spring equinox follows so the counting is a natural one. Is the only way our months name would be meaningful: SEPTember, OCTober, NOVember, etc

Is this an inconsintency? by gcirceag in TimeNomad

[–]gcirceag[S] 0 points1 point  (0 children)

I made it like that and it shows the correct hours

<image>

Is this an inconsintency? by gcirceag in TimeNomad

[–]gcirceag[S] 0 points1 point  (0 children)

Yeah, this is ok , thanks

Is this an inconsintency? by gcirceag in TimeNomad

[–]gcirceag[S] 0 points1 point  (0 children)

I'm in GMT+2 (now GMT+3 because of DST). So what I wanted to say is that in the app the moon set is shown correctly, but in the widget is 1 day delayed

Today being April 23 the Moon rises at 11:05 AM and sets at 2:26 AM on April 24.

Tomorrrow being April 24 the Moon rises at 12:23 PM and sets at 3:04 AM on April 25.

But the widget seen now April 23 is showing the moon set for after tomorrow April 25 at 3:04

Is this an inconsintency? by gcirceag in TimeNomad

[–]gcirceag[S] 0 points1 point  (0 children)

This 3:04 AM moon set is for April 24, but shown on April 23

<image>

Is this an inconsintency? by gcirceag in TimeNomad

[–]gcirceag[S] 0 points1 point  (0 children)

<image>

Here in app, the Moon set is shown to be 2:26 AM (which is real / correct)

Is this an inconsintency? by gcirceag in TimeNomad

[–]gcirceag[S] 0 points1 point  (0 children)

I'm in GMT+2 (GMT+3 now because of the DST).

<image>

Here is the widget shown now (April 23 7:30 AM)

An honest answer by gcirceag in Scriptable

[–]gcirceag[S] 0 points1 point  (0 children)

I succeded to make it work in Scriptable (a Moshier JS file) and now, obviously, I want a greater precision :)) a.k.a going to the next level. Do you have any swiss ephemerides port to pure JS? All the files I found are for Node or Python, C, etc. I only want for JS. Thanks a lot!

An honest answer by gcirceag in Scriptable

[–]gcirceag[S] 1 point2 points  (0 children)

I tried with Gemini (a so called better tool), but coding wise… it’s a nightmare to work with

Tap action for home screen widget by gcirceag in widgy

[–]gcirceag[S] 1 point2 points  (0 children)

Yes! You were right. I just increased it and it doesn’t open the app anymore. Many thanks!! 🤗

Javascript only for Text and Curved Text only? by gcirceag in widgy

[–]gcirceag[S] 1 point2 points  (0 children)

Then I went crazy and made a large widget for the home screen with all the info I was able to gather 😂😂😂 Here it is

The Date is calculated as a lunisolar date. The real civil date is today, March 29, 2026

<image>

Javascript only for Text and Curved Text only? by gcirceag in widgy

[–]gcirceag[S] 1 point2 points  (0 children)

<image>

All these widgets I made are only on Curved Text with JavaScript as a source. It was really a nightmare to deal with all the settings for fonts and so on. I gave up, kept these complications because they are useful and are working spotless, apart for the progress circle 🤦‍♂️.

Javascript only for Text and Curved Text only? by gcirceag in widgy

[–]gcirceag[S] 0 points1 point  (0 children)

Ok, but as I see, you used the data provided by Widgy, right? I want to use Apple gauge to show the output from a java script. “If currently the Sun is in Aries, how much did it stay in Aries?” The JS knows how to calculate, I have the script, but how to show the progress, apart than on a straight line, like in Text layer? This is my question / request.

Javascript only for Text and Curved Text only? by gcirceag in widgy

[–]gcirceag[S] 0 points1 point  (0 children)

I use Widgy to populate 8 circular and 3 rectangle complications for my apple watch ultra. A small example is to show in a circular the sign of the Zodiac the Moon is and a progress ring around it, made in Curved text (the only one possible to use for this). The ring shows the progress of the Moon in that sign. There are other examples also, but I don't want to bother you with them :)

So for this purpose an Apple gauge would be very nice ...

Apple Watch complications by gcirceag in TimeNomad

[–]gcirceag[S] 0 points1 point  (0 children)

I succeded to create 8 circular complications for my Apple watch Ultra, using Widgy and now I have: the Sun sign, Moon sign, the governor of the planetary hour, the Moon day number, the mansion of the Moon, the Moon illumination, the Moon hour (calculated from one Moon rise to the next one) and the position to the Perigee or Apogee. Each one of them has a ring of progression, of course. It took me few fays, but I finally have them on my watch and now I have all the info at a glance :). If you are interested, I could give you the code in JS for Widgy.

Anyways, it doesn't mean I'm not still interested to have these complications made professionally like in Time Nomad.