Re: [DISCUSS] Thoughts on Cordova Electron Roadmap
My vote is to go for a single release bumping everything to the latest.
I’m sharing this with the other guys here - I’m sure they will have more
comments.
- George Henne
> On Jan 18, 2024, at 3:50 PM, Bryan Ellis wrote:
>
> Currently the main branch is pinned for next major release 4.0.0 and is quite
> outdated.
>
> Looking at some options.
>
> Release what is currently in the main branch. I believe you can test the
> current main branch by installing nightly. Again, nightly not recommend in
> production. It could be unstable, constantly changing, and has not been
> reviewed or voted on.
> Update to the latest Electron and then prepare a release.
> https://github.com/apache/cordova-electron/pull/263
> Release multiple majors…
>
> Follow up with last two options..
>
> There is a lot of breaking changes between our last release, what’s in our
> main branch, and what’s in the latest release Electron.
>
> To sum up some of the main breaking points:
>
> Our current release version uses Electron is 14.2.9
> Our current main branch, nightly-4.0.0, has already bumped to 19.0.3
>
> 19.0
> Removes of Linux IA32 Binary
> 20.0
> Removes macOS 10.11 (El Capitan) and macOS 10.12 (Sierra)
> 23.0
> Removes Windows 7, Windows 8, and Windows 8.1
> 25.0
> Deprecated:
> protocol.{register,intercept}{Buffer,String,Stream,File,Http}Protocol - This
> is something we used to support custom scheme but there is a replacement.
> 27.0
> Removes macOS 10.13 (High Sierra) and macOS 10.14 (Mojave)
>
> There is plenty of other breaking changes (deprecation), but in terms of what
> APIs Cordova uses, its not an issue. You would need to investigate and
> resolve on your end if your using any of the APIs they deprecated.
>
> Full Breaking Changes: https://www.electronjs.org/docs/latest/breaking-changes
>
> I am leaning more towards a single release and just bump to the latest. The
> main branch already contains the feature to allow custom Electron versions
> <https://github.com/apache/cordova-electron/pull/230>. The above PR #263
> should support the use of older Electron versions, if people wish to use an
> older versions to build for older OS. The only downside I foresee would come
> from plugins if they choose to use a deprecated or new API.
>
> Also does anyone develop/maintain plugins made for Cordova Electron? Using
> the plugin ecosystem that was introduced in version 2.0.0?
>
> There was a bad pattern that was added accidentally. It doubled wrap the
> arguments that were passed to the native side. This multidimensional array is
> not needed and should be resolved. As the fix would be breaking change I
> just wanted to hear what others think.
>
> I did an npmjs search for the keyword cordova-electron and it yielded 37
> modules.
>
> Not all modules maybe be valid.
>
> Some didn’t appear to have a source folder for electron. 26 of them appear to
> be some variations of one plugin.
>
> Since the number of plugins are small, and possibly still maintained, it
> might be best to make this change now.
>
> Let me know if anyone has thoughts:
>
> -> Merge in PR #263
> -> Remove the accidental multidimensional array from plugin.
> -> Include an upgrade for all the other dependencies
> -> Release a single release with Electron bumped to its latest 28.x
>
>
Re: Plugin Search
I agree with Norm: +1 on #2. The npmjs.com search works fairly well - it wouldn’t be worth trying to make something better. George Henne VoltBuilder Support > On Oct 21, 2022, at 10:23 AM, Norman Breau wrote: > > Hi Team, > > I want to reach a final verdict on how deal with the broken search page at > https://cordova.apache.org/plugins/ > > We have an active issue being tracked at > https://github.com/apache/cordova-docs/issues/1128 but in summary, > the rest service used to power the search has gone offline and doesn't appear > to be coming back. > > Throughout the thread there has been several ideals about how to move forward > including: > > 1. Using another third-party API service: https://api-docs.npms.io/ > 2. Having a static page listing the officially supported Apache plugins, with > a link to https://www.npmjs.com/search?q=ecosystem%3Acordova > 3. Removing the page entirely, maybe with a blog post explaining how to find > third-party plugins. > > Additionally there are few ideas floated around with using the NPM Couch API > directly, but there may be terms of use issues involved without having > self-managed server hosting a mirror. > > Personally, I vote -1 for #1 and #3. npms.io doesn't have a clear terms of > use, as far as I can find. I'm not sure if the API matches the old npmsearch > that we did use, and we may just run into the same issue > down the road. For #3, community members have already explicitly expressed > dissent with removing the page entirely. > > I vote +1 for #2, having the static page with a mention + link to NPM for > third-party plugins. I think this is most likely the best path forward. > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org >
VoltSigner
We’ve got a new tool we’d like to share with the Cordova community. It facilitates the creation of signing certificates for Android and iOS. https://voltsigner.com - It’s free - No login is required - We’re in the process of making of making the source public on GitHub - Runs completely in the browser - Generates Android and iOS .p12 files on a Windows or MacOS computers. - Certificates are made 100% locally - passwords and files are not shared to the cloud. Would a link to this from the Cordova Tools page be ok? What can we do to make this more useful or appropriate for Cordova users? George Henne VoltBuilder Team
Re: [DISCUSS] Cordova Plugin Geolocation 4.1.0 Release
Looks good to me. I tested it with this in config.xml: https://github.com/apache/cordova-plugin-geolocation.git#4.1.0";> After cordova platform add, this appears in AndroidManifest.xml" Thumbs up! - George Henne
Introduction - George Henne
Hi everyone, I’m George Henne. I have been working with Cordova (and PhoneGap) since 2010, mostly as one of the developers of AppStudio. AppStudio creates web apps then passes them to Cordova/PhoneGap. I’m also part of the VoltBuilder dev team, which uses Cordova to provide a modern implementation of PhoneGap. We’ve been working on it for months, releasing it a couple of weeks ago. We’re deeply appreciative of the work that Cordova has done. We’re happy to be part of the community here, giving back where we can. Feel free to contact me anytime. George Henne gh (at) nsbasic.com <http://nsbasic.com/> Toronto, Canada https://volt.build <https://volt.build/>
Adding NSB/AppStudio to Tools section of Cordova home page
I'd like to nominate NSB/AppStudio for inclusion in the Cordova Tools section of Cordova home page. See https://github.com/apache/cordova-docs/pull/626 NSB/AppStudio is a tool for developing apps using Apache Cordova. It has supported PhoneGap since its initial release in December, 2010. AppStudio includes a drag and drop Design Screen, using built-in definitions for Bootstrap, jQuery Mobile and jqWidgets controls. Their events hook into the Code Window for JavaScript development. A BASIC to JavaScript transpiler is included. The Properties Window guides customization of the controls. AppStudio creates all the dependent code and feeds the resulting package of files, HTML, CSS and JavaScript to Apache Cordova or PhoneGap Build to create native apps. AppStudio is used to develop commercial and personal apps. It is also used for teaching: more than a million high school students have learned programming with AppStudio. It is in use in over 70 countries and has been localized in 16 languages. It's an important way people learn about Apache Cordova. Disclosure: I am one of the developers of AppStudio. Let me know if you have questions! George Henne NS BASIC Corporation http://www.nsbasic.com - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
