Make ScreenInteractive methods public

[techsupport-noah]

I would like to include ftxui into a realtime scheduling framework where there are tasks from which you derive so that you get the rt functionality without much work.
For that it would be pretty nice to be able to skip the usage of the screens loop functionality and just call the RunOnce, ... methods directly by the scheduling defined in the framework.

I think my request could be done by just making these methods inside the class public:

public:
  void ExitNow();

  void Install();
  void Uninstall();

  void PreMain();
  void PostMain();

  bool HasQuitted();
  void RunOnce(Component component);
  void RunOnceBlocking(Component component);

  void HandleTask(Component component, Task& task);
  void Draw(Component component);
  void ResetCursorPosition();

  void Signal(int signal);

I think this change would actually be great for other scenarios as well, not only when you need tight control over resources but also when you just want to have a little more control over the ui rendering in general.
I don't think this change would affect the current usage of ftxui too much.

[ArthurSonzogni]

Hello!

Would the ftxui::Loop work for you?

FTXUI/examples/component/custom_loop.cpp

Lines 47 to 51 in 55af678

	while (!loop.HasQuitted()) {
	custom_loop_count++;
	loop.RunOnce();
	std::this_thread::sleep_for(std::chrono::milliseconds(10));
	}

See doc:
https://arthursonzogni.github.io/FTXUI/classftxui_1_1Loop.html

You directly have access to:

Loop::RunOnce();
Loop::RunOnceBlocking();

This way, you can control when "processing" FTXUI happen, and when to wait.

[techsupport-noah]

Hey Arthur, thanks for you quick reply!

First of all yes, i could make it work with your loop class, but currently i am doing a multi page application which uses a collection of layout containers each making a single page. If I would use your loop class i would need one loop per page, which doesn't make much sense in my opinion as all the loop does is making sure you call preMain and postMain. The class doesn't add more functionality and i would love to remove the need for extra loop objects so i thought it may be easier to open these methods up fo r public access. In the end you could still use the loop class with that change!

Maybe i am missing something here, but i still think that this would be better.