You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Dirk Verbeeck <di...@pandora.be> on 2004/05/31 16:12:36 UTC
[site] main + sandbox site update
OK, the next step in making commons website more uniform is taken.
All sandbox components now have a logo, use the commons menu and have
the commons l&f (more or less).
http://cvs.apache.org/~dirkv/sandbox/
There are also 2 new components:
http://cvs.apache.org/~dirkv/sandbox/feedparser/
http://cvs.apache.org/~dirkv/sandbox/transaction/
I will also update the main commons pages to include the 2 new
components and to update the wiki link.
http://cvs.apache.org/~dirkv/commons/
Unless anyone wants a last minute change, I'll push these changes
online in a couple of hours.
-- Dirk
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [site] main + sandbox site update
Posted by Oliver Zeigermann <oz...@apache.org>.
Dirk Verbeeck wrote:
> OK, the next step in making commons website more uniform is taken.
>
> All sandbox components now have a logo, use the commons menu and have
> the commons l&f (more or less).
> http://cvs.apache.org/~dirkv/sandbox/
>
> There are also 2 new components:
> http://cvs.apache.org/~dirkv/sandbox/feedparser/
> http://cvs.apache.org/~dirkv/sandbox/transaction/
I have updated the transaction description to make it match what
currently is there.
Thanks again for your efforts and help!
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [site] main + sandbox site update
Posted by Oliver Zeigermann <ol...@zeigermann.de>.
Dirk Verbeeck wrote:
> OK, the next step in making commons website more uniform is taken.
>
> All sandbox components now have a logo, use the commons menu and have
> the commons l&f (more or less).
> http://cvs.apache.org/~dirkv/sandbox/
>
> There are also 2 new components:
> http://cvs.apache.org/~dirkv/sandbox/feedparser/
> http://cvs.apache.org/~dirkv/sandbox/transaction/
I have updated the transaction description to make it match what
currently is there.
Thanks again for your efforts and help!
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [site] Thoughts on breadcrumbs
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
I now think your right. I went and looked at several large maven sites,
I have to say, no one really uses this as a bread crumb trail. Its
mostly just used to provide links to related projects. For instance:
Maven, Jelly, Plugins etc...
-Mark
Dirk Verbeeck wrote:
> Personally I don't see a lot of added value.
> Jakarta already has a big logo with a link and the Commons Homepage is
> the first item in the menu.
>
> If it becomes a real bread crumb trail, from apache to the actual page
> then it might be more usefull.
>
> -- Dirk
Re: [site] Thoughts on breadcrumbs
Posted by Dirk Verbeeck <di...@pandora.be>.
Personally I don't see a lot of added value.
Jakarta already has a big logo with a link and the Commons Homepage is
the first item in the menu.
If it becomes a real bread crumb trail, from apache to the actual page
then it might be more usefull.
-- Dirk
Mark R. Diggory wrote:
> Site looks good.
>
> I was considering the idea that we should go through each project and
> make sure the navigation.xml files contain proper bread crumb links in
> the grey breadcrumb bar.
>
> See Math for example:
> http://jakarta.apache.org/commons/math/
>
> This is something that can be a global entity include just like the
> other navigation sections.
>
>
> <project name="Math">
>
> <title>Math</title>
> <organizationLogo href="/images/jakarta-logo-blue.gif">
> Jakarta
> </organizationLogo>
>
> <body>
> <links>
> <item name="Jakarta"
> href="http://jakarta.apache.org"/>
> <item name="Jakarta Commons"
> href="http://jakarta.apache.org/commons/"/>
> </links>
>
> ...
>
>
> the following could be in a file global-links.ent that gets included
> into menus.dtd
>
> <links>
> <item name="Jakarta"
> href="http://jakarta.apache.org"/>
> <item name="Jakarta Commons"
> href="http://jakarta.apache.org/commons/"/>
> </links>
>
>
> included into the dtd as
>
> <!ENTITY global-links SYSTEM "global-links.ent">
> <!ENTITY common-menus "&top-menus;&bottom-menus;&global-links;">
>
>
> -Mark
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[site] Thoughts on breadcrumbs
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Site looks good.
I was considering the idea that we should go through each project and
make sure the navigation.xml files contain proper bread crumb links in
the grey breadcrumb bar.
See Math for example:
http://jakarta.apache.org/commons/math/
This is something that can be a global entity include just like the
other navigation sections.
<project name="Math">
<title>Math</title>
<organizationLogo href="/images/jakarta-logo-blue.gif">
Jakarta
</organizationLogo>
<body>
<links>
<item name="Jakarta"
href="http://jakarta.apache.org"/>
<item name="Jakarta Commons"
href="http://jakarta.apache.org/commons/"/>
</links>
...
the following could be in a file global-links.ent that gets included
into menus.dtd
<links>
<item name="Jakarta"
href="http://jakarta.apache.org"/>
<item name="Jakarta Commons"
href="http://jakarta.apache.org/commons/"/>
</links>
included into the dtd as
<!ENTITY global-links SYSTEM "global-links.ent">
<!ENTITY common-menus "&top-menus;&bottom-menus;&global-links;">
-Mark
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [site] main + sandbox site update
Posted by Dirk Verbeeck <di...@pandora.be>.
Glad you like it, sandbox + main site are updated just now...
-- Dirk
Mark R. Diggory wrote:
> I saw this and burst out laughing. How totally unexpected... ;-) Very
> inventive!
>
> Dirk Verbeeck wrote:
>
>> The css only contains a max height for the header so the header will
>> resize.
>>
> Yes, your right, but my main point was that the min height is going to
> be constrained by the projects logo and resizing this logo will be very
> ugly.
>
>> But to support small screens I just added a small javascript to switch
>> logo if window size < 850.
>> Larger browser windows or browsers with javascript disabled get the
>> wide version.
>>
>> Result can be seen/tested here:
>> http://cvs.apache.org/~dirkv/commons/index.html
>>
>> And to make testing easier:
>> http://cvs.apache.org/~dirkv/commons/size.html
>>
>> Please test & report browser problems.
>>
>> -- Dirk
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [site] main + sandbox site update
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
I saw this and burst out laughing. How totally unexpected... ;-) Very
inventive!
Dirk Verbeeck wrote:
> The css only contains a max height for the header so the header will
> resize.
>
Yes, your right, but my main point was that the min height is going to
be constrained by the projects logo and resizing this logo will be very
ugly.
> But to support small screens I just added a small javascript to switch
> logo if window size < 850.
> Larger browser windows or browsers with javascript disabled get the
> wide version.
>
> Result can be seen/tested here:
> http://cvs.apache.org/~dirkv/commons/index.html
>
> And to make testing easier:
> http://cvs.apache.org/~dirkv/commons/size.html
>
> Please test & report browser problems.
>
> -- Dirk
>
> Mark R. Diggory wrote:
>
>> Please review the discussion we had previously on this...
>>
>> http://www.mail-archive.com/commons-dev@jakarta.apache.org/msg38884.html
>>
>>
>> This is the reason we settled on the selected logo's, because it was
>> of less overall impact on the group and accomplished our goals of
>> maintaining the site fits within 600x800 as a standard.
>>
>> Just to point out, with your changes, the height of the header is not
>> going to adjust to be narrower because all the individual project
>> logos are at 80px height, having the jakarta logo narrower than 80px
>> in height is of little benefit, your going to have to press every
>> single project to generate new logos that are narrower in height so
>> that the whole header is narrower. The downfall of this is that these
>> logos are already hard-pressed for space to fit adequately within the
>> header without looking totally "crunched".
>>
>> If your using the /commons-build/commons-site.jsl. It has the height
>> of the header hardcoded in the css style to enforce that the same
>> height is maintained across the whole commons. It doesn't look like
>> your using it for the sandbox site. I'm not complaining, just
>> noticing that theres a difference, there are modifications in the
>> commons-build jsl that are absent form the sandbox copy.
>>
>> I'm not trying to be argumentative. We definitely need this kind of
>> experimentation and redesign efforts done to the overall site. I
>> think everyone agrees these efforts are very appreciated. I just want
>> us to be methodical and consensus driven in our approach.
>>
>> -Mark
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
RE: [site] main + sandbox site update
Posted by "Noel J. Bergman" <no...@devtech.com>.
> to support small screens I just added a small javascript to switch
> logo if window size < 850. Larger browser windows or browsers with
> javascript disabled get the wide version.
Works great. My normal browser window is < 850, and a maximized window is >
850, so I was easily able to verify both.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [site] main + sandbox site update
Posted by Dirk Verbeeck <di...@pandora.be>.
The css only contains a max height for the header so the header will
resize.
But to support small screens I just added a small javascript to switch
logo if window size < 850.
Larger browser windows or browsers with javascript disabled get the
wide version.
Result can be seen/tested here:
http://cvs.apache.org/~dirkv/commons/index.html
And to make testing easier:
http://cvs.apache.org/~dirkv/commons/size.html
Please test & report browser problems.
-- Dirk
Mark R. Diggory wrote:
> Please review the discussion we had previously on this...
>
> http://www.mail-archive.com/commons-dev@jakarta.apache.org/msg38884.html
>
>
> This is the reason we settled on the selected logo's, because it was of
> less overall impact on the group and accomplished our goals of
> maintaining the site fits within 600x800 as a standard.
>
> Just to point out, with your changes, the height of the header is not
> going to adjust to be narrower because all the individual project logos
> are at 80px height, having the jakarta logo narrower than 80px in height
> is of little benefit, your going to have to press every single project
> to generate new logos that are narrower in height so that the whole
> header is narrower. The downfall of this is that these logos are already
> hard-pressed for space to fit adequately within the header without
> looking totally "crunched".
>
> If your using the /commons-build/commons-site.jsl. It has the height of
> the header hardcoded in the css style to enforce that the same height is
> maintained across the whole commons. It doesn't look like your using it
> for the sandbox site. I'm not complaining, just noticing that theres a
> difference, there are modifications in the commons-build jsl that are
> absent form the sandbox copy.
>
> I'm not trying to be argumentative. We definitely need this kind of
> experimentation and redesign efforts done to the overall site. I think
> everyone agrees these efforts are very appreciated. I just want us to be
> methodical and consensus driven in our approach.
>
> -Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [site] main + sandbox site update
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Please review the discussion we had previously on this...
http://www.mail-archive.com/commons-dev@jakarta.apache.org/msg38884.html
This is the reason we settled on the selected logo's, because it was of
less overall impact on the group and accomplished our goals of
maintaining the site fits within 600x800 as a standard.
Just to point out, with your changes, the height of the header is not
going to adjust to be narrower because all the individual project logos
are at 80px height, having the jakarta logo narrower than 80px in height
is of little benefit, your going to have to press every single project
to generate new logos that are narrower in height so that the whole
header is narrower. The downfall of this is that these logos are already
hard-pressed for space to fit adequately within the header without
looking totally "crunched".
If your using the /commons-build/commons-site.jsl. It has the height of
the header hardcoded in the css style to enforce that the same height is
maintained across the whole commons. It doesn't look like your using it
for the sandbox site. I'm not complaining, just noticing that theres a
difference, there are modifications in the commons-build jsl that are
absent form the sandbox copy.
I'm not trying to be argumentative. We definitely need this kind of
experimentation and redesign efforts done to the overall site. I think
everyone agrees these efforts are very appreciated. I just want us to be
methodical and consensus driven in our approach.
-Mark
Dirk Verbeeck wrote:
> Yes, this logo looks better, is also used on main jakarta site and
> reduces the height of the header.
>
> I know about the small screen issue but my opinion is to optimize for
> the largest group (using a large screen size).
>
> If you want to optimize for a small screen then you also need to change
> the menu etc, so for now I choose for the better looking logo
>
>
> -- Dirk
>
>
> Mark R. Diggory wrote:
>
>> I notice your using the long jakarta logo. Was that an intentional
>> change?
>>
>> -Mark
>>
>> Dirk Verbeeck wrote:
>>
>>> OK, the next step in making commons website more uniform is taken.
>>>
>>> All sandbox components now have a logo, use the commons menu and have
>>> the commons l&f (more or less).
>>> http://cvs.apache.org/~dirkv/sandbox/
>>>
>>> There are also 2 new components:
>>> http://cvs.apache.org/~dirkv/sandbox/feedparser/
>>> http://cvs.apache.org/~dirkv/sandbox/transaction/
>>>
>>> I will also update the main commons pages to include the 2 new
>>> components and to update the wiki link.
>>> http://cvs.apache.org/~dirkv/commons/
>>>
>>> Unless anyone wants a last minute change, I'll push these changes
>>> online in a couple of hours.
>>>
>>> -- Dirk
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [site] main + sandbox site update
Posted by Dirk Verbeeck <di...@pandora.be>.
Yes, this logo looks better, is also used on main jakarta site and
reduces the height of the header.
I know about the small screen issue but my opinion is to optimize for
the largest group (using a large screen size).
If you want to optimize for a small screen then you also need to
change the menu etc, so for now I choose for the better looking logo
-- Dirk
Mark R. Diggory wrote:
> I notice your using the long jakarta logo. Was that an intentional change?
>
> -Mark
>
> Dirk Verbeeck wrote:
>
>> OK, the next step in making commons website more uniform is taken.
>>
>> All sandbox components now have a logo, use the commons menu and have
>> the commons l&f (more or less).
>> http://cvs.apache.org/~dirkv/sandbox/
>>
>> There are also 2 new components:
>> http://cvs.apache.org/~dirkv/sandbox/feedparser/
>> http://cvs.apache.org/~dirkv/sandbox/transaction/
>>
>> I will also update the main commons pages to include the 2 new
>> components and to update the wiki link.
>> http://cvs.apache.org/~dirkv/commons/
>>
>> Unless anyone wants a last minute change, I'll push these changes
>> online in a couple of hours.
>>
>> -- Dirk
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [site] main + sandbox site update
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
I notice your using the long jakarta logo. Was that an intentional change?
-Mark
Dirk Verbeeck wrote:
> OK, the next step in making commons website more uniform is taken.
>
> All sandbox components now have a logo, use the commons menu and have
> the commons l&f (more or less).
> http://cvs.apache.org/~dirkv/sandbox/
>
> There are also 2 new components:
> http://cvs.apache.org/~dirkv/sandbox/feedparser/
> http://cvs.apache.org/~dirkv/sandbox/transaction/
>
> I will also update the main commons pages to include the 2 new
> components and to update the wiki link.
> http://cvs.apache.org/~dirkv/commons/
>
> Unless anyone wants a last minute change, I'll push these changes online
> in a couple of hours.
>
> -- Dirk
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: going with the site update Was: [site] main + sandbox site
update
Posted by Henri Yandell <ba...@generationjava.com>.
On Mon, 31 May 2004, Michael Davey wrote:
> Henri Yandell wrote:
>
> [snip]
>
> >The major change for the prepare page is that I switched it to Cc the PMC
> >for a [RESULT] and not for a [VOTE]. I might be wrong here, but I think
> >that's the intended practice. Looking at the PMC history, Commons are the
> >only ones that Cc them on a vote. Everyone else does results.
> >
> >
> That means that it is now essential that the votes are summarized in the
> [RESULT] post (not just the outcome of the ballot), right?
Yep. Even when the [VOTE] was Cc'd to the PMC, few of the replying votes
were. Which is good, it would have gotten very noisy.
I'll modify that page again to mention that the votes should be summarized.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: going with the site update Was: [site] main + sandbox site
update
Posted by Michael Davey <Mi...@coderage.org>.
Henri Yandell wrote:
[snip]
>The major change for the prepare page is that I switched it to Cc the PMC
>for a [RESULT] and not for a [VOTE]. I might be wrong here, but I think
>that's the intended practice. Looking at the PMC history, Commons are the
>only ones that Cc them on a vote. Everyone else does results.
>
>
That means that it is now essential that the votes are summarized in the
[RESULT] post (not just the outcome of the ballot), right?
--
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
going with the site update Was: [site] main + sandbox site update
Posted by Henri Yandell <ba...@generationjava.com>.
Just so there is an awareness, Dirk's update will take the voted on
charter:
http://cvs.apache.org/~dirkv/commons/charter.html
and some additions I made to the release page based on the IO release.
http://cvs.apache.org/~dirkv/commons/releases/prepare.html
The major change for the prepare page is that I switched it to Cc the PMC
for a [RESULT] and not for a [VOTE]. I might be wrong here, but I think
that's the intended practice. Looking at the PMC history, Commons are the
only ones that Cc them on a vote. Everyone else does results.
Hen
On Mon, 31 May 2004, Dirk Verbeeck wrote:
> OK, the next step in making commons website more uniform is taken.
>
> All sandbox components now have a logo, use the commons menu and have
> the commons l&f (more or less).
> http://cvs.apache.org/~dirkv/sandbox/
>
> There are also 2 new components:
> http://cvs.apache.org/~dirkv/sandbox/feedparser/
> http://cvs.apache.org/~dirkv/sandbox/transaction/
>
> I will also update the main commons pages to include the 2 new
> components and to update the wiki link.
> http://cvs.apache.org/~dirkv/commons/
>
> Unless anyone wants a last minute change, I'll push these changes
> online in a couple of hours.
>
> -- Dirk
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org