david at kineticode
Apr 30, 2008, 7:13 PM
Post #3 of 9
(274 views)
Permalink
|
On Apr 30, 2008, at 18:29, Marshall Roch wrote:
> As you found, this may be difficult to fix. A clean way to do it is
> to return Javascript instead of HTML (which is how Rails' RJS
> works), but perhaps there's an easier way.... I may be able to take
> a look in about 2 weeks when my finals are over.
I would really appreciate that. I mean, couldn't it return HTML with
an HTTP status so you'd know if it succeeded or not? If it's 200, then
do as normal. Otherwise, display the HTML returned as an error.
>> Another thing I noticed: You can no longer reorder elements in a
>> story. Or can you, outside of bulk edit? I couldn't figure it out.
>> Marshall?
>
> You can, or at least you could... the name of the element (i.e.
> "Paragraph" or "Pull Quote") is theoretically a drag handle.
Oh, I'll be damned. That's really nice! I have only three comments:
* We should have some sort of graphic next to the field and element
names to indicate that they're draggable. I didn't know without you
telling me.
* In Camino, at least, the browser would not scroll when I tried to
move past its bottom or top edge. That made it impossible to drag a
field very far (which can be a PITA when there is a large subelement
in the way, with lots of subelements of its own).
* Can subelements be collapsed by a > vs v icon of some kind? Or did
that not make it in.
Thanks, it really looks great! And BTW, I updated Kineticode's
Bricolage to 1.11.0 running on Apache 2, so I'll be eating the dog
food myself on those rare occasions when I work on the Kineticode
site. :-)
Best,
David
|
