On Tue, Jul 21, 2015 at 10:12 AM, Bill Farner wrote:
> >
> > One thing that did come up in the context of this discussion, however,
> was
> > the ability for Aurora to serve up a custom UI. There was a suggestion
> for
> > allowing Aurora operators to specify a custom UI path that would be
> serv
>
> One thing that did come up in the context of this discussion, however, was
> the ability for Aurora to serve up a custom UI. There was a suggestion for
> allowing Aurora operators to specify a custom UI path that would be served
> up, allowing users to swap in a non-default UI. I'm curious what
I don't really disagree with any of the points you raise, David, they were
all concerns I had going into the work, the only uncertainty was exactly
how big of a change going from Angular to React would turn out to be. The
primary reason why I ventured down this path to begin with is the looming
Ang
I actually checked into a React replacement for smart-table, and one does
exist: https://github.com/zippyui/react-datagrid.
On Thu, Jul 16, 2015 at 3:05 PM, Suman Karumuri <
skarum...@twitter.com.invalid> wrote:
> Thanks for building this Joshua!
>
> I am -1 on a proposal to switch FE technology
Thanks for building this Joshua!
I am -1 on a proposal to switch FE technology stacks for the same reasons
David mentioned.
Also, the current scheduler UI uses an angularJS library called smart table
for rendering tables, searching and sorting columns and pagination. Since
there is no react equiv
Thanks for doing this and sharing code!
I'd be -1 to any proposal to switch our FE technology stack for several
reasons.
I find this stack way too advanced for what the scheduler UI currently
does. This is also a problem with Angular, but we're already stuck with
that now.
I also don't think any
There are numerous large and stable sites powered by this technology. Not
least among them are Facebook and Instagram for which these technologies
were developed (that being React/Flux). ES6 being transpiled down to ES5 is
widely adopted as well (off the top of my head, I know Slack does it). ES6
i
I'm pretty ignorant of this space, please bear with me.
You'll notice that the app is written in ES6 and not ES5 (i.e. the
> javascript you're likely familiar with). As of React 0.13.x, ES6 with a
> transpiler (i.e. a tool to compile the ES6 syntax into vanilla ES5 syntax)
> is the preferred metho
For those who are not familiar with React, here's some more details/helpful
links on the underlying technologies.
1) You'll notice that the app is written in ES6 and not ES5 (i.e. the
javascript you're likely familiar with). As of React 0.13.x, ES6 with a
transpiler (i.e. a tool to compile the ES6
