-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improvements #28
Improvements #28
Conversation
it's possible when placement="center" fixed way tour-step is added into document - instead adding tourstep after element, it's added directly into body. This way we won't have an issue with parent styling affecting our step popover fixed way position is calculated
default step should be -1 instead of previous 0
and it can be really random one added way to debug JS unit tests > npm run-script test-debug
fixing mess with offsets on demo page
on-show and on-proceed
methods, test structure improved
some refactoring of the *show* function improvement for virtual steps is additional option, which help determine target scope which will be used to evaluate onShow or onProgress callbacks it's affecting only virtual steps, as in normal case everytime it's the same scope this improvement can be disabled for whole application (by new option in tourConfig) or individually by use-source-scope="true" attribute on selected virtual tour steps
added throwing exception when target element does not exist
This is really nice. I did notice, however, that there is one behavior change - it is now necessary to set the step of the tour to initiate it (say in the Controller). Whereas with the previous version, they would automatically start. |
Yeah, you are right. I had to change it as in our application tour is not starting by default (which in my opinion is better - before showing some popups we are asking user if he would like to see the tour). It's much better to set up active step number by hand than hiding it just after starting tour. |
I agree - and my implementation is actually doing a check with the backend service to see whether the user is showing the tour, so it’s conditional as well. But the default behavior of the parent project was to show by default, so I was confused when using this fork.
|
+1 for merging this. |
fixed code snippets in README updated template code snippet to the improved version
Great stuff, +1 for merging |
+1 for merging, this would solve the problems I've been having integrating this module into a complex app |
Looks very promising. I'll review this and see about merging it after the holidays |
Good stuff. Any update on merging? Thanks. |
Please merge this! |
Any word on when this will be merged? |
default values were not read by the component bumped version
@DaftMonk - did this PR get lost in the shuffle? |
@DaftMonk - added support for being able to parent tourtips against a something other than body. would love to see this PR merged! |
Looks great! +1 |
+1 |
1 similar comment
+1 |
…sition of tips + improved tip scrolling
fix(scrolling): account for container scroll offsets when updating position of tips + improved tip scrolling
…th custom container
fix(scrolling): fix miscalculation when determining scroll offsets with custom container
Merging this! |
Nice! |
Yay! :) |
I've been using angular-tour in a big Angular application and I had to make necessary adjustments, extensions and improvements to the original code to make integration successful. There are no breaking changes, and after my changes apps using original angular-tour should work as before. With those changes angular-tourtip works like a charm in a ~40 controller app. Even having simultaneous tours is possible without any hustle.
Changes:
tourComplete
- which run only when user fully completed touron-show
,on-proceed
tourtips
are now appended to thebody
, not to the target's element container. It's important, because this waytourtip
is more consistent and it's styling doesn't depend on the element it was attached to.backdrop
optioncenter
andcenter-top
- when using them tourtip will be placed visually in the center of target element. It's good for a welcometourtip
on the page.Cheers,