Little refresh for web pages of Grails 3.1.0

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Little refresh for web pages of Grails 3.1.0

Sandro Martini
Hi all,
for new Grails 3.1.0 (or a later 3.1.x), what do you think on a little update of default web pages (generally speaking) ?

For example I'm thinking at something like this:
- update colors to those of new Grails web site, and maybe even larger fonts
- update Grails logo with the new logo (from Grails web site) ? Maybe the svg version ?
- update header and footer to spread all page width, with responsive content
- add another minimal css for smartphone, and maybe another for print
- in header, add a sample navigation toolbar with Grails logo inside (optional), and with links to Home and maybe other already-published resources
- use better HTML5 tags like header, nav, footer
- put content inside section HTML5 tag, as a sample ... one for status div, another for controllers, etc
- remove inline styles
- move "Skip to content…" in a div
- move some (important) parts from "Application Status" in footer, maybe publishing them only in  DEV environment
- etc ...

All this for sure in the Home Page of a generated webapp (and related layout).
Maybe (if wanted) even in template pages (but of course this has to be tested a lot). All without using other libraries (css / js).

I now there are many changes, but relatively simple, only some time (and a lot of tests) are needed ...
If wanted I can prototype something (starting from a preview of static files) and add to a new issue, to better track it.

Tell me what you think.

Thanks a lot,
Sandro

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/deab1f8c-27e6-4803-9fd2-4abb44a287e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Little refresh for web pages of Grails 3.1.0

Graeme Rocher-2
Sounds great, pull requests / contributions would be greatly appreciated


On 02 Dec 2015, at 18:21, Sandro Martini <[hidden email]> wrote:

Hi all,
for new Grails 3.1.0 (or a later 3.1.x), what do you think on a little update of default web pages (generally speaking) ?

For example I'm thinking at something like this:
- update colors to those of new Grails web site, and maybe even larger fonts
- update Grails logo with the new logo (from Grails web site) ? Maybe the svg version ?
- update header and footer to spread all page width, with responsive content
- add another minimal css for smartphone, and maybe another for print
- in header, add a sample navigation toolbar with Grails logo inside (optional), and with links to Home and maybe other already-published resources
- use better HTML5 tags like header, nav, footer
- put content inside section HTML5 tag, as a sample ... one for status div, another for controllers, etc
- remove inline styles
- move "Skip to content…" in a div
- move some (important) parts from "Application Status" in footer, maybe publishing them only in  DEV environment
- etc ...

All this for sure in the Home Page of a generated webapp (and related layout).
Maybe (if wanted) even in template pages (but of course this has to be tested a lot). All without using other libraries (css / js).

I now there are many changes, but relatively simple, only some time (and a lot of tests) are needed ...
If wanted I can prototype something (starting from a preview of static files) and add to a new issue, to better track it.

Tell me what you think.

Thanks a lot,
Sandro

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/deab1f8c-27e6-4803-9fd2-4abb44a287e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/FBBA7FA8-5B48-4269-8FCB-93CE483DE470%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Little refresh for web pages of Grails 3.1.0

Sandro Martini

Ok, in a few days I'll create an issue and put (if possible) a zip with my tests on a sample Grails Home page static html file, or better a link to some collaborative tool so before making the pull request we all agree that the proposal looks good ... still I'm not fully satisfied for the result of my work in progress, and some feedback would be really useful.

Thanks for now, it's amazing to contribute to a great framework like Grails, even for my small contributions :-) .

Let's update.

Bye

Il 03/Dic/2015 22:53, "Graeme Rocher" <[hidden email]> ha scritto:
Sounds great, pull requests / contributions would be greatly appreciated


On 02 Dec 2015, at 18:21, Sandro Martini <[hidden email]> wrote:

Hi all,
for new Grails 3.1.0 (or a later 3.1.x), what do you think on a little update of default web pages (generally speaking) ?

For example I'm thinking at something like this:
- update colors to those of new Grails web site, and maybe even larger fonts
- update Grails logo with the new logo (from Grails web site) ? Maybe the svg version ?
- update header and footer to spread all page width, with responsive content
- add another minimal css for smartphone, and maybe another for print
- in header, add a sample navigation toolbar with Grails logo inside (optional), and with links to Home and maybe other already-published resources
- use better HTML5 tags like header, nav, footer
- put content inside section HTML5 tag, as a sample ... one for status div, another for controllers, etc
- remove inline styles
- move "Skip to content…" in a div
- move some (important) parts from "Application Status" in footer, maybe publishing them only in  DEV environment
- etc ...

All this for sure in the Home Page of a generated webapp (and related layout).
Maybe (if wanted) even in template pages (but of course this has to be tested a lot). All without using other libraries (css / js).

I now there are many changes, but relatively simple, only some time (and a lot of tests) are needed ...
If wanted I can prototype something (starting from a preview of static files) and add to a new issue, to better track it.

Tell me what you think.

Thanks a lot,
Sandro

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/deab1f8c-27e6-4803-9fd2-4abb44a287e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/grails-dev-discuss/c0It6caDQ5E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/FBBA7FA8-5B48-4269-8FCB-93CE483DE470%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAH4gT7rKijCWyWEK5YTw5SyzjzwKt%3DngcE6YsXBWh4u0WkFj6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Little refresh for web pages of Grails 3.1.0

Ronny Løvtangen

Great news!

It would be great to have the CSS more in line with principles from OOCSS/SMACSS. One problem with the current implementation is that the styling of scaffolded pages is too bound to the default sitemesh layout. It should ideally be self contained so that it can be used with custom layouts. Even better would be if the scaffolding related CSS could be moved to the scaffolding plugin. Same goes for the other scaffolding related assets, like e.g. database_edit.png.
The current main.css has some general styling of table elements, this should be moved to using class. I guess this is CSS related to scaffolding, so something like .scaffold-xxx {…}

What about breaking main.css into smaller chunks? One for scaffolding related CSS is obvious. And maybe one for default sitemesh layout related CSS. Not sure how much is left then, maybe the rest goes into a third file or maybe grouped even more if necessary. These files could the be included by main.css using asset-pipeline. Would make it a lot easier for users to keep some parts and leave out others.

Best Regards,

Ronny Løvtangen


On 03 Dec 2015, at 17:31, Sandro Martini <[hidden email]> wrote:

Ok, in a few days I'll create an issue and put (if possible) a zip with my tests on a sample Grails Home page static html file, or better a link to some collaborative tool so before making the pull request we all agree that the proposal looks good ... still I'm not fully satisfied for the result of my work in progress, and some feedback would be really useful.

Thanks for now, it's amazing to contribute to a great framework like Grails, even for my small contributions :-) .

Let's update.

Bye

Il 03/Dic/2015 22:53, "Graeme Rocher" <[hidden email]> ha scritto:
Sounds great, pull requests / contributions would be greatly appreciated


On 02 Dec 2015, at 18:21, Sandro Martini <[hidden email]> wrote:

Hi all,
for new Grails 3.1.0 (or a later 3.1.x), what do you think on a little update of default web pages (generally speaking) ?

For example I'm thinking at something like this:
- update colors to those of new Grails web site, and maybe even larger fonts
- update Grails logo with the new logo (from Grails web site) ? Maybe the svg version ?
- update header and footer to spread all page width, with responsive content
- add another minimal css for smartphone, and maybe another for print
- in header, add a sample navigation toolbar with Grails logo inside (optional), and with links to Home and maybe other already-published resources
- use better HTML5 tags like header, nav, footer
- put content inside section HTML5 tag, as a sample ... one for status div, another for controllers, etc
- remove inline styles
- move "Skip to content…" in a div
- move some (important) parts from "Application Status" in footer, maybe publishing them only in  DEV environment
- etc ...

All this for sure in the Home Page of a generated webapp (and related layout).
Maybe (if wanted) even in template pages (but of course this has to be tested a lot). All without using other libraries (css / js).

I now there are many changes, but relatively simple, only some time (and a lot of tests) are needed ...
If wanted I can prototype something (starting from a preview of static files) and add to a new issue, to better track it.

Tell me what you think.

Thanks a lot,
Sandro


-- 
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/deab1f8c-27e6-4803-9fd2-4abb44a287e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to a topic in the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/grails-dev-discuss/c0It6caDQ5E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/FBBA7FA8-5B48-4269-8FCB-93CE483DE470%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAH4gT7rKijCWyWEK5YTw5SyzjzwKt%3DngcE6YsXBWh4u0WkFj6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/863C32C9-51A0-403A-8D17-B104F5B9338B%40lovtangen.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Little refresh for web pages of Grails 3.1.0

Sandro Martini

Hi Ronny,
thanks for all suggestions :-) .
I fear that we don't have so much time before 3.1.0 final, so probably we should do this in different steps (to try to improve scaffold results without break something :-) ); moving some parts in scaffold plugin should be great even to provide updates in a simpler way.

Tomorrow I'll open the issue and add a link to this discussion and to some online HTML code sharing because before push changes we should agree on results on static pages (and generally speaking this requires many iterations and tests).

Let's update.
Thanks for now.

Bye,
Sandro

Il 06/Dic/2015 03:31, "Ronny Løvtangen" <[hidden email]> ha scritto:

Great news!

It would be great to have the CSS more in line with principles from OOCSS/SMACSS. One problem with the current implementation is that the styling of scaffolded pages is too bound to the default sitemesh layout. It should ideally be self contained so that it can be used with custom layouts. Even better would be if the scaffolding related CSS could be moved to the scaffolding plugin. Same goes for the other scaffolding related assets, like e.g. database_edit.png.
The current main.css has some general styling of table elements, this should be moved to using class. I guess this is CSS related to scaffolding, so something like .scaffold-xxx {…}

What about breaking main.css into smaller chunks? One for scaffolding related CSS is obvious. And maybe one for default sitemesh layout related CSS. Not sure how much is left then, maybe the rest goes into a third file or maybe grouped even more if necessary. These files could the be included by main.css using asset-pipeline. Would make it a lot easier for users to keep some parts and leave out others.

Best Regards,

Ronny Løvtangen


On 03 Dec 2015, at 17:31, Sandro Martini <[hidden email]> wrote:

Ok, in a few days I'll create an issue and put (if possible) a zip with my tests on a sample Grails Home page static html file, or better a link to some collaborative tool so before making the pull request we all agree that the proposal looks good ... still I'm not fully satisfied for the result of my work in progress, and some feedback would be really useful.

Thanks for now, it's amazing to contribute to a great framework like Grails, even for my small contributions :-) .

Let's update.

Bye

Il 03/Dic/2015 22:53, "Graeme Rocher" <[hidden email]> ha scritto:
Sounds great, pull requests / contributions would be greatly appreciated


On 02 Dec 2015, at 18:21, Sandro Martini <[hidden email]> wrote:

Hi all,
for new Grails 3.1.0 (or a later 3.1.x), what do you think on a little update of default web pages (generally speaking) ?

For example I'm thinking at something like this:
- update colors to those of new Grails web site, and maybe even larger fonts
- update Grails logo with the new logo (from Grails web site) ? Maybe the svg version ?
- update header and footer to spread all page width, with responsive content
- add another minimal css for smartphone, and maybe another for print
- in header, add a sample navigation toolbar with Grails logo inside (optional), and with links to Home and maybe other already-published resources
- use better HTML5 tags like header, nav, footer
- put content inside section HTML5 tag, as a sample ... one for status div, another for controllers, etc
- remove inline styles
- move "Skip to content…" in a div
- move some (important) parts from "Application Status" in footer, maybe publishing them only in  DEV environment
- etc ...

All this for sure in the Home Page of a generated webapp (and related layout).
Maybe (if wanted) even in template pages (but of course this has to be tested a lot). All without using other libraries (css / js).

I now there are many changes, but relatively simple, only some time (and a lot of tests) are needed ...
If wanted I can prototype something (starting from a preview of static files) and add to a new issue, to better track it.

Tell me what you think.

Thanks a lot,
Sandro


-- 
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/deab1f8c-27e6-4803-9fd2-4abb44a287e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to a topic in the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/grails-dev-discuss/c0It6caDQ5E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/FBBA7FA8-5B48-4269-8FCB-93CE483DE470%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAH4gT7rKijCWyWEK5YTw5SyzjzwKt%3DngcE6YsXBWh4u0WkFj6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/grails-dev-discuss/c0It6caDQ5E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/863C32C9-51A0-403A-8D17-B104F5B9338B%40lovtangen.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAH4gT7rBN9W3gPPzrvignV6dXdAVGSRNZ%3DE6ODDSoOttBaMkcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Little refresh for web pages of Grails 3.1.0

Graeme Rocher-2

We go GA at the end of January so whatever you can come up with will need to he done by then. Thanks!

On 06 Dec 2015, at 09:16, Sandro Martini <[hidden email]> wrote:

Hi Ronny,
thanks for all suggestions :-) .
I fear that we don't have so much time before 3.1.0 final, so probably we should do this in different steps (to try to improve scaffold results without break something :-) ); moving some parts in scaffold plugin should be great even to provide updates in a simpler way.

Tomorrow I'll open the issue and add a link to this discussion and to some online HTML code sharing because before push changes we should agree on results on static pages (and generally speaking this requires many iterations and tests).

Let's update.
Thanks for now.

Bye,
Sandro

Il 06/Dic/2015 03:31, "Ronny Løvtangen" <[hidden email]> ha scritto:

Great news!

It would be great to have the CSS more in line with principles from OOCSS/SMACSS. One problem with the current implementation is that the styling of scaffolded pages is too bound to the default sitemesh layout. It should ideally be self contained so that it can be used with custom layouts. Even better would be if the scaffolding related CSS could be moved to the scaffolding plugin. Same goes for the other scaffolding related assets, like e.g. database_edit.png.
The current main.css has some general styling of table elements, this should be moved to using class. I guess this is CSS related to scaffolding, so something like .scaffold-xxx {…}

What about breaking main.css into smaller chunks? One for scaffolding related CSS is obvious. And maybe one for default sitemesh layout related CSS. Not sure how much is left then, maybe the rest goes into a third file or maybe grouped even more if necessary. These files could the be included by main.css using asset-pipeline. Would make it a lot easier for users to keep some parts and leave out others.

Best Regards,

Ronny Løvtangen


On 03 Dec 2015, at 17:31, Sandro Martini <[hidden email]> wrote:

Ok, in a few days I'll create an issue and put (if possible) a zip with my tests on a sample Grails Home page static html file, or better a link to some collaborative tool so before making the pull request we all agree that the proposal looks good ... still I'm not fully satisfied for the result of my work in progress, and some feedback would be really useful.

Thanks for now, it's amazing to contribute to a great framework like Grails, even for my small contributions :-) .

Let's update.

Bye

Il 03/Dic/2015 22:53, "Graeme Rocher" <[hidden email]> ha scritto:
Sounds great, pull requests / contributions would be greatly appreciated


On 02 Dec 2015, at 18:21, Sandro Martini <[hidden email]> wrote:

Hi all,
for new Grails 3.1.0 (or a later 3.1.x), what do you think on a little update of default web pages (generally speaking) ?

For example I'm thinking at something like this:
- update colors to those of new Grails web site, and maybe even larger fonts
- update Grails logo with the new logo (from Grails web site) ? Maybe the svg version ?
- update header and footer to spread all page width, with responsive content
- add another minimal css for smartphone, and maybe another for print
- in header, add a sample navigation toolbar with Grails logo inside (optional), and with links to Home and maybe other already-published resources
- use better HTML5 tags like header, nav, footer
- put content inside section HTML5 tag, as a sample ... one for status div, another for controllers, etc
- remove inline styles
- move "Skip to content…" in a div
- move some (important) parts from "Application Status" in footer, maybe publishing them only in  DEV environment
- etc ...

All this for sure in the Home Page of a generated webapp (and related layout).
Maybe (if wanted) even in template pages (but of course this has to be tested a lot). All without using other libraries (css / js).

I now there are many changes, but relatively simple, only some time (and a lot of tests) are needed ...
If wanted I can prototype something (starting from a preview of static files) and add to a new issue, to better track it.

Tell me what you think.

Thanks a lot,
Sandro


-- 
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/deab1f8c-27e6-4803-9fd2-4abb44a287e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to a topic in the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/grails-dev-discuss/c0It6caDQ5E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/FBBA7FA8-5B48-4269-8FCB-93CE483DE470%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAH4gT7rKijCWyWEK5YTw5SyzjzwKt%3DngcE6YsXBWh4u0WkFj6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/grails-dev-discuss/c0It6caDQ5E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/863C32C9-51A0-403A-8D17-B104F5B9338B%40lovtangen.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAH4gT7rBN9W3gPPzrvignV6dXdAVGSRNZ%3DE6ODDSoOttBaMkcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/A8A1A791-0CC5-4046-865C-89692F633F65%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Little refresh for web pages of Grails 3.1.0

Sandro Martini
Hi all,

We go GA at the end of January so whatever you can come up with will need to he done by then. Thanks!
ok, good to know :-) ... I don't think we'll be able to do all the stuff for 3.1.0, but probably something good yes :-) .

I just created the issue, it's: https://github.com/grails/grails-core/issues/9467

General info:
please if possible keep discussions here (in mailing list/forum) and put in the issue only things related to implementation/fixes.

Thanks to all.

Bye,
Sandro

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/127a5466-0752-4a6d-887f-116b113b5303%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Little refresh for web pages of Grails 3.1.0

Owen Rubel
In reply to this post by Sandro Martini
This would definitely create a more general purpose view: one that can work for centralized and distributed architectures. That way if you build centralized and then later want to move the view to something like Node and angular, this makes for a far easier transition.

On Wednesday, December 2, 2015 at 9:21:46 AM UTC-8, Sandro Martini wrote:
Hi all,
for new Grails 3.1.0 (or a later 3.1.x), what do you think on a little update of default web pages (generally speaking) ?

For example I'm thinking at something like this:
- update colors to those of new Grails web site, and maybe even larger fonts
- update Grails logo with the new logo (from Grails web site) ? Maybe the svg version ?
- update header and footer to spread all page width, with responsive content
- add another minimal css for smartphone, and maybe another for print
- in header, add a sample navigation toolbar with Grails logo inside (optional), and with links to Home and maybe other already-published resources
- use better HTML5 tags like header, nav, footer
- put content inside section HTML5 tag, as a sample ... one for status div, another for controllers, etc
- remove inline styles
- move "Skip to content…" in a div
- move some (important) parts from "Application Status" in footer, maybe publishing them only in  DEV environment
- etc ...

All this for sure in the Home Page of a generated webapp (and related layout).
Maybe (if wanted) even in template pages (but of course this has to be tested a lot). All without using other libraries (css / js).

I now there are many changes, but relatively simple, only some time (and a lot of tests) are needed ...
If wanted I can prototype something (starting from a preview of static files) and add to a new issue, to better track it.

Tell me what you think.

Thanks a lot,
Sandro

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/d2511572-3efd-4e91-8e11-77b40091f169%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Little refresh for web pages of Grails 3.1.0

Ronny Løvtangen
In reply to this post by Sandro Martini
Hi,

Just to get a grasp at what the different parts of the current main.css is, I tried to split things up into different files. Looks like almost everything is related to scaffolding.
Here’s what I did:

- Created a new Grails 3.1.0.M3 project
- Created a simple domain object and generated scaffolded views (/foo).
- Added a dynamic scaffolded view (foo2) and a simple almost empty page (/bar).
- Kept main.css, but created a similar main_modularized.css split up into smaller files.
- Changed application.css to require main_modularized instead of main.

The reason I kept main.css as is, is that it is then easy to switch back and forth between main.css and main_modularized.css and see that the page looks exactly the same (as order of some css styles has changed slightly).

First take ended up like this:

grails-app/assets/stylesheets/
├── application.css
├── errors.css
├── lib
│   ├── message-error.css
│   ├── page-layout.css
│   ├── scaffold-action.css
│   ├── scaffold-create-edit.css
│   ├── scaffold-list.css
│   ├── scaffold-navigate.css
│   ├── scaffold-paginate.css
│   └── scaffold.css
├── main.css
├── main_modularized.css
└── mobile.css


- message-error.css includes styles for error messages and success messages. Used both by scaffolded pages and on the general error page.
- page-layout.css includes styles related to the header, footer, site background, width and placement of main content area etc.
- scaffold.css just includes the other scaffold sub files.
- scaffold-action.css is the bottom button row on scaffolded pages (Edit, Delete, Create)
- scaffold-create-edit.css is the body of scaffolded create, edit and show pages
- scaffold-list.css is the body of scaffolded list (/index) page
- scaffold-navigate.css is the top button row on scaffolded pages (Foo List, New Foo)
- scaffold-paginate.css is the pagination links on scaffolded pages


In main_modularized.css there are a few styles left, related to general styling of elements like h1, links etc.

What I think is most problematic with the current css is the styling of table elements in scaffold-list.css, as they are intrusive to all other use of tables on a site that includes this css, not just scaffolded views. To have these styles scoped to a css class would be a good improvement IMO. This is also the case in scaffold-create-edit.css where elements like label, input, select, textarea etc are styled. The scaffolded related styles should not influence anything other than the scaffolded pages.


Run with ./gradlew bootRun

Best Regards,
Ronny




On 07 Dec 2015, at 23:56, Sandro Martini <[hidden email]> wrote:

Hi all,

We go GA at the end of January so whatever you can come up with will need to he done by then. Thanks!
ok, good to know :-) ... I don't think we'll be able to do all the stuff for 3.1.0, but probably something good yes :-) .

I just created the issue, it's: https://github.com/grails/grails-core/issues/9467

General info:
please if possible keep discussions here (in mailing list/forum) and put in the issue only things related to implementation/fixes.

Thanks to all.

Bye,
Sandro


--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/127a5466-0752-4a6d-887f-116b113b5303%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/F80783B7-98E1-4B1A-ADD1-D06719DE02BA%40lovtangen.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Little refresh for web pages of Grails 3.1.0

Sandro Martini
Hi Ronny,
thank you very much for the prototype, during next days I'll try to better align with your proposal (looks very interesting and useful to me) ... to have it implemented right we need to test a lot of combinations, so let's start :-) ...

Just a note, having all css splitted, we should be able to get all different bundles (for example from an AngularJS client) knowing the URL where that bundle is published, right ?
Sorry, because this is something that I don't find explained very well in documentation (could be my fault), as should be (at least for a simpler way to get published bundles URLs) ... for example for consuming them by static clients like single page AngularJS applications (hosted inside the Grails webapp, or maybe external).

I'll tell you something next week.
Thank you again for now.

Bye,
Sandro


Il giorno mercoledì 9 dicembre 2015 23:39:16 UTC+1, Ronny Løvtangen ha scritto:
Hi,

Just to get a grasp at what the different parts of the current main.css is, I tried to split things up into different files. Looks like almost everything is related to scaffolding.
Here’s what I did:

- Created a new Grails 3.1.0.M3 project
- Created a simple domain object and generated scaffolded views (/foo).
- Added a dynamic scaffolded view (foo2) and a simple almost empty page (/bar).
- Kept main.css, but created a similar main_modularized.css split up into smaller files.
- Changed application.css to require main_modularized instead of main.

The reason I kept main.css as is, is that it is then easy to switch back and forth between main.css and main_modularized.css and see that the page looks exactly the same (as order of some css styles has changed slightly).

I put it up on GitHub here: <a href="https://github.com/rlovtangen/profilerefresh/blob/master/grails-app/assets/stylesheets/main_modularized.css" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Frlovtangen%2Fprofilerefresh%2Fblob%2Fmaster%2Fgrails-app%2Fassets%2Fstylesheets%2Fmain_modularized.css\46sa\75D\46sntz\0751\46usg\75AFQjCNH4F_HKUOsxvx8AAUd5-v1ZMFiIXg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Frlovtangen%2Fprofilerefresh%2Fblob%2Fmaster%2Fgrails-app%2Fassets%2Fstylesheets%2Fmain_modularized.css\46sa\75D\46sntz\0751\46usg\75AFQjCNH4F_HKUOsxvx8AAUd5-v1ZMFiIXg&#39;;return true;">https://github.com/rlovtangen/profilerefresh/blob/master/grails-app/assets/stylesheets/main_modularized.css
First take ended up like this:

grails-app/assets/stylesheets/
├── application.css
├── errors.css
├── lib
│   ├── message-error.css
│   ├── page-layout.css
│   ├── scaffold-action.css
│   ├── scaffold-create-edit.css
│   ├── scaffold-list.css
│   ├── scaffold-navigate.css
│   ├── scaffold-paginate.css
│   └── scaffold.css
├── main.css
├── main_modularized.css
└── mobile.css


- message-error.css includes styles for error messages and success messages. Used both by scaffolded pages and on the general error page.
- page-layout.css includes styles related to the header, footer, site background, width and placement of main content area etc.
- scaffold.css just includes the other scaffold sub files.
- scaffold-action.css is the bottom button row on scaffolded pages (Edit, Delete, Create)
- scaffold-create-edit.css is the body of scaffolded create, edit and show pages
- scaffold-list.css is the body of scaffolded list (/index) page
- scaffold-navigate.css is the top button row on scaffolded pages (Foo List, New Foo)
- scaffold-paginate.css is the pagination links on scaffolded pages


In main_modularized.css there are a few styles left, related to general styling of elements like h1, links etc.

What I think is most problematic with the current css is the styling of table elements in scaffold-list.css, as they are intrusive to all other use of tables on a site that includes this css, not just scaffolded views. To have these styles scoped to a css class would be a good improvement IMO. This is also the case in scaffold-create-edit.css where elements like label, input, select, textarea etc are styled. The scaffolded related styles should not influence anything other than the scaffolded pages.


Run with ./gradlew bootRun

Best Regards,
Ronny




On 07 Dec 2015, at 23:56, Sandro Martini <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="hBfpayP3BAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">sandro....@...> wrote:

Hi all,

We go GA at the end of January so whatever you can come up with will need to he done by then. Thanks!
ok, good to know :-) ... I don't think we'll be able to do all the stuff for 3.1.0, but probably something good yes :-) .

I just created the issue, it's: <a href="https://github.com/grails/grails-core/issues/9467" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails%2Fgrails-core%2Fissues%2F9467\46sa\75D\46sntz\0751\46usg\75AFQjCNEGS80vYNWfKrHcqbbiG2uXPLkPLw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails%2Fgrails-core%2Fissues%2F9467\46sa\75D\46sntz\0751\46usg\75AFQjCNEGS80vYNWfKrHcqbbiG2uXPLkPLw&#39;;return true;">https://github.com/grails/grails-core/issues/9467

General info:
please if possible keep discussions here (in mailing list/forum) and put in the issue only things related to implementation/fixes.

Thanks to all.

Bye,
Sandro


--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="hBfpayP3BAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-dev-discuss+unsubscribe@....
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="hBfpayP3BAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">grails-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/127a5466-0752-4a6d-887f-116b113b5303%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/127a5466-0752-4a6d-887f-116b113b5303%40googlegroups.com?utm_medium\75email\46utm_source\75footer&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/grails-dev-discuss/127a5466-0752-4a6d-887f-116b113b5303%40googlegroups.com?utm_medium\75email\46utm_source\75footer&#39;;return true;">https://groups.google.com/d/msgid/grails-dev-discuss/127a5466-0752-4a6d-887f-116b113b5303%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/4cf5db61-b65d-46bc-a15e-c5c912f76163%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Loading...