[Clipart] [Bug 719544] Re: List Items unstyled in various portions of OCAL
chovynz at gmail.com
Tue Feb 15 21:16:19 PST 2011
Opened a discussion on mailing list because I agree with you that the bug is
closed, but only in terms of it "looking" like it is closed - visually.
The far more serious underlying bug is that there is disagreement about how
to go about issues like these.
On Wed, Feb 16, 2011 at 4:26 PM, Brad Phillips <719544 at bugs.launchpad.net>wrote:
> I don't think changing html structure is necessary either, especially
> for styling purposes. They should be separate beasts. All html does is
> group elements together, whether it's a list item or a div or a span or
> anything else.
Ok, answer me this then. Why is the upload button grouped with nothing else?
Why is the upload button even a ul il? It need not be wrapped in such, and
IMHO should not have been from the beginning - In my view, it is broken
structure from the start of OCAL 2.0. The fact is, that when OCAL was ported
to aiki, it was un-ready and rushed. Now we need to deal with such things.
For these to work, we need some discussion on how to approach them.
I provided a partial solution, and was moving forwards on getting things
actually both, good structurally, and good in terms of css.
I view what you and Jon having done as having moved backwards in terms of
all the things I said on that bug.
What you have effectively done is said "No, Chovynz, don't do that." and
undone what I did, without giving me an alternative, and without
understanding where I was headed towards it. I want solutions that work. If
you say no to something that I am working towards you must give me another
way. Not just a No.
That bug was invalid, because the solution (which I provided in the css
cleanup) is to style those individual (once off used mostly once per page
easily fixed by styling) lists, according to class, or ID that are being
used in the incorrect structurally way. The bug and "fix: was rushed through
to make the site look good, to achieve the 2.9 milestone, without thought to
how it works when there is no styling applied, as to what the actual
structure of the site IS. Look at it in firefox sometime, without styling
and you will see what I mean. Things are used in lists that shouldn't be.
You say that a structure overhaul isn't necessary, but you are ignoring the
structurally wrong way of the widgets and html that are being used. Aiki and
css (and php for that matter) is supposed to make things easier on
developers, not harder.
Yes, you are correct that html groups things. That is what I am doing,
grouping things to logic, where there is not much logic at the moment.
Things that don't need lists should be removed from lists, and positioned
via css, as well as positoned in teh correct order structurally. That is a
structural issue, and a display issue ravelled up. At the moment they are
interlinked, and it is my hope that we can unravel the two.
I told Jon there was a partial fix, and I said what the solution was (two
sets of ul, one for standard textual lists - unformatted for now, until
someone comes up with an alternative, and one for the other ways we use them
which removes all bullets and margins + paddings.) I already did all the
hard work for achieving what you guys wanted to do, but *that solution was
ignored*, and I don't know why. It's sound, it works, it removes unecessary
work, and makes it easy for anyone to make a* textual list - of which there
will be lots.*
By the way, I'm not suggesting that ul li can only ever stay unstyled, what
I am saying is
- Textual lists need to be lists. In structure, heirarchy, and in
display. I can achieve that (at the moment) by leaving that up to the
browser. It does no harm, it is flexible in all browsers, and it works.
Every browser that I know of will show an unstyled list as a list, with the
correct heirarchy - therefore you assertion that it is not good to leave
this up to the browsers is incorrect. This is the correct way to go about it
structurally. This is the first step in unraveling the css and structure.
- At a later date, we can style it so that it displays the same on every
browser. If that is ever actually needed. (if you were to say that XYZ
browser lists lists as what we see currently in the sitemap,
then your point
would be valid, but for the argument of browser displaying lists
or not, your assertion is not valid.)
- Bullet points and headings/titles make things easier to read. Fact.
They lead the eye. In large blocks of text, we need bullets. (or
visual indicator and eye-line breakup.
- Other types of lists, need to be ALSO structurally sound, AND
display correctly (i.e. how we intend it to display.) The nav menu list
needs the bullet points removed, and custom margins put on. I provided a way
to do that. Use it. Don't blanket all lists, without styling the textual
- Things that should not be in lists, should be removed and these should
be styled appropriately, otherwise you are relying on structure things for
display. That is the part I don't understand why you are pushing your
method. Your method forces others to use certain things and to do extra
work, and relies on the css skill levels of others. Mine does not, and
allows for future development in the direction of separation of presentation
and content, by someone who knows what they are doing, and also allowing
anyone to use the html list. Upload button is not grouped with anything,
should not be a ul li, and needs to be structurally removed from the list
format, and all the unecessary css removed from it. It can be a div, or
something else, by why a list item? That doesn't make any sense. Doing so
just creates spaghetti css.
What am I not saying clearly?
Am I misunderstanding something?
Am I saying too much all in one email, or being too generic in my
Can you ask me questions so that I can show you my thoughts and goals with
I want us to find an agreement on how to go about these things, then we
follow that. At the moment there is lots of different "programmer styles"
that are not meshing well.
I've worked long and hard on OCAL. I want understanding on both sides, not a
brush-off, as was done in the bug. I'm willing to learn, if need be.
I've also worked long and hard on OCAL constantly for quite awhile now, so
I'm entitled to talk more at this stage - during my rest time. :-)
> You received this bug notification because you are a member of
> openclipart.devel, which is subscribed to openclipart.
> List Items unstyled in various portions of OCAL
> Status in openclipart:
> Fix Released
> Bug description:
> I noticed, when making a new page (/packages-presidents) that certain
> elements on the page that had been styled in previous instances of
> similar pages were no longer styled. Mainly, the images that are list
> items seem to default to basic list-item styles.
> For current examples of this, see any clip art's detail page. I
> assume this is related to the css overhaul that is taking place.
> Solution is to place "list-style: none;" in the global css files on
> ocal so that each <li></li> element won't default to basic styles.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the clipart