jepler/beeware.github.io
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Merge pull request #486 from mhsmith/july-typos

Browse source
This commit is contained in:
Russell Keith-Magee 2022-08-01 16:32:26 +08:00 committed by GitHub
commit c5567eedba
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
content/news/buzz/july-2022-status-update/contents.lr
View file

@ -16,11 +16,11 @@ During July:
* We `added support for Linuxdeploy plugins <https://github.com/beeware/briefcase/pull/756>`__ for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
* We `added a Flatpak backend for Linux packaging <https://github.com/beeware/briefcase/pull/802>`__. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
* We `improved the packaging of Windows apps by adding a stub binary <https://github.com/beeware/briefcase/pull/782>`__. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
* We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; `register at for details <https://event.on24.com/wcc/r/3766379/B50F020E006CF935D87609BF3E247ED7?partnerref=anaconda.com>`__.
* We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; `register here to watch <https://event.on24.com/wcc/r/3766379/B50F020E006CF935D87609BF3E247ED7?partnerref=anaconda.com>`__.
* We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
* We modified Briefcase to `use OS-appropriate directories for caching <https://github.com/beeware/briefcase/pull/777>`__. While the ``~.briefcase`` location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
* We modified Briefcase to `use OS-appropriate directories for caching <https://github.com/beeware/briefcase/pull/777>`__. While the ``~/.briefcase`` location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
* We addressed an issue with the `current working directory leaking into the runtime path <https://github.com/beeware/briefcase/pull/803>`__. This was especially common with Linux apps, but it could potentially be an issue with other platforms as well.
* We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
* We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
* We've started looking into binary dependencies on iOS apps.
What's next?