I spent some time really digging into the README to learn in the ins/outs of how everything works.
These changes are just some suggestions based on my experience going through the docs.
100% no pressure to use them, but thought they might be helpful.
Thanks for this awesome project!
I spent some time really digging into the README to learn in the ins/outs of how everything works.
These changes are just some suggestions based on my experience going through the docs.
100% no pressure to use them, but thought they might be helpful.
Hey @thewatts, thanks for your very extensive pull request. I'm sorry it's taken a while for someone to get back to you about it!
On a quick first read through, it seems like there are some helpful additions and amendments. I will try and find some time a bit later to give it a full review, as there are a lot of changes 😉
Hey @thewatts, thanks for your very extensive pull request. I'm sorry it's taken a while for someone to get back to you about it!
On a quick first read through, it seems like there are some helpful additions and amendments. I will try and find some time a bit later to give it a full review, as there are a lot of changes 😉
robinnorth
(Migrated from github.com)
left a comment
Copy link
Copy source
@thewatts, by and large all of these changes look great to merge! You've made some nice improvements here.
I've just made a few comments which are mostly concerned with readability and style which would be great to action, if you could.
We also need to see what @BehindTheMath has to say, as they are the most active maintainer of this library.
@thewatts, by and large all of these changes look great to merge! You've made some nice improvements here.
I've just made a few comments which are mostly concerned with readability and style which would be great to action, if you could.
We also need to see what @BehindTheMath has to say, as they are the most active maintainer of this library.
Something like '...to make users feel like they are browsing an app, especially for those with low bandwidth connections.' would read a bit better here, I think
Something like _'...to make users feel like they are browsing an app, especially for those with low bandwidth connections.'_ would read a bit better here, I think
@robinnorth instead of ...like any other page... here I reversed the language of the true example: ...without a full page reload....
Does that sound okay?
@robinnorth instead of `...like any other page...` here I reversed the language of the `true` example: `...without a full page reload...`.
Does that sound okay?
@BehindTheMath the original document had both - and * for bullets, so I just converted one to the other.
I have no preference on * over the other.
I can change them all to - if you'd prefer :)
@BehindTheMath the original document had both `-` and `*` for bullets, so I just converted one to the other.
I have no preference on `*` over the other.
I can change them all to `-` if you'd prefer :)
Certainly we should settle on either Title Case or Sentence case throughout, 'about' should be capitalised here if we keep title case.
I usually have a preference for sentence case, FWIW.
Certainly we should settle on either _Title Case_ or _Sentence case_ throughout, 'about' should be capitalised here if we keep title case.
I usually have a preference for sentence case, FWIW.
the original document had both - and * for bullets, so I just converted one to the other.
Ok, I didn't realize that.
I'm not sure which one is more intuitive.
@robinnorth ?
>the original document had both - and * for bullets, so I just converted one to the other.
Ok, I didn't realize that.
I'm not sure which one is more intuitive.
@robinnorth ?
I usually have a preference for sentence case, FWIW.
I do as well (unless it's a proper noun). There are a few places where that was changed.
Truthfully, here I was focusing more on the A.
>I usually have a preference for sentence case, FWIW.
I do as well (unless it's a proper noun). There are a few places where that was changed.
Truthfully, here I was focusing more on the `A`.
@BehindTheMath would you prefer it all to fall under a single bullet?
ex:
*`X-PJAX-Selectors`: A serialized JSON array of selectors, taken from `options.selectors`. You can use this to send back only the elements that Pjax will use to switch, instead of sending the whole page. Note that you'll need to deserialize this on the server (Such as by using `JSON.parse()`)
@BehindTheMath would you prefer it all to fall under a single bullet?
ex:
```md
* `X-PJAX-Selectors`: A serialized JSON array of selectors, taken from `options.selectors`. You can use this to send back only the elements that Pjax will use to switch, instead of sending the whole page. Note that you'll need to deserialize this on the server (Such as by using `JSON.parse()`)
```
Ah, I see. I think either is OK, it could also just be shortened to 'DOM ready state'. I leave it up to you.
Having re-read it in situ, it seems that it should be a level 2 heading so that it does not appear to be a sub-heading of the preceding HTTP headers section.
Ah, I see. I think either is OK, it could also just be shortened to _'DOM ready state'_. I leave it up to you.
Having re-read it in situ, it seems that it should be a level 2 heading so that it does not appear to be a sub-heading of the preceding _HTTP headers_ section.
You can move the paragraph to the next line, just don't use a bullet. Bullets are for lists, but here there's only 1.
* `X-PJAX-Selectors`
A serialized JSON array of selectors, taken from `options.selectors`.
You can use this to send back only the elements that Pjax will use to switch, instead of sending the whole page. Note that you'll need to deserialize this on the server (Such as by using `JSON.parse()`)
You can move the paragraph to the next line, just don't use a bullet. Bullets are for lists, but here there's only 1.
```
* `X-PJAX-Selectors`
A serialized JSON array of selectors, taken from `options.selectors`.
You can use this to send back only the elements that Pjax will use to switch, instead of sending the whole page. Note that you'll need to deserialize this on the server (Such as by using `JSON.parse()`)
```
There are a few more comments ([here](https://github.com/MoOx/pjax/pull/176/files#r219254546), [here](https://github.com/MoOx/pjax/pull/176/files#r219254759), [here](https://github.com/MoOx/pjax/pull/176/files#r219255132), and [here](https://github.com/MoOx/pjax/pull/176/files#r219255243)).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Thanks for this awesome project!
I spent some time really digging into the README to learn in the ins/outs of how everything works.
These changes are just some suggestions based on my experience going through the docs.
100% no pressure to use them, but thought they might be helpful.
Hey @thewatts, thanks for your very extensive pull request. I'm sorry it's taken a while for someone to get back to you about it!
On a quick first read through, it seems like there are some helpful additions and amendments. I will try and find some time a bit later to give it a full review, as there are a lot of changes 😉
@thewatts, by and large all of these changes look great to merge! You've made some nice improvements here.
I've just made a few comments which are mostly concerned with readability and style which would be great to action, if you could.
We also need to see what @BehindTheMath has to say, as they are the most active maintainer of this library.
Something like '...to make users feel like they are browsing an app, especially for those with low bandwidth connections.' would read a bit better here, I think
After testing against the latest build, it looks like this has crept up to 6kb
'Allows page transitions with CSS animations'
'non-HTML'
'non-HTML'
@@ -335,30 +395,29 @@ var pjax = new Pjax({}'Here is some CSS that works well with the above configuration:'
'...when positioning absolutely'
@@ -402,7 +463,7 @@ To give context to this CSS, here is an HTML snippet:<!doctype html>'...Pjax attempts...'
'...the browser cache'
'...like any other page...'
@@ -518,41 +573,32 @@ document.addEventListener('pjax:send', topbar.show)document.addEventListener('pjax:complete', topbar.hide)```'...(such as by using
JSON.parse()).'@@ -568,20 +614,16 @@ document.addEventListener("pjax:success", whenDOMReady)_Note: Don't create the Pjax instance in the `whenDOMReady` function._I'm not sure that this or the line below is useful, so I would be inclined to remove them.
'If you want to just update a specific part of the page (which is a good idea)...'
@@ -638,2 +678,3 @@// see http://help.disqus.com/customer/portal/articles/472107-using-disqus-on-ajax-sites// if disqus <script> is already loaded, we just reset disqus the right way// see https://help.disqus.com/developer/using-disqus-on-ajax-siteselse {Update URL to https://help.disqus.com/developer/using-disqus-on-ajax-sites
Hey @robinnorth - thanks for the feedback!
I'm going through your suggestions and will add another commit with the fixes :)
@@ -402,7 +463,7 @@ To give context to this CSS, here is an HTML snippet:<!doctype html>@robinnorth instead of
...like any other page...here I reversed the language of thetrueexample:...without a full page reload....Does that sound okay?
@robinnorth - feedback commit added :)
These all look good to me, thanks very much! 👍
@robinnorth Thank You for looking at everything, and for your work on this project. I'm very much enjoying working with it!
Is there a reason to change all the bulleted lists from
-to*? They're rendered the same anyway.Please remove the bullets from the second level.
@@ -313,18 +373,18 @@ var pjax = new Pjax({switchesOptions: {This change is incorrect. These classes are added to the old element that is being replaced, e.g. a fade out.
@BehindTheMath the original document had both
-and*for bullets, so I just converted one to the other.I have no preference on
*over the other.I can change them all to
-if you'd prefer :)@@ -313,18 +373,18 @@ var pjax = new Pjax({switchesOptions: {@BehindTheMath good catch! This is something I was confused on - I'll adjust!
@@ -313,18 +373,18 @@ var pjax = new Pjax({switchesOptions: {This change makes it less clear. These classes are added to the new element that is replacing the old one, e.g. a fade in.
@@ -402,7 +463,7 @@ To give context to this CSS, here is an HTML snippet:<!doctype html>Or ...will attempt....
@@ -518,41 +573,32 @@ document.addEventListener('pjax:send', topbar.show)document.addEventListener('pjax:complete', topbar.hide)Please remove the bullet from the 2nd level.
@@ -518,41 +573,32 @@ document.addEventListener('pjax:send', topbar.show)document.addEventListener('pjax:complete', topbar.hide)IMO the old way looked better.
@robinnorth ?
@@ -518,41 +573,32 @@ document.addEventListener('pjax:send', topbar.show)document.addEventListener('pjax:complete', topbar.hide)Certainly we should settle on either Title Case or Sentence case throughout, 'about' should be capitalised here if we keep title case.
I usually have a preference for sentence case, FWIW.
Ok, I didn't realize that.
I'm not sure which one is more intuitive.
@robinnorth ?
@@ -518,41 +573,32 @@ document.addEventListener('pjax:send', topbar.show)document.addEventListener('pjax:complete', topbar.hide)I do as well (unless it's a proper noun). There are a few places where that was changed.
Truthfully, here I was focusing more on the
A.@@ -518,41 +573,32 @@ document.addEventListener('pjax:send', topbar.show)document.addEventListener('pjax:complete', topbar.hide)@BehindTheMath would you prefer it all to fall under a single bullet?
ex:
@@ -518,41 +573,32 @@ document.addEventListener('pjax:send', topbar.show)document.addEventListener('pjax:complete', topbar.hide)Ah, I see. I think either is OK, it could also just be shortened to 'DOM ready state'. I leave it up to you.
Having re-read it in situ, it seems that it should be a level 2 heading so that it does not appear to be a sub-heading of the preceding HTTP headers section.
I normally use
-in Markdown lists, so that would be my preference.@@ -518,41 +573,32 @@ document.addEventListener('pjax:send', topbar.show)document.addEventListener('pjax:complete', topbar.hide)You can move the paragraph to the next line, just don't use a bullet. Bullets are for lists, but here there's only 1.
I changed the
*to be-Fixed!
@@ -313,18 +373,18 @@ var pjax = new Pjax({switchesOptions: {Fixed here - used your terminology provided in your feedback
@@ -313,18 +373,18 @@ var pjax = new Pjax({switchesOptions: {Same as above -
@@ -518,41 +573,32 @@ document.addEventListener('pjax:send', topbar.show)document.addEventListener('pjax:complete', topbar.hide)Fixed
@@ -518,41 +573,32 @@ document.addEventListener('pjax:send', topbar.show)document.addEventListener('pjax:complete', topbar.hide)Changed to
## Dom Ready Statei.e.should bee.g., and the same below.i.e.= in other words.e.g.= an example.@BehindTheMath will do!
@thewatts Thank you for making those changes.
There are a few remaining comments. Can you take a look at those?
@BehindTheMath fixed :)
@BehindTheMath - I've made those adjustments, and rebased the commit.
Let me know if there's anything else you need!
There are a few more comments (here, here, here, and here).
@BehindTheMath oh sorry I missed those! I never received email notifications of the additional requests.
Working on them right now -
@BehindTheMath all set!