g6d3np81

TIL there is a closer approximation than 22/7

Thank you, I already skimmed through that article before posting. Maybe I failed to put my question into words properly.

I want examples similar to pool/fence circumference in the article. Along the line of "We're building x, and this is the worst rounding we can go, one fewer digit and it will be off by y"

I would not place my hope on kadokawa doing anything like that. I don't think they even care about anime industry aside from make money part of it.

TFW girl a 3-in-1 kemono fang midriff and you don't know which community to post.

Misinformation may reduce repeat visit, that part, I have no idea if google take into account when they rank the result. Domain/page age also plays a role. But what about other "problems"? If I try to de-optimize every items on that guide, will it speed up the de-rank as well?

Regarding SEO, What's stopping maintainers from vandalizing their own fandom page?

It would not be difficult to make a bot to update fandom page with a convincing but slightly wrong info, after a few hundred iterations, it's all useless. Go look at what google recommend and do complete opposite. I'm convinced this will bomb ranking and put whatever wiki they migrated to at the top.

Can you explain a bit more about "zooming, different levels of detail" you mention? Maybe break them down to separate issue you are having with the library, what does it do, what do you want that it's not doing. If there is a way to tweak it then you don't have to build the component from scratch.

But if you already abandoned the idea of tweaking timeline-js then you can have full control in vue, have to build it yourself though. Start by breaking the functionality of the timeline into separate interaction. From a quick look, timeline-js just make style attribute reactive. Have a box? good. Now put really long div in it with placeholder texture. Can you drag/scroll it? no? grab a suitable function from vueuse and make it scrollable. Follow with markers, zoom, dummy event items, data fetching (the actual width, marker spacing, events placement can be calculated from timestamp in json after this step), lazy loading, styling, animation, so on.

I don't know how much experience do you have with each things required (html, css, js, vue) so it is a bit difficult to give useful answer.

Events?? TimelineJS3/blob/master/API.md
Not sure what else is available if you want to build the component yourself though.

but note that because TimelineJS's primary use case is the embedded iframe, some of these methods have not been thoroughly tested.

I think you can replicate most of its function with vue alone, skip all the tedious work with vueuse. Lazy-load with Intersection Observer. Basic events and refs for zoom level.

I would start with putting all entries into a usable format. A CMS will help a lot. Maybe a JSON from your django server containing batch of entries, its timestamp, length, importance, tags, etc. Anything that is required to place entry on the timeline properly in vue.

EDIT:
Have you tried the official tutorial?

Flac is a low bar for any music player though. I don't know whether itunes support it yet, don't care.

I'm sure Rhythmbox works well for you and that is great. But I also need some niche features which might not be in it.

Mostly conversion and forensic thing.
ape tak tta format, bit compare, audio checksum, mass-tag/batch-tag, replaygain, custom playlist columns, statistic driven field. Don't know what else until I try and find it's missing.

I'm also sure I can get all those and more in different cli tool if I want but getting them in one software is very convenient.

After a quick look, DeaDBeeF might have most of what I want.

• Sort and group the tracks in any order you wish, using advanced Title Formatting scripting, compatible with Foobar2000

Got the date wrong, last time I tried it was 2018. Lot of new features added since then.

What if I use foobar and will not settle for anything less?
I have not fully moved to linux yet. Last time I tried it through wine back in 2020 it ran like shit. Deadbeef did not have feature parity either. Wonder how good is it now.

There is a trend line of the amount of shit you need to do to get linux to do things you want.
There is a trend line of the amount of shit you need to do to stop windows from doing things you don't want.

Those two lines have crossed quite a while ago.

If you've just open Blender for the first time and then you've tried to... do things.
Maybe, trying to see how far you can go... without getting help. [laugh]
You might have discovered... you need help immediately.

-- some donut guy

This is janky but will do the best I can. Maybe someone way smarter than me can find a more efficient way to do it.

I'm doing this demo on some park with Butt in Germany (OSM)
Blend file
Layout window
Node setup

Limitation
Line of sight is made from the 'origin' of (building) geometry (one-to-many).

I have tried the same method but in reverse and combine lines of sight (many-to-many) and iterate through them but can not get any result, 'position node' output is changed based on whatever you are using with it and two sets of point cloud hurts my head.

However, with this node setup if you model each room as separated object, it will still work but at room level instead of building level. Wowowee itsa very nice. Just no way to quickly get an ID that I know of.

Process

1. Import GIS stuff as usual
2. You MUST set the origin of each object to its own geometry (orange dot must stay in the geometry) as GIS plugin will set origin as world center 0,0,0 and that will break stuff.
3. Any object that will potentially obstruct the view must be put inside a flat one-level collection.
   3.1 Buildings to analyze can be put in any collection or not at all.
   3.2 If any potentially obstructing object is also an analyzing target from (3.1), it should be duplicate-link with Alt+D then ESC and put in the obstruction collection.
4. View target e.g. park, lake, must have face, can not be just curves, edges, vertices.
5. Add geometry node modifier to any buildings you want analyzed.
   5.1 Browse for a node named 'visibility' I already set up.
   5.2 Select target.
   5.3 Set ray length (meter) long enough to reach your target.
   5.4 Select any other buildings you want analyzed, with copy source in yellow, paste target in orange hilight. Ctrl+L to copy geo-node modifier to all of them.
6. Open spreadsheet window and select a unit to see visibility value.

EDIT: I forget to expose obstruction selector, you can select it inside geometry node window. I also got an idea for V2 which may solve issue of getting IDs list. Will try again tomorrow.

HAPPY ACCIDENT: you can also stack the modifier and select another target, spreadsheet will show another line of visibility attribute for each additional target in the stack.

Be careful though, too much and blender might crash.

I don't recommend watching/doing the whole donut series, but you still need some familiarity to get around and understand more complex part of blender that other tutorials may teach you :|

Maybe you can cobble together something even better from these tutorial channels. Erindale, Chris P