On Sat, Nov 15, 2008 at 5:35 AM, Scott Haneda <talklists@xxxxxxxxxx> wrote:
> On Nov 15, 2008, at 2:02 AM, Paul Lesniewski wrote:
>> On Fri, Nov 14, 2008 at 11:12 PM, Scott Haneda
>> <talklists@xxxxxxxxxx> wrote:
>>> On Nov 14, 2008, at 7:21 PM, Paul Lesniewski wrote:
>>>
>>>> Also, if you can please report the style name for the table issue
>>>> you
>>>> identified (and even the fix if you find it), I will put the fix
>>>> into
>>>> the default skins.
>>>
>>>
>>> <td class="col_date"
>>
>> Why col_date? The whole table is what isn't stretched out, right?
>
> I thought you wanted me to report the name of the css class I could
> not find referenced in any css files. I am no longer trying to
> resolve the issue of a table not fitting into the correct width, which
> is easily solved by setting the second inner table to 100% the same as
> the outer table.
You didn't specify that you found a fix for the problem you first
reported. If you can indicate where you made this change, I'd like to
commit it to SVN. Please do tell.
> I can certainly provide a path for that, that is a simple issue.
Please, thanks.
> Ay any rate, eventually, if this is to remain as a table, I would need
> access to every td in every table. I think I can manage this with the
> new template based theme system, it looks a lot like phpBB, which I
> have hacked around in a good deal.
I think ultimately the idea was to leave the simple table layout and
allow skin developers to go table-less if they felt like it. But I'd
be interested to hear if you have another proposal for the basic
default template.
>> Anyway,
>>
>>> I can not locate that in any css file. I think it just needs to be
>>
>> $ grep -rin col_date css
>> css/default.css:403:.table_messageList td.col_date {
>
> Yes, but I read somewhere, and also you posted in your other email to
> me, that /css was to be depricated. What do you suggest in this
> case? It seems a wholly non logical place for that style control to
> be at this point.
See my earlier email. No matter what we finally decide about that
directory, you should still be able to override that style in your
skin. If not, something needs to be fixed.
>>> As a matter of practice, I have avoided it, certainly you do not want
>>> to lead with an underscore, as those make some very interesting
>>> things
>>> happen, sometimes to the advantage of the developer to work around a
>>> bug.
>>
>> I'd be amenable to changing all the classes to not use them if there
>> is a better chance SM would retain maximum compatibility. A patch
>> would be most welcome for that one. :-)
>
> Ok, I can do that as well, that is a simple find and replace as long
> as I am careful. I think the new template/theme/skin system will make
> it a non issue anyway, as I should be able to rename anything I desire
> to whatever I desire, as soon as /css and the other little bits are
> compartmentalized into the template system.
Well, but it makes A LOT of sense to keep a consistent list of
commonly used base styles. Forcing every skin developer to create a
whole slew of styles of their own is overkill and won't be very
inviting to more casual skin developers.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
-----
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
