August 7th/8th

[franknoirot]

Kurt (@Irev-Dev)

• Struggling to get the social image cards to work. Following guides but the lambda keeps rejecting still.
• Have been working with @hrgdavor to get a first version of the customizer working, OpenJSCAD-only version that borrows from their code.
• Discussions being had in Discord, the metadata for customizer parameters should contain type, step value, and so on, but should not enforce a type of UI. User should be able to suggest UI such as "slider", but not need to.
• Someone reached out and couldn't rename their project and upon investigation it seems like Safari is pretty broken, we didn't realize it doesn't support the gap CSS property, opened Safari styling errors #435, and renaming projects just fails silently for some reason?

Torsten (@t-paul)

• Found it difficult to get free time this past week, covering vacation period.
• On board with discussions between @Irev-Dev and @hrgdavor on moving away from implicit values in customizer configuration to a more explicit model.
• Wants to move away from the "magic comment" strategy Thingiverse used for the customizer, but sees why they did it and understands that OpenJSCAD needs to continue supporting it even as they find the future implementation.
• Working through how to offer a new implementation in a stable and transparent way, still searching for the most responsible strategy.
• Wants a way to allow users to be explicit about the version within the metadata, to support larger shifts like parsing logic changes.
• Thinks that the current suggestions are a good starting point, and is happy to see how it works initially. The proposed model as it stands is not dramatically different from the Thingiverse implementation, which is sensible to start.
• Thinks that a good metaphor for this discussion of defining the data/input models but not how they look is similar to HTML and CSS's roles in web development. The markup is not expected to control the presentation, the browser controls the basic styling and the CSS defines specifications beyond that.
• @Irev-Dev mentioned a discussion with @hrgdavor the desire to save down parameters, and potentially allow users in future to save a "fork" of a project with their own defined parameter values. This is hairy so he wants to think about it more, because the model may change after the user saves those parameter values; there is no guarantee that a set of params will work into the future.
  • Neither of them want to implement this in the near future, and @t-paul isn't super concerned about it yet.
• Asked if the Share button is working correctly, or best way to share projects in a stable way right now.
  • @Irev-Dev said the Share button URL is currently including the encoded project in the URL (leftover from the /dev-ide implementation) which is broken. Simply share the url, with /ide on the end if you want to show the code or without if you want users to see project information.
  • Kicked off a brief discussion about stable URLs which is of key interest to @t-paul and many others, wants a links that don't break down the line because they are often used as published resources.
  • Discussed the potential fragility of links breaking when either a user changes their name or the project's name and solutions to prevent that break, such as a permalink with the ugly part ID in them, a redirect list that's added to if the user changes either their username or projects' names, or URLs that contain IDs along with human-readable parts.

Frank (@franknoirot)

• Not much work to report, just got settled back at home today.
• Had one question about the settings tray design: he struggled to think of what settings would go under each section of this pane, and thought that the discussion was bigger than could be handled within Figma comments. Should he open a discussion in GH about this?
  • @Irev-Dev thinks this is in a decent stopping place for now, will open a discussion later as the implement for the settings pane really gets underway. At least has shown the basic layout and setting types.
  • @Irev-Dev mentioned a couple other Viewer-specific settings he's interested in supporting, such as selecting from a set of pre-defined scene styles, some practical and some whimsical. High on the "nice to have" list after a few more basic UX functionalities, multifile support, and the Github Integration™
• Really wants to get UX blog posts done this week, design the home page, and get back to helping with a bit of dev.
  • Will ping @Irev-Dev if he runs into any issues getting local dev environment set up.
  • Will take on Safari styling errors #435 as a first issue.