Skip to content
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

Difference between SWRevealViewController & PBRevealViewController, and migration path #86

Open
BootMaker opened this issue Oct 16, 2020 · 8 comments

Comments

@BootMaker
Copy link

Even it's not actually an issue but a problem with which all developer have to face later or sooner who use SWRVC as me, that even SWRVC is a fantastic solution, it is several years old and without support.

Finding a viable alternative PBRVC could be a good candidate, so my questions:

  1. What are the main differences between the base features of the the solutions.
  2. What are the new additional features which PB delivers vs SW.
  3. What is difference in the usage and installation of the two alternatives.
  4. What is difference in usage with storyboard and using it programmatically?.
  5. How could migrate from SW to PB without the too much pain, what are the steps you could offer.

One thing is evident from the code and the support that your solution is very professional and especially useful the Obj-C and swift alternatives, so I am eager to switch but I'd like to check the cost before I start to migrate to PBRevealViewController on my all apps.

Thanks for your help in advance...

@iDevelopper
Copy link
Owner

iDevelopper commented Oct 16, 2020

PBRevealViewController is very similar to SWRevealViewController.

Indeed, at the time, I had developed this framework to replace SWRevealViewController in my applications.

The main difference is that PBRevealViewController allows the left and right views to be presented above the main view (this was a much requested feature). But you can still present these views below, like with SWRevealViewController.

The identifiers of the setting segues are pb_main, pb_left and pb_right instead of sw_front, sw_rear and sw_right.

You can leave panGestureRecognized and tapGestureRecognizer provided by the PBRevealViewController as they are for the default behavior, cancel the gestures recognizer behavior using the delegate functions revealControllerPanGestureShouldBegin and / or revealControllerTapGestureShouldBegin.

In general, even in the name of functions, front, and rear are replaced by main and left.

You use it with storyboard or programmatically in the same way you do with SWRevealViewController.

Can you provide a link to one of your applications so I can have a look?

@BootMaker
Copy link
Author

Thank you very much your fast replay.
I am working on the update of the apps and I am just before publishing them I will contact you as they updated in the store.
Thanks again...

@BootMaker
Copy link
Author

As I promised, the name of the app in which I used the SWRevealViewController is 101Positions. It has a free version so you can check the UI.
Actually it's a coordination controller setup, the frontviewcontroller is the coordination controller and deliver the menu for the app, and as I see your version is even more appropriate for this setup. If you are interested in more details we can discuss by email.
I just start to build a new app so I start with your PBRevealViewController, let see how I can progress.
Thanks again for your work...

@iDevelopper
Copy link
Owner

I can't find an app named 101Positions in the Apple Store.

@BootMaker
Copy link
Author

BootMaker commented Nov 28, 2020 via email

@BootMaker
Copy link
Author

BootMaker commented Dec 3, 2020 via email

@iDevelopper
Copy link
Owner

Yes, I found it. The user interface is very nice!

@BootMaker
Copy link
Author

BootMaker commented Dec 4, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants