Lmst

Domotizo Ventilador con esp8266

Resultado del proyecto dónde domotizo un ventilador viejo usando un esp8266 con home assistant y una sencilla interfaz en ionic (app android e ios)

#esp8266 #ionic #homeassistant #domotica #iot #maker #proyecto #project

I feel bad for the teams behind things like #Ionic and #Flutter who try to recreate the iOS style in cross-platform frameworks. I don't think the effects can be done at all via HTML/CSS and I'm sure whatever Flutter does will be nothing but jank.

Which of course means I might have to finally buckle down and learn Swift/SwiftUI...

#zincbenefits #digestivehealth #intestinalhealth #absorption #angstromminerals #liquidminerals #ionic #supplements #funfacts

More app development #ionic

I'm making an app #ionic

Game changer in my #mobile #coding was, when i figured out that i don't need #androidstudio to compile and sign #apk !
Just plain java development kit, android sdk and platform tools, #gradle and #apksigner

Btw, i use #ionic with #vue to make mobile apps.

Well, I'm the lucky winner of this fancy arcade cabinet. No excuses for my terrible gaming skills now. Thanks so much to #Ionic for hosting this giveaway on discord! 🥰 I'll be sure to put it to good use.

If you aren't aware, Ionic's Capacitor and Ionic Framework (https://ionic.io) powers @voyagerapp! Some seriously awesome and underrated tech. If you have any questions about #ionic or #capacitor... AMA!

An Ionic Branded Mortal Kombat 30TH Anniversary Legacy Edition Arcade from Arcade1Up

Presenting at Motto Berlin in 2023, (before the boycott), on my book Ricochet - Cultural Epigenetics and the Philosophy of Change, Ljä Forlag (2021). I also presented on #UFO aka #UAPs the #goldstandard #cryptofascism and #libertarianism
The week prior to the talk I found a plaster model of an #ionic column that was a great prop for talking about #spirals and #interdimensional #travel

Does anyone own an Ionic 5?
I'd be interested to hear your experience of owning it.

#car #ev #ionic #hyundai

#Arch with #Ionic #Entablature and #Keystone Detail

The #dentils arrangement we saw in https://pixelfed.social/p/Splines/791013152244518907 goes well with the classic entablature #profile we saw in https://pixelfed.social/p/Splines/790888454384861893, and they both go well with #simpleIntercolumniation, also known as #architravato.

However, with arches, the entablature profile has to be adjusted a bit so that the dentils arrangement is as shown here. The shape, size, and gap between individual dentils remains the same, but a crucial difference is that the dentils at the #outer corners touch each other.

As I mentioned in https://pixelfed.social/p/Splines/803615973439041638, in #arcadeIntercolumniation, the entablature is repeated on the wall behind the half-column. It doesn't end at the columns and has two "outside" corners and one "inside" corner. While the dentils at the outer corners touch each other, there is a single dentil in the inside corner that is shared by both walls.

A bedrock principle of dentils (like that with #flutes and with eggs in the #EggsAndDarts motif) is that when viewed directly from the front or the sides, a dentil must be centered on the column axis. It is this principle that forces us to adjust the profile of the entablature in arcade intercolumniation giving us the arrangement shown here.

The image also shows the detail of the decoration in front of the #keystone. The most easily recognizable component of that is the large #volute, which is the exact same size as the ones on the #capital. The smaller volute is exactly half the size of the larger one. It is mirrored, rotated and put within a bounding rectangle whose height is exactly 2µ (288 units). The channels of both volutes are bridged with #sinusoids derived from half turn of #helix curves that have been flattened.

This motif in the keystone, where volutes of different sizes are combined with sinusoids is very common. It will be seen in the #modillions of the #modernEntablature.

#IonicColumn #Flutes

This diagram shows the 2D geometry of an #Ionic #flute. The larger blue circle shows the flute outline near the #base of the #column. The smaller blue circle shows the flute outline near the #neck of the #shaft. Both subtend a 12° angle at the center of the column.

Like an egg in the #EggsAndDarts motif, a flute must be centered on the column axis when viewed directly from the front, back, or the sides. This is why the 12° are split into 6° on either side of the X axis. The center of the larger circle is µ = 144 units from the origin on the X axis. The center of the smaller circle is 5/6 of µ, or 120 units from the origin.

In https://pixelfed.social/p/Splines/799340150182400358, I mentioned working at sub-micron precision, and you might wonder where that came from when we have been using abstract units like µ without specifying any physical units. My apologies for not making it clear that I had assumed 1 unit was equal to 1 mm. If that assumption holds, then µ = 144 mm gives a total order height of 4104 mm, that is 13.46 ft. At smaller scales, the precision is even higher than 1/10 of a micron.

With that said, here the radius of the larger circle is 15.0728 units and that of the smaller circle is 12.5606 units, with sub-micron precision if 1 unit = 1 mm.

Refer to https://pixelfed.social/p/Splines/791399680747885646 and place the center of the smaller circle exactly at point J on the neck line. Later we will draw a sphere at the same location with the same radius.

If you want a flat bottom for flutes, place the center of the larger circle at exactly 28 units (12 for the #fillet and 16 for the #cavetto or #conge) above point A in that figure. If you want a round bottom, then further move the larger circle up by the size of its radius.

Nobody would quibble if you used a radius of 15 units instead of 15.0728 units, but it would make it easier to switch from flat to round bottom or vice-versa by simply moving the circle up or down 15 units.

#IonicColumn

#Flutes have a different configuration in the #IonicOrder than they do in the #DoricOrder. In #Doric, the flutes run right next to each other, dividing the circumference of the column into 24 equal sectors, or 15° each.

In #Ionic, there is a small gap between the flutes. This gap used to vary, but over time, Ionic designers seemed to have settled and standardized the measurements by splitting 15° in 4:1 ratio, giving 12° to a flute and 3° to the gap between flutes.

Because of this standardization, there would seem to be little room for variants, but there is. In his #RegolaArchitettura [see https://archive.org/details/gri_33125008229458/page/n37/mode/2up], #Vignola documented flutes with hemispherical tops but flat bottoms, as shown in the image here.

However, it is acceptable to have hemispheres at both top and bottom as long as they are consistently used within a #colonnade or #arcade.

Flute geometry is interesting. Just like the #IonicColumn #shaft, a flute also gradually tapers as it rises from bottom to top. Additionally, it bends along the shaft surface due to #entasis [see https://pixelfed.social/p/Splines/791794072490907090]. In other words, flutes hug the column shaft.

Unlike other decorative elements like #eggsAndDarts and #3StrandBraids, flutes are #subtractive, not #additive to the rest of the design. In other words, we have to carve the flutes out instead of adding them to the design.

Medusa is a composable, open-source commerce for developers. Try it out..!!!!

How I Created an Ecommerce App with Medusa and Ionic Silvia O'Dwyer for Medusa ・ Aug 25 '22 #ionic #opensource #javascript #programming source

https://devnews.tech/medusa-is-a-composable-open-source-commerce-for-developers-try-it-out/?utm_source=mastodon&utm_medium=jetpack_social

⁉️ #Ionic et #Capacitor sont-ils en danger ?

On peut s'interroger, vu que la société Ionic a annoncé l'arrêt de tous les services commerciaux (#Appflow, Identity Vault…).
En revanche, toute la partie opensource est bien maintenue.

⬇️ Plus d'infos ⬇️
https://buff.ly/4hU01ke
#android #ios #html #css #hybridapp #webapp #mobileapp

#IonicVolutes are the sinews of #IonicScrolls. Without #volutes, there would be scrolls, but not #Ionic Scrolls. Each scroll starts with a volute in front and is modulated by as many as six volutes of different shapes and sizes as it reaches the back, with the scroll surface tightly hugging the volutes at each contact point in ALL 3 dimensions. This is a key point to remember before we start #reverseEngineering the first #primaryProfileCurves from old image scans.

This diagram shows the #scaffolding we will construct using straight lines and rectangles, first in 2 dimensions, then place them front-to-back in 3 dimensions using precise markers, and finally scale and superimpose the volutes on this scaffolding.

All of this will be done before we derive the primary profile curves from the image scans.

How did I know about this scaffolding? I didn't. It is not documented anywhere that I'm aware of. I developed this after years of striving to derive the correct shape, and I hope that there are people who can still "see" things I might have missed and help improve the design.

So, the actual process went like this: I drew outlines from 2D image scans in the top view, getting close to #Vignola's detailed sketches. Then, I did the same thing with image scans in the side view, and I found that the designs didn't line up.

After several iterations, I got the designs to line up in both views, and it was obvious that the bell shape of the scroll would follow the large volute in the front.

So, I used the large volute as a "rail" and tried to sweep the primary profile curves on one rail. Big mistake! The undulating shapes of the primary profile curves wobbled wildly on the single rail — The middle, 3/4, and back of the scroll were twisted out of shape!

Instead of trying to #sweepOneRail, I decided to clamp down wobbling with another operation called #sweepTwoRails, using volutes at both front and back ends as rails with less wobbling.

You will need a #CAD tool to practice.

Plan for #ColumnShaft of #IonicColumn

The #shaft of an #Ionic column is not perfectly cylindrical but gradually tapers off in the top 2/3 of the shaft. As such, the #primaryProfileCurve is not a straight line, nor is it composed of regular arcs. Instead, it is a complex amalgam of straight lines, circular arcs, and #NURBS curves, where the fancy acronym stands for an even fancier name — "Non-Uniform Rational B-Splines."

So, the promise [https://pixelfed.social/p/Splines/789956327130679640] was that we were going to get through this by drawing just straight lines and arcs. How are we going to draw NURBS? The answer is that we won't. The #CAD program will, as long as we give it sufficient information to carry out the task.

There are three NURBS curves in the profile shown in the plan. The longest and the most important one is between the points marked C through J. There is a smaller one between B and C, and an even smaller one between J and K.

While all three NURBS curves are mathematically similar, the information we must provide to the CAD program for the longest one is different from the other two short ones, and the operations the CAD program carries out to construct the longest one and the other two curves is also different.

This brings us to two new operations — #interpolate or "fit through points," and #blend shapes (existing curves or surfaces). When you choose a CAD program, make sure it supports NURBS, #interpolation, and #blending.

Starting at the bottom of the shaft, point A is 144 units from the #columnAxis, and so is point B, which is also 768 units higher than A. Starting with C through J, the points gradually move closer to the axis until J is exactly µ * 5/6, or 120 units from the axis. These points are equidistant vertically — all 192 units apart. However the horizontal distance is non-uniform.

In the next post we will mark the 8 points C through J using using one arc and 8 straight lines — I will keep my promise.

#Vitruvius defined the single parameter called #module or µ, which is the radius of a column at its base [https://pixelfed.social/p/Splines/790357912719769731].

#Vignola divided µ into 12 parts for the #Tuscan and #Doric orders, and into 18 parts for the #lonic, #Corinthian and #Composite orders. To make it easier to move between the orders, it is helpful to choose a value for µ that is a multiple of both 12 and 18. We could start with module µ = 36, which is the least common multiple of 12 and 18.

However, in classical design, it's a lot easier if minor grid lines are multiples of 8 (as in music 'octaves' and poetry 'octets'). So, I use a grid with minor grid marks at 8 and major grid marks at 32, which leads us to choose µ = 144 as that is the least common multiple of 12, 18, 8, and 32.

This value of µ = 144 is still abstract because we haven't chosen a physical unit like mm or inch, but it does not matter at this point. Once the model is constructed with the chosen value of µ, it can be scaled up or down in software to get the desired column width or order height in physical units.

The total height of columns for the same µ are in the ratio 7:8:9:10 for the #Tuscan, #Doric, #Ionic, and #Corinthian, with #Composite the same as Corinthian. When µ = 144, the diameter is 288. So the height of the Ionic column is 288*9 = 2592 units.

The #pedestal, #column, and #entablature are always in 4:12:3 ratio across all orders. So the height of the Ionic pedestal is 864 and height of the entablature is 648, and the total height of the order is 4104 units.

Remember that in the Ionic order, µ is divided into 18 "parts". So each part is 144/18 = 8 units. With this we can convert between µ and parts in either direction.

Total order height of 4104 units is then 4104/8 = 513 parts. If you are trained in computer science, you will grow despondent that it is 513, not 512. Let go, and everything will be all right.

The pedestal is the easiest component, and we start with that.

This is a sketch of the complete #IonicOrder, excluding #intercolumniation and #arches, which came later.

Different people have different abilities and different levels of mathematical knowledge. I make few assumptions about the minimum knowledge one must possess to follow my posts. At a minimum, one must understand ratio, proportion, similar, congruent triangles, Pythagoras, and basic properties of circles, including radius, diameter, circumference, tangents, secants, and chords.

No trigonometry or calculus is assumed, but people who have a knowledge of differentiable continuity, maxima, minima, and inflection points will have increased appreciation of the nuances of some designs featuring smooth curves and surfaces.

I start with first principles, even if it might be a little boring for people with advanced skills. The most basic requirement is that one must be able to mark points on a 3D grid, draw a straight line between two points, and draw a circle or arc from the center. The CAD tools should help with the rest, for example, to find a point of tangency, draw a circle through three arbitrary points, or tangential to three curves (if possible).

There are three components in the #Ionic order. Starting at the bottom is the #pedestal (which is optional), the #column, and the #entablature. Each of these three components has three subcomponents:
— Pedestal has #basement, #dado, and #cap.
— Column has #base, #shaft, and #capital.
— Entablature has #architrave, #frieze, and #cornice.

The pedestal, column, and entablature are always in 4:12:3 ratio. If all components are present, the total order height is divisible by 19. If there's no pedestal, the total height is divisible by 15.

The entire order is parameterized by a SINGLE parameter — the radius of the column at its base. #Vitruvius called the radius a "module" (µ) — an abstract unit of measure independent of physical units.

Components of Ionic column and entablature also have classic and modern variations.

This is a sketch of the top of an #IonicColumn with #scrolls, #volutes, and other embellishments. Before I delve into my modern designs, I want to emphasize that most of them are rooted in classical designs of antiquity but still retain their timeless essence.

Different regions of the world have developed and refined distinct design patterns over thousands of years. Greeks, Romans, Ottomans, Arabs, Moghuls, Hindus, and others — all have something to contribute to what we call #art and #design in human civilization.

My initial focus is on Greco-Roman architecture and design which has five distinct orders: #Tuscan, #Doric, #Ionic, #Corinthian, and #Composite. Of these, the #IonicOrder is of medium complexity. The Doric and Tuscan are simpler, while Corinthian and Composite are more complex.

Because of its moderate complexity, I chose the Ionic Order for a complete and systematic look at its design methodology and proportions of its elements. I use concrete measurements to make concepts easier to understand. Once you understand the Ionic order, it's easy to step down to the Doric and Tuscan orders. It's more work to step up to the Corinthian and Composite orders, but if you follow my methodology with dedication, you will learn the skills necessary to tackle the more complex orders or branch out on your own.

In an earlier post, I mentioned the importance of sticking to proportions and measurements. I'll point out opportunities for variation as we progress systematically.

An additional, but very important point I want to emphasize is that this #digitalArt is not just #art, but #engineering design as well, because the end result is to realize physical artifacts from these designs, whether by #AdditiveManufacturing (#3DPrinting), #SubtractiveManufacturing (#CNC #Carving), #ReliefEngraving, #Printing, or any other physical realization.

You'll need a #CAD tool to practice, but you can also follow along as a reader initially, and come back when you're ready to practice

It appears Android WebViews finally implement `safe-area-inset-*` environment variables properly¹²³ 🎉

---

1. Only on Android 15+ when built with an SDK version 35+

2. Because Android 15 & SDK 35 now enforce edge-to-edge display mode on everything, so have fun with the bottom navigation bar for people who don't use gesture navigation

3. `viewport-fit=cover` vs `viewport-fit=contain` makes no difference on Android

#Android #AndroidDev #Cordova #Ionic #Capacitor #WebView

#Ionic

Client Info