just being curious: what´s the argument against defining the rows in the
model?

using id´s works fine with a few tables, but with hundreds of tables it´s
getting complicated: because "body" in "films" may be a large textarea
whereas "body" in "comments" may be a smaller one. ok, one could use
"film_body" for "films" and "comments_body" for "comments". then again, one
has to update the css-file when changing the model (which is not a good
thing to do in my opinion).

patrick

> 
> You can use ID's: "id_summary", "id_body", and so on.
> 
> #id_summary {
>   width: 100%;
>   height: 5em;
> }
> 
> #id_body {
>   width: 100%;
>   height: 10em;
> }
> 
> Thanks,
> 
> Eugene
> 
> 
> "patrick k" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> 
> as far as i know, textares have classes like "vLargeTextField". so, i dont
> know how one can change that.
> 
> by the way, with doing what you suggested you have to update the .css-file
> everytime you add (or change) a model.
> 
> patrick
> 
>> 
>> On 12/27/05 18:28, patrick k wrote:
>>>> On 12/27/05, patrick k <[EMAIL PROTECTED]> wrote:
>>>>> - how do i change the numrows for a textarea-field?
>>>> 
>>>> You can do this with CSS; create custom admin templates that include
>>>> some custom CSS code.
>>> 
>>> what i meant was changing the numrows for each textarea-field seperately.
>>> e.g., a body-field needs more space than a summary (at least in my app).
>>> why not thinking about extending the textfield-model with something like
>>> "numrows=xxx"?
>>> 
>> 
>> Maybe add css classes to textareas (or generally inputs) based on model
>> and fieldname?
>> 
>> e.g.:
>> class Article(meta.Model)
>>  summary = meta.TextField()
>>  body = meta.TextField()
>> 
>> becomes:
>> <textarea class="article-summary"></textarea>
>> <textarea class="article-body"></textarea>
>> 
>> .article-summary {
>>  width: 100%;
>>  height: 5em;
>>  }
>> .article-body {
>>  width: 100%;
>>  height: 10em;
>>  }
>> 
>> 
>> That's how some other tools I've used do it.
>> 
>> I'ld prefer such a solution to values hardcoded in the model.
>> 
>> cheers
>> Steven
> 
> 
> 
> 

Reply via email to