How can I create my own custom instance of ft.Page?

[Klu1d]

Question

I heavily use custom controllers, and I would be surprised if a developer decided to build their product in any other way than through custom controllers.
https://flet.dev/docs/getting-started/custom-controls/

At some point, I decided to rewrite one of the classes and thought it would be cool to have my own methods and attributes directly in the ft.Page instance.

I really liked this idea, so I tried this:

import flet as ft

class CustomPage(ft.Page):
    def __init__(self):
        super().__init__()
        self.account = "text"
    
    def get_text(self):
        print(self.account)

async def main(page: CustomPage):
    print(page.account) 

ft.app(main)

However, I got this error:

Of course, there is a solution. I can do it this way (although VS Code won’t highlight the new attribute’s syntax as if I had assigned it in a class):

import flet as ft

async def main(page: ft.Page):
    page.text = 'text'
    print(page.text)

ft.app(main)

After several attempts to achieve this, I suspect that Flet already creates an instance of ft.Page, and ft.app() expects exactly this instance.

I have two questions:

1. At what point is the ft.Page instance created? (If my suspicions are correct)
2. How can I create my own custom instance of ft.Page?

And as far as I remember from reading the documentation, it was mentioned that ft.Page is just like ft.Container or ft.Column.

Code sample

No response

Error message

No response

------------------------------------------------------

• I have searched for answers to my question both in the issues and in previous discussions.

[Klu1d]

I can also simply copy the entire page.py file from core.py, add a separate file, and assign new functions and attributes.
And it works really well. So I think I just don't know how to do it properly.

[ndonkoHenri]

I suspect that Flet already creates an instance of ft.Page, and ft.app() expects exactly this instance.

Yeah, actually.

I dont know what's your goal exactly, but if you wish to simply have your class attached to the page, you could do something like this:

import flet as ft


class MyClass:
    def __init__(self):
        super().__init__()
        self.account = "text"

    def get_text(self):
        print(self.account)


def main(page: ft.Page):
    page.my_class = MyClass()
    print(page.my_class.account)
    print(page.my_class.get_text())

    page.add(ft.Text("Hello, World!"))


ft.app(main)

[Klu1d]

My motivation is to define my custom ft.View() elements directly in the __views attribute from the start. This would eliminate unnecessary code and provide an additional layer of abstraction, allowing me to manage these views in a more convenient and structured way.

Why should I add new ft.View instances manually if I already know which ones should be present when ft.Page is created?

Additionally, this approach would allow me to add my own functions directly to page and call them wherever the build function is used or where self.page is accessible.

Of course, there are already solutions mentioned in this chat, but they feel like workarounds rather than a clean approach. Instead of relying on such tricks, I would prefer to simply create a custom instance of ft.Page.

[Klu1d]

Moreover, I intended to add more complex code where multiple instances of other classes are contained within a single class. Syntax highlighting would be very helpful for me.