Shorten text area for Tags in step 2 of video upload form

[and]

Reduce the size of the input widget to be the same size as TOPICs. At present it stretches all the way across the page. At present no parameters are set for this text area. Its possible a class needs to be added to it and then some CSS done to make the necessary changes.

[and]

This has been done in testing and needs to go into code in plumi and engage skins. The boxes on step 2 are all different sizes now but keren said she doesn't have time to fix them at the moment so I will make a new ticket for that to happen later down the track.

[anonymous]

air heater

[and]

this doesn't seem to be in testing.plumi any more though it was previously in available in testing.engage. I have no idea where the code is for that but it would be good to add back in.

[and]

FYI there is a related ticket to this in 0.4 http://plumi.org/ticket/81

This ticket however needs to happen within this milestone as we find that many people enter the tags across the page rather than one underneath the other.

[andycat]

http://dev.plone.org/collective/changeset/57874

[and]

Re-opening this as it doesn't seem to be evident to me. Placing in 0.3 and its small and I'm getting sick of fixing people's posts who add in tags the wrong way :)

[andycat]

Did u try it on a plumi site , for instance? Its a plumi ticket.

As you can see, it is _evident_ on both demo.plumi and testing.plumi.org

closing.

[datakid]

I thought what And was getting at here was the size of the box, not in pixels, but in columns.

Can we not change the number of columns in the Keyword box from 40 to 20 for instance?

ATVideo/Content/engage.py?

I still don't know enough about this, but I think that's what he meant.

Anyway, at the end of the day, we cannot account for users that cannot read - that happens all the time, and is something we will have to learn to live with or find another solution to.

[andycat]

I dont think so at all. The ticket is about making the tags textarea the same width as the widget above, which is what has been done.

The "columns" is another way of saying the width. and why would we change the columns, when the widget has already been changed by CSS. And again, changing the widget of the text widget does NOT affect how or what the user puts in there! You cannot stop them not putting a line break between tags, nor stop them using commas, or whatever, by changing the appearance of the widget itself.

I thought we all knew the difference between the surface and the implementation!!

[and]

all good, apols for not checking, I _assumed_ that such skin diffs would be carried across to EM, my mistake.

Re-still being able to write across the page, thats fine, it's more a psychological effect I was going for, a skinner box inclines people to writing down the page one one under the other.

cheers

[fatos_durak_1995@…]

mehmet