Summary | moving rules |
Queue | Ingo |
Queue Version | 1.0 |
Type | Enhancement |
State | Resolved |
Priority | 1. Low |
Owners | |
Requester | ivan.zilic (at) mainnetworks (dot) net |
Created | 01/04/2005 (7492 days ago) |
Due | |
Updated | 07/25/2005 (7290 days ago) |
Assigned | 01/04/2005 (7492 days ago) |
Resolved | 07/25/2005 (7290 days ago) |
Milestone | |
Patch | No |
State ⇒ Resolved
instead of risko@risko.hu in changelog entries, so google can find it ;)
Thanks,
Gergely
New Attachment: ingo-move-v2.patch
- Don't use a POST submit, but a document.location redirection.
- Use the rule_up/rule_down actions, just add an optional offset. You
can do the calculation with JavaScript.
- in ruleUp()/ruleDown() merge the while() test into the for() test.
- Move the JavaScript to a separate function in filters/header.inc.
Gergely
State ⇒ Feedback
- Don't use a POST submit, but a document.location redirection.
- Use the rule_up/rule_down actions, just add an optional offset. You
can do the calculation with JavaScript.
- in ruleUp()/ruleDown() merge the while() test into the for() test.
- Move the JavaScript to a separate function in filters/header.inc.
New Attachment: ingo-sort.patch
no one has submitted a patch that handles this gracefully.
Please note, that there is debbuging output, etc., I just submit it,
because now I have to sleep and I hope for some feedback by tomorrow ;)
Is it basically acceptable? Where should I put "long" generated javascripts?
Thanks,
Gergely
State ⇒ Assigned
one has submitted a patch that handles this gracefully.
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ moving rules
Queue ⇒ Ingo
State ⇒ New
make changes in their positions using this numbers, specially when
having lots of rules.
Best Regards,
IVAN