3 ms·

Meant with all the love in the world: If you want to show show things please show them. Particularly when it's something you can show with html and I'm looking

by IanCal 2y ago

Meant with all the love in the world: If you want to show show things please show them. Particularly when it's something you can show with html and I'm looking at a web page! We see so many so many new proposals and things you have to show me something early or I'll move on. My path was GitHub. Text starting with "in the beginning". The first link is to a page maybe from 1993? I scroll to find the webpage which is not clearly linked but under "scope of work - plan". Website, talks about plans. Look in the menu. Only in the third section are graduated proposals. Open one. Nothing showing me any examples. Someone else here says that customisable select came out of this and link to a Google page which has code, screenshots and I think a live code editor. You can accuse me of being lazy. Sure. But this setup feels like it's putting a lot of roadblocks in the way where people who want to care about this and help will drop out.

bux93 2y ago
The 'graduated proposals' for UI elements don't even have any mockups at all. Great if your UI proposals are for gopher, I guess. The people proposing deliberately bad UI on reddit as a joke make GIFs, just saying.
troupo 2y ago
The site is better, and shows research on how and what is considered. https://open-ui.org/ https://open-ui.org/
- IanCal 2y ago
  That's the site I visited and saw the graduated proposals.
  - troupo 2y ago
    The existing graduated proposals don't even have anything strictly UI-related that needs UI prototypes or screenshots, but I do agree that as docs they should probably link to some of the discussions/proposals/prototypes more prominently.
    - IanCal 2y ago
      Perhaps I'm misunderstanding but the first one I see is an exclusive accordion (https://open-ui.org/components/accordion.explainer/ https://open-ui.org/components/accordion.explainer/). This links out to several websites to show examples in the wild. Unfortunately, this is highly dependent on sites not changing, the links are not to exactly where they need to go and the link to the pixel 7 page actually goes to pixel 8 now. One of the others goes straight into a privacy policy and never takes you to the right link unless you then close out and follow it again. It links off to the spec for the details element, which itself actually has an example https://html.spec.whatwg.org/multipage/interactive-elements.html#the-details-element https://html.spec.whatwg.org/multipage/interactive-elements.... It feels like a great candidate to have something interactive with the explanation of the behaviour desired (but not standardised) and then the proposed code for the same behaviour when it's standardised.
lyu07282 2y ago
> show me something early or I'll move on. Tbh. you probably should, you are not the target audience, they aren't trying to sell you anything this isn't "for you".
- IanCal 2y ago
  If the project wants no attention from developers or to bring in any new people to get involved, sure, make it as complex as possible to see what is being talked about. If it's an internal document that simply doesn't need protecting, great. However they are explicitly asking people to get involved.

by IanCal 2y ago

bux93 2y ago

The 'graduated proposals' for UI elements don't even have any mockups at all. Great if your UI proposals are for gopher, I guess. The people proposing deliberately bad UI on reddit as a joke make GIFs, just saying.

troupo 2y ago

The site is better, and shows research on how and what is considered. https://open-ui.org/ https://open-ui.org/

IanCal 2y ago
That's the site I visited and saw the graduated proposals.
- troupo 2y ago
  The existing graduated proposals don't even have anything strictly UI-related that needs UI prototypes or screenshots, but I do agree that as docs they should probably link to some of the discussions/proposals/prototypes more prominently.
  - IanCal 2y ago
    Perhaps I'm misunderstanding but the first one I see is an exclusive accordion (https://open-ui.org/components/accordion.explainer/ https://open-ui.org/components/accordion.explainer/). This links out to several websites to show examples in the wild. Unfortunately, this is highly dependent on sites not changing, the links are not to exactly where they need to go and the link to the pixel 7 page actually goes to pixel 8 now. One of the others goes straight into a privacy policy and never takes you to the right link unless you then close out and follow it again. It links off to the spec for the details element, which itself actually has an example https://html.spec.whatwg.org/multipage/interactive-elements.html#the-details-element https://html.spec.whatwg.org/multipage/interactive-elements.... It feels like a great candidate to have something interactive with the explanation of the behaviour desired (but not standardised) and then the proposed code for the same behaviour when it's standardised.

lyu07282 2y ago

> show me something early or I'll move on. Tbh. you probably should, you are not the target audience, they aren't trying to sell you anything this isn't "for you".

IanCal 2y ago
If the project wants no attention from developers or to bring in any new people to get involved, sure, make it as complex as possible to see what is being talked about. If it's an internal document that simply doesn't need protecting, great. However they are explicitly asking people to get involved.