we don't own the apert.us domain anymore...

Seen the new footage? http://apert.us/iK3l

Works have migrated to LaTeX and GitHub - https://github.com/apertus-open-source-cinema/beta-documentation

A more recent version is Polr Project:

REST has a license in "develop" branch, but Github does not recognize it. Possibly .txt is missing as extension (see OC repo and the license info in the top-right corner).

Feed2toot automatically parses rss feeds, identifies new posts and posts them on the Mastodon social network.

Noticed this recently with Mission Briefings

But both Chrome & Firefox on Android render the page fine.

We should probably weigh all individual parts of the enclosure, as they come out. Why not eh.

27.9g for the footplate and 47.9g for the mountbase/skeleton.

We should probably weigh all individual parts of the enclosure, as they come out. Why not eh.

dimensions drawing:

I asked Herbert to weight one skeleton and footplate metal part each.

Also the weight of the skeleton enclosure on its own (as this isn't necessarily required, and as in cases like Mavrx, it can be reduced from the dev kit total weight for consideration with respect to aerial stuff).

Precise bounding box dimensions of the Dev Kit: 111.76 x 65.15 x 55.4 mm

Weight of the Dev Kit: 319g

Again lets not overthink this simple image, we can swap it out anytime later.

Then it might be best to do it the other way around, for Michael to match the perspectives of the Dev Kit photo, seeing as he's busy with product revisions I'd imagine.

Max will pick up a dev kit to snap those pictures on monday.
If you want to give him a briefing on what perspectives, background and lighting, etc. you want for these now is a perfect time :)

You know when I keep asking for the dev kit on a white background? It's not to picture it on a white background (although that can/will sometimes be useful) it's because it's easier to cut the background away when the contrast is that high. Then it can be transposed onto C1C1C1 and given some subtle drop shadow. It could be done with the promo dev kit image we already have, but unfortunately it has two cameras facing each other so someone can see the reverse. That's useful too in certain circumstances but not here I don't think because it becomes a space/detail issue. In addition a lens being attached probably isn't necessary.

newest update on pholio: https://lab.apertus.org/M25

Ah. Thanks.

Hi Rexor, the hole is acutally there, it's just not visible due to perspective and it isn't connected to the outer frame like the other holes, see attached image.

There's also a screw-hole missing on the internal shot Michael, dunno if you missed that. On the upper plate on the side closest to camera there's only one screw-hole, whereas on the external shot, on the lower plate, on the side furthest away from the camera, there are two... The one that's meant to be right in the corner.

Strange, the extra spaces are in the post data but they don't show in the thread.

Can we get the ref line on one line. There are typically 2 spaces between a previous or following character and the '|' symbol,

Aaaaaand update. If everybody is good, I will create a pholio and upload upcoming mocks.

While we are at it with the labels and such should we also add the website apertus.org and that its for the AXIOM Beta?

Hi Sebastian & RexOr,

Good idea with the label!

^ Edited.

A quick note Michael.

Looks very nice.

proposal for part viz

In T790#11745, @RexOr wrote:

Edit - There are no margins here but the lines in this post have 50 words and that's nice.

This word rule is not a standard or trend or design choice.
It's the result of research that evaluates how we humans with our eyes and brains are most effective at reading - meaning we do not loose track of where we are in the sentence and need the least amount of concentration while reading.

I don't know about this 9 to 12 word thing that you've mentioned before. When I look at http://apertus-d8-dev.w4f.eu/drupal8/products on a desktop the text seems great. It should be ever so slightly larger possibly, but I'm not sure about limiting text to 9 words per line. If this has been fashionable with websites at some point in the past then what works best for us should be what's important, as opposed to conforming to previous standards.

Agreed. Roboto or Open Sans are much better choices for main bodies, but where titles are concerned we can probably afford to be exploratory... although being uniform is fail-safe.

Fine for me for now but could it could get a very long page once we have more content

The present layout for Beta is bad by the way. It's ok to have these tabs but all the information contained on those tabs should be on one scrolling page, with tabs being a means to jump to specific sections of that page.

Needs a bit of investigation, but feel free to go to BlackMagic site to see their mobile navigation.

if it works on mobile :)

Nice demo of the inline menu -> http://output.jsbin.com/rusup/1/

Maybe we can show sub-menus underneath the navigation, similar to this -> https://i.stack.imgur.com/vmI0M.jpg

not with dropdownmenu

Something like this? -> https://bootsnipp.com/snippets/featured/multi-level-dropdown-menu-bs3

I set the board to "disabled". We can enable it again at any time in the future.

Sure. Let's reappraise the forum closer to shipping.

first draft complete: https://www.apertus.org/smt-workshop

Margin fade h400

the "freeze" would basically mean we set the forum read-only for now and in the future we can at any time decide to revive it.

Yes, the breadcrumbs were positioned just below the navbar, but are not there at the moment. Have to investigate it, maybe it has to do with the left shift of the middle section of the navbar. When they are available again, we can discuss where the should be positioned for final version, but currently i've tried to add them similar to BM ones.

Definitely in favour of reducing problems where possible. Whatever happens if we could make some sort of save so that if we ever want to re-employ it then that task is made easier for having done so.

Is it something like this we're after?

For me the message to the viewer of this image should be twofold:

The problem currently is that we are collecting spam in the forums and have to manually clean up after it constantly - that spam might get us blacklisted in search engines...

If you want to. I would have just left it. Is this something to do with server upgrade I guess. Yeah I suppose so, I think it would only ever move to any degree once the cameras were shipping certainly.

So should we freeze the forums until phabricator is updated?

Well even though it seems we've got little control over how Phabricator looks it would be best for all comms to remain here, in one place. If we're gonna accomplish that we're gonna have to either configure a more unified 'front page' with a forum-like appearence or create some other sort of system to integrate the site and the labs. At the moment it seems that people don't know how to make sense of this place, so let's see what an upgrade does to appearences and available plug-ins/applications.

So should we freeze the forums until phabricator is updated?

I think these exact thoughts often, and can't make my mind up. Don't think we should scrap it and not sure it warrants any time either.