9 Jan
2008
9 Jan
'08
12:11 p.m.
Hallo,
when I use #cssClass:, for example:
descriptionInfo
^ (MAStringDescription
auto: #info
label: 'Info') beReadonly; cssClass: 'info'; yourself
I don't see class="readonly info" in my page source code, only
class="readonly". The problem seems to be in
MAComponentRenderer>>classFor:,
which ignores aDescription attributes. Right?
Cheers,
Michal
10 Jan
10 Jan
1:28 p.m.
I don't see class="readonly info" in my
page source code, only
class="readonly". The problem seems to be in
MAComponentRenderer>>classFor:, which ignores aDescription
attributes. Right?
#cssClass: is added to the form element, not to the enclosing div. In
the case of the readonly view the attributes are not used.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
3:48 p.m.
It was an example only. Generally I have been searching how to add css
classes to my decsriptions. Is #cssClass: not intended for it ? So in
which way I should do it, please ? (for labels or controls in
MATableRenderer...)
Michal
2008/1/10, Lukas Renggli <renggli(a)iam.unibe.ch>ch>:
I don't
see class="readonly info" in my page source code, only
class="readonly". The problem seems to be in
MAComponentRenderer>>classFor:, which ignores aDescription
attributes. Right?
#cssClass: is added to the form element, not to the enclosing div. In
the case of the readonly view the attributes are not used.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
4:27 p.m.
It was an example only. Generally I have been
searching how to add css
classes to my decsriptions. Is #cssClass: not intended for it ? So in
which way I should do it, please ? (for labels or controls in
MATableRenderer...)
Ok, that was a dark area in Magritte. This is fixed in:
Name: Magritte-Seaside-lr.252
Author: lr
Time: 10 January 2008, 4:26:27 pm
UUID: 844438d1-df1f-491d-95bc-ddbee1ae6da1
Ancestors: Magritte-Seaside-lr.251
- remove #attributes from description (too fuzzy and too generic), but
added #cssClasses that will be used by the updated renderer
- fixed several issues with the table renderer that generated invalid
html
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
14 Jan
14 Jan
4:58 p.m.
Ok, that was a dark area in Magritte. This is fixed in:
Name: Magritte-Seaside-lr.252
Author: lr
Time: 10 January 2008, 4:26:27 pm
UUID: 844438d1-df1f-491d-95bc-ddbee1ae6da1
Ancestors: Magritte-Seaside-lr.251
- remove #attributes from description (too fuzzy and too generic), but
added #cssClasses that will be used by the updated renderer
Oh, quite a radical fix ;-) I had to redesign my app as I was using
attributes frequently. But, no matter, it's already done.
Cheers,
Michal
5:11 p.m.
Oh, quite a radical fix ;-) I had to redesign my app
as I was using
attributes frequently. But, no matter, it's already done.
Sorry for the trouble.
I hope you can still archive the same effects with #cssClass: ? I
think this is much cleaner from a mode-view separation perspective.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
6:20 p.m.
>>>> "Lukas" == Lukas Renggli
<renggli(a)iam.unibe.ch> writes:
Lukas> I hope you can still archive the same effects with #cssClass: ? I think
Lukas> this is much cleaner from a mode-view separation perspective.
Yeah, it did seem a bit odd that I was asking a description to know
what its CSS class was. :)
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
5949
days inactive
5954
days old
6 comments
3 participants
participants (3)
-
Lukas Renggli -
merlyn＠stonehenge.com -
Michal Perutka