GWTproject site menu

[Manuel Carrasco Moñino]

Hi all

I was thinking on modify a couple of things in the menu structure:

- Remove useless 'Latest' branch inside 'Documentation'

- Move 'Tutorial' inside 'Documentation' to the top menu and sort each step.

- Make some groups inside 'Documentation': 'Coding Basics' 'Html5' 'I18n' 'Testing' 'UI' 'FAQ' and 'Ref' so as Documentation section is easier to navigate.

WDYT?

- Manolo

[Jens]

Sounds reasonable :)

-- J.

[Daniel Kurka]

If you move stuff around you will need to make sure that links (also external) won't break. (we still get a lot of traffic from external links)

But I think working on the navigation menu of the page is quite overdue.

-Daniel

On Mon, Apr 7, 2014 at 4:53 PM, Jens <jens.ne...@gmail.com> wrote:

Sounds reasonable :)

-- J.

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Google Germany GmbH

Dienerstr. 12
80331 München

Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Graham Law, Katherine Stephens

[Julien Dramaix]

Hi Manolo,

It's something I wanted to do for a while. Let's organize a conf call to talk about that.

Julien

[Manuel Carrasco Moñino]

Hi all,

Julien and me have created a document with some plans about the gwtproject.org site.

Please, feel free to add any comment you have.

[Manuel Carrasco Moñino]

Sorry forgot the link to the document :-(

https://docs.google.com/document/d/1LJm-xDAK23uASwK59JUAnAeaNjPH5dF9N4LWdgSI9Ik/edit

- Manolo

[Manuel Carrasco Moñino]

Hello,

I have committed some patches, and deployed a demo version  so as you guys can test the new menu distribution.

What I've done based on Thomas suggestion is to maintain a toc file instead of moving or renaming pages.

Apart from the menu distribution, the demo includes some navigation fixes, small css changes, and the ability to adapt to mobile screens when the window is narrowed.

Once this distribution is reviewed I want to focus on updating some contents, especially outdated pages.

Feel free to give feedback.

- Manolo

[1] https://gwt-review.googlesource.com/#/c/7180/

[2] http://gwtproject.gquery.org

[3] https://gwt-review.googlesource.com/#/c/7180/17/src/main/resources/toc.md

[Goktug Gokdogan]

Looks better; thanks for the work.

Some suggestions:

 - Removes the versions submenu from Downloads as it is already included as a link from Downloads page.

 - Move GWT surveys under resources

 - Perhaps we can group Making GWT Better, Life of an Issue, Steering Committee under a submenu

 - Release Notes -> drop it from menu? its already linked from Downloads page.

 - In Documentation menu:

    - We need to re-order stuff for people who are reading documentation in a sequential manner.

      e.g. Communicate with a server should probably earlier, maybe in basics?

   - We may want Organize Projects and Compile/Debug to be part of coding basics.

   - Drop IE9 specific page from menu

   - Perhaps group RequestFactory, Act.&Places, Validation, Access., I18N etc. in "Advanced Topics"

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAv_-4R_uR-G40yKbPgV4PpGxLcctXZ%3DR__K%3DuFcoqe8vA%40mail.gmail.com.

[Jamie Nelson]

Looks really slick.

My only suggestion is that we turn the animations down to a quarter second or less.

They look good on big menus, but for single items, it feels needlessly slow when the animation takes any amount of time.

This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use, or distribution of the information included in this message is prohibited -- please immediately and permanently delete this message.

[Jens]

I noticed that it is not possible anymore to close a menu category by clicking on the menu item text again. You can now only close a category by using the triangle icon.

-- J.

[Manuel Carrasco Moñino]

I will deploy a new demo with these changes tomorrow.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA14_Mp_cDP4qF%3DofY%2BrZOVx5RpHH%2B%3DToR0_9di5FiFiNw%40mail.gmail.com.

[Manuel Carrasco Moñino]

On Thu, May 8, 2014 at 5:07 PM, Jamie Nelson <james....@appian.com> wrote:

Looks really slick.

My only suggestion is that we turn the animations down to a quarter second or less.

It is set to 300ms, I will change it to 200 when deploy the demo again.

 

They look good on big menus, but for single items, it feels needlessly slow when the animation takes any amount of time.

This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use, or distribution of the information included in this message is prohibited -- please immediately and permanently delete this message.

--

You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/c69adbb1-4ca7-4771-b005-97a31d0f78fa%40googlegroups.com.

[Manuel Carrasco Moñino]

On Thu, May 8, 2014 at 6:19 PM, Jens <jens.ne...@gmail.com> wrote:

I noticed that it is not possible anymore to close a menu category by clicking on the menu item text again. You can now only close a category by using the triangle icon.

-- J.

--

You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/2f99fddc-668c-449a-8e98-2abf26d8a3bd%40googlegroups.com.

[Manuel Carrasco Moñino]

That's intentional, it is the same behavior than tree menus in google wikis and GWT trees.

Now the parent item link is only clickable when it has a page associated (it was not possible in the last version), so the click is handled to load that page.

On Thu, May 8, 2014 at 6:19 PM, Jens <jens.ne...@gmail.com> wrote:

I noticed that it is not possible anymore to close a menu category by clicking on the menu item text again. You can now only close a category by using the triangle icon.

-- J.

--

You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/2f99fddc-668c-449a-8e98-2abf26d8a3bd%40googlegroups.com.

[Brian Slesinsky]

If you click "Tutorial" and then "Documentation" the animation is a bit unfortunate. Because the previous menu closes at the same time that the new one opens, the new menu expands both up and down so that your cursor ends up pointing to the middle of the new menu, and then you have to wait until it stops moving to figure out where to move the mouse next. In the old UI, the menu item you just clicked on never moves.

But I'm not sure what to do about it. Maybe skip animating closing a menu when it's not the one you clicked on?

Also, it's not in the demo, but we should make sure sourcemap debugging works with the new version. I sometimes include a link to gwtproject.org in browser bug reports since I don't know any other public websites that have GWT with sourcemaps on. Unfortunately this is going to break any specific directions I put into the bug reports, but hopefully something equivalent should work.

- Brian

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAsxeDCVrEHLrMm4icr%2BY-OVh89RBqfDdnbBUi_qyudZaA%40mail.gmail.com.

[Ray Cromwell]

While not part of this CL, the bottom footer being in the center of the page on some short pages looks ugly. The footer should always be at least at the bottom, or offscreen.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2B%2BRBT8z5gtVUbMpkmtLdoykvYv%2BrGgYDT79agjLBG0VzC1X_Q%40mail.gmail.com.

[Manuel Carrasco Moñino]

@Goktug I have deployed a new demo with the changes in the menu you suggested. http://gwtproject.gquery.org/v2/

@Jamie In this version I've set 200ms for animations

@Brian, the fact of collapsing unrelated branches is intentional in order to focus on the active branch. You can open branches clicking on the arrow, but once you click on a subject, that branch is selected. I've been playing a long with the menu and see this behaviour much more usable since I don't have click on other branches for closing them. Anyway I have deployed another version in http://gwtproject.gquery.org/v3/ with the feature of collapse-unrelated-branches disabled so as other people can give an opinion.

In this demo sourcemaps are disabled, but in gwtproject they should be enabled

@Ray, I think that what you say is something called 'sticky footer' which means that the footer is at the bottom unless the content is large enough. I have fixed the css in both demos.

Julien and me want to deploy this version at the beginning of next week.

Please check it in desktop and mobile and let us know if you have any suggestion.

Thanks

- Manolo

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAPVRV7dU9o9uPZiHN14Y8p0E1ZHzjy5PLkw2xhQYqZOmht4Ztg%40mail.gmail.com.

[Goktug Gokdogan]

Pretty cool. Thanks for all the work. Also special kudos for fixing the styling for download page, it is much more elegant now!

Footer:

 - We are now missing the extra space in the bottom of the pages (the one before the footer)

 - The area for the footer is larger and the text is closer to the bottom - I think the original spacing was better. Also if you take a look at the overview page you will see the footer hides part of the image.

Others:

 - Clicking images shows blank page - perhaps just a deployment issue

 - There is a broken "Advanced Topics" menu item - I think it is mixed up with the Logging menu item.

 - I would put "Optimize" to Advanced topics. Perhaps security and i18n as well.

 - Perhaps move Community -> Developer Spotlight under Resources?

 - In Resources, we can move gwt surveys to the end of the list

 

Below are other issues that doesn't look like regressions. Perhaps we can have some other quick wins before publishing the final version?

Menu:

 - Ideally the arrows shouldn't indent the menu items and instead menu items should be aligned by text (e.g. gmail). I'm not sure if you are reusing any widgets here; if you aren't reusing we might want to change that.

- We might want to change how menus behave. I actually like GWT Developer pages (e.g. https://developers.google.com/appengine/pricing) where menu items that are parents of the other menu items are not used as links to a content, instead they serve as a placeholder and collapses/expands based when clicked. Also it won't auto collapse existing items. I think all together that is more useable.

General:

 - We have smaller size font for links (probably regular text font is larger than it suppose to be).

 - Looks like you made the body wider which I think is good but making the whole page right aligned (i.e. all extra space goes to left) is not a good idea. It looks really bad in widescreen (which many developers has). We should probably follow a different approach for distributing the space (e.g. add the extra space to left until a max value is reached).

 - All code samples lost formatting and even some lost line wrapping after site migration.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtj_OptEfr%3D7At5KW1YdgxyVyqjppMR26vASC0-dSoPsQ%40mail.gmail.com.

[Manuel Carrasco Moñino]

On Sat, May 10, 2014 at 2:33 AM, 'Goktug Gokdogan' via GWT Contributors <google-web-tool...@googlegroups.com> wrote:

Pretty cool. Thanks for all the work. Also special kudos for fixing the styling for download page, it is much more elegant now!

Footer:

 - We are now missing the extra space in the bottom of the pages (the one before the footer)

 

done 

 - The area for the footer is larger and the text is closer to the bottom - I think the original spacing was better. Also if you take a look at the overview page you will see the footer hides part of the image.

fixed css

 

Others:

 - Clicking images shows blank page - perhaps just a deployment issue

Don't see this issue, what images do you mean?

 

 - There is a broken "Advanced Topics" menu item - I think it is mixed up with the Logging menu item.

Fixed, the logging item was indented wrong

 

 - I would put "Optimize" to Advanced topics. Perhaps security and i18n as well.

Done, I think i18n could be out. But anyway is difficult to put the edge about what are or not advanced topics

 

 - Perhaps move Community -> Developer Spotlight under Resources?

done 

 - In Resources, we can move gwt surveys to the end of the list

done 

 

Below are other issues that doesn't look like regressions. Perhaps we can have some other quick wins before publishing the final version?

Menu:

 - Ideally the arrows shouldn't indent the menu items and instead menu items should be aligned by text (e.g. gmail). I'm not sure if you are reusing any widgets here; if you aren't reusing we might want to change that.

done. We dont use any widget, just html+css. gquery enhances the list adding handlers using selectors.

 

- We might want to change how menus behave. I actually like GWT Developer pages (e.g. https://developers.google.com/appengine/pricing) where menu items that are parents of the other menu items are not used as links to a content, instead they serve as a placeholder and collapses/expands based when clicked. Also it won't auto collapse existing items. I think all together that is more useable.

I have changed parents with not content (href = #)  to expand/collapse menu (See 'Advance topics' in docs).

Having parent-items with content makes the menu shorter and easy to use, like 'side bars' in google code wikis https://code.google.com/p/support/wiki/WikiSyntax#Side_navigation

I'd rather auto-collapse on, but I have set it off as you prefer.

 

General:

 - We have smaller size font for links (probably regular text font is larger than it suppose to be).

Fixed

 

 - Looks like you made the body wider which I think is good but making the whole page right aligned (i.e. all extra space goes to left) is not a good idea. It looks really bad in widescreen (which many developers has). We should probably follow a different approach for distributing the space (e.g. add the extra space to left until a max value is reached).

I dont know if I understand correctly. The width is adjusted based on media sizes, and I have set 3 sizes: wide desktop, small desktop & tablets and mobile. Also I have changed the font size (16 -> 14px) so as there is more text in the same place, and text alignment (left -> justify).

I have adjusted content padding for big desktop, I see correctly the pages, let me know if that works for you.

 

 - All code samples lost formatting and even some lost line wrapping after site migration.

Code styling has not changed for code blocks, I see these pages (current site, demo site) in the same way, maybe there is some other page wrong or some style interfering

http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsClient.html

http://gwtproject.gquery.org/v2/doc/latest/DevGuideCodingBasicsClient.html

Can you check if you see them in the same way? or send me a link or screenshot of the page which works wrong?

You can test new changes at http://gwtproject.gquery.org

- Manolo

 

[Goktug Gokdogan]

On Sat, May 10, 2014 at 8:02 AM, Manuel Carrasco Moñino <man...@apache.org> wrote:

On Sat, May 10, 2014 at 2:33 AM, 'Goktug Gokdogan' via GWT Contributors <google-web-tool...@googlegroups.com> wrote:

Pretty cool. Thanks for all the work. Also special kudos for fixing the styling for download page, it is much more elegant now!

Footer:

 - We are now missing the extra space in the bottom of the pages (the one before the footer)

 

done 

 - The area for the footer is larger and the text is closer to the bottom - I think the original spacing was better. Also if you take a look at the overview page you will see the footer hides part of the image.

fixed css

 

Others:

 - Clicking images shows blank page - perhaps just a deployment issue

Don't see this issue, what images do you mean?

 

Click devmode screenshot in http://gwtproject.gquery.org/gettingstarted.html

 

 - There is a broken "Advanced Topics" menu item - I think it is mixed up with the Logging menu item.

Fixed, the logging item was indented wrong

 

 - I would put "Optimize" to Advanced topics. Perhaps security and i18n as well.

Done, I think i18n could be out. But anyway is difficult to put the edge about what are or not advanced topics

 

 - Perhaps move Community -> Developer Spotlight under Resources?

done 

 - In Resources, we can move gwt surveys to the end of the list

done 

 

Below are other issues that doesn't look like regressions. Perhaps we can have some other quick wins before publishing the final version?

Menu:

 - Ideally the arrows shouldn't indent the menu items and instead menu items should be aligned by text (e.g. gmail). I'm not sure if you are reusing any widgets here; if you aren't reusing we might want to change that.

done. We dont use any widget, just html+css. gquery enhances the list adding handlers using selectors.

 

- We might want to change how menus behave. I actually like GWT Developer pages (e.g. https://developers.google.com/appengine/pricing) where menu items that are parents of the other menu items are not used as links to a content, instead they serve as a placeholder and collapses/expands based when clicked. Also it won't auto collapse existing items. I think all together that is more useable.

I have changed parents with not content (href = #)  to expand/collapse menu (See 'Advance topics' in docs).

Having parent-items with content makes the menu shorter and easy to use, like 'side bars' in google code wikis https://code.google.com/p/support/wiki/WikiSyntax#Side_navigation

I'd rather auto-collapse on, but I have set it off as you prefer.

 

Even if you look at the menu in that wiki page, you will see that parent menu items are not acting as links to their own content instead they are just placeholders for grouping and  will collapse/expand on click. I think that is the most intuitive and what we should do in the long run, however that might require some work to move the content to child pages.

Nevertheless I think the last version is problematic:

 - Having menu item sometimes collapse sometimes not collapse when clicked is not user friendly as they will behave inconsistently.

 - As it is difficult and not easy to discover how to collapse a menu with content after it is expanded, it can become annoying for users to not have auto-collapse enabled on navigation.

So I think we should either keep the old behavior (i.e. auto-collapse) or move the new behavior (no content association for ALL parent menus, expand and collapse on click,  NO auto-collapse).
Again the second option is ideal from my point of view but we may want to do it later for reducing the amount work.

 

General:

 - We have smaller size font for links (probably regular text font is larger than it suppose to be).

Fixed

 

 - Looks like you made the body wider which I think is good but making the whole page right aligned (i.e. all extra space goes to left) is not a good idea. It looks really bad in widescreen (which many developers has). We should probably follow a different approach for distributing the space (e.g. add the extra space to left until a max value is reached).

I dont know if I understand correctly. The width is adjusted based on media sizes, and I have set 3 sizes: wide desktop, small desktop & tablets and mobile. Also I have changed the font size (16 -> 14px) so as there is more text in the same place, and text alignment (left -> justify).

I have adjusted content padding for big desktop, I see correctly the pages, let me know if that works for you.

LGTM. It looks like it distributes the spacing evenly for left and right sight. I would use less padding before the leftnav but this is mostly ok.

I'm not sure if this is a new problem or not but now when you switch through menu items, left nav sometimes jumps around. It looks this is related to scrollbar being shown on the right or not. Perhaps you can use the scrollbar only for the content bar to prevent that from happening.

 

 

 - All code samples lost formatting and even some lost line wrapping after site migration.

Code styling has not changed for code blocks, I see these pages (current site, demo site) in the same way, maybe there is some other page wrong or some style interfering

http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsClient.html

http://gwtproject.gquery.org/v2/doc/latest/DevGuideCodingBasicsClient.html

Can you check if you see them in the same way? or send me a link or screenshot of the page which works wrong?

I know this is not a regression - as I noted earlier, all of my comments on the second part are already existing problems. The code examples was broken when we moved to gwtproject.org.

 - We don't have syntax highlighting for example code (you can see that in the pages that you have linked)

 - Content is not formatted at all in some sample codes (see http://gwtproject.gquery.org/doc/latest/tutorial/JUnit.html#write) - I guess I only saw a few of them.

We can defer all these stuff, just pointed in case if they are easy to fix.

 

You can test new changes at http://gwtproject.gquery.org

- Manolo

 

--

You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAsipeC_DX-bjA9hstM%2B03QBkd6x6SeztgwOtPswX7xdkw%40mail.gmail.com.

[Julien Dramaix]

>>> Others:
>>>  - Clicking images shows blank page - perhaps just a deployment issue
>>
>>
>> Don't see this issue, what images do you mean?
>>  
>
> Click devmode screenshot in http://gwtproject.gquery.org/gettingstarted.html
 

This issue already exists in the production website. I created a bug to track it and I propose to fix it later in another patch : https://code.google.com/p/google-web-toolkit/issues/detail?id=8707

> So I think we should either keep the old behavior (i.e. auto-collapse) or move the new behavior (no content association for ALL parent menus, expand and collapse on click,  NO auto-collapse).
> Again the second option is ideal from my point of view but we may want to do it later for reducing the amount work.

I'm more in favor of the second option also.

> I know this is not a regression - as I noted earlier, all of my comments on the second part are already existing problems. The code examples was broken when we moved to gwtproject.org.

> - We don't have syntax highlighting for example code (you can see that in the pages that you have linked)

> - Content is not formatted at all in some sample codes (see http://gwtproject.gquery.org/doc/latest/tutorial/JUnit.html#write) - I guess I only saw a few of them.

> We can defer all these stuff, just pointed in case if they are easy to fix.

Indeed we should defer these stuff. During the gwt-meetup, I would like to propose and discuss of a possible revamp of the website. During this revamp, we could fixe all these problems.

I propose that Manolo (thanks again for the good job) fixes the behavior of the menu according to the Goktug second option and then merge his patches in order that we can deploy this version in production. This version improves a lot the existing web site and I would like to add a search box (using google custom search) asap.

Julien

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA3qEr%2BQ_DziyHmUASTDk7%3Da4oE%3D02W0cphWYLAVB%3DDjVA%40mail.gmail.com.

[Goktug Gokdogan]

SGTM

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D70o8oK3Yw0EYrW4Z2f0BTaxALi5ffnefH4aYh2wQ9vMQ%40mail.gmail.com.

[Manuel Carrasco Moñino]

All your suggestions are done and committed to gerrit.

Demo instance has been updated with those changes: http://gwtproject.gquery.org 

- Manolo

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA3_QC2iaMhGRA-ROZg8VKrsbhB16-K%3DzjBZnh8oO6hjwg%40mail.gmail.com.

[Julien Dramaix]

Thanks for the good job Manolo ! The mobile version of the site is really better now.

I've deployed the new version in production : http://www.gwtproject.org/ 

Julien

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuvyFEX%3Du59JJd_6w_Cus8iSjmmcaTmu17NGheqWDF1VA%40mail.gmail.com.

[Manuel Carrasco Moñino]

Hi Julien, it seems sourcemap has not been uploaded, Brian uses them.

- Manolo

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D5_1_2BwMP54HP47cK-Jg%2BpKaWXfiZ7UWDV2GMgxV0XFg%40mail.gmail.com.

[Goktug Gokdogan]

Great job! Everything looks/behaves flawlessly. Much appreciated!

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAuvyFEX%3Du59JJd_6w_Cus8iSjmmcaTmu17NGheqWDF1VA%40mail.gmail.com.

[Julien Dramaix]

I'll do that tomorrow morning

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAstGsLf_hqji2tN4XvqK6WTHeksKJdizL2gmyrHTGXvEg%40mail.gmail.com.

[Julien Dramaix]

> Hi Julien, it seems sourcemap has not been uploaded, Brian uses them.

It should be ok now.

Julien

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAstGsLf_hqji2tN4XvqK6WTHeksKJdizL2gmyrHTGXvEg%40mail.gmail.com.