Did you look through the plain js demos? e.g. https://material-ui.com/demos/steppers/ I've found that it's not that hard to convert from that to scala js.
That's what i am already doing with this https://codesandbox.io/s/r6401x80o but i am facing difficltues with it as you can see!
I haven't used the steppers at all @hamzarhaiem so I cannot help directly either. What i normally do is to inspect the component with react dev tools (in your browser) to see that the data it gets looks reasonable, and try to compare against javascript demos like @rleibman suggested
I am trying to localised rhe MuiDatePicker (fr) like this exemple https://v0.material-ui.com/#/components/date-picker
val frDt = "global.Intl.DateTimeFormat".asInstanceOf[js.Function]
MuiDatePicker(
DateTimeFormat = frDt,
locale = "fr",
mode = PortraitLandscape.landscape
)()And i am having this error..
material_ui-bundle.js:4 Uncaught TypeError: e is not a constructor
at h (material_ui-bundle.js:4)
at material_ui-bundle.js:18
at Array.map (<anonymous>)
at t.value (material_ui-bundle.js:18)
at index-bundle.js:30
at s (index-bundle.js:29)
at g._renderValidatedComponentWithoutOwnerOrContext (index-bundle.js:30)
at g._renderValidatedComponent (index-bundle.js:30)
at g.performInitialMount (index-bundle.js:30)
at g.mountComponent (index-bundle.js:29)Any help please?? :(
or rather, if it is already typed up and
DateTimeFormat is a class (i havent used this) you could try js.constructorOf[Intl.DateTimeFormat] and cast that
I was just wondering how the code generation for material-ui facade works? Would be great to be up to date with mui 1.5.0, I was looking at their API docs, and I think they generate them with https://github.com/reactjs/react-docgen
Which made me think that might be a good place to start for code generation, I tried it out and react-docgen will indeed generate a giant json file with contents very like the API docs, slightly annoyingly it just says "object" in a lot of places, but I was thinking it would be a start
I guess it is doing a similar thing but with its own parsing, wow that's impressive :)
It might be easy to do, depending on how much has changed
I'll see if there's anything I can do, would be nice to have the most recent version, it does seem like they've made some improvements
Did anyone ever look at using the docgen approach, or is the direct JS parsing just better?
so propTypes and documentation, none of those approaches are optimal
@oyvindberg Yup it seems like a tricky task... I put up some very basic code based on react-docgen json output here: https://github.com/trepidacious/scalajs-react-material-ui
It seems to kind of work, no icons or support for sum (oneof) props yet
One nice thing is it puts the API docs in as scaladocs for the prop parameters
It processes everything (unless I've missed something) from 1.5.0, I've tried a couple of components and they seem to kind of work ;)
I want to keep the search but not the Total and Page Size selector https://imgur.com/a/7u3woln
Hey guys, just wanted to share my repo https://github.com/dborisenko/scalajs-react-components . I migrated Semantic UI React to the latest version of React (16.7) and scalajs-react (1.3.1, because the upstream repo was quite outdated). And I ported some more components to scalajs-react, which might be useful: React Sortable (HOC), react-trello, STORM React Diagrams, react-markdown, React Syntax Highlighter. My aim was not migrate to the latest version of scalajs-react everything, but migrate only that component which I needed (in particular , only Semantic UI). That is why I dropped a lot of components from my repo and I cannot make PR to the upstream repo. So, if you think, it could be useful, feel free to use.
@dborisenko @here.... I've been really bad. A while ago, we forked the project to create a community project at https://github.com/scalajs-react-components/scalajs-react-components. I have not been able to work on it, though I have made a few changes to some of the semantic-ui things. Anyway, I am about to get back into it. And here are my plans:
- Full Tech refresh, latest react, latest scala, latest scala.js, latest scalajs-react.
- Split the project into a number of projects
- Core and macro
- Semantic UI
- Elemental UI
- Material UI
- Other wrapper projects
- Other custom components written in scala (besides the ones already in the repo, I'll add a few of my own)
I'm going to start with what I have and then try to merge Denis' changes.
Once it's all done, I'll try to deploy this to the mvn repo, that's already been set up a while ago.
Hey... @dborisenko I'd love to work with you to try to figure out what it is you did... I see that you moved things around a lot, but you also removed huge sections of code, including all of MaterialUI and ElementalUI... what time/timezone works for you to talk about it?
Hi @rleibman, well, yes, I moved around a lot of code. The main reason was to split one monolith project with all possible components to multiple smaller ones. It helps to keep track on dependencies and update only what’s needed. I also changed package names - the original thought was to be able to use monolith scalajs-react-components together with my refactored libraries, but I ended up completely moving away a lot of stuff and refactoring. I also added unit tests to simplify upgrade process. And I dropped some libraries. First of all, I needed only semantic-ui. In second, there are some libraries without any support. I think, elemental-ui doesn’t have react 16 support and I found somewhere that support of that library is discontinued. So, this was, in short, my motivation.
But we can have a chat. My time zone is CEST (GMT+1)
@dborisenko @trepidacious ... I think I like the idea of multiple sbt projects for different parts, I'm not sure if mono-repo or multi-repo. Either way.... yes, I understand the need to remove those things that cannot work with the latest react. But I know a few people are using material-ui, so I think I'd keep at least that. I myself only use semantic-ui out of this repo, and have a few other components for which I've built manual wrappers. I desperately need a couple of features out of the newer semantic-ui.
I'm looking to see if there are other options besides this project (ahem... ) and some of 'em look promising and easier to manage and maintain, so I'm holding off from touching all this stuff for a bit.
@rleibman Before I ran into that I was wondering about using the same technique I used for my material-ui facade to semantic-ui. It seemed to be working out pretty well, I got a working facade to the latest mui going, I didn't get much of a chance to try it before running into the performance issues that have put me off mui ;)
It's based on using react-docgen output to generate scala code, if the proptypes are ok in semantic-ui it might work ok. I'm a little worried that all the
as='random' stuff might be hard though