Add #destroy method

[tiquelou]

<div id="truncateThis">Some text<div id="dynamic01></div></div>

truncateThis is the div on which smart truncate is being used. If you are using dynamic01 to display some dynamic data, like, say, the text of a selected item in a dropdown, nothing is rendered in dynamic01.

[polarblau]

Is it that you'd like to change the content of an element on which you've called the plugin?

[tiquelou]

correct, which is not happening. Is there something I am missing?

also, going thru the code, I realised that the plugin might not work well with internationalization... plz do confirm.

On Tue, Mar 29, 2011 at 12:42 PM, polarblau < [email protected]>wrote:

Is it that you'd like to change the content of an element on which you've called the plugin?

Reply to this email directly or view it on GitHub: https://github.com/polarblau/smarttruncation/issues/2#comment_929844

Arnab Bandyopadhyay

Director, Operations & New Ventures [email protected] | Mobile: +91 9986029040 www.plavaga.in | Jump start possibilities

[polarblau]

You're absolutely correct what comes to the dynamic content. The plugin stores the original content of the element for you and this content would need to be updated when the content of the element is changed. However, I'm wondering if this is a logical place to add this kind of functionality. I' could imagine adding a destroy method to remove the plugins functionality, giving the user the possibility to re–attach it after changing the content. Monitoring if the content has changed seems overly costly to me. What do you think?

Could you give an example on where do you see problems with the internationalization?

I've noticed that — depending on your font–settings — you might have to quite a lot of tweaking to get things to work as you want them to. (Just as a warning ;) ) . I'm working on a test suite and some options to improve this situation as well as a solution to handle HTML entities properly.

[tiquelou]

aah! so let me try a few tweaks and I will let you know if I have any success!! :)

On Tue, Mar 29, 2011 at 1:14 PM, polarblau < [email protected]>wrote:

You're absolutely correct what comes to the dynamic content. The plugin stores the original content of the element for you and this content would need to be updated when the content of the element is changed. However, I'm wondering if this is a logical place to add this kind of functionality. I' could imagine adding a destroy method to remove the plugins functionality, giving the user the possibility to reattach it after changing the content. Monitoring if the content has changed seems overly costly to me. What do you think?

Could you give an example on where do you see problems with the internationalization?

I've noticed that depending on your fontsettings you might have to quite a lot of tweaking to get things to work as you want them to. (Just as a warning ;) ) . I'm working on a test suite and some options to improve this situation as well as a solution to handle HTML entities properly.

Reply to this email directly or view it on GitHub: https://github.com/polarblau/smarttruncation/issues/2#comment_929924

[tiquelou]

Another update - I checked for the internationalization, the plugin works just fine with non-latin scripts :)

On Tue, Mar 29, 2011 at 1:14 PM, polarblau < [email protected]>wrote:

You're absolutely correct what comes to the dynamic content. The plugin stores the original content of the element for you and this content would need to be updated when the content of the element is changed. However, I'm wondering if this is a logical place to add this kind of functionality. I' could imagine adding a destroy method to remove the plugins functionality, giving the user the possibility to reattach it after changing the content. Monitoring if the content has changed seems overly costly to me. What do you think?

Could you give an example on where do you see problems with the internationalization?

I've noticed that depending on your fontsettings you might have to quite a lot of tweaking to get things to work as you want them to. (Just as a warning ;) ) . I'm working on a test suite and some options to improve this situation as well as a solution to handle HTML entities properly.

Reply to this email directly or view it on GitHub: https://github.com/polarblau/smarttruncation/issues/2#comment_929924

Arnab Bandyopadhyay

Director, Operations & New Ventures [email protected] | Mobile: +91 9986029040 www.plavaga.in | Jump start possibilities

[tiquelou]

Ouch! Hit a brick wall... looks like a 'destroy' method is very much required!

On Tue, Mar 29, 2011 at 1:14 PM, polarblau < [email protected]>wrote:

You're absolutely correct what comes to the dynamic content. The plugin stores the original content of the element for you and this content would need to be updated when the content of the element is changed. However, I'm wondering if this is a logical place to add this kind of functionality. I' could imagine adding a destroy method to remove the plugins functionality, giving the user the possibility to reattach it after changing the content. Monitoring if the content has changed seems overly costly to me. What do you think?

Could you give an example on where do you see problems with the internationalization?

I've noticed that depending on your fontsettings you might have to quite a lot of tweaking to get things to work as you want them to. (Just as a warning ;) ) . I'm working on a test suite and some options to improve this situation as well as a solution to handle HTML entities properly.

Reply to this email directly or view it on GitHub: https://github.com/polarblau/smarttruncation/issues/2#comment_929924

Arnab Bandyopadhyay

Director, Operations & New Ventures [email protected] | Mobile: +91 9986029040 www.plavaga.in | Jump start possibilities

[polarblau]

Thanks for your feedback. Good to hear that the plugin works for other languages than English as well. What comes to the destroy method: I'll look into that as soon as I get around to. In the mean time you could use remove() to get rid of the wrapper and then re–insert the wrapper + content and then attach the plugin again. It's a bit of a hack but might just do the trick. Haven't tested it, though. —Let me know you get in trouble.

[tiquelou]

will do. thanks for listening!

On Tue, Mar 29, 2011 at 2:30 PM, polarblau < [email protected]>wrote:

Thanks for your feedback. Good to hear that the plugin works for other languages than English as well. What comes to the destroy method: I'll look into that as soon as I get around to. In the mean time you could use remove() to get rid of the wrapper and then reinsert the wrapper + content and then attach the plugin again. It's a bit of a hack but might just do the trick. Haven't tested it, though. Let me know you get in trouble.

Reply to this email directly or view it on GitHub: https://github.com/polarblau/smarttruncation/issues/2#comment_930173