That involves a bunch of things. It means “how do I get Python to run on my device” (when your device isn’t a laptop). It involves “How do I talk to the system libraries on my device”. It means “How do I put a window and a button on the screen”. And it means “how do I take this collection of code and package it in a way I can give it to someone else."
Those subprojects are, respectively “Python-*-support”, “Rubicon”, “Toga”, and “Briefcase”.
For your purposes, you don’t need to worry about the support and rubicon projects. You only need Toga and briefcase.
Toga is a GUI library. It’s like Qt or Tkinter or WXWindows or GTK.
It’s an API for putting a window on the screen, responding to button clicks.
ok so, i wanted my code (rookie btw) to have a user interface, and also be installable using msi, exe or something, and then i searched on google about how to do that, found out about beeware and briefcase, realised that the gui on briefcase comes from toga, not briefcase itself(which does the packaging), but i thought "ok, if toga is supported in briefcase then i can use briefcase for the whole process)
PLEASE
I would suggest doing the BeeWare tutorial (docs.beeware.org)
And I mean the entire tutorial. Not “I did step one and then I decided to do something on my own”.
Because the tutorial is a learning path.
It introduces concepts.
And again: Toga tutorial 2 or Beeware tutorial 2?
beeware
Let me guess. You get to the “Adding some content on our own” section, you replace the content, and the app stops working?
it does work fine, but i dont understand what im doing
Ok - so… what part is confusing? You defined a label, a textinput and a button; and the GUI contains a label, a text input, and a button. The label and the textinput are in a “row” box - so they appear in the same row. The row box and the button are in a column box, so they appear above each other.
This is the same as:
<div>
<div>
<p>Your Name</p>
<input />
</div>
<button>Say Hello</buttion>
</div>
(with appropriate CSS styling)
...build them in the cloud, e.g. with appcenter.ms You only need a Mac once when you upload the app the first time to AppStore or TestFlight. Snx
And this one time, you can use MacInCloud. Is this also possible with BeeWare
@t-arn Sure - Github Actions, for example, ships with an Xcode install, so you could use Briefcase in a CI environment to generate and build an iOS binary. Briefcase can’t currently automate the process of pushing that binary to the App Store, but that’s something that we want to add.
As for “briefcase support” - it’s a pip installable package, so as long as you can set up a Python environment and pip install briefcase, you’re set.
@freakboy3742 would it make sense to use tensorflow, keras as dependencies of the app and then making an android version?
Hi, I need some help with an issue. I'm trying to package a binary on Linux using docker. I manage to run the command "docker run - it - v..." and then then install the rest of the necessary requirements but then after I try to create a briefcase I get an ERROR : Could not find dependency:libcrypto. So. 1.0.0
@opheliagame The Resources folder is a convenient location; but you can use any file location you want. If you want to store user configuration, cache or log files, you might want to use the
app.paths attribute; that gives a number of operating-system level paths for storing files. As for “how” - you can use any normal Python file system operations.
@opheliagame I’d be very hesitant to recommend any package with binary modules for mobile distribution at this point. It’s certainly possible to get them to work, but it’s not simple - you need to know a lot about Android tooling. You definitely can’t “just pip install” something like Keras or Tensorflow.
@MarkoTammeorg If you’re seeing that error, it means there’s some discrepancy between your build environment and the support package. We’ve seen a lot of that on Linux; and so, we’ve recently modified the Linux build to internally use Docker by default.
It will be in the 0.3.1 release; but if you install from Github, you can get those features right now. It manages docker in the background, so as an end developer you only need to run “briefcase build” etc.
In all seriousness - it’s on our list; we’ve just got a lot of stuff on that list :-)