Big refactor

[chiquitinxx]

I have created branch 'events' where I'm changing a lot of things.

1. The project will be multiproject. A project with the plugin, a test application to test the plugin and a new library grails-core, to do the same grooscript stuff with the grails and gradle plugin.
2. Remove the needed of execute the grails scripts to work with remote domain classes and components. The gradle plugin will do that job.
3. Increase tests and stability with the test application.
4. Improve the events in the client side, to allow listen to any application event. Using the grails events system.
5. Remove the needed of add grooscript js libs, will be added by grooscript tags.
6. I think can be good time to move to grails 3.2. Also be a good friend of grails websockets plugin.
7. Remove jquery dependency of all tags.

Any suggestion / comment?

[chiquitinxx]

Merged to master, in progress

[ulrichenslin]

Hi Jorge

2 things that will be useful going forward, would be:

1. Source maps - let error reporting point to the line of grooscript code
   that caused it.
2. Hot reloading - I am not sure if this is the right term, but the use
   case is : Reload the javascript layer in the browser, when the developer
   update grooscript code. This prevents pressing refresh all the time during
   development.

These are quite ambitious features, but would be useful to put it on the
roadmap for the future.

All the best
Ulrich

mobile : +27794274270

http://twitter.com/#!/i3flow
http://www.linkedin.com/pub/ulrich-enslin/9/882/85b

On 14 June 2016 at 23:47, Jorge Franco notifications@github.com wrote:

I have created branch 'events' where I'm changing a lot of things.

1. The project will be multiproject. A project with the plugin, a test
   application to test the plugin and a new library grails-core, to do the
   same grooscript stuff with the grails and gradle plugin.
2. Remove the needed of execute the grails scripts to work with remote
   domain classes and components. The gradle plugin will do that job.
3. Increase tests and stability with the test application.
4. Improve the events in the client side, to allow listen to any
   application event. Using the grails events system.
5. Remove the needed of add grooscript js libs, will be added by
   grooscript tags.
6. I think can be good time to move to grails 3.2. Also be a good
   friend of grails websockets plugin.
7. Remove jquery dependency of all tags.

Any suggestion / comment?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#9, or mute
the thread
https://github.com/notifications/unsubscribe/AFsVvQ2kAMzqQ0JN174ugpX7XPcdf-S2ks5qLyGBgaJpZM4I1y9a
.

[chiquitinxx]

Sure, I have created chiquitinxx/grooscript#56 improvement in grooscript project, to support source maps.

About the hot reloading, do you think about hot reloading in a grails application?

[ulrichenslin]

Hi Jorge

I was thinking in terms of the javascript in browser reloading using
something like:
https://webpack.github.io/docs/hot-module-replacement-with-webpack.html

This allows developers to save the file, it is recompiled a pushed to the
browser in (almost) realtime. When developing single page apps using
Angular or React, this is very useful to not have to reload the whole page
every time.

All the best
Ulrich

mobile : +27794274270

http://twitter.com/#!/i3flow
http://www.linkedin.com/pub/ulrich-enslin/9/882/85b

On 4 July 2016 at 10:36, Jorge Franco notifications@github.com wrote:

Sure, I have created chiquitinxx/grooscript#56
chiquitinxx/grooscript#56 improvement in
grooscript project, to support source maps.

About the hot reloading, do you think about hot reloading in a grails
application?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#9 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AFsVvQRoAmTuaoS85GOkmTa9gMw6K_ouks5qSMYNgaJpZM4I1y9a
.