isn't that the whole point of IPE, to make elements, you know,
Editable In Place?
if everyone wanted to use FORMs then we would never have any reason
for an IPE, but someone decided that this IPE thing might be a good
idea, that there was value in it, and i happen to agree.
my issue is with the extremely limited nature of the element. to use
it, i pretty much have to rewrite it from the ground up. that's fine,
but it's presented as something that's essentially ready to use, and
then i find out that there's no built-in/configurable way to unselect
all the text upon entering edit mode. stuff like that is frustrating
as all get out. there's no reason i can see that this element can't do
everything we want it to. there's no reason not to have a simple
working example on the website of something not completely trivial.
there's no reason to not explain design decisions at an api level.
i mean, you have to plop the same event code into your HTML for ever
single instance of the IPE you want to use - one for each unique
element ID. how about a simple selector mechanism based on class or
element type or _anything_? no configurable translation for nl2br().
and, more on the TEXTAREA, maybe i want my screen to look essentially
the same when a user 'activates' an element for edit mode - i don't
want my page shifting all over the place based on some arbitrary
number of columns and rows. this seems possible with a simple input
box, but what if i wanted something useful, like a TEXTAREA?
so, what needs to happen is I need to update the documentation on the
scriptaculous page so that it doesn't give the false impression that
this IPE element can be used in anything other than the most limited
circumstances - unless you're ready to rewrite it yourself. i need to
update the docs so that they make more clear that your server-side
script must return the text you just sent to the server-side script.
then i need to look at this IPE code and make it work for TEXTAREAs.
then i need to add a config option to not select/highlight the
existing text.
scripcrapulous. that's what i say.
i tried jquery, too, and that thing didn't even _think_ about being
useful.
On Mar 19, 8:01 am, Walter Lee Davis <[EMAIL PROTECTED]> wrote:
> On Mar 16, 2007, at 3:49 PM, Peter2 wrote:
>
>
>
>
>
> > yes, that's part of what i mean, but the more important part is that
> > i
> > want to _start with_ a textarea. that is, i want a TEXTAREA on my
> > screen
> > - not a one-line INPUT element. here is my code:
>
> > <textarea id="editme" rows="5" cols="50">This is what is in the box
> > already.</textarea>
>
> > <script type="text/javascript">
> > new Ajax.InPlaceEditor('editme', '/ajaxWaitReturn.php',
> > {rows:5,cols:50});
> > </script>
>
> > The 'ajaxWaitReturn.php' script just sleeps 5 seconds, then ends. So,
> > taking easy things first, there never is a 'Saving...' message -
> > whether
> > I use a 'wait/spinning' icon or not. Is this normal? A bug?
>
> > (didn't realize this forum was the same as the google group sort of.)
>
> > On Mar 16, 9:39 am, Walter Lee Davis <[EMAIL PROTECTED]> wrote:
> >> On Mar 16, 2007, at 11:14 AM, Peter2 wrote:
>
> >>> when i use a TEXTAREA within-place-editor, all sorts of weird stuff
> >>> happens - like it disappears, or the callbacks don't work, the 'wait'
> >>> indicator stops working after the first save, i never get a 'Save...'
> >>> message, etc. is this all from using a TEXTAREA as opposed to a P
> >>> tag?
>
> >> Not sure what you mean here. Do you mean if you set the editor to use
> >> columns and rows, rather than letting it default to a single-line
> >> (input type=text) you get different behavior? I haven't seen that
> >> personally, and I have used both types of IPE.
>
> >>> also, is there a non-hack way to not pre-select all the text in the
> >>> textarea?
>
> >> There was a long discussion of this recently on this list. Please have
> >> a search of the archives.
>
> >> Walter
>
> That's whacked! It's a textarea, so just use that! Are you trying to
> get the textarea's form to submit over Ajax? Cuz that's pretty easy:
>
> (in your <form> tag)
> onsubmit="Element.show('spinner'); new
> Ajax.Updater('parent_div_of_the_form', 'form_handler.php',
> {asynchronous:true, parameters:Form.serialize(this)}); return false;"
>
> I'm not at all clear why you would have a form element and then make
> the form element itself editable with IPE. Form elements are editable
> to begin with!
>
> Walter
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
