> If such constrain is enforced in the initial TML design, we could leave > the TML as mandatory for Tizen 3 base, avoiding a fork, and adding only > a few KB of extra code in single user devices. > > Comparing the cost of maintaining a fork versus a few kB of RAM, I feel > that a fork is an extrem model that is not justified in this case. > > So I propose to remove the optional status for TML and its associated > services in the multiuser architecture release candidate. > > Your feedback will be appreciated. >
I agree that the use of TML should be mandatory as it incurs too much burden to maintain two different code tree. Actually Alvin had same conclusion with me after last conference call conditionally that TML should not incur too much run-time overhead. Young
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
