Reimplement property system for easier AIR support, better maintainability and performance. (BZ#2712)

[qx-bug-importer]

Sebastian Werner (@swernerx) wrote:

I am currently working on a new version of the property managment. Maybe this is good to be part of 0.9 (as the last major version for 1.0). Not sure about other priorities though. I am currently on the way, but still have to fix a few oddities.

assigned to Sebastian Werner (@swernerx)

[qx-bug-importer]

Andreas Ecker (@ecker) wrote:

Thanks for the info, Sebastian. To be fair: The impact of a new property system seems to be high. Even if it corrects some oddities (and supposedly gets rid of runtime evaluation for AIR), I doubt it would make it into the 0.9 (even 1.0) release, also given that there hasn't been a technical discussion, yet.

The earlier you could describe the proposed changes, the better, also focusing on deprecation/migration.

[qx-bug-importer]

Sebastian Werner (@swernerx) wrote:

I am working on this one. Not yet sure when this will be ready though.

[qx-bug-importer]

Andreas Ecker (@ecker) wrote:

Cannot be assigned to none, please correct, see http://qooxdoo.org/documentation/general/bug_handling

As a reminder, since you're about to put much effort into this: such a fundamental change clearly needs technical discussion and review before considering it for the framework (it is not on the roadmap for either 0.9 or 1.0). I could imagine to start hosting such an alternative implementation separately, e.g. a project in qooxdoo-contrib.

[qx-bug-importer]

Sebastian Werner (@swernerx) wrote:

Not sure what you mean, Andreas. I have assigned it to me. Otherwise it was not accepted by the system.

My idea is to make the change in the property system totally transparent and do not see why that's such a huge problem to be part of a 0.9 or 1.0 release. Sure it is not "yet" on the roadmap, but that does not mean that it could not be part of the roadmap, right?

An alternative plan which further delays the practical usage of qooxdoo inside Adobe AIR apps is IMHO not a good idea. These eval-ing is also problematic in some cases of declined PhoneGap apps. It's not good to have a core class of qooxdoo depending on such a feature.

Sure I will share the code and solution and offer it for discussion as soon as I have some more stability than right now. There need to be enough time to check it for stability, too. But hopefully it will be a part of a fresh qooxdoo release as soon as possible.

[qx-bug-importer]

Andreas Ecker (@ecker) wrote:

Was still accepted by noneqooxdoo.org, so untargeted it into pool of enhancements.

[qx-bug-importer]

Sebastian Werner (@swernerx) wrote:

Wouldn't it make sense to assign this to me... not sure regarding your new rules. But I still working on this one.

[qx-bug-importer]

Sebastian Werner (@swernerx) wrote:

See also #2014.

[qx-bug-importer]

Andreas Ecker (@ecker) wrote:

Sure this enhancement could be regularly assigned to you (previously bug attributes were just faulty). Mind my comments, though, that a reimplemented property system won't be a replacement (an alternative at most) for the existing one in the next releases. In principle an eval-free implementation might be great for many limited runtimes, of course.

[qx-bug-importer]

Andreas Ecker (@ecker) wrote:

Closed outdated issue as wontfix, as bug became stale without feedback from assignee.