Calling All Experts!!

[rawsweets]

Hello all,

I've come up with an incredible method for validating forms with JavaScript. I'm working on documenting the conventions and recommended uses of the system. I've set aside a month for the task.

I'm committed to this system having a wide range of uses for the larger developer community. I can't achieve this without comments and suggestions from other developers. I need help staying on track with the main purpose, or at least documenting the possibilities for later versions. I'm having a blast inventing this system, but it's slow and frustrating to work inside a vacuum.

Please, if you've got the time, are experienced, and enjoy working on high-level JavaScript systems, contact me at rawsweets@yahoo.com. I would like to invite you into a Y! group which is the working group for this documentation phase.

A second draft of the documentation will be uploaded in about one week. The initial draft is there now, along with every thought I have had about the way the concept could be implemented. I'm stuck in a lot of places and could really use some fresh prespectives. I'm using Y! services, to capture everyones thoughts. There are a lot of messages to catch up on as well.

Again, I'm looking for support with the documentation, not coding, of this proposed system. This will allow for coding to go smoothly and provide other developers with a blueprint for extending the concept.

Write me, at rawsweets@yahoo.com, if you would like to participate!

Much obliged! :-)

- rawsweets

[mordred]

Sounds interesting, but where is the URL pointing to the first draft of your incredible form validation project? Would be nice take a closer look at that before deciding whether to participate in the documentation team.

BTW, quite a lame message subject.

[rawsweets]

It's a private work group and you would need to speak with me to join.

BTW: You're quite right.

[mordred]

I don't want to be set on a mailinglist just to inspect some code, that's my primary concern right now. Right now I'm suspecting that your "incredible" method just involves some advanced regular expressions and the onsubmit event handler. Why don't you register your project at sourceforge.net so everyone can see the source if they are interested?

[beetle]

Hey rawsweets. Check out my validation project, fValidate (http://www.peterbailey.net/fValidate/) and let me know how it compares.

[rawsweets]

Do what's best for you. I've chosen to use Y! groups to handle the documentation phase. I am not speculating about any aspect of the coding phase right now.

[rawsweets]

Hey Peter! Great work!

The few people in my group have already analyzed the two, and found it comparable in some aspects. Lots of differences between your implementation and my concept. My concept has specific design principles that your library doesn't fulfill. In the end, my solution may serve a different audience of developers who demand different features to their validator solution. Keep up the good work, and I hope to create something just as fantastic!

[mordred]

Another form API I know of can be found here (http://www.pengoworks.com/index.cfm?action=qForms) , and it's discussion group at http://groups.yahoo.com/group/qformsapi/

rawsweets, it's okay for me if you plan to keep your project secret at the moment, but your statements are making me curious, and I would *really* like to see the beta (or alpha, if that's the case) version if possible.

[rawsweets]

There is no alpha or beta code, because this is the documentation phase. If all goes as planned, the final documentation will be made available...

If the coding phase is done publicly (eg, sourceforge.net), you will be able to see every version of this system. Either way, once the code is used publicly... it's yours.

I am aware of qForms, and the group has analyzed it as well. There are a number of differences between the two, and my concept is designed for a different audience of developers.

[nolachrymose]

Just a question: why are you writing a documentation for nonexistent (at the moment) code? Maybe you should consider doing the most important part of a project first: the programming.

Happy coding! :)

[rawsweets]

Your question seems to stem from a confusion over what I'm doing.
I am documenting a concept. Perhaps a better phrase would be "writing the specification for the system to be coded". The name won't be changed, since the group is clear about our task, and your confusion appears to be in the minority.

We may simply have different programming principles. I'm comfortable with specifying the requirements of a program before I begin coding. You're comfortable programming however you code. No reasons needed on my part, and explaining mine to you are out of scope for this thread.

I won't continue this discussion here, but you are welcome to contact me with any further questions.

[brothercake]

dfkg dk 82 sds &"&^ skkjskj kjhd ... lkskjsdfkj k :) kskin l;aoiwqmdn lklwo 989**nsk kahbsdk .. eon ... 028dhjnks .... :rolleyes:

skjfs //// snmi kdkwnjv o onem ll;xife lo 937 m && msj; ms, osinj ls, owsomns , psdo93j ((78 msdfsjk ) lkjsdcam :D

[johnnigrey]

Hello,

My name is John. I am new to java script. This is fun and I would appreciate time to join.

My email is jg@wcbn.com.sg. My english writing is not very good, but I read good.

Thank you.

[beetle]

Hey, whatever happened to this "incredible method"??

:D

/curious

[rawsweets]

I had been coding this for some time, but because of financial concerns it'll remain on the shelf for the next four months, at least.

- rawsweets

[RadarBob]

Something is rotten in the state of Denmark
------ Hamlet

[Quiet Storm]

LOL!

Mc Donald's is hiring!

Maybe you should keep your 'top secret' code for the nubies! :rolleyes:

[brothercake]

This thread has a strange vibe; I'm closing it, just in case.

Please PM me if anyone wants to object.