Simon Allaway wrote:
> [EMAIL PROTECTED] wrote:
> >
> > You have to give me a friggen break...you gave up on ECS because you
> > couldn't compile our testing classes?
>
> No, it wasn't the compilation of the testing classes. I gave up because
> there was no useful documentation to help me get anything done. But I do
> admit that it didn't fill me with confidence when they didn't compile.
> Not a good start.
>
The testbed stuff now compiles just fine, the 'fix' involved removing the
imports for openxml, thats it delete 4 lines of code. TestBed.java is just
that 'our' testbed it isn't gauranteed to compile or work at any given
moment, thus the name testbed. It does however contain useful examples if
you want to look at the source, and take the time to understand what they
do. Like jon said this isn't rocket science.
>
> The whole Javadoc thing comes from a certainly more hard-core
> programming environment.
> I'd suppose a large proportion of web developers have not moved into
> that field via programming. Rather they have come from scripting.
Javadoc is really a way of tagging programmers comments so that they can be
turned into documentation. Even people from scripting environements should
appreciate the use of comments, you also get something with ecs you don't
get with htmlKona and that is the source, the power to fix/change/adapt the
code to fit your needs ( and perhaps those of others )
>
>
> I myself have been scripting ASP applications/components for years now,
> but I went the servlet route to make sure I didn't hang myself with the
> Micro$oft rope, thus limiting my career options. Servlet technology
> itself has plenty of good tutorials/examples and therefore I have
> sucessfuly built servlet based database driven sites. So far so good.
Me and Jon both do this in our 'spare' time, and quite honestly only a
handful of the users of ecs have contributed anything back to the project.
I ( like most other developers I know ) despise creating documentation, and
am not apt to do anything that i despise in my 'spare' time. If someone
out there wants to pay me to create documentation for ecs I might do it.
If someone out there wants to contribute and create a more useful set of
documentation we would be happy to add it to the project.
>
>
> So, I see talk about HTML generation, and most of it talks about
> htmlKona which is no longer available as a standalone set of classes.
> This leads me to ECS. On the surface it looked great, and I don't
> dispute it's functionality, please dont get me wrong there. But in
> simple terms I have to ask myself a question: "How much time can I
> justify spending on learning a new method/technology/application to get
> the job done?" The answer to that 'ease of adoption' question in this
> case was htmlKona.
It isn't all that difficult to figure out, least i didn't think so if you
kinda know java and you know html you ought to be able to figure it out.
Lets create a table. 10 rows deep 5 columns wide.
========================================
import org.apache.ecs.html.Table;
import org.apache.ecs.html.TR;
import org.apache.ecs.html.TD;
public class Test {
public static void main(String[] args) {
Table mytable = new Table();
for (int x = 0 ; x < 10 ; x++) {
TR row = new TR();
for ( int y = 0 ; y < 5 ; y++ ) {
TD col = new TD();
col.addElement(Integer.toString(x) + ":" + Integer.toString(y));
row.addElement(col);
}
mytable.addElement(row);
}
mytable.output(System.out);
}
}
result is
<table><tr><td>0:0</td><td>0:1</td><td>0:2</td><td>0:3</td><td>0:4</td></tr><tr><td>1:0</td><td>1:1</td><td>1:2</td><td>1:3</td><td>1:4</td></tr><tr><td>2:0</td><td>2:1</td><td>2:2</td><td>2:3</td><td>2:4</td></tr><tr><td>3:0</td><td>3:1</td><td>3:2</td><td>3:3</td><td>3:4</td></tr><tr><td>4:0</td><td>4:1</td><td>4:2</td><td>4:3</td><td>4:4</td></tr><tr><td>5:0</td><td>5:1</td><td>5:2</td><td>5:3</td><td>5:4</td></tr><tr><td>6:0</td><td>6:1</td><td>6:2</td><td>6:3</td><td>6:4</td></tr><tr><td>7:0</td><td>7:1</td><td>7:2</td><td>7:3</td><td>7:4</td></tr><tr><td>8:0</td><td>8:1</td><td>8:2</td><td>8:3</td><td>8:4</td></tr><tr><td>9:0</td><td>9:1</td><td>9:2</td><td>9:3</td><td>9:4</td></tr></table>
again, not to terribly difficult.
>
>
> I am quite happy to send you the kinds of tutorials/documentation that I
> found on the Weblogic site. They didn't bother trying to get me to read
> the somewhat abstract API for their classes, they simply stated 'if you
> want to do this, do this'. Even the book I bought , 'Java Servlet
> Programming' doesn't bother to explain the API docs. In fact I've yet to
> find anything useful from those things, and I'm not stupid, I've been in
> this game for more than ten years.
Thus the difference in being paid to create something and doing something
because you want to do it. I agree weblogic probably has the best
documentation I have ever seen or used with any product, and if you want to
pony up and spend the 10k + for a license be my guest. If you don't ecs is
an alternative.
>
>
> So, to that end I make a plea on behalf of all us 'learn-on-the-fly' web
> developers: 'Please, please, please provide useful documentation and
> example'
On the behalf of developers who contribute their own time to create
something that can be used by the community for free and at no profit to
themselves. Contribute back to the project. If you guys want more
documentation start creating it and sending it to me or jon, I simply have
too many other things I enjoy doing in my 'spare' time to do something I
absoluty despise
>
>
> To paraphrase: "If you give a man a fish he eats for a day, but if you
> teach him to fish, he eats for a lifetime"
Opensource software is about scratching an itch. I personally scratched
until i drew blood when creating ecs, and no longer have much of an itch
left.
-stephan
--
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
