Yes it is the new ipad. Any thought :)?

@cvp Learn a lot from your script,Thanks again for your help.😆

@mikael huh, thats very strange I get the same effect using your example on my IPad Pro 11” (2018). It seems like initially the view overlaps with the info bar at the top of the screen (time, wifi, battery, etc) and upon touching the screen the view shifts down to not overlap with it. It’s hard to tell in your example due to the black text on black background. However if you set hide_title_bar to true in the built in example a similar effect happens. I will look into a fix in the next day or two.

@mikael Just a tiny correction, please correct me if I’m wrong. In the multipeer readme it says one should use <pip install multipeer> to install your module, which doesn’t work. You probably meant <pip install pythonista-multipeer>.

@Veorra, if I remember right, I noticed that the swipe was not working and googled the issue, coming up with a stack answer related to the same ObjC object.

I guess one key thing to realize is that most of the view are wrappers around the UIKit views, which can be accessed with view.objc_instance, after which you can dir(...) the available attributes and methods, and look at the related Apple docs.

@Olaf Thanks a lot, I didn't know this \1

a few of us. i tend to hide under the south bridge 😅

@shinyformica, very interesting. I have wondered about the rapid prototyping aspect myself.

My first reaction is that you do not need to learn ObjC to use the necessary iOS capabilities in Pythonista. Just some syntax conversion tricks, and then look up the manual.

But I get that the intent is more to lower the barrier of entry.

In terms of using actual custom Swift code as part of your non-App Store-deployed Pythonista app, I guess we are out of luck.

And going via ObjC looks like a no go without including some generated header files.

@omz, @jonb, @dgelessus, any expert opinions?

@JonB your statment on alias is correct 😃

But in this case we are speaking of Scene module importing ui and then Developer using ui module through scene with without making a separate import of ui in active script where __name__=="__main__"

Inside scene.py ...

from _scene2 import * import _scene2 from scene_drawing import * import math from numbers import Number from io import BytesIO import ui DEFAULT_ORIENTATION = 0 PORTRAIT = 1 LANDSCAPE = 2 ...

inside myScript.py ...

from scene import ui class MyView(ui.View): ...

@masscode No problem 😊 just remember to check if they are Pure Python. otherwise import will fail.

@mikael sorry my error, I have modified it now lol
I'll test and modify if needed, if I come with something useful I'll make a pull request

@ccc

I remember seing this a while back and a couple games became helpful for referencing. but i had to go to other websites and translate what they would say about SceneKit so that it made since for scene. if it wasnt for my previous experience with C# and a few third party engines i would of been completly lost.. I just feel it would be helpfull for current and future Pythonistas to have an isolated source to handle such topic. Game Development has been a wonderfull journey this past 8 years or so but by no means has it been easy lol.

@jh2020 try https://pypi.org/project/mpmath

EDIT:

mpmath i believe is already included in Pythonista. someone please correct me if im wrong lol

Thank you for the magnificent problem-solving information. Allow me to submit the following step-by-step instructions for installing MySQL access to pythonista for iOS; it worked for me.

https://mysql.wisborg.dk/2018/08/31/mysql-connector-python-on-ios-using-pythonista-3/

While most of the code is completely rewritten, it should be 99% backwards-compatible with the old scene module. For new projects, I would recommend using the new Node/Action-based API instead of implementing a draw method though UPSers

@mikael said:

The web tab needs to be the active one to get URL.

I had only tested with one tab, thus...

@ccc that did it.
For anyone interested, in short:
img is a 4x4 image,
img1 = view_as_blocks(img, block_shape=(2,2))
can be inverted by:
img1.transpose(0,2,1,3).reshape(4,4)

@stephen I had already written that here but, at this moment, to close the edited tab did crash, and now, it doesn't