See and try sample of @JonB here
It uses attributedText in Objective-C

Sample based on this code

# coding: utf-8 # set attributed text dor existing textview # see JonB code at # https://github.com/jsbain/objc_hacks/blob/master/attribtext2.py import ui from objc_util import * class MyView(ui.View): def __init__(self): self.width = 300 self.height = 300 tv=ui.TextView(flex='wh',frame=self.bounds) tv.delegate = self self.add_subview(tv) tv.begin_editing() UIColor=ObjCClass('UIColor') self.UIred = UIColor.redColor() self.UIfont=ObjCClass('UIFont').fontWithName_size_('Courier',20) #set up objc instance self.tvo=ObjCInstance(tv) def textview_did_change(self, textview): self.stro=ObjCClass('NSMutableAttributedString').alloc().initWithString_( textview.text) i = 0 st = textview.text.find('[',i) l = 1 while st >= 0: self.stro.addAttribute_value_range_('NSBackgroundColor',self.UIred,NSRange(st,l)) self.stro.addAttribute_value_range_(ObjCInstance(c_void_p.in_dll(c,'NSFontAttributeName')),self.UIfont,NSRange(st,l)) self.setAttribs() i = st + 1 st = textview.text.find('[',i) @on_main_thread #apparently this must be called on main thread for textview def setAttribs(self): self.tvo.setAllowsEditingTextAttributes_(True) self.tvo.setAttributedText_(self.stro) v=MyView() v.present('sheet')

It allows you to enter your text and it set the red color for all "[" found in it.

The other approach would be to have your datasource provide a tableviewcell with a highlight applied based on the list of cells to highlight -- you would have to reload to update.

Another option is to create your tableviewcell's once, and store these in your datasource. tableview_cell_for_row would need to return the stored cell. But then you have access to the cell, so can change its contents in realtime. This is not recommended if you have a very large table, since you are wasting memory on cells that are off screen.

@Phuket2 thanks for your reply and comments.
I had played a little with tkinter befor trying pythonista. There, I made a frame called root and placed all of my widgets in the root.
When I start to think of parent child relationships at different levels, things are starting to make sense.
I will read up on superview.

Thank you

No, Pythonista 3 is a separate app, so you need to purchase it again. For a while after Pythonista 3 was released, there was a bundle with Pythonista 2 and 3 in it, which allowed you to get Pythonista 3 at a lower price if you already owned Pythonista 2. This is no longer possible though. (Pythonista 2 is also no longer available for purchase - Pythonista 3 supports both Python 2 and 3, so there's no advantage to buying version 2 instead of 3. If you already own the app, you can still redownload it of course.)

If you do buy Pythonista 3, there is one upgrade-related feature that you can still use. If you go into Pythonista 3's settings, you can enable the "Pythonista 2 Files" option. This shows your Pythonista 2 Script Library as a special folder inside the Pythonista 3 file list, which you can use to easily transfer your files from Pythonista 2 to 3, using the normal "move" button in the file list. You can disable the option later to hide the Pythonista 2 files again (nothing will be deleted of course).

@ccc, just something I need , very nice indeed! I import a game, that for grand-son and daughter, and run it before the background cardimages are shown, meeaning I am on the way for an 4-level game ...
Next try, just using one of the marvallous available games , as next levels ..
.. Topscore files will be used for further interaction ..

Thanks to your example ... Helps a lot 😊 , happy OpaPeter

@procryon , if you look at one of my code examples in this thread you see the delegate being used as @JonB pointed out.
You can see the TextFields Delegate Documentation here

@technoway Python actually has a built-in limit on how deep the Python call stack can go. You can get the current limit with sys.getrecursionlimit() and change it with sys.setrecursionlimit(limit). The default limit is 1000, which is normally enough that you don't overflow the native stack even if you hit the Python recursion limit. In Pythonista that seems to be too much though, if I run an infinitely recursing function with the default limit, Pythonista crashes. With a lower limit (such as 500) I get a Python RecursionError as expected. I have no idea what the size of the native stack is on iOS, but it's probably lower than on Mac.

@Phuket2 Hi, I‘m on the beta program, too, and will have a look at this library! Thanks for the hint! 😃

@AlinMechenici , sorry I can open this in Twitter as I stopped using it. But I think the below link will work for you
https://twitter.com/olemoritz/status/700770989114667009?lang=en

@ihf, I just updated the example to have a copy to clipboard and clear methods and menu items. Not sure they are useful, but good to see how to add menu Items anyway, if you haven't played with them yet.
My example is not as compact looking as it could be, but I try and following the PEP8 style now. Eg, only one import per line, 2 lines after the imports etc.

import ui import clipboard import console class MyConsole(ui.View): def __init__(self, *args, **kwargs): super().__init__(*args, **kwargs) self.tv = None self.make_view() def make_view(self): tv = ui.TextView(frame=self.bounds, flex='wh', font=('Menlo', 24), editable=False, ) self.tv = tv self.add_subview(self.tv) ''' Create 2 ui.ButtonItem to insert into the menubar. ButtonItem's are one of those pesky ui Items that are not subclassed from ui.View Its not a big deal, just good to know they differ from ui.Button. You can see in the docs. Below, I am adding the 2 menu buttons to the right side as it seems to make sense. There is a method left_button_items also. ''' mbtn_clear = ui.ButtonItem(title='Clear', action=self.clear_console, tint_color='red') mbtn_copy = ui.ButtonItem(title='Copy', action=self.copy_console) self.right_button_items = (mbtn_clear, mbtn_copy) def write_line(self, txt): self.tv.text += "{}\n".format(txt) def clear_console(self, sender=None): ''' sender is set to None so sender is not required to call this method. The action from the menu ButtonItem needs to see it there though. But it means you can call this method on the object withouut having to pass a sender. i.e if youwanted to clear the console from your code rather than the menu button action. ie. obj.clear_console() will work. Same goes for the copy_console method below. ''' self.tv.text = "" def copy_console(self, sender=None): clipboard.set(self.tv.text) console.hud_alert('{} characters copied.'.format(len(self.tv.text))) if __name__ == '__main__': f = (0, 0, ui.get_screen_size()[0], ui.get_screen_size()[1]) v = MyConsole(frame=f, name='My Full Sceen Console') v.present(style='', animated=False) for i in range(100): v.write_line('line-{}'.format(i))

@Phuket2 , @ccc Thanks for your inputs. I will try to have a look at it. Much appreciated..

It would be cool if you could add the futurize process (at least steps 0 and 1) which is a much more modern, less distructive approach to the 2to3 conversion that is built into Pythonista.

@omz, sorry back to this subject. But if you decide to include TinyDB you might also consider including ujson also. Apparently a ultrafast json encoder/decoder written in pure C. However does not have the extensibility of python json. But if the extensibility is not required apparently is a big speed up for TinyDB. I am sue it could be used else where also. However I do see a problem. That is the package name. If a package called ujson is present it will just use it, it imports ujson as json. This maybe not what you want to do. On a desktop this would be more manageable. So maybe the package name could be ultrajson and if you wanted to use it in TinyDB you could import ultrajson as ujson before starting to work with TinyDB. I think that would work. I am not sure. Another way would be to ask the dev of TinyDB to have a switch to use ujson if its present. At the moment if ujson is seen, its used. Anyway, just more food for thought.

@ccc THAT was the real timesaver, thanks a lot 😉

Thank you for documenting the steps and your process. I went through similar attempts and find your explanations very clear.

Note to omz, correct me if I am wrong, but there should be easy integration with WorkingCopy in the next version of Pythonista. That should facilitate working with Git repositories from Pythonista (and consequently syncing, versioning, etc...). Do we have an idea/target for the new Pythonista version release?

#! python2 # Piano # # A simple multi-touch piano. from scene import * import sound from itertools import chain class Key (object): def __init__(self, frame): self.frame = frame self.name = None self.touch = None self.color = Color(1, 1, 1) self.highlight_color = Color(0.9, 0.9, 0.9) def hit_test(self, touch): return touch.location in self.frame class Piano (Scene): def setup(self): self.white_keys = [] self.black_keys = [] white_key_names = ['Piano_C3','Piano_D3', 'Piano_E3', 'Piano_F3', 'Piano_G3', 'Piano_A3', 'Piano_B3', 'Piano_C4', 'Piano_D4', 'Piano_E4', 'Piano_F4', 'Piano_G4'] #white_key_names_nogniiet = #['Piano_02','Piano_D2','Piano_E2','Piano_F2','Piano_G2','Piano_A2','Piano_B2','Piano_C3'] black_key_names = ['Piano_C3#', 'Piano_D3#', 'Piano_F3#', 'Piano_G3#', 'Piano_A3#', 'piano:C4#', 'Piano_D4#', 'Piano_F4#'] for key_name in chain(white_key_names, black_key_names): sound.load_effect(key_name) white_positions = range(12) black_positions = [0.5, 1.5, 3.5, 4.5, 5.5, 7.5, 8.5, 10.5] key_w = self.size.w / 2# pkhg factor 0.5 key_h = self.size.h / 8 /2 for i in range(len(white_key_names)): pos = white_positions[i] key = Key(Rect(0, pos * key_h, key_w, key_h)) key.name = white_key_names[i] self.white_keys.append(key) for i in range(len(black_key_names)): pos = black_positions[i] key = Key(Rect(0, pos * key_h + 10, key_w * 0.6, key_h - 20)) key.name = black_key_names[i] key.color = Color(0, 0, 0) key.highlight_color = Color(0.2, 0.2, 0.2) self.black_keys.append(key) def draw(self): stroke_weight(1) stroke(0.5, 0.5, 0.5) for key in chain(self.white_keys, self.black_keys): if key.touch is not None: fill(*key.highlight_color.as_tuple()) else: fill(*key.color.as_tuple()) rect(*key.frame.as_tuple()) def touch_began(self, touch): for key in chain(self.black_keys, self.white_keys): if key.hit_test(touch): key.touch = touch sound.play_effect(key.name) return def touch_moved(self, touch): hit_key = None for key in chain(self.black_keys, self.white_keys): hit = key.hit_test(touch) if hit and hit_key is None: hit_key = key if key.touch is None: key.touch = touch sound.play_effect(key.name) if key.touch == touch and key is not hit_key: key.touch = None def touch_ended(self, touch): for key in chain(self.black_keys, self.white_keys): if key.touch == touch: key.touch = None run(Piano(), PORTRAIT)

Append the Piano till G4