More compact view for Image field in front item form

I know that you have done great job on image field and it is absolutely fantastic..but I was suggesting not to duplicate Maximum size and Allowed Extensions every time when add a new image. It will be better to put these on top of input field, between Label and Image holder..
Another reason I am asking this is to fit into mobile screen (Responsive design).

I see, will do

-- note that the that update item form is now more responsive to screen sizes, but still a couple of things to do,

e.g. in frontend it should be little work to change form to make
- basic data and slider to be TABs, this will compact the form and make give an easier navigation (i think), the good is that if some parameter is needed the validation will auto-focus into the TAB

In regards to information of file size and available extensions

-- I moved these too in r1668 (which you have), they appear only if you try to select file
now they do not fit because of the commas in file filename extensions ?

-- I will put space there so that the wrap / fold to a second line

I think that this will be enough for it to fit

Yes, available extension's value is the problem.
current extensions I specified is bmp,gif,jpg,jpeg,png,BMP,GIF,JPG,JPEG,PNG
and Do I have to specify with capital letter as well?
And yes space will be wrapped..

Thanks
Brandon

yes currently this case sensitive (except for windows servers), we may do something in the future for it

i ll put code to replace "," with ", " so that it wraps

and will also put an inline CSS to force the cell to wrap when needed

<td style="white-space: normal;">'

note most fields, add for their <li> of sortables a

white-space: no-wrap

Thank you,
One more thing I want to mention is that Can you disable(hide) Existing Image Selection if I set Existing Reusable Image List Limit to 0 ?

Brandon

Edit: Image field is very powerful but I want it to be appeared as simple as possible and all of my users won't need selecting from existing images.

I see,

-- but if hiding existing image selection,
then maybe we would need a button "restore image" in case the user clicks "remove"?

Hmmm, not really needed for me but definitely good to have it.

ggppdk wrote: -- but if hiding existing image selection,
then maybe we would need a button "restore image" in case the user clicks "remove"?

I guess we need this..

Once user remove image without saving item, the image is gone.

So we need
1. Restore Image button.
2. Display File Size and File Type once(place outside of ul class=fcfield-sortables)
3. Hide Existing Image Selection if I set Existing Reusable Image List Limit to 0.

Regards,