Hi again,
I have come to the following conclusion so far:
-Use detailed CSS specifications is the way to avoid #id clashing.
-We will also keep some automatic disabling of CSSs that are no longer in
use... we will try not to rely on this mechanism though, and still use what
i said in the line
Hi all, its been a while.
Finally we started migrating other applications from swing to wicket thanks
to all your help provided last year.
Having said that, I have some colleagues that are looking to develop a way
to disable style sheets that are loaded as part of panel replacement.
Here is the
Hi Francisco
I'd much rather go with more detailed naming of your styles, instead of
doing complex stuff with dom? Like
.DetailPanel-A-fieldPersonName{
position:absolute;
left:50px;
top: 50px;
}
Or maybe the problem are more complex than this..?
That was my approach exactly but I lack the arguments to convince them. I
managed to send this mail and see if I'll get better ones :-), or at least
community consensus.
Maybe if I started a thread I could get some other experiences and opinions
on the matter.
Thanks Nino.
f(t)
On Wed, Jun 18,
Hi,
I'm here with Francisco, discussing this subject.
The main difference between the approach is the amount of stuff to write in
CSS: With the detailed naming of styles (.DetailPanel-A fieldPersonName)
you have to write a lot more in the CSS. That is, for each field in
DetailPanelA, you have to
what happens if you ever need to use both panels on the page
simultaneously. personally i would stick with the .panela selector
stylesheets
-igor
On Wed, Jun 18, 2008 at 11:28 AM, German Morales
[EMAIL PROTECTED] wrote:
Hi,
I'm here with Francisco, discussing this subject.
The main
Igor,
Yes, in such case the only solution is the full detailed style info.
In our case, however, we talk about panels that always replace each other.
Or at least that is the common case. Perhaps finding cases that does not
follow this rule helps to solve this dilemma.
Thanks for the new point of
One extrathing though! you could take a look at the scriptacoulus
toaster I added last week. I do some dynamic styling there if. Because
if you have more than one popup window on your page you do not want them
to clash, so it's sort of the same. But it has some extra work though,
since I use a
German Morales wrote:
Hi,
I'm here with Francisco, discussing this subject.
The main difference between the approach is the amount of stuff to write in
CSS: With the detailed naming of styles (.DetailPanel-A fieldPersonName)
you have to write a lot more in the CSS. That is, for each field in
