Two reasons for this post: 1) I''ve built a number of prototype-based input widgets over the years that I use quite regularly on my web projects, but I just realized I''ve never shared them with the community (they''re GPL licensed). So here you go: http://home.jongsma.org/software/js/ 2) The demos on my site are using prototype 1.4.0. I just tested and all of them work fine on the latest (1.6.0.2) except the colorpicker. If you download and use the colorpicker widget with prototype 1.6.0.2, the color swatches in the dropdown box do not appear (the whole panel is gray). But mousing over the panel still shows the colors that should be there, and clicking selects a color as it should. Before I waste a lot of time debugging this, does anyone know of a difference between 1.4.x and 1.6.x that could cause this? I tried loading prototype_update_helper.js to see if it gives me any insight but it fails (console not defined in FF?) I hope you find these useful, and I''ll try to fix up the colorpicker for 1.6.0.2 as soon as possible. -j --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Hi Jeremy, Very cool, thanks for sharing those. I really like your take on the RTE (feature bloat and ugliness are defnitely issues many of the RTEs out there have). If you haven''t already done so, have you considered submitting these to scripteka.com? FWIW: Your RTE shares two common problems I have with others out there, so I thought I should mention them: 1. It''s easy to get into a situation where Ctrl+End puts you at the end of the last line of visible text, but as soon as you type a letter, the letter is put at the beginning of the next line instead. This is *incredibly* frustrating, and it''s a common problem with several RTEs I''ve found. If you could fix that one, you''d be golden. One of the myriad ways to create it: * Press Ctrl+A to select all text * Press Del * Type a sentence and press Enter * Press backspace * Press Ctrl+Home * Press Ctrl+End At this point, the cursor is at the end of the line of text. But if you type a letter, it appears at the beginning of a new line. (Firefox 2.0.0.14, Windows XP) That series of steps looks complicated, but you understand it''s just a reliable example; in practice, this situation is incredibly easy to set up. I don''t know why so many RTEs have this problem, perhaps they''re all deriving Kevin Roth''s code. 2. Clicking in the blank area underneath all text you''ve typed should put the cursor at the end of the text like Ctrl+End does, rather than ignoring the click (IMHO). Again, thanks for sharing, and these are nits being picked. -- T.J. Crowder tj / crowder software / com On Apr 23, 7:45 am, Jeremy Jongsma <jjong...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Two reasons for this post: > > 1) I''ve built a number of prototype-based input widgets over the years > that I use quite regularly on my web projects, but I just realized > I''ve never shared them with the community (they''re GPL licensed). So > here you go:http://home.jongsma.org/software/js/ > > 2) The demos on my site are using prototype 1.4.0. I just tested and > all of them work fine on the latest (1.6.0.2) except the colorpicker. > If you download and use the colorpicker widget with prototype 1.6.0.2, > the color swatches in the dropdown box do not appear (the whole panel > is gray). But mousing over the panel still shows the colors that > should be there, and clicking selects a color as it should. Before I > waste a lot of time debugging this, does anyone know of a difference > between 1.4.x and 1.6.x that could cause this? I tried loading > prototype_update_helper.js to see if it gives me any insight but it > fails (console not defined in FF?) > > I hope you find these useful, and I''ll try to fix up the colorpicker > for 1.6.0.2 as soon as possible. > > -j--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Thanks for sharing. I wish this had been posted ages ago I wouldn''t be using YahooUI stuff right now if it had been. I have a question about the RTE: does it load properly if loaded via AJAX? A few weeks ago I was looking for a way to easily load a RTE via AJAX without having to install ruby and rails and this and that and the other to get special functionality out of Prototype to allow AJAX loaded js access to the global scope -- i finally figured out how to do it with TinyMCE, my only dislike of TinyMCE is how massive it is. PS did you fix the color chooser because its working fine for me (Windows Vista Business (gag me - I''m at work) FF 2.0.0.14) On Wed, Apr 23, 2008 at 2:45 AM, Jeremy Jongsma <jjongsma-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > Two reasons for this post: > > 1) I''ve built a number of prototype-based input widgets over the years > that I use quite regularly on my web projects, but I just realized > I''ve never shared them with the community (they''re GPL licensed). So > here you go: http://home.jongsma.org/software/js/ > > 2) The demos on my site are using prototype 1.4.0. I just tested and > all of them work fine on the latest (1.6.0.2) except the colorpicker. > If you download and use the colorpicker widget with prototype 1.6.0.2, > the color swatches in the dropdown box do not appear (the whole panel > is gray). But mousing over the panel still shows the colors that > should be there, and clicking selects a color as it should. Before I > waste a lot of time debugging this, does anyone know of a difference > between 1.4.x and 1.6.x that could cause this? I tried loading > prototype_update_helper.js to see if it gives me any insight but it > fails (console not defined in FF?) > > I hope you find these useful, and I''ll try to fix up the colorpicker > for 1.6.0.2 as soon as possible. > > -j > > >--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Good stuff, Jeremy. RTE is something that prototype ecosystem always lacked : ) Feel free to submit it to http://scripteka.com. Best, kangax On Apr 23, 2:45 am, Jeremy Jongsma <jjong...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Two reasons for this post: > > 1) I''ve built a number of prototype-based input widgets over the years > that I use quite regularly on my web projects, but I just realized > I''ve never shared them with the community (they''re GPL licensed). So > here you go:http://home.jongsma.org/software/js/ > > 2) The demos on my site are using prototype 1.4.0. I just tested and > all of them work fine on the latest (1.6.0.2) except the colorpicker. > If you download and use the colorpicker widget with prototype 1.6.0.2, > the color swatches in the dropdown box do not appear (the whole panel > is gray). But mousing over the panel still shows the colors that > should be there, and clicking selects a color as it should. Before I > waste a lot of time debugging this, does anyone know of a difference > between 1.4.x and 1.6.x that could cause this? I tried loading > prototype_update_helper.js to see if it gives me any insight but it > fails (console not defined in FF?) > > I hope you find these useful, and I''ll try to fix up the colorpicker > for 1.6.0.2 as soon as possible. > > -j--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
TJ -
Thanks for the feedback. I will look into those issues. This is also
the first of I''ve heard of scripteka, I''ll definitely post
these
there.
Brian -
That''s actually the main reason I built RTE. I had a site that loaded
content and forms via AJAX, and couldn''t find a good editor that I
could setup and tear down at will. To add it to a textarea with a CSS
id of "my_editor", just use:
var rte = new Control.RTE(''my_editor'',
''/images/rte'');
If you replace the form (via AJAX or something), or just want to
restore the original textarea, use:
rte.destroyEditor();
...and the original textarea will reappear. I find this particularly
useful when you give the user a choice of entering content in
plaintext or HTML; as they select their choice, you can instantly
convert the textarea to the desired format.
Did you download and test ColorPicker locally with 1.6? On my site
I''m still using Prototype 1.4, which it works fine with.
-j
On Apr 23, 3:32 am, "T.J. Crowder"
<tjcrow...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> Hi Jeremy,
>
> Very cool, thanks for sharing those. I really like your take on the
> RTE (feature bloat and ugliness are defnitely issues many of the RTEs
> out there have).
>
> If you haven''t already done so, have you considered submitting
these
> to scripteka.com?
>
> FWIW: Your RTE shares two common problems I have with others out
> there, so I thought I should mention them:
>
> 1. It''s easy to get into a situation where Ctrl+End puts you at
the
> end of the last line of visible text, but as soon as you type a
> letter, the letter is put at the beginning of the next line instead.
> This is *incredibly* frustrating, and it''s a common problem with
> several RTEs I''ve found. If you could fix that one,
you''d be golden.
> One of the myriad ways to create it:
>
> * Press Ctrl+A to select all text
> * Press Del
> * Type a sentence and press Enter
> * Press backspace
> * Press Ctrl+Home
> * Press Ctrl+End
>
> At this point, the cursor is at the end of the line of text. But if
> you type a letter, it appears at the beginning of a new line.
> (Firefox 2.0.0.14, Windows XP)
>
> That series of steps looks complicated, but you understand it''s
just a
> reliable example; in practice, this situation is incredibly easy to
> set up. I don''t know why so many RTEs have this problem, perhaps
> they''re all deriving Kevin Roth''s code.
>
> 2. Clicking in the blank area underneath all text you''ve typed
should
> put the cursor at the end of the text like Ctrl+End does, rather than
> ignoring the click (IMHO).
>
> Again, thanks for sharing, and these are nits being picked.
> --
> T.J. Crowder
> tj / crowder software / com
>
> On Apr 23, 7:45 am, Jeremy Jongsma
<jjong...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> > Two reasons for this post:
>
> > 1) I''ve built a number of prototype-based input widgets over
the years
> > that I use quite regularly on my web projects, but I just realized
> > I''ve never shared them with the community (they''re
GPL licensed). So
> > here you go:http://home.jongsma.org/software/js/
>
> > 2) The demos on my site are using prototype 1.4.0. I just tested and
> > all of them work fine on the latest (1.6.0.2) except the colorpicker.
> > If you download and use the colorpicker widget with prototype 1.6.0.2,
> > the color swatches in the dropdown box do not appear (the whole panel
> > is gray). But mousing over the panel still shows the colors that
> > should be there, and clicking selects a color as it should. Before I
> > waste a lot of time debugging this, does anyone know of a difference
> > between 1.4.x and 1.6.x that could cause this? I tried loading
> > prototype_update_helper.js to see if it gives me any insight but it
> > fails (console not defined in FF?)
>
> > I hope you find these useful, and I''ll try to fix up the
colorpicker
> > for 1.6.0.2 as soon as possible.
>
> > -j
--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
Very nice! Already thinking of a use for the RTE. Darrin On Apr 23, 1:45 am, Jeremy Jongsma <jjong...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Two reasons for this post: > > 1) I''ve built a number of prototype-based input widgets over the years > that I use quite regularly on my web projects, but I just realized > I''ve never shared them with the community (they''re GPL licensed). So > here you go:http://home.jongsma.org/software/js/ > > 2) The demos on my site are using prototype 1.4.0. I just tested and > all of them work fine on the latest (1.6.0.2) except the colorpicker. > If you download and use the colorpicker widget with prototype 1.6.0.2, > the color swatches in the dropdown box do not appear (the whole panel > is gray). But mousing over the panel still shows the colors that > should be there, and clicking selects a color as it should. Before I > waste a lot of time debugging this, does anyone know of a difference > between 1.4.x and 1.6.x that could cause this? I tried loading > prototype_update_helper.js to see if it gives me any insight but it > fails (console not defined in FF?) > > I hope you find these useful, and I''ll try to fix up the colorpicker > for 1.6.0.2 as soon as possible. > > -j--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
ah, my bad, it was on the site that i was testing it On Wed, Apr 23, 2008 at 11:56 AM, Jeremy Jongsma <jjongsma-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > TJ - > > Thanks for the feedback. I will look into those issues. This is also > the first of I''ve heard of scripteka, I''ll definitely post these > there. > > Brian - > > That''s actually the main reason I built RTE. I had a site that loaded > content and forms via AJAX, and couldn''t find a good editor that I > could setup and tear down at will. To add it to a textarea with a CSS > id of "my_editor", just use: > > var rte = new Control.RTE(''my_editor'', ''/images/rte''); > > If you replace the form (via AJAX or something), or just want to > restore the original textarea, use: > > rte.destroyEditor(); > > ...and the original textarea will reappear. I find this particularly > useful when you give the user a choice of entering content in > plaintext or HTML; as they select their choice, you can instantly > convert the textarea to the desired format. > > Did you download and test ColorPicker locally with 1.6? On my site > I''m still using Prototype 1.4, which it works fine with. > > -j > > On Apr 23, 3:32 am, "T.J. Crowder" <tjcrow...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > Hi Jeremy, > > > > Very cool, thanks for sharing those. I really like your take on the > > RTE (feature bloat and ugliness are defnitely issues many of the RTEs > > out there have). > > > > If you haven''t already done so, have you considered submitting these > > to scripteka.com? > > > > FWIW: Your RTE shares two common problems I have with others out > > there, so I thought I should mention them: > > > > 1. It''s easy to get into a situation where Ctrl+End puts you at the > > end of the last line of visible text, but as soon as you type a > > letter, the letter is put at the beginning of the next line instead. > > This is *incredibly* frustrating, and it''s a common problem with > > several RTEs I''ve found. If you could fix that one, you''d be golden. > > One of the myriad ways to create it: > > > > * Press Ctrl+A to select all text > > * Press Del > > * Type a sentence and press Enter > > * Press backspace > > * Press Ctrl+Home > > * Press Ctrl+End > > > > At this point, the cursor is at the end of the line of text. But if > > you type a letter, it appears at the beginning of a new line. > > (Firefox 2.0.0.14, Windows XP) > > > > That series of steps looks complicated, but you understand it''s just a > > reliable example; in practice, this situation is incredibly easy to > > set up. I don''t know why so many RTEs have this problem, perhaps > > they''re all deriving Kevin Roth''s code. > > > > 2. Clicking in the blank area underneath all text you''ve typed should > > put the cursor at the end of the text like Ctrl+End does, rather than > > ignoring the click (IMHO). > > > > Again, thanks for sharing, and these are nits being picked. > > -- > > T.J. Crowder > > tj / crowder software / com > > > > On Apr 23, 7:45 am, Jeremy Jongsma <jjong...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > Two reasons for this post: > > > > > 1) I''ve built a number of prototype-based input widgets over the years > > > that I use quite regularly on my web projects, but I just realized > > > I''ve never shared them with the community (they''re GPL licensed). So > > > here you go:http://home.jongsma.org/software/js/ > > > > > 2) The demos on my site are using prototype 1.4.0. I just tested and > > > all of them work fine on the latest (1.6.0.2) except the colorpicker. > > > If you download and use the colorpicker widget with prototype 1.6.0.2, > > > the color swatches in the dropdown box do not appear (the whole panel > > > is gray). But mousing over the panel still shows the colors that > > > should be there, and clicking selects a color as it should. Before I > > > waste a lot of time debugging this, does anyone know of a difference > > > between 1.4.x and 1.6.x that could cause this? I tried loading > > > prototype_update_helper.js to see if it gives me any insight but it > > > fails (console not defined in FF?) > > > > > I hope you find these useful, and I''ll try to fix up the colorpicker > > > for 1.6.0.2 as soon as possible. > > > > > -j > > >--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
I submitted RTE, ColorPicker, and DatePicker to scripteka. Thanks for the suggestion. -j On Apr 23, 9:38 am, kangax <kan...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Good stuff, Jeremy. > > RTE is something that prototype ecosystem always lacked : ) > > Feel free to submit it tohttp://scripteka.com. > > Best, > kangax > > On Apr 23, 2:45 am, Jeremy Jongsma <jjong...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > Two reasons for this post: > > > 1) I''ve built a number of prototype-based input widgets over the years > > that I use quite regularly on my web projects, but I just realized > > I''ve never shared them with the community (they''re GPL licensed). So > > here you go:http://home.jongsma.org/software/js/ > > > 2) The demos on my site are using prototype 1.4.0. I just tested and > > all of them work fine on the latest (1.6.0.2) except the colorpicker. > > If you download and use the colorpicker widget with prototype 1.6.0.2, > > the color swatches in the dropdown box do not appear (the whole panel > > is gray). But mousing over the panel still shows the colors that > > should be there, and clicking selects a color as it should. Before I > > waste a lot of time debugging this, does anyone know of a difference > > between 1.4.x and 1.6.x that could cause this? I tried loading > > prototype_update_helper.js to see if it gives me any insight but it > > fails (console not defined in FF?) > > > I hope you find these useful, and I''ll try to fix up the colorpicker > > for 1.6.0.2 as soon as possible. > > > -j--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
The colorpicker was updated to work with 1.6.0.2. Apparently somewhere between 1.4 and 1.6 Element.setStyle() stopped accepting css attributes (i.e. margin-left) and insisted on camelized JS styles (i.e. marginLeft). -j On Apr 23, 12:27 pm, Jeremy Jongsma <jjong...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> I submitted RTE, ColorPicker, and DatePicker to scripteka. Thanks for > the suggestion. > > -j > > On Apr 23, 9:38 am, kangax <kan...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > Good stuff, Jeremy. > > > RTE is something that prototype ecosystem always lacked : ) > > > Feel free to submit it tohttp://scripteka.com. > > > Best, > > kangax > > > On Apr 23, 2:45 am, Jeremy Jongsma <jjong...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > Two reasons for this post: > > > > 1) I''ve built a number of prototype-based input widgets over the years > > > that I use quite regularly on my web projects, but I just realized > > > I''ve never shared them with the community (they''re GPL licensed). So > > > here you go:http://home.jongsma.org/software/js/ > > > > 2) The demos on my site are using prototype 1.4.0. I just tested and > > > all of them work fine on the latest (1.6.0.2) except the colorpicker. > > > If you download and use the colorpicker widget with prototype 1.6.0.2, > > > the color swatches in the dropdown box do not appear (the whole panel > > > is gray). But mousing over the panel still shows the colors that > > > should be there, and clicking selects a color as it should. Before I > > > waste a lot of time debugging this, does anyone know of a difference > > > between 1.4.x and 1.6.x that could cause this? I tried loading > > > prototype_update_helper.js to see if it gives me any insight but it > > > fails (console not defined in FF?) > > > > I hope you find these useful, and I''ll try to fix up the colorpicker > > > for 1.6.0.2 as soon as possible. > > > > -j--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
FYI... the RTE doesn''t appear to work in Safari (v 3.1.1 on a Mac). On Apr 23, 2008, at 2:45 AM, Jeremy Jongsma wrote:> > Two reasons for this post: > > 1) I''ve built a number of prototype-based input widgets over the years > that I use quite regularly on my web projects, but I just realized > I''ve never shared them with the community (they''re GPL licensed). So > here you go: http://home.jongsma.org/software/js/ > > 2) The demos on my site are using prototype 1.4.0. I just tested and > all of them work fine on the latest (1.6.0.2) except the colorpicker. > If you download and use the colorpicker widget with prototype 1.6.0.2, > the color swatches in the dropdown box do not appear (the whole panel > is gray). But mousing over the panel still shows the colors that > should be there, and clicking selects a color as it should. Before I > waste a lot of time debugging this, does anyone know of a difference > between 1.4.x and 1.6.x that could cause this? I tried loading > prototype_update_helper.js to see if it gives me any insight but it > fails (console not defined in FF?) > > I hope you find these useful, and I''ll try to fix up the colorpicker > for 1.6.0.2 as soon as possible. > > -j > >--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
I''ll check into it. It''s been awhile since I''ve tested RTE since I''ve been forced to use TinyMCE on some projects lately due to the difficulty of cleaning up the unholy mess that is Microsoft Word cut- and-paste HTML. -j On Apr 24, 9:28 am, Greg Hemphill <gregl...-Os9gbmDpkZVBDgjK7y7TUQ@public.gmane.org> wrote:> FYI... the RTE doesn''t appear to work in Safari (v 3.1.1 on a Mac). > > On Apr 23, 2008, at 2:45 AM, Jeremy Jongsma wrote: > > > > > Two reasons for this post: > > > 1) I''ve built a number of prototype-based input widgets over the years > > that I use quite regularly on my web projects, but I just realized > > I''ve never shared them with the community (they''re GPL licensed). So > > here you go:http://home.jongsma.org/software/js/ > > > 2) The demos on my site are using prototype 1.4.0. I just tested and > > all of them work fine on the latest (1.6.0.2) except the colorpicker. > > If you download and use the colorpicker widget with prototype 1.6.0.2, > > the color swatches in the dropdown box do not appear (the whole panel > > is gray). But mousing over the panel still shows the colors that > > should be there, and clicking selects a color as it should. Before I > > waste a lot of time debugging this, does anyone know of a difference > > between 1.4.x and 1.6.x that could cause this? I tried loading > > prototype_update_helper.js to see if it gives me any insight but it > > fails (console not defined in FF?) > > > I hope you find these useful, and I''ll try to fix up the colorpicker > > for 1.6.0.2 as soon as possible. > > > -j--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Jeremy Jongsma wrote:> I''ll check into it. It''s been awhile since I''ve tested RTE since I''ve > been forced to use TinyMCE on some projects lately due to the > difficulty of cleaning up the unholy mess that is Microsoft Word cut- > and-paste HTML. > > -j >If you''re using PHP, you ought to check out HTMLPurifyer (http://htmlpurifier.org/demo.php) to wrangle Microsoft Word''s demonic HTML. I just started using HTMLPurifier with a jQuery WYSIWYG editor and it is fantastic. - Ken Snyder --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Jeremy,
You should be able to use
element.setStyle(''margin-left:10px'');
-JDD
--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
Jeremy I was trying to use your RTE but was having a few problems. I''m using IE8 in 7 emulation mode, but I haven''t encountered many oddities. My problem was that the Iframe didn''t appear to have a width or a height. The developer toolbar wasn''t much help, but eventually I found that if I applied the width and height settings to frameDiv as well as to the frame, then it worked. What confuses me, is that it works on your website, in the same browser - so there must be something screwing my style up. Just thought i''d give you a heads up anyway. Gareth On Fri, Apr 25, 2008 at 5:25 AM, jdalton <John.David.Dalton-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > Jeremy, > > You should be able to use element.setStyle(''margin-left:10px''); > > -JDD > > >--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---