You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kylin.apache.org by jason zhong <he...@gmail.com> on 2015/01/14 16:37:04 UTC

refactor data model in kylin front end

Currently all data model info are defined in controller in angularjs.data
and presentation mixed together.

It's ok for small app.but for kylin,It's not a good idea. with application
grows,we need to refactor the code by seprating the data model from
controller. in angularjs ,service is a good feature to make this happen.
The controller in angularjs will manage the presentation.and data model
managed in service.
so I propose to refactor the code

here's a blog explain more clearly. FYI

http://joelhooks.com/blog/2013/04/24/modeling-data-and-state-in-your-angularjs-application/#

Re: refactor data model in kylin front end

Posted by jason zhong <he...@gmail.com>.

I created a ticket for this ,working on this

 https://issues.apache.org/jira/browse/KYLIN-532

On Thu, Jan 15, 2015 at 6:35 PM, Li Yang <li...@apache.org> wrote:

> Can we have a JIRA for this task?
>
> On Thu, Jan 15, 2015 at 9:17 PM, Luke Han <lu...@apache.org> wrote:
>
> > Thanks Jason, this refactor is very important for front-end to adapt to
> > next generation of metadata.
> >
> > Looking forward for the first version:)
> >
> > Regards.
> > Luke
> >
> > 2015-01-14 23:37 GMT+08:00 jason zhong <he...@gmail.com>:
> >
> > > Currently all data model info are defined in controller in
> angularjs.data
> > > and presentation mixed together.
> > >
> > > It's ok for small app.but for kylin,It's not a good idea. with
> > application
> > > grows,we need to refactor the code by seprating the data model from
> > > controller. in angularjs ,service is a good feature to make this
> happen.
> > > The controller in angularjs will manage the presentation.and data model
> > > managed in service.
> > > so I propose to refactor the code
> > >
> > > here's a blog explain more clearly. FYI
> > >
> > >
> > >
> >
> http://joelhooks.com/blog/2013/04/24/modeling-data-and-state-in-your-angularjs-application/#
> > >
> >
>

Re: refactor data model in kylin front end

Posted by Li Yang <li...@apache.org>.

Can we have a JIRA for this task?

On Thu, Jan 15, 2015 at 9:17 PM, Luke Han <lu...@apache.org> wrote:

> Thanks Jason, this refactor is very important for front-end to adapt to
> next generation of metadata.
>
> Looking forward for the first version:)
>
> Regards.
> Luke
>
> 2015-01-14 23:37 GMT+08:00 jason zhong <he...@gmail.com>:
>
> > Currently all data model info are defined in controller in angularjs.data
> > and presentation mixed together.
> >
> > It's ok for small app.but for kylin,It's not a good idea. with
> application
> > grows,we need to refactor the code by seprating the data model from
> > controller. in angularjs ,service is a good feature to make this happen.
> > The controller in angularjs will manage the presentation.and data model
> > managed in service.
> > so I propose to refactor the code
> >
> > here's a blog explain more clearly. FYI
> >
> >
> >
> http://joelhooks.com/blog/2013/04/24/modeling-data-and-state-in-your-angularjs-application/#
> >
>

Re: refactor data model in kylin front end

Posted by Luke Han <lu...@apache.org>.

Thanks Jason, this refactor is very important for front-end to adapt to
next generation of metadata.

Looking forward for the first version:)

Regards.
Luke

2015-01-14 23:37 GMT+08:00 jason zhong <he...@gmail.com>:

> Currently all data model info are defined in controller in angularjs.data
> and presentation mixed together.
>
> It's ok for small app.but for kylin,It's not a good idea. with application
> grows,we need to refactor the code by seprating the data model from
> controller. in angularjs ,service is a good feature to make this happen.
> The controller in angularjs will manage the presentation.and data model
> managed in service.
> so I propose to refactor the code
>
> here's a blog explain more clearly. FYI
>
>
> http://joelhooks.com/blog/2013/04/24/modeling-data-and-state-in-your-angularjs-application/#
>