>You may have misunderstood my post.
Yes, I did. My apologies =;^)
>so the question is, is documentation that looks like this:
> http://www.your-site.com/~rinfo//examples/apiNew/dynapi_8js.html
>In a usable format or not. (Bear in mind that I tried every available
>command, so the output is not p
Hi,
You may have misunderstood my post.
The point of the test I did, was that I did NOT use a second version of the
source-code.
I commented the sourcecode in the same way you and Martin recommended, and
let Doxygen produce the docs from the original commented dynapi code.
so the question is, is d
I like your suggestion with the @ symbol and * to start each line. Perhaps I
can expand on your suggestion and develop a final src comment standard so we
can finaly begin commenting the src.:
What every file should begin with:
/**
* DynAPI Distribution
* The DynAPI Distribution is distributed u
Totally agree with you. two versions is one too much to maintain
and since DynAPI requires some Javascript-knowledge it shouldn't
be too hard to understand the Doxygen-generated docs.
we could extend the documentation with own keywords, not yet
supported by Doxygenm, but could be supported if we
>I presume it's a little quite around the documentation topic because
>everyone's busy writing the docs :o)
Accually I have been coding the documentation structure as I have originally
outlined with the different modules (intro, reference, examples, tuturials).
I don't have enough coded to provid
Keep on doing the rest of the documentation this way. It's perfect! :)
__
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1
___
Dynap
wow, I'm impressed.
___
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://www.mail-archive.com/[email protected]/
Hello,
This looks good. I think it should replace the current
inline.js in the DynAPI Core
Can that be done?
--
Raymond
--- Doug Melvin <[EMAIL PROTECTED]> wrote:
> And here it is (for the second time)
> I've renamed the extension as the sourceforge mail
> servers are now bouncing
> messages
hi,
I presume it's a little quite around the documentation topic because
everyone's busy writing the docs :o)
I did some testing on Doxygen.
I don't think it's feasible to update two versions of our source-code, and
to be honest, the docs generated from the Java version of our source code
did not
And here it is (for the second time)
I've renamed the extension as the sourceforge mail servers are now bouncing
messages with attached .js files//
just rename inline.j_ to inline.js
- Original Message -
From: "Doug Melvin" <[EMAIL PROTECTED]>
To: "Richard Bennett" <[EMAIL PROTECTED]>; "Q
I think your sourceforge branching idea is great.
Have one main branch, that only gets updated with tried and tested code from
the side branches, and use the side branches to develop widget packs, and
alternate code structures.
The releases would only include code from the main branch, and one of
Hi guys,
Opera6 beta is out, for those who missed it:
http://www.opera.com/pressreleases/2003.html
LiveConnect
Opera now has support for LiveConnect, to enable scripting of Java applets
and plug-ins through JavaScript.
Standards-Compliance
Opera continues its commitment to the standards a
Mailserver was down yesterday, so I don't know if this got through...
Bfff there are so many thinks I'd like to comment that I don't know
where to start. Whereas the concept is nice from a Software Engineering
point of view, I'm not sure it is the best way to go IN THIS PR
Thanks, you are right. Before reciving this email I entered bugzilla
page to see that is a reportered bug recently reopened.
Is seems not to be fixed in the release of Mozilla 0.9.6 :_(
>Forget the setTimeout. Sometimes it works, sometimes it doesn't.
>It is not an DynAPI bug.
>Mozilla has proble
14 matches
Mail list logo
