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

[RFC] Improve platform-centered workflow #791

Closed
brody4hire opened this issue Feb 18, 2020 · 1 comment
Closed

[RFC] Improve platform-centered workflow #791

brody4hire opened this issue Feb 18, 2020 · 1 comment

Comments

@brody4hire
Copy link

coming from #769 (comment) (in response to my comment in #769 (review)):

It looks like there is a Python script (bin/cordova_plist_to_config_xml) that is needed to support platform centered workflow ([1]), and it would be possible to find a better way to do this. I think it would be ideal if we can find a better, more generic way to do this without need for Python which we know has caused instability between Python 2 and Python 3.

I would like to raise this issue as an enhancement to avoid losing track of something I think we should try to improve at some point (someday).

[1] https://cordova.apache.org/docs/en/latest/guide/platforms/ios/#platform-centered-workflow

@jcesarmobile
Copy link
Member

The comment says:

IMO, I think we do not have a lot of resources to focus on the Platform-Center workflow. I think it may have been discussed to consolidate our focus only on the CLI workflow and potentially dropping Platform-Center workflow.

So it says the opposite as you are proposing, he said we should drop the platform-centered workflow and focus only on the CLI, not improve it.

And I think it makes sense since the Platform-Center workflow has been broken on cordova-android from version 4 (~6 years as far as I remember). And even if you are able to make it work on your own, you can't install plugins because it was also broken on the CLI and/or plugman.

Our docs don't work for iOS neither, there are some docs from phonegap team that can be used, but to install the plugins they have to be published as CocoaPods libraries, which they are not.

So it's not just the tooling, to make it work again it would require an immense amount of work on platforms and plugins too.

So, it's it worth fixing something that has been broken for years and would need a ton of work to be usable? or is it better to just drop it?

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

No branches or pull requests

2 participants