Opened 16 years ago
Closed 15 years ago
#1733 closed defect (fixed)
fix widget in template implementation
Reported by: | alex | Owned by: | liucougar |
---|---|---|---|
Priority: | high | Milestone: | 0.9beta |
Component: | Widgets | Version: | 0.4 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
the current implementation of widgets in templates is pretty janky. In addition to having hard-coded attachPoint values, it iterates far too much and doesn't reuse the existing parsing/attachment code. A sane implementation should at least avoid code duplication.
Change History (4)
comment:1 Changed 16 years ago by
comment:2 Changed 16 years ago by
Milestone: | 0.4.1 → 0.5 |
---|
OK, let's mark this as 0.5 for now, and then if all the other 0.4.1 bugs get finished early come back to it. (The current code is working so code cleanup is not time critical.)
comment:3 Changed 15 years ago by
Milestone: | 0.9 → 0.9beta |
---|---|
Owner: | changed from alex to liucougar |
Cougar has a nice new implementation which he will check in soon.
comment:4 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
which "hard-coded attachPoint values" do you refer to?
I chose subContainerWidget as the counterpart to containerNode (which is also hard-coded for none widget containers)