Re: Structs 2 feedback

[Brian Pontarelli]

Me likey!

-bp


[EMAIL PROTECTED] wrote:

That is actually a big improvement over the current homepage.  +1!!!

-----Original Message-----
From: Musachy Barroso [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 08, 2007 11:07 AM
To: Struts Developers List
Subject: Re: Structs 2 feedback


Because I'm artistically challenged I got help from a friend of mine to get
mockup done, check it out here:

http://picasaweb.google.com/musachy/

that's an idea of what I had in mind.

thanks Vlad!
musachy

On 2/8/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:

Phil is right, what I meant with "open to anyone", was, open to anyone
that wants to help :).

I think some of the most important things for new users are:

1. Features List
These are on the home page, quite visible, no problem.

2. Getting started
The whole difference between "Tutorial" and "Guides" is rather confusing
for new users, and navigating the wiki is not a simple task. There is also
the idea of "Documentation" whose home page, is the getting started.

I think the links under documentation on the homepage should be:
Getting Started -> Bootstrap tutorial    (I'll try to spend time on this
one, pulling content from the wiki, help wanted :) )
Tutorials           -> Keep current link     (We should link to Matt's
tutorial on that page)
FAQ                   -> Keep current link
Developers Guide -> Keep the link       (I know it is just a rename, but
at least a user will note the difference between it and the "Getting
Started")
Wiki Pages            -> Link to wiki          (currently, it is under
"Support")

The "Release Notes" should be a link, where the download is, for each
download, not under documentation. Right now if you click on the release
notes you will see the release notes for 2.0.6, but you won't find a
download for 2.0.6 anywhere.

3. Downloads
Clicking on the "Releases" link will take you to a page, that has releases
for both S1, and S2, but the user was already on S2, no reason why he/she
should be seeing S1 releases listed there. I think there should be a
"Downloads" category on the menu with these links:
Latest Stable Release     -> Link to download page for the latest stable
release, which has a link to the release notes.
Older Releases                -> Other builds, releases, etc (just S2)

On the home page, there should be a "Download Now" and a "Get Started"
image , that pops out of the page (to the eye). Open Office's website is a
good example: http://www.openoffice.org/. If you are a new user, you will
find the links to what you need easily (Download + Getting Started), if you
are a user already, you will find your way around the navigation menu.

that was more than 2 cents right? :)

regards
musachy

On 2/8/07, Philip Luppens <[EMAIL PROTECTED] > wrote:

The wiki's not open to anyone - you need the karma ;-)

But you're right, Musachy. The docs might indeed be geared towards
experienced developers rather than newcomers. I've heard from quite a
few they like the S1 user documentation - maybe we can copy its
structure ? I'm all for it [1].

Cheers,

Phil

[1] https://issues.apache.org/struts/browse/WW-1721

On 2/8/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:

About the documentation I'd like to point out that I had a similar
experience. The wiki is great for users that already know the

framework and

are looking for a reference, or specific information, but for new

users it

is quite hard, I always found the "User Guide" on S1 quite useful. The

good

thing is that the information is there already (on the wiki), it is

the

structure the one that is not easy to follow for new users. The wiki

is open

to anyone, so help is welcome :)

regards
musachy

On 2/7/07, Brian Pontarelli <[EMAIL PROTECTED]> wrote:

Looks like it could be an issue with the xwork2 2.0-beta1 JAR file

from

the 2.0.1 beta bundle conflicting with the nightly because there

doesn't

seem to be an xwork JAR in with the nightlys. Again, this is pretty
cumbersome to get working because of the numerous JAR files floating

around and the versioning and dependency management. I'll grab the

final

XWork 2.0 release from OpenSymphony and try it with the nightlys,

but I

would suggest creating nightly bundles if the dependencies are

tightly

coupled.

However, last night the build was broken in subversion, so I'm not

sure

how the nightlys are working. I'll try the build again tonight or
tomorrow morning to make sure I'm not smoking crack or anything.

There

isn't much build information that I could find except for the 'mvn
install' command from the 'Source Code' page, so I could be missing
something there as well. Could also be beneficial to have some build

info in the docs if there are more steps. Plus, with the memory

issue

I've encountered, might be nice to have something on that if it

isn't a

bug and builders do need to increase the maven memory maximum to

around

256M.

-bp


Nate Drake wrote:

Brian Pontarelli <brian <at> pontarelli.com> writes:

3. The documentation for Struts 2 contains references to zero
configuration and the web.xml configuration file also contains

this

stuff. There are also a number of references to all the

annotations.

These are not available in the 2.0.1BETA JAR files and therefore

I had

a

hard time using them ;) I did find them in the nightly snapshots,

which

aren't functional. I would keep the documentation inline with the

latest

beta and not the latest nightly snapshot. Anyone who wants

bleeding

edge

will be willing to look at the source to see new stuff or build

the

latest snapshot docs themselves.

What seems to be broken with the nightlies?  Zero configuration is

working

ok for us with the 2.0.5 build.

---------------------------------------------------------------------

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

--
"Hey you! Would you help me to carry the stone?" Pink Floyd

--
iDTV System Engineer
"Always code as if the guy who ends up maintaining your code will be a
violent psychopath who knows where you live." - John F. Woods

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

--
"Hey you! Would you help me to carry the stone?" Pink Floyd

smime.p7s
Description: S/MIME Cryptographic Signature