[TheJerk]

Wow, talk about topic derailment.

I agree with nujackk. Look, I've been programming HTML, PHP, etc., etc., etc. for quite some time now. But it's not the issue of whether or not examples are easy to follow or the directions are user friendly for me - follow the common standard if you're going to write documentation. Any type of writing has, since the beginning of the age of reason, had three common elements, and were always more or less in order: beginning, middle, end. In the case of this manual, who's to say which is which?

My $.02, not that it matters. Honestly, I don't have time to figure out the documentation or how this application works, so yes, I'll be moving on. But you asked the question....

[hohner]

I had a little trouble understanding how to write the xml at first, but managed to work it out using a combination of examples which come with the xplode program and also by reading working xmls contributed in posts by forum members and by also reading the manual.
I think the manual (pdf) which comes with XPlode is well written, however I can understand how someone with no prior knowledge of writing xml code could feel lost. I found myself skipping back and forth through the chapters of the manual rather than reading it in the order it was written. It's a difficult job to write a manual of any kind, it's even harder to write it so that many different people who all have different thinking patterns can use it well. I think you did a good job
One thing which I think helps very much is when a question is posted and the response is "read the manual". I am guilty of posting such a question and I'm kind of glad that I got this response cause I think it's easier to understand the answer if you take the time and effort to work it out for yourself rather than just be hand fed the answer.

[TheJerk]

I really meant no disrespect by my post, so let me clarify. I know writing a manual's no easy chore. And more often than not, programmers are NOT writers and vic versa. It's usually better that if you want a good manual written, you give the responsibility to someone who's good at writing them. Not always a plausible solution, I know.

[Wraith]

It wasn't specifically supposed to be a manual, just a reference for what people needed to look up.

Getting it to work is described better in the unattended guide, and I've always said that people should be looking at that and knowing how the methods described there work before even attempting to try XPlode.

[Alanoll]

slight problem....
a. the Unattended guide doesn't really have a section that goes through detailing all the parts of setup you can launch something form...
b. the page for XPlode just tells them to read your PDF

Now if you're little project for was done.... and you weren't off doing school stuff right now...

[Wraith]

I meant that after you'd used CMDLINES.TXT or RunOnce or whatever, you'd know how to launch XPlode and get it running.

Not how to run stuff from XPlode in the first place - that's what the examples and the PDF are for.

[S0mE0nesMiNd1]

I agree with Wraith....you dont need a manual to describe this stuff..... hmmmmm theres a tag called <program>.....common sense tells you it has something to do with the program you wish to run in that <execute> tab....therefore, you would be <EXECUTING> a <PROGRAM>. You dont need a manual to describe every function.....Its common sense.

[Wraith]

Unfortunately, a lot of people in this world don't have common sense.

[Maelstorm]

Agreed. Look at the EULA fiasco.

[Nanaki]

I agree, I tried XPlode in the beginning and I gave up. After a month or so (when I actually made my first uA disc with RunOnceEx) I tried XPlode and it only took a couple of minutes to make it work.

[nujackk]

The point of guides is to get past the so called common sense issue.
My common sense told me to not bother with xplode, because it did not give me a way to get started!
It didn't say look at the examples right from the start. ( again going back to putting in a simple how to get started section right at the begining )

My common sense said WPI is better because I could see and figure out where to get started.

I try not to be rude, especially since I will probably need most of you to help me at some point, But....

Instead of being smug jerks about it, take the constructive critizism and simple add a section at the begining telling us where and how to start.
How hard is that?

[S0mE0nesMiNd1]

No, thats common laziness. If you dont even wanna to examine the code, thats PURE laziness. You just admitted it, you were too lazy to examine the code.

[Alanoll]

nujackk, on Apr 17 2005, 04:23 PM, said:

The point of guides is to get past the so called common sense issue.
My common sense told me to not bother with xplode, because it did not give me a way to get started!
It didn't say look at the examples right from the start. ( again going back to putting in a simple how to get started section right at the begining )

My common sense said WPI is better because I could see and figure out where to get started.

I try not to be rude, especially since I will probably need most of you to help me at some point, But....

Instead of being smug jerks about it, take the constructive critizism and simple add a section at the begining telling us where and how to start.
How hard is that?
<{POST_SNAPBACK}>

Here's the problem with that statement....

I expect you to START and understand the process of batch file/runonceEX before moving on to XPlode/WPI/WIHU or similar ADVANCED methods. Since we EXPECT you to know how to start something doing setup, there is NO NEED for a repeat of it in the ADVANCED methods. Wait, that's that you're asking? What about the switches for XPlode? Well...that's what the documentation is included for. It details the switches, but we have no need to specifically say "Enter this into CMDLINES.TXT to have XPlode start during setup" as we EXPECT you to already know this once progressing to XPlode or similar. Even WPI doesn't tell you to put it in CMDLINES.TXT.

Perhaps I've gone on a complete tangent to what you were trying to say, I don't know. But this is my general way of teaching and doing things. I start peopel with the basics, prior to advanced stuff. As a analogy, let's take math. It'd be like a Calculus teacher explaining how to add two numbers. They don't, they expect you to have already learned that.

XML is one of the easiest languages to pick up, especially XPlode XML as it's mre of a simplified form. XML isn't really a language anyway. Just a way to store data and access it easily.

We tell you to start looking at the examples, and such. By the way, you never actually responded to my other XPlode page that didn't make it into the guide? Is that helpful?

[nujackk]

No the only thing I admited was I didn't know where to start.
And if you would read the entire thread, you would see that, I am admittedly code impaired, and trying to learn.
So the assumption that I would know what to do just by looking at the code is silly!!

I have answered the question, if you would rather insult and be smug low self esteem jerks then please feel free just don't ask the question if you can't take the answer.

I would think the whole point of this thread is to find a way to make xplode
not put us (us being the less coderifc amoung you gods ) off.

I have said my peace, I will only look at this one more time to make note of the one's who feel the need to insult me, to be sure not to ignore them in the future.

[nujackk]

Alanoll, on Apr 17 2005, 03:48 PM, said:

nujackk, on Apr 17 2005, 04:23 PM, said:

The point of guides is to get past the so called common sense issue.
My common sense told me to not bother with xplode, because it did not give me a way to get started!
It didn't say look at the examples right from the start. ( again going back to putting in a simple how to get started section right at the begining )

My common sense said WPI is better because I could see and figure out where to get started.

I try not to be rude, especially since I will probably need most of you to help me at some point, But....

Instead of being smug jerks about it, take the constructive critizism and simple add a section at the begining telling us where and how to start.
How hard is that?
<{POST_SNAPBACK}>

Here's the problem with that statement....

I expect you to START and understand the process of batch file/runonceEX before moving on to XPlode/WPI/WIHU or similar ADVANCED methods. Since we EXPECT you to know how to start something doing setup, there is NO NEED for a repeat of it in the ADVANCED methods. Wait, that's that you're asking? What about the switches for XPlode? Well...that's what the documentation is included for. It details the switches, but we have no need to specifically say "Enter this into CMDLINES.TXT to have XPlode start during setup" as we EXPECT you to already know this once progressing to XPlode or similar. Even WPI doesn't tell you to put it in CMDLINES.TXT.

Perhaps I've gone on a complete tangent to what you were trying to say, I don't know. But this is my general way of teaching and doing things. I start peopel with the basics, prior to advanced stuff. As a analogy, let's take math. It'd be like a Calculus teacher explaining how to add two numbers. They don't, they expect you to have already learned that.

XML is one of the easiest languages to pick up, especially XPlode XML as it's mre of a simplified form. XML isn't really a language anyway. Just a way to store data and access it easily.

We tell you to start looking at the examples, and such. By the way, you never actually responded to my other XPlode page that didn't make it into the guide? Is that helpful?
<{POST_SNAPBACK}>

As for your xplode page that didn't make into the guide, I thought I did respond and say it was, I aslo asked why it was not in the guide.
as for the rest of the statement, the main problem is that assumptions are being made.
I actually came across xplode and wpi, and this sight, by way of nlite's website.
And never actually saw the guide until after much explorering.
So I was put off by xplode before ever seeing a guide, thus you point doesn't work.
without the guide I was able to figure out wpi and nlite( who couldn't figure out nlite right) xplode just made no sense and Plainly did show me where to start.

You Asked a question I gave an answer and instead of taking an objective look at it and comming up with way to do it or just not. I get insulted

what's that? that's not helping me, that not teaching me how to use it.
I am coompletely self taught, I know how to read guides I can figure this out on my own, that is not the point. I simple answer the question "why do you consider xplode hard to use?"

That being said you guys figure it out. I wrote it off a long time ago since I have no need for the pretty gui anyway.

thx

[S0mE0nesMiNd1]

No one is insulting you. The only thing you hear from me or anyone else is facts. If I wanted to insult you I would turn 10 all over again and cause a roar. Not having the willingness to look and compare is LAZINESS if thats not, then I dont know what is. The only person insulting others is YOU.

[Wraith]

Enough.