Working on the admin interface: JS vs Mako

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Working on the admin interface: JS vs Mako

Peter van Heusden
Hi there

Zipho and I'd would like to make some changes to the admin pages, including the tool info page and the local data page. These are currently rendered from mako templates - should we change these or is the interface going to be rewritten in client side / javascript in the near(ish) future?

Thanks,
Peter

___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/
Reply | Threaded
Open this post in threaded view
|

Re: Working on the admin interface: JS vs Mako

John Chilton-4
Peter,

  We would like to replace all the mako with JS, if I was going to put
a bunch of effort into admin pages I'd start by reworking what was
there to use JavaScript and the API. That is me however, I have lots
of time to put into Galaxy fundamentals and refactoring. This is more
work and I am happy to field PRs that modify mako for the time
being.(https://github.com/galaxyproject/galaxy/pull/1632/files looks
great for instance).

  A middle ground between rewriting everything and still depending on
mako is to dump dictionaries to JavaScript in the mako and render
things in JS. This will make it easier to adapt your changes once the
pages are ultimately rewritten to JavaScript SPAs. In the case 1632 -
that DependencyResolversView class produces dictionaries that can be
dumped as JSON easily into the page and JavaScript could be used to
build up the tables in
templates/webapps/tool_shed/repository/common.mako.

-John


On Mon, Feb 1, 2016 at 11:51 AM, Peter van Heusden <[hidden email]> wrote:

> Hi there
>
> Zipho and I'd would like to make some changes to the admin pages, including
> the tool info page and the local data page. These are currently rendered
> from mako templates - should we change these or is the interface going to be
> rewritten in client side / javascript in the near(ish) future?
>
> Thanks,
> Peter
>
> ___________________________________________________________
> Please keep all replies on the list by using "reply all"
> in your mail client.  To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
>   https://lists.galaxyproject.org/
>
> To search Galaxy mailing lists use the unified search at:
>   http://galaxyproject.org/search/mailinglists/
___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/
Reply | Threaded
Open this post in threaded view
|

Re: Working on the admin interface: JS vs Mako

Peter van Heusden
Yeah I noticed that about the DependencyResolversView.

In terms of writing JS - where's a good example to look at? I tried digging around the client/ directories but couldn't make sense of how it works.

Thanks,
Peter

On 1 February 2016 at 16:48, John Chilton <[hidden email]> wrote:
Peter,

  We would like to replace all the mako with JS, if I was going to put
a bunch of effort into admin pages I'd start by reworking what was
there to use JavaScript and the API. That is me however, I have lots
of time to put into Galaxy fundamentals and refactoring. This is more
work and I am happy to field PRs that modify mako for the time
being.(https://github.com/galaxyproject/galaxy/pull/1632/files looks
great for instance).

  A middle ground between rewriting everything and still depending on
mako is to dump dictionaries to JavaScript in the mako and render
things in JS. This will make it easier to adapt your changes once the
pages are ultimately rewritten to JavaScript SPAs. In the case 1632 -
that DependencyResolversView class produces dictionaries that can be
dumped as JSON easily into the page and JavaScript could be used to
build up the tables in
templates/webapps/tool_shed/repository/common.mako.

-John


On Mon, Feb 1, 2016 at 11:51 AM, Peter van Heusden <[hidden email]> wrote:
> Hi there
>
> Zipho and I'd would like to make some changes to the admin pages, including
> the tool info page and the local data page. These are currently rendered
> from mako templates - should we change these or is the interface going to be
> rewritten in client side / javascript in the near(ish) future?
>
> Thanks,
> Peter
>
> ___________________________________________________________
> Please keep all replies on the list by using "reply all"
> in your mail client.  To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
>   https://lists.galaxyproject.org/
>
> To search Galaxy mailing lists use the unified search at:
>   http://galaxyproject.org/search/mailinglists/


___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/
Reply | Threaded
Open this post in threaded view
|

Re: Working on the admin interface: JS vs Mako

Ziphozakhe Mashologu
Hi All

In terms of the future, are we using or considering using any JS SPA frameworks or the route is plain JavaScript?

I ask as we aim to satisfy our pursued RESTful architecture.

Thanks 
Zipho







On Mon, Feb 1, 2016 at 7:30 PM, Peter van Heusden <[hidden email]> wrote:
Yeah I noticed that about the DependencyResolversView.

In terms of writing JS - where's a good example to look at? I tried digging around the client/ directories but couldn't make sense of how it works.

Thanks,
Peter

On 1 February 2016 at 16:48, John Chilton <[hidden email]> wrote:
Peter,

  We would like to replace all the mako with JS, if I was going to put
a bunch of effort into admin pages I'd start by reworking what was
there to use JavaScript and the API. That is me however, I have lots
of time to put into Galaxy fundamentals and refactoring. This is more
work and I am happy to field PRs that modify mako for the time
being.(https://github.com/galaxyproject/galaxy/pull/1632/files looks
great for instance).

  A middle ground between rewriting everything and still depending on
mako is to dump dictionaries to JavaScript in the mako and render
things in JS. This will make it easier to adapt your changes once the
pages are ultimately rewritten to JavaScript SPAs. In the case 1632 -
that DependencyResolversView class produces dictionaries that can be
dumped as JSON easily into the page and JavaScript could be used to
build up the tables in
templates/webapps/tool_shed/repository/common.mako.

-John


On Mon, Feb 1, 2016 at 11:51 AM, Peter van Heusden <[hidden email]> wrote:
> Hi there
>
> Zipho and I'd would like to make some changes to the admin pages, including
> the tool info page and the local data page. These are currently rendered
> from mako templates - should we change these or is the interface going to be
> rewritten in client side / javascript in the near(ish) future?
>
> Thanks,
> Peter
>
> ___________________________________________________________
> Please keep all replies on the list by using "reply all"
> in your mail client.  To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
>   https://lists.galaxyproject.org/
>
> To search Galaxy mailing lists use the unified search at:
>   http://galaxyproject.org/search/mailinglists/


___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/


___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/
Reply | Threaded
Open this post in threaded view
|

Re: Working on the admin interface: JS vs Mako

Martin Čech
Hi,

Galaxy is implementing frontend with the help of these libraries: https://github.com/galaxyproject/galaxy/tree/dev/client/galaxy/scripts/libs

Notably the MV-paradigm is being implemented in Backbone.

Good examples of applications/pieces that are written in JS are at https://github.com/galaxyproject/galaxy/tree/dev/client/galaxy/scripts/mvc

The easiest one to look into is probably the shortest one: `citation`. If you want to look into full backbone superpower check out `history`

Martin

On Mon, Feb 1, 2016 at 3:26 PM Ziphozakhe Mashologu <[hidden email]> wrote:
Hi All

In terms of the future, are we using or considering using any JS SPA frameworks or the route is plain JavaScript?

I ask as we aim to satisfy our pursued RESTful architecture.

Thanks 
Zipho







On Mon, Feb 1, 2016 at 7:30 PM, Peter van Heusden <[hidden email]> wrote:
Yeah I noticed that about the DependencyResolversView.

In terms of writing JS - where's a good example to look at? I tried digging around the client/ directories but couldn't make sense of how it works.

Thanks,
Peter

On 1 February 2016 at 16:48, John Chilton <[hidden email]> wrote:
Peter,

  We would like to replace all the mako with JS, if I was going to put
a bunch of effort into admin pages I'd start by reworking what was
there to use JavaScript and the API. That is me however, I have lots
of time to put into Galaxy fundamentals and refactoring. This is more
work and I am happy to field PRs that modify mako for the time
being.(https://github.com/galaxyproject/galaxy/pull/1632/files looks
great for instance).

  A middle ground between rewriting everything and still depending on
mako is to dump dictionaries to JavaScript in the mako and render
things in JS. This will make it easier to adapt your changes once the
pages are ultimately rewritten to JavaScript SPAs. In the case 1632 -
that DependencyResolversView class produces dictionaries that can be
dumped as JSON easily into the page and JavaScript could be used to
build up the tables in
templates/webapps/tool_shed/repository/common.mako.

-John


On Mon, Feb 1, 2016 at 11:51 AM, Peter van Heusden <[hidden email]> wrote:
> Hi there
>
> Zipho and I'd would like to make some changes to the admin pages, including
> the tool info page and the local data page. These are currently rendered
> from mako templates - should we change these or is the interface going to be
> rewritten in client side / javascript in the near(ish) future?
>
> Thanks,
> Peter
>
> ___________________________________________________________
> Please keep all replies on the list by using "reply all"
> in your mail client.  To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
>   https://lists.galaxyproject.org/
>
> To search Galaxy mailing lists use the unified search at:
>   http://galaxyproject.org/search/mailinglists/


___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/

___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/

___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/
Reply | Threaded
Open this post in threaded view
|

Re: Working on the admin interface: JS vs Mako

Ziphozakhe Mashologu
Super, thanks Martin. I will dive into these links soon and please excuse any obvious questions from me in the process.

Thanks,
Z

On Mon, Feb 1, 2016 at 10:36 PM, Martin Čech <[hidden email]> wrote:
Hi,

Galaxy is implementing frontend with the help of these libraries: https://github.com/galaxyproject/galaxy/tree/dev/client/galaxy/scripts/libs

Notably the MV-paradigm is being implemented in Backbone.

Good examples of applications/pieces that are written in JS are at https://github.com/galaxyproject/galaxy/tree/dev/client/galaxy/scripts/mvc

The easiest one to look into is probably the shortest one: `citation`. If you want to look into full backbone superpower check out `history`

Martin


On Mon, Feb 1, 2016 at 3:26 PM Ziphozakhe Mashologu <[hidden email]> wrote:
Hi All

In terms of the future, are we using or considering using any JS SPA frameworks or the route is plain JavaScript?

I ask as we aim to satisfy our pursued RESTful architecture.

Thanks 
Zipho







On Mon, Feb 1, 2016 at 7:30 PM, Peter van Heusden <[hidden email]> wrote:
Yeah I noticed that about the DependencyResolversView.

In terms of writing JS - where's a good example to look at? I tried digging around the client/ directories but couldn't make sense of how it works.

Thanks,
Peter

On 1 February 2016 at 16:48, John Chilton <[hidden email]> wrote:
Peter,

  We would like to replace all the mako with JS, if I was going to put
a bunch of effort into admin pages I'd start by reworking what was
there to use JavaScript and the API. That is me however, I have lots
of time to put into Galaxy fundamentals and refactoring. This is more
work and I am happy to field PRs that modify mako for the time
being.(https://github.com/galaxyproject/galaxy/pull/1632/files looks
great for instance).

  A middle ground between rewriting everything and still depending on
mako is to dump dictionaries to JavaScript in the mako and render
things in JS. This will make it easier to adapt your changes once the
pages are ultimately rewritten to JavaScript SPAs. In the case 1632 -
that DependencyResolversView class produces dictionaries that can be
dumped as JSON easily into the page and JavaScript could be used to
build up the tables in
templates/webapps/tool_shed/repository/common.mako.

-John


On Mon, Feb 1, 2016 at 11:51 AM, Peter van Heusden <[hidden email]> wrote:
> Hi there
>
> Zipho and I'd would like to make some changes to the admin pages, including
> the tool info page and the local data page. These are currently rendered
> from mako templates - should we change these or is the interface going to be
> rewritten in client side / javascript in the near(ish) future?
>
> Thanks,
> Peter
>
> ___________________________________________________________
> Please keep all replies on the list by using "reply all"
> in your mail client.  To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
>   https://lists.galaxyproject.org/
>
> To search Galaxy mailing lists use the unified search at:
>   http://galaxyproject.org/search/mailinglists/


___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/

___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/


___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/