1. meta info in EU: was what standards...
- Posted by Alan Tu <ATU5713 at COMPUSERVE.COM>
Dec 20, 1998
-
Last edited Dec 21, 1998
Thanks for your reply, Jeffrey. I now know what you're saying.
What you are saying is an "extention" of EU, kind of like meta tags in
HTML. Again, I was just confused, and re-itterate that the standards are
the specs (language definition) which RDS sets, with our input, of course!
I think that there must be at least a prototype of an update software.
Right now there's no EU prog that can really do Internet/web operations, as
I understand it. What I suggest is that library routine authors can maybe
define a global constant and then users of that routine can do a
type-check, aborting if necessary. Good idea.
There is no such thing like this in other languages, including HTML, that
"mandates" recording of author/date info. Everything in HTML <meta> is
non-standard, there is no standard, by W3C's admission, in HTML 4.0, of
what goes into a meta tag. So I think this may be voluntary?
Alan
2. Re: meta info in EU: was what standards...
- Posted by JJProg at CYBERBURY.NET
Dec 20, 1998
-
Last edited Dec 21, 1998
EU>Thanks for your reply, Jeffrey. I now know what you're saying.
EU>What you are saying is an "extention" of EU, kind of like meta tags in
EU>HTML. Again, I was just confused, and re-itterate that the standards are
EU>the specs (language definition) which RDS sets, with our input, of course!
EU>I think that there must be at least a prototype of an update software.
EU>Right now there's no EU prog that can really do Internet/web operations, as
EU>I understand it. What I suggest is that library routine authors can maybe
EU>define a global constant and then users of that routine can do a
EU>type-check, aborting if necessary. Good idea.
EU>There is no such thing like this in other languages, including HTML, that
EU>"mandates" recording of author/date info. Everything in HTML <meta> is
EU>non-standard, there is no standard, by W3C's admission, in HTML 4.0, of
EU>what goes into a meta tag. So I think this may be voluntary?
EU>Alan
Yes, it would be voluntary. It would just allow compliant Euphoria
programs to take advantage of the "standards" so that most things would
be compatable.
Another example of the possibilities of "standards" would be
documentation. Right now, there is standard documentation (library.doc
etc.), and then there are various documentation formats in diferent
files for pretty much every Euphoria program. Wouldn't it be nice to,
say, be able to easily view the documentation for any file in some
standard format. There could be a standard documentation format that
some future Euphoria editor could take advantage of so you could, for
example, add to ed.ex so that when you ask for help, it could not just
provide library.doc and the other standard help files, but also the
documentation for any library you spesify.
Jeffrey Fielding
JJProg at cyberbury.net
http://members.tripod.com/~JJProg/
3. Re: meta info in EU: was what standards...
- Posted by JJProg at CYBERBURY.NET
Dec 20, 1998
-
Last edited Dec 21, 1998
More on my last message:
I could, for example, create a version of HTML called
SuperDynamicHTML+++ and write a great web page based entirely on it, but
since it is almost completely incompatable with standard HTML, about 0%
of the people visiting my site would be able to see anything.
Another example would be the metric system. There is no requirement that
every scientist use the metric system, but pretty much every scientist
does because it is a "standard".
Jeffrey Fielding
JJProg at cyberbury.net
http://members.tripod.com/~JJProg/
4. Re: meta info in EU: was what standards...
For documemtation, version control, author, etc. I see some posibilities,
however before I and most will accept a so-called standard (read: use it),
make a *handy* tool that does such things for you.
For example, incorporate it with David's TexGUI.
The past has learned us, that when you make a *good* tool as the first, it
will become the standard, look at Micheal Bolin's keyread.e or Jiri's
Font.e, does any one use any alternatives ? Or is any one making any ?
I rest my case. You make a tool/incorporate into an editor, make a special
documentation editor that handles standard layout, (and maybe allows us to
save it in html/txt/etc.) and if its good enough, everybody will start using
it. Just dont go about: but its a good standard. If the tool isnt good
enough, we are better of using an already existing standard, namely: a
readme.txt where we use simple 'book' formatting and an file_id.diz
Maybe you want to work together with Hawke & Blackdog (the ppl of the
EuServer) that are currently trying to make a windows 'environment' to edit
an Euphoria program, but in such way you can work on an Euphoria program
with more people online. So much more project managing (author, version
control) ..
Ralf
