There are more than two genders about tabler HOT 28 CLOSED

Sorry guys, as at the beginning, this discussion made me smile, now it seems to me that it is starting to go in the wrong direction. This is an icon input, not gender input.

If someone wants to make a reason to express their own views, please fork it to tabler-with-gender-input repo. All base components from tabler allows you do it.

I made tabler for people, for fun. I lose the urge to do anything when I hear such conversations. How will you use it, it's up to you.

I changed icons in icons input for weather icons. I'm sorry I did not include snow, hurricane and I do not know what the weather is like icon in it, because there were no such icons in icon-pack.

from tabler.

I completely disagree with accommodating the transcended community with their radical left ideas! This project should not fall into that trap lest I fork this myself and take out that change on my fork!

from tabler.

Look guys don't turn this project into a platform for your political views. If you want to put those stuff, fork this library and create a separate branch on your fork. That way you can have the latest changes from the master and still have your own changes without everyone having to put up with your "sizes" thing or "gender" thing. That's what I'm going to do.

from tabler.

Am I the only one who remembers that this is a template? It's meant to be a starting point, not a complete working site. If you need more sizes or genders, add them to your own project. The samples don't need to account for every possible use case. They are, after all, just that--examples.

from tabler.

I agree with keeping things development related and that's all I come here for. However, designing a program so that it is accessible and inclusive to people isn't that much of a political statement to me - it's just good user experience. It is clear that the inputs are totally an example/template but if simple changes (that hurt absolutely no one) like this are made this early on, more users in the future have a chance to feel like their identity isn't being denied by a simple web tool from the first moments they use it.

from tabler.

Please add my XXXL to this example

from tabler.

Let's also remember that you are bound to follow the project's code of conduct.

from tabler.

I opened an issue and am waiting for a response from the maintainer. That's the beauty of GitHub.

from tabler.

Fork it and add it. That's the beauty of Github.

from tabler.

Let's keep it on topic folks and keep the sarcastic comments to a minimum.

from tabler.

these inputs are just examples.

from tabler.

When you just copy a Code of Conduct from somewhere without reading it (nor agreeing with it) yourself.

Insert meme here

from tabler.

@jamiebuilds, @LasseRafn you are crazy guys, I'm open for any ideas ;)

from tabler.

I tend to agree with @luizbills that it are just examples on how to work with Icons input.

That being said, I'm all for inclusivity.

Maybe the solution should be a new gender form component that allows people to select their genders, and that is not based on this Icons input, as I'm not sure if icons are a inclusive way to select them; there might be better ways.

Font awesome has a big selection in their set, would that work?

from tabler.

@seleznevdev There is a difference between gender, and size (one being discrimination and lack of understanding...). However if you feel like this is necessary, I think you should create another issue or even a pull request. In which case I think you should also add: XS, XXS, XXXS, XXXXL, XXL and so on.

Personally, I feel that the size example is broad enough, while gender is not. We don't even need a option for each gender, simply a "Other" field as suggested.

from tabler.

@LasseRafn It's just the simple "Icons input" example, not the complete "Gender" field. You're free to add any icons or text fields in your project

from tabler.

@LasseRafn Exactly!

from tabler.

@seleznevdev and so are you, with your sizes. 👍

from tabler.

@LasseRafn He was being sarcastic.

from tabler.

The current binary gender options exclude people and that should be changed, no question there IMO.

#74 removes the existing exclusion while keeping the Icons Input example simple and clear. #73 is more actively inclusive of gender identity, to the detriment of the simplicity of the example.

Maybe a middle ground of having the inputs from #73 somewhere in the Form Elements page, while keeping something like #74 for the basic Icons Input section?

from tabler.

Very nice idea 👍

from tabler.

I might find time for such thing, but I mean if @jamiebuilds has the HTML already I think that could be implemented right away

from tabler.

I don't think you want my half-assed work in devtools. I just overwrote a bunch of inline styles

from tabler.

@luizbills I recognise that, they still should be inclusive.

from tabler.

Look guys don't turn this project into a platform for your political views. If you want to put those stuff, fork this library and create a separate branch on your fork. That way you can have the latest changes from the master and still have your own changes without everyone having to put up with your "sizes" thing or "gender" thing. That's what I'm going to do.

from tabler.

@Nilpo I’m aware

from tabler.

The gender input element by @jamiebuilds is done in #73

from tabler.

@LasseRafn It should be definitely Nicolas Cage

from tabler.