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

WIP: Add webview, tidy up & simplify the plugin source code, #94 #162

Closed
wants to merge 22 commits into from

Conversation

olilarkin
Copy link
Contributor

Hey Steve,

I started this branch to show @d3NNEb how to add a webview properly to the iPlug2 project, however when doing so I realised the NAM plug-in source code has ballooned and become very unwieldy. There are things that can be done much more cleanly in iPlug2.

Unfortunately I don't have time to make very atomic PRs to fix all the problems, but I wondered if you would consider a PR like this, trusting me, without being arrogant, that I know what I am doing :-). I don't have the time to go through lots of Q&A on the PR, but I absolutely know how to make the code for the plug-in part of the project much cleaner and better, and easier for others to contribute to. If I can do this I will feel much happier about fixing the various bits of iPlug2 that are coming up as issues with the rapidly expanding NAM community!

Oli

@mikeoliphant
Copy link
Contributor

@olilarkin - regarding this commit: 63763be - are the project files generated in some way, or is this done manually?

@olilarkin
Copy link
Contributor Author

Unfortunately, at the moment, it's manual, but we have seen cmake support on a branch which I hope to merge soon

@mikeoliphant
Copy link
Contributor

Cmake support would be great - right now it requires dev intervention on each platform to add/remove/rename plugin code files.

@sdatkinson
Copy link
Owner

sdatkinson commented Apr 3, 2023

Just checking in since this is a draft. Is it close to ready?

Otherwise I may proceed to merge a few of the other PRs. But I'll hang onto them for a bit if this is coming soon & we can avoid some potential merge conflicts (I'm happy to deal w/ them on mine instead)

@olilarkin
Copy link
Contributor Author

please proceed, i need to redo this PR anyway.

@sdatkinson
Copy link
Owner

Thanks for letting me know.

I may steal some pieces anyways like the formatting :)

@sdatkinson sdatkinson mentioned this pull request Apr 9, 2023
@olilarkin olilarkin closed this May 1, 2023
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

Successfully merging this pull request may close these issues.

3 participants