[Gimp-web] questions, questions, questions

Branko Collin collin at xs4all.nl
Sun Feb 23 19:28:01 2003


On 22 Feb 2003, at 18:26, Niklas Mattisson wrote:
> On Fri, 2003-02-21 at 02:43, Branko Collin wrote:

> > - Why was a new mailing list (apparently) created when we already
> > have this one?
> 
> Have you read the mail you got from the person creating the list? 

Who would that be and which mail? I found out about the list in an e-
mail from Brix. 

> The list is created because of the development and not for public viewing
> that is why. We had a small talk about it and the mailinglist is the
> result of the talk. This list is for the announcement between the
> developers and not developers and public. (sorry)

Since when is this list for announcements? Who decided that? This 
list (the one I am writing to now) was started for the discussion 
about the new web site. 

> > - Why are there no headings being used on the site?
> 
> The site uses <div> and <p> mostly to deside the headers for the
> sections being done. 

I think you mean headings. Headers contain meta-information that is 
usually not visible to the end user. In HTML and XHTML, the headers 
can be found in the 'head' element. 

Headings are titles of chapters and sections. You cannot indicate a 
header with 'div' and 'p', which are a generic block element and a 
paragraph element respectively. In XHTML, headings can only be 
indicated by using 'h1', 'h2', etc.

> The <div> and <p> are after this in class files
> in the CSS file. If you need a class file for the titles you will have
> to talk with the designer about it.
> 
> > - I added an ALT attribute + value to an image; it got reverted with
> > the argument "alt texts are primarily used in text-only browsers,
> > and they need not see our logo". ALT texts are a replacement for
> > images when an image is not displayed. Who uses ALT texts primarily
> > for what is completely irrelevant. You cannot predict how a user is
> > going to use a site. For an accessible web site, you need ALT texts
> > to take over the function of an image if the image is not there. If
> > Lynx users need not see the ALT text, Mozilla users need not see the
> > text in the image either. 
> 
> I don't understand what you are talking about here with <a image=""
> alt=""/>. 

I am not talking about <a image="" alt="">. As far as I know, 'alt' 
and 'image' are not valid attributes for the anchor tag 'a'. Perhaps 
you mean <img src="" alt="">?

> But the alt="" option is there because of many reasons and
> not only one reason.

I know why the alt 'option' is there. I don't know why I am not 
allowed to use it where it should be used.

> > - Last time I checked (admittedly a while ago), there was no 
> > mechanism for adding menus. However, if I need to implement a 
> > subsection of the site, submenus can be very handy. The current GIMP
> > site, which is much smaller than the planned new one, allows for
> > this navigational aid. What's up with that?
> 
> The main menu is not going to be changed more then by the designer.
> The submenus after this is created within the menus you enter. If you
> want to know something about GIMP and Unix then you actually go to
> GIMP and Unix section and in that section you have menus and choices
> to go in to it more. Now this is the design done and this is what we
> are going to follow now. IMHO the site before on www.gimp.org is hard
> because I feel they where messy (No offense to the people developing
> it) but that is how I see it. At least now you can go to that section
> and you have all the info there. So the place you edit is the
> index.html file for the section you have and do not edit anything to
> the main menu. (Sorry can't explain it better)

Er... which submenus? Last time, I was not allowed to use submenus 
(IIRC).

> > - README.repository says: "When adding an html file that has SSI
> > directives (the <!--#... --> lines) in it, the file needs to be
> > 'chmod +x file.html' (yes, the *.html file needs to be
> > executeable!). Furthermore, it need to be executeable at 'cvs add
> > file.html'; it's a pain to change the permissions when the file is
> > already checked in."
> 
> Well the best thing here is to make a template file for the section
> you have and then use that as the file to copy to the right place.
> Example: tutorials have a template/template.html and I copy this file
> to the index.html file I need to edit. This means I don't have to
> worry about the chmod +x more then with the template file. The README
> is going to be updated really soon because of changes done to the
> site.

I don't quite understand this. How will permissions be preserved? Is 
this some 'under water' option in Windows?

> > Any idea how I should change the permissions before checking in?
> > 
> > Well, that's it for now. :-)
> 
> Just ask there is no problem but sending the mail to the wrong list is
> not a very good idea I think.. :) -- Niklas Mattisson
> <scizzo@gimp.org>

As far as I know, this _is_ the right list. But I guess the old 
problem rears its ugly head again, that executive changes are only 
communicated during full moon and lunch time in Michigan on an IRC 
channel in an abandoned cellar behind a cabinet that has a sign 
attached to it that reads "beware of the tiger". 

If (and I mean _if_) the purpose of this list, the one I am writing 
to now, has changed from 'discussion about the new GIMP web site' to 
'announcements about the new GIMP web site', it would seem to me that 
the first announcement should have been about the new mailing list.

-- 
branko collin
collin@xs4all.nl