Venkat,
This is looking very good. I have a few minor comments. None of these
are showstoppers for making the new Web site live, but we should address
them as soon as possible after publication.
1. There are formatting problems on the java_sca_overview.html page.
Some of the subsections (in Courier font) of "Packaging a Standalone
Tuscany Application" and "Building a Tuscany Web Application" have
completely lost their original formatting/spacing/line breaks and
are difficult or impossible to understand. The subsections starting
and ending with the following text have this problem:
META-INF/MANIFEST.MF .... resources
WEB-INF/default.scdl .... see below
<listener> <listener-class> .... </servlet-mapping>
<?xml version="1.0" .... </java>
These need reformatting using explicit <br /> tags, or in the second
case, a <table>.
2. On the same page, there are some problems with the list of files that
are publshed to the maven repository.
a. The first file in the list:
org/apache/tuscany/sca/parent/1.0-incubator-M2/parent-1.0-incubator-M2.pom
was accidentally removed when the <pre> formatting was changed to
use <font size="-2" face="Courier New">.
b. With the new formatting, this list of files needs an explicit
<br /> after each line to prevent multiple files appearing on
the same line in a wide browser window.
c. The font size "-2" for the list of files in the maven repository
is very small and hard to read in my browser. Increasing
this to "-1" solves the problem, but makes the font a bit larger
than it was with the previous <pre>...</pre> markup.
3. It would be good to have real content on the SCA Releases and SDO
Releases page. The SCA Releases page is quite easy to fix, since we
have suitable html content covering M2 in the file
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca-samples/1.0-incubator-M2/readme.html
4. I've created a bat file (see separate posting) that can generate
online javadocs for M2 in a form that is suitable for publishing
on the Web site. These could be linked from the SCA Docs and
SDO Docs pages.
5. On the Tuscany Java page, the Checkout and Build Tuscany section
has obsolete instructions that don't work any more. These should be
replaced by links to the SCA Java, SDO Java, and DAS Java pages.
For SDO and DAS, these have the correct instructions. For SCA,
the correct instructions for a full checkout and build need to be
added to the SCA Java page.
6. In section 5 of the Getting Started page, it would be useful to have
links to the SCA Java, SCA C++, SDO Java, SDO C++, and DAS Java pages.
This is the right place in the Getting Started sequence to show these
links, because the user should read these pages (as appropriate)
after doing the downloads and before attempting to run samples.
7. The DAS Releases page talks about downloading M1 within the M2 section
(cut and paste error). Also, it is probably better to put the most
recent release first, as we are doing on the Downloads pages.
8. It would make sense to remove the M1 and M2 release content from the
DAS Java page now that we have it on its own DAS Releases page.
9. On the News page, it would be good for the links to the download pages
from C++ M2, C++ M1, and Java M1 to not go to the top of the download
page but to go to a correctly positioned label within the page.
Simon
Venkata Krishnan wrote:
Hi all,
Thanks for looking this up and giving in your feedback. I have taken in
the
comments from each of you and have made the necessary changes. Please
check
them out at http://people.apache.org/~svkrish/tuscanySite/site-publish/.
Unless I hear any significant change to be made, I plan to commit this
tomorrow and hope the site refreshes when folks in the US start their day.
Thanks
- Venkat
On 12/21/06, Luciano Resende <[EMAIL PROTECTED]> wrote:
Simon Nash wrote:
>5. The Documentation page lists 0.9 specs, and points to
boulder.ibm.com.
> It's probably best to just remove this list of specs and let people
> go via osoa.org via the links that you have. It would make sense to
> also remove the links to white papers as these are on osoa.org.
> I wouldn't remove this page altogether as it provides a place to
> put references to documentation that applies to Tuscany as a whole,
> rather than the individual technologies of SCA/SDO/DAS. (Hopefully
> there will be more of this Tuscany-related material in the future.)
I think we still should have the links here, probably poiting to
osoa.orginstead of the
boudler.ibm.com, as we have little more description saying what is
discussed
in each spec, where in the osoa.org, we just have the links to the spec
and
that's it.
If we really decided that we don't want them here, we should have it
explicitly saying something like "The specifications is available in the
osoa.org and you can find them at <direct link like
http://www.osoa.org/display/Main/Service+Component+Architecture+Specifications
>
" . This would avoid beginners to get lost trying to find the right
info...
I think this is also true for any other resources that is available at
osoa.org
--
Luciano Resende
http://people.apache.org/~lresende
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
