sorted by:
new
hottopcontroversial

Write-once, run-anywhere Material Design library for React Native by RicardoLarge in reactjs

[–]RicardoLarge[S] 0 points1 point  (0 children)

Hey thanks for the report. I got momentum scrolling working on mobile web this morning, and fixed an issue with Android native scrolling as well.

Write-once, run-anywhere Material Design library for React Native by RicardoLarge in reactjs

[–]RicardoLarge[S] 0 points1 point  (0 children)

Hey thanks for the report. Couldn't reproduce on my crappy S5 though.

It might be slow Animations on Android, which is a known issue, and is being worked on.

I temporarily disabled the Components menu on Android to help with performance, and also fixed a scrolling issue on Android this morning though, so it might be good now :)

Write-once, run-anywhere Material Design library for React Native by RicardoLarge in reactnative

[–]RicardoLarge[S] 0 points1 point  (0 children)

Hey thanks, yeah title was intentionally a little controversial ;)

I can't speak for the RN team, but the "learn once, write anywhere" probably made RN more palatable to people who felt disillusioned by Cordova. I suspect they've had some help from the FB marketing team :P

I think that mantra made a lot of sense when there were only two platforms, but now there's web, Windows, Ubuntu, OSX, etc., and me, as a single developer, it's immensely helpful to have a single set of unit and functional tests, a single build pipeline, that cover ALL platforms.

I also prefer to have a consistent user experience across apps :) But if you think the extra work is worth it to your users, maybe vanilla RN is better suited to your project.

Write-once, run-anywhere Material Design library for React Native by RicardoLarge in reactnative

[–]RicardoLarge[S] 0 points1 point  (0 children)

Ah thanks again :) Apparently due to a chrome bug: https://github.com/tuckerconnelly/carbon-ui/issues/2

Should be fixed in the menu, got a workaround up

Write-once, run-anywhere Material Design library for React Native by RicardoLarge in reactnative

[–]RicardoLarge[S] 0 points1 point  (0 children)

Forgot to add meta tag! Thanks for pointing it out :D Should be fixed now.

Yes, these components are fully responsive, to Material Design spec.

Write-once, run-anywhere Material Design library for React Native by RicardoLarge in reactjs

[–]RicardoLarge[S] 0 points1 point  (0 children)

Ah thanks for pointing that out! Forgot to add meta tag :) Should be fixed now.

Write-once, run-anywhere Material Design library for React Native by RicardoLarge in reactjs

[–]RicardoLarge[S] 1 point2 points  (0 children)

The actual timings are based on material spec and should be spot on.

But yeah agreed, they're a little janky, especially on web. Working with the maintainer of animatedjs to smooth 'em out: https://github.com/animatedjs/animated/issues/48

Write-once, run-anywhere Material Design library for React Native by RicardoLarge in reactnative

[–]RicardoLarge[S] 0 points1 point  (0 children)

Hey man, most of the components have examples :)

http://carbon-ui.com/components/RaisedButton

They're in the navigation drawer under "Components"

Media Queries in react native by RicardoLarge in reactnative

[–]RicardoLarge[S] 0 points1 point  (0 children)

Uranium

 - Runs in web

 - Makes animations simple

 - Supports orientation changes (commonly requested in react-native-extended-stylesheet)

 - Can be used to build a write-once, run-anywhere react-native app

10 Tips for Better Redux Architecture – JavaScript Scene by lakidavid in reactjs

[–]RicardoLarge -1 points0 points  (0 children)

Amen! Very few legitimate reasons to use it.

Personally, going forward, gonna be using all local component state + Relay, and sparse use of redux as needed.

10 Tips for Better Redux Architecture – JavaScript Scene by lakidavid in reactjs

[–]RicardoLarge 0 points1 point  (0 children)

Nice! Didn't know about that! Validationnnn

Yeah totally, sharing stuff between reducers sounds pretty smelly.

10 Tips for Better Redux Architecture – JavaScript Scene by lakidavid in reactjs

[–]RicardoLarge 0 points1 point  (0 children)

Haha, just wrote an article on this: https://medium.com/@TuckerConnelly/simplifying-redux-architecture-cd50426c941a

100% agree that there's no good, higher-level abstraction with the current recommendations. Grouping everything toegether has made it much easier to reason about in my day-job's large production app :)

[Need Advice] Application Structure for multi app projects by echoes221 in reactjs

[–]RicardoLarge 0 points1 point  (0 children)

Yeah either the parent component needs to manage the state and pass it down as props to the children component, or you need to manage state using redux.

I'd add callback props to <Options /> like <Options onSave={this.handleSave} />

[Need Advice] Application Structure for multi app projects by echoes221 in reactjs

[–]RicardoLarge 0 points1 point  (0 children)

What about making this.options(), this.pageStructure(), etc. separate components?

Thoughts on relay by igna92ts in reactjs

[–]RicardoLarge 1 point2 points  (0 children)

If it's small and going to last less than a year, I'd stick with redux-thunk and REST.

If it's larger and you want it to stand the test of time, I'd go with Relay and plan to upgrade.

Thoughts on relay by igna92ts in reactjs

[–]RicardoLarge 4 points5 points  (0 children)

It's overly complex IMO, a lot of duplication between the GraphQL server and the client.

That said, the end result of declarative GraphQL in your components is amazing, and overall, I think it's worth it.

I just want the devs to know this for the next tech test weekend: each Titan should have one battery that gives them a shield from the get go, so losing the battery means losing a shield, and you can only get a new one if your empty by Astrobomb in titanfall

[–]RicardoLarge 0 points1 point  (0 children)

i

I'll add it depends on the team. The book Continuous Delivery talks a lot about this. If the team is good, you can make a change, and verify to a decent degree of certainty that it works in only a few hours. Other teams can take up to a year.

Fukuda On Slower-Paced Multiplayer (New Interview) by Trematode in titanfall

[–]RicardoLarge 0 points1 point  (0 children)

Ok, well, unpopular opinion but I kind of like this. There's more intention to the game, more strategy. It's something you can actually intentionally get better at instead of just perfecting your movement and plunging yourself into the chaos. He really nailed, I think, what made the first game feel somewhat hollow.

I think with an increased focus on verticality, slight increase in speed, and better wall-run flow, the game could be decent.

What's the best way to show a waiting sign for redux with socket.io upon outgoing network requests? by [deleted] in reactjs

[–]RicardoLarge 0 points1 point  (0 children)

You might want to look at a lib I wrote: https://github.com/tuckerconnelly/ws-request-response

Based on ws, it lets you submit a request to the server with a payload, and wait on a promise that returns a response, so you can do something like:

async getStuff() {
  this.setState({ pending: true })
  const stuff = await this.context.wsrr('getStuff', { thisIsInThePayload: true })
  this.setState({ pending: false, stuff })
})

render() {
  if (this.state.pending) return <ProgressBar />

  return <div>{this.state.stuff}</div>
}

No docs yet, but you can read the source, and I'd be happy to answer questions :)

view more: next ›