1. Yay or Nay? Framed reference manual
- Posted by Jeremy Cowgar <jeremy at c?wg?r.com>
May 05, 2008
-
Last edited May 06, 2008
http://jeremy.cowgar.com/euphoria/index.htm
I have not committed this to SVN yet. Would like to have some feedback.
--
Jeremy Cowgar
http://jeremy.cowgar.com
2. Re: Yay or Nay? Framed reference manual
- Posted by Greg Haberek <ghaberek at gm?i?.com>
May 05, 2008
-
Last edited May 06, 2008
Jeremy Cowgar wrote:
>
> <a
> href="http://jeremy.cowgar.com/euphoria/index.htm">http://jeremy.cowgar.com/euphoria/index.htm</a>
>
> I have not committed this to SVN yet. Would like to have some feedback.
Yay. I think it looks great. I'm not too keen on frames though. Perhaps a
two-column DIV layout would work just as well?
-Greg
3. Re: Yay or Nay? Framed reference manual
- Posted by Jason Gade <jaygade at ?ahoo?com>
May 05, 2008
-
Last edited May 06, 2008
Greg Haberek wrote:
>
> Jeremy Cowgar wrote:
> >
> > <a
> > href="http://jeremy.cowgar.com/euphoria/index.htm">http://jeremy.cowgar.com/euphoria/index.htm</a>
> >
> > I have not committed this to SVN yet. Would like to have some feedback.
>
> Yay. I think it looks great. I'm not too keen on frames though. Perhaps a
> two-column
> DIV layout would work just as well?
>
> -Greg
Agree -- columns good, frames bad.
--
A complex system that works is invariably found to have evolved from a simple
system that works.
--John Gall's 15th law of Systemantics.
"Premature optimization is the root of all evil in programming."
--C.A.R. Hoare
j.
4. Re: Yay or Nay? Framed reference manual
- Posted by Jeremy Cowgar <jeremy at ?owgar.?om>
May 05, 2008
-
Last edited May 06, 2008
Greg Haberek wrote:
>
> Yay. I think it looks great. I'm not too keen on frames though. Perhaps a
> two-column
> DIV layout would work just as well?
>
Greg, I am no HTML/CSS guru. Can you make a div layout w/o fancy Javascript
where the navigation div stays on the side, no matter how high or low you scroll
in the docs? For instance, you can click on Language Manual, scroll down a
substantial amount and with the frames, the navigation frame will still be right
there at your finger tips.
If there are other ways of doing this, I'm open for suggestions, but I think
having the links there for quick access is the major benefit.
--
Jeremy Cowgar
http://jeremy.cowgar.com
5. Re: Yay or Nay? Framed reference manual
- Posted by c.k.lester <euphoric at ?kl?ster.com>
May 05, 2008
-
Last edited May 06, 2008
Jeremy Cowgar wrote:
>
> <a
> href="http://jeremy.cowgar.com/euphoria/index.htm">http://jeremy.cowgar.com/euphoria/index.htm</a>
>
> I have not committed this to SVN yet. Would like to have some feedback.
My feedback: nice! keep.
6. Re: Yay or Nay? Framed reference manual
- Posted by ChrisBurch3 <crylex at gmail.?om>
May 05, 2008
-
Last edited May 06, 2008
Frames - old fashioned but functional, useful, easy to maintain, dead easy to
navigate.
Keep it like this. Aye. Yay.
Chris
7. Re: Yay or Nay? Framed reference manual
- Posted by Jeremy Cowgar <jeremy at ?owgar.c?m>
May 05, 2008
-
Last edited May 06, 2008
Greg Haberek wrote:
>
> Jeremy Cowgar wrote:
> >
> > <a
> > href="http://jeremy.cowgar.com/euphoria/index.htm">http://jeremy.cowgar.com/euphoria/index.htm</a>
> >
> > I have not committed this to SVN yet. Would like to have some feedback.
>
> Yay. I think it looks great. I'm not too keen on frames though. Perhaps a
> two-column
> DIV layout would work just as well?
I've updated the style a bit to make it more visually appealing. Prior to was
just a let's see what happens.
But, please, if you have an easy way to make the navigation column always
visible, let me know.
--
Jeremy Cowgar
http://jeremy.cowgar.com
8. Re: Yay or Nay? Framed reference manual
- Posted by jacques deschênes <desja at g?obetrotter?net>
May 05, 2008
-
Last edited May 06, 2008
Firefox as no problem with frames so I don't,
I vote Yay.
Jeremy Cowgar wrote:
>
> <a
> href="http://jeremy.cowgar.com/euphoria/index.htm">http://jeremy.cowgar.com/euphoria/index.htm</a>
>
> I have not committed this to SVN yet. Would like to have some feedback.
>
> --
> Jeremy Cowgar
> <a href="http://jeremy.cowgar.com">http://jeremy.cowgar.com</a>
9. Re: Yay or Nay? Framed reference manual
Looks great. I've checked the source of your index. I would change:
<html>
<head><title>Euphoria 4.0 Documentation</title></head>
<frameset cols="15%,85%">
<frame src="menu.htm" name="menu">
<frame src="overview.htm" name="page">
</frameset>
<noframes>
<!-- THE CONTENTS AT MENU.HTM MUST TO BE REPEATED HERE !-->
</noframes>
</html>
This way you will have great compatibility with any existing
html browser, including text mode browsers (Lynx, Links,
netrik, Freedos's htmlhelp system), speach system. Also
a lot of browsers at palmtops, and cell phones don't support
frames, and even some people would like to disable the frames.
+-+-+-+-+-+-+-+
Marco A. Achury
Caracas, Venezuela
10. Re: Yay or Nay? Framed reference manual
Jeremy Cowgar wrote:
> > > <a
> > > href="http://jeremy.cowgar.com/euphoria/index.htm">http://jeremy.cowgar.com/euphoria/index.htm</a>
> > >
> > > I have not committed this to SVN yet. Would like to have some feedback.
Yay.
While you are at it, can you take a look at the individual pages and ensure that
they wrap?
This one wraps:
http://jeremy.cowgar.com/euphoria/overview.htm
This one doesn't:
http://jeremy.cowgar.com/euphoria/install.htm
Mike
11. Re: Yay or Nay? Framed reference manual
> On 5 May 2008 at 17:30, Mike777 wrote (maybe snipped):
> Yay.
>
> While you are at it, can you take a look at the individual pages and
> ensure that they wrap?
>
> This one wraps:
>
> http://jeremy.cowgar.com/euphoria/overview.htm
>
> This one doesn't:
>
> http://jeremy.cowgar.com/euphoria/install.htm
>
Both wrap ok here (Firefox/WinXP SP2). Yay!
--
_
_| euler f german
_| sete lagoas, mg, brazil
_| efgerman{AT}gmail{DOT}com
12. Re: Yay or Nay? Framed reference manual
Euler German wrote:
>
> > On 5 May 2008 at 17:30, Mike777 wrote (maybe snipped):
>
> > Yay.
> >
> > While you are at it, can you take a look at the individual pages and
> > ensure that they wrap?
> >
> > This one wraps:
> >
> > <a
> > href="http://jeremy.cowgar.com/euphoria/overview.htm">http://jeremy.cowgar.com/euphoria/overview.htm</a>
> >
> > This one doesn't:
> >
> > <a
> > href="http://jeremy.cowgar.com/euphoria/install.htm">http://jeremy.cowgar.com/euphoria/install.htm</a>
> >
> Both wrap ok here (Firefox/WinXP SP2). Yay!
How big did you make the font? Go bigger. Bigger still. And then bigger. What
do you get?
Mike
13. Re: Yay or Nay? Framed reference manual
Mike777 wrote:
>
> Jeremy Cowgar wrote:
> > > > <a
> > > > href="http://jeremy.cowgar.com/euphoria/index.htm">http://jeremy.cowgar.com/euphoria/index.htm</a>
> > > >
> > > > I have not committed this to SVN yet. Would like to have some feedback.
>
> Yay.
>
> While you are at it, can you take a look at the individual pages and ensure
> that they wrap?
>
> This one wraps:
>
> <a
> href="http://jeremy.cowgar.com/euphoria/overview.htm">http://jeremy.cowgar.com/euphoria/overview.htm</a>
>
> This one doesn't:
>
> <a
> href="http://jeremy.cowgar.com/euphoria/install.htm">http://jeremy.cowgar.com/euphoria/install.htm</a>
>
> Mike
Mike, use Proxo to edit the <pre> tags, and add a space or <br> at the '?' in
the url:
http://www.rapideuphoria.com/cgi-bin/guru.exu?refDoc=on&libDoc=on&otherDoc=on&keywords=euinc
on the page.
Kat
14. Re: Yay or Nay? Framed reference manual
Mike777 wrote:
>
> While you are at it, can you take a look at the individual pages and ensure
> that they wrap?
> This one wraps:
> <a
> href="http://jeremy.cowgar.com/euphoria/overview.htm">http://jeremy.cowgar.com/euphoria/overview.htm</a>
> This one doesn't:
> <a
> href="http://jeremy.cowgar.com/euphoria/install.htm">http://jeremy.cowgar.com/euphoria/install.htm</a>
> Mike
Checking the source:
The reason why install.html don't wrap is because the section about
autoexec.bat defines a table, and the section about Uninstall Euphoria uses
<pre>
We can change it this way:
<b>How to manually edit autoexec.bat (WinME/98/95/3.1) </b></font>
<p>
<ol>
<li>In the file <b>c:\autoexec.bat</b> add ... </li>
<li>In the same <b>autoexec.bat</b> file ...
Another comment:
Is very important, but many web designers don't remember
that google and other search engines are text browsers.
If your web is not text friendly, your page will never
get a good range in search engines.
If you don't want to install Lynks, send an email to
webpage at rumkin.com
the subject must to be the url e.g.:
http://jeremy.cowgar.com/euphoria/install.htm
Left blank the message and send. You will receive an
image of how a text browser will see will see your page.
+-+-+-+-+-+-+-+
Marco A. Achury
Caracas, Venezuela
15. Re: Yay or Nay? Framed reference manual
Mike777 wrote:
>
> How big did you make the font? Go bigger. Bigger still. And then bigger.
> What do you get?
>
Wow, I had to go huge before it would start wrapping. I hope nobody ever reads
web pages that large.
http://jeremy.cowgar.com/snap/1210036625039796944.png
It's not because of the PRE tag, it's because of the long link w/no spaces in
it:
http://www.rapideuphoria.com/cgi-bin/guru.exu?refDoc=on&libDoc=on&otherDoc=on&keywords=euinc
--
Jeremy Cowgar
http://jeremy.cowgar.com
16. Re: Yay or Nay? Framed reference manual
Kat wrote:
>
> Mike, use Proxo to edit the <pre> tags, and add a space or <br> at the '?'
> in the url:
> <a
> href="http://www.rapideuphoria.com/cgi-bin/guru.exu?refDoc=on&libDoc=on&otherDoc=on&keywords=euinc">http://www.rapideuphoria.com/cgi-bin/guru.exu?refDoc=on&libDoc=on&otherDoc=on&keywords=euinc</a>
> on the page.
>
I understand the URL is causing it to wrap, but say the URL didn't exist and the
pre tags were causing it to wrap. Removing the pre tags and inserting br's
instead would cause all examples to be badly formatted, possibly to the point of
not being able to understand what's going on. Is that better than scrolling?
--
Jeremy Cowgar
http://jeremy.cowgar.com
17. Re: Yay or Nay? Framed reference manual
Jeremy Cowgar wrote:
>
> Kat wrote:
> >
> > Mike, use Proxo to edit the <pre> tags, and add a space or <br> at the '?'
> > in the url:
> > <a
> > href="http://www.rapideuphoria.com/cgi-bin/guru.exu?refDoc=on&libDoc=on&otherDoc=on&keywords=euinc">http://www.rapideuphoria.com/cgi-bin/guru.exu?refDoc=on&libDoc=on&otherDoc=on&keywords=euinc</a>
> > on the page.
> >
>
> I understand the URL is causing it to wrap, but say the URL didn't exist and
> the pre tags were causing it to wrap. Removing the pre tags and inserting br's
> instead would cause all examples to be badly formatted, possibly to the point
> of not being able to understand what's going on. Is that better than
> scrolling?
We already had a cure for this in a previous wordwrap thread. If you remove the
url, the pre tags will cause it to stop wrapping. And yeas, Mike wants it to use
bigger fonts.
Kat
18. Re: Yay or Nay? Framed reference manual
> On 5 May 2008 at 17:57, Mike777 wrote (maybe snipped):
> How big did you make the font? Go bigger. Bigger still. And then
> bigger. What do you get?
>
Mike, if I put THIS BIG, my neighbour two blocks away will be able to
read my display without his glasses. This is beyond reasonable, IMO.
Best & Good Night!
Euler
--
_
_| euler f german
_| sete lagoas, mg, brazil
_| efgerman{AT}gmail{DOT}com
19. Re: Yay or Nay? Framed reference manual
Euler German wrote:
>
> > On 5 May 2008 at 17:57, Mike777 wrote (maybe snipped):
>
> > How big did you make the font? Go bigger. Bigger still. And then
> > bigger. What do you get?
> >
> Mike, if I put THIS BIG, my neighbour two blocks away will be able to
> read my display without his glasses. This is beyond reasonable, IMO.
Nice to see you guys can still make fun of a disability. Or restrict the
available technology to keep people out.
Kat
20. Re: Yay or Nay? Framed reference manual
Marco Achury wrote:
>
> This way you will have great compatibility with any existing
> html browser, including text mode browsers (Lynx, Links,
> netrik, Freedos's htmlhelp system), speach system. Also
> a lot of browsers at palmtops, and cell phones don't support
> frames, and even some people would like to disable the frames.
>
Hm. I only had links installed, but it supports frames just fine. I then
installed lynx, and it does not support frames directly but allowed me to choose
which frame I wanted to view.
However, I did as you said with the noframes tags. Everyone seemed to like the
new changes including Rob, so I committed the changes to SVN and this is how the
4.0 docs will look. There will more than likely be style issue fixes.
--
Jeremy Cowgar
http://jeremy.cowgar.com
21. Re: Yay or Nay? Framed reference manual
Kat wrote:
>
> Euler German wrote:
> >
> > > On 5 May 2008 at 17:57, Mike777 wrote (maybe snipped):
> >
> > > How big did you make the font? Go bigger. Bigger still. And then
> > > bigger. What do you get?
> > >
> > Mike, if I put THIS BIG, my neighbour two blocks away will be able to
> > read my display without his glasses. This is beyond reasonable, IMO.
>
> Nice to see you guys can still make fun of a disability. Or restrict the
> available
> technology to keep people out.
Mike, these are the precious eucode lines that are not allowing you to see the
help pages as you want:
add_handler("pre", routine_id("tag_pre"))
add_handler("/pre", routine_id("tag_end_pre"))
in global procedure html_init()
But i don't see how the code get to that point, or how the routine_id() are
called, so i can't fix it. And considering how well my code is appreciated,
poeple would fight against making it better anyhow. Changing the <pre></pre> tags
to something that isn't printed out in a browser, and adding the <br> tags would
be trivial. Sorry.
Kat
22. Re: Yay or Nay? Framed reference manual
Kat wrote:
>
> Mike, these are the precious eucode lines that are not allowing you to see the
> help pages as you want:
>
> }}}
<eucode>
> add_handler("pre", routine_id("tag_pre"))
> add_handler("/pre", routine_id("tag_end_pre"))
> </eucode>
{{{
>
> in global procedure html_init()
>
> But i don't see how the code get to that point, or how the routine_id() are
> called,
> so i can't fix it. And considering how well my code is appreciated, poeple
> would
> fight against making it better anyhow. Changing the <pre></pre> tags
> to something that isn't printed out in a browser, and adding the <br> tags
> would be trivial. Sorry.
>
Kat, please view docgen.e and doc.exw. docall.bat will allow you to test your
changes. If you come up with a working solution that will keep source code
formatted properly that I will insert your code into the document parsing system
no problem. But the answer is not to just strip the pre tags, that will break
more than it will fix. It's actually much more complicated than the two lines
you've pasted, but it's not at all impossible. The two files I referenced should
get you going.
--
Jeremy Cowgar
http://jeremy.cowgar.com
23. Re: Yay or Nay? Framed reference manual
Jeremy Cowgar wrote:
>
> Kat wrote:
> >
> > Mike, these are the precious eucode lines that are not allowing you to see
> > the
> > help pages as you want:
> >
> > }}}
<eucode>
> > add_handler("pre", routine_id("tag_pre"))
> > add_handler("/pre", routine_id("tag_end_pre"))
> > </eucode>
{{{
> >
> > in global procedure html_init()
> >
> > But i don't see how the code get to that point, or how the routine_id() are
> > called,
> > so i can't fix it. And considering how well my code is appreciated, poeple
> > would
> > fight against making it better anyhow. Changing the <pre></pre> tags
> > to something that isn't printed out in a browser, and adding the <br> tags
> > would be trivial. Sorry.
> >
>
> Kat, please view docgen.e and doc.exw. docall.bat will allow you to test your
> changes. If you come up with a working solution that will keep source code
> formatted
> properly that I will insert your code into the document parsing system no
> problem.
> But the answer is not to just strip the pre tags, that will break more than
> it will fix. It's actually much more complicated than the two lines you've
> pasted,
> but it's not at all impossible. The two files I referenced should get you
> going.
Let me rephrase: no.
We discussed it in #Euphoria , no need to restate it all here, RobC would just
delete the post.
Kat
24. Re: Yay or Nay? Framed reference manual
I am against frames.
Other business: check the wildcard_match() reference on the
http://jeremy.cowgar.com/euphoria/library.htm page.
Regards,
Salix
25. Re: Yay or Nay? Framed reference manual
I'm checking install.htx. The solution to eliminate
the tables is not so simple.
I would add at text.e , procedure text_init()
a new tag to manage <ol>, that do the same as <ul>,
but the <li> must to receive numeration.
add_handler("ol", routine_id("tag_ol"))
add_handler("/ol", routine_id("tag_end_ol"))
The routine would be allmost the same as tag_ul.
But tag_li must to be modified. Must to check if the last open list
is <ul> or <ol>. If is <ol> then add the number.
The last opened last must to be a filo stack.
Numeration also may be a stack or global variable.
text.e is very nice. With some more enhacements we can get a
Lynx like text mode web browser portable to any platform!
+-+-+-+-+-+-+-+
Marco A. Achury
Caracas, Venezuela
26. Re: Yay or Nay? Framed reference manual
Marco Achury wrote:
>
> I'm checking install.htx. The solution to eliminate
> the tables is not so simple.
>
> I would add at text.e , procedure text_init()
> a new tag to manage <ol>, that do the same as <ul>,
> but the <li> must to receive numeration.
>
> }}}
<eucode>
> add_handler("ol", routine_id("tag_ol"))
> add_handler("/ol", routine_id("tag_end_ol"))
> </eucode>
{{{
>
> The routine would be allmost the same as tag_ul.
>
> But tag_li must to be modified. Must to check if the last open list
> is <ul> or <ol>. If is <ol> then add the number.
> The last opened last must to be a filo stack.
> Numeration also may be a stack or global variable.
>
Marco,
If you can come up with some tags to help out, that would be fantastic. Thanks
for looking into it!
--
Jeremy Cowgar
http://jeremy.cowgar.com
27. Re: Yay or Nay? Framed reference manual
Salix wrote:
>
> I am against frames.
>
A few people have said that. Can you tell me why? Or tell me how the menu area
can be always visible no matter where you are in the document, so I do not have
to use frames?
> Other business: check the wildcard_match() reference on the <a
> href="http://jeremy.cowgar.com/euphoria/library.htm">http://jeremy.cowgar.com/euphoria/library.htm</a>
> page.
I looked but I am not sure what you want me to see.
--
Jeremy Cowgar
http://jeremy.cowgar.com
28. Re: Yay or Nay? Framed reference manual
Jeremy Cowgar wrote:
> Salix wrote:
> > Other business: check the wildcard_match() reference on the <a
> > href="http://jeremy.cowgar.com/euphoria/library.htm">http://jeremy.cowgar.com/euphoria/library.htm</a>
> > page.
>
> I looked but I am not sure what you want me to see.
It's a broken link for me.
29. Re: Yay or Nay? Framed reference manual
I'm not /strongly/ against frames but I just don't like them. Probably because
of bad memories from web browsers past.
I'm okay with navigation that scrolls with the page. I've seen navigation do
what you describe but I think it requires Javascript and I don't really know how
to do it.
--
A complex system that works is invariably found to have evolved from a simple
system that works.
--John Gall's 15th law of Systemantics.
"Premature optimization is the root of all evil in programming."
--C.A.R. Hoare
j.
30. Re: Yay or Nay? Framed reference manual
Jason Gade wrote:
>
> I'm okay with navigation that scrolls with the page. I've seen navigation do
> what you describe but I think it requires Javascript and I don't really know
> how to do it.
>
To me, the benefit of the new way I did things was that the navigation is always
at your finger tips. w/o that, I'd just revert to what we had before.
--
Jeremy Cowgar
http://jeremy.cowgar.com
31. Re: Yay or Nay? Framed reference manual
c.k.lester wrote:
>
> Jeremy Cowgar wrote:
> > Salix wrote:
> > > Other business: check the wildcard_match() reference on the
> <a
> href="http://jeremy.cowgar.com/euphoria/library.htm">http://jeremy.cowgar.com/euphoria/library.htm</a></font></i>
> > > page.
> >
> > I looked but I am not sure what you want me to see.
>
> It's a broken link for me.
Hm, works for me.
--
Jeremy Cowgar
http://jeremy.cowgar.com
32. Re: Yay or Nay? Framed reference manual
Jeremy Cowgar wrote:
>
> Jason Gade wrote:
> >
> > I'm okay with navigation that scrolls with the page. I've seen navigation do
> > what you describe but I think it requires Javascript and I don't really know
> > how to do it.
> >
>
> To me, the benefit of the new way I did things was that the navigation is
> always
> at your finger tips. w/o that, I'd just revert to what we had before.
>
> --
> Jeremy Cowgar
> <a href="http://jeremy.cowgar.com">http://jeremy.cowgar.com</a>
It's at my fingertips regardless -- just a scrollbar or a page up or page down
or home or end or spacebar away. Instead of changing focus and then scrolling.
--
A complex system that works is invariably found to have evolved from a simple
system that works.
--John Gall's 15th law of Systemantics.
"Premature optimization is the root of all evil in programming."
--C.A.R. Hoare
j.
33. Re: Yay or Nay? Framed reference manual
Jeremy Cowgar wrote:
>
> c.k.lester wrote:
> >
> > Jeremy Cowgar wrote:
> > > Salix wrote:
> > > > Other business: check the wildcard_match() reference on the
> > <a
> > href="http://jeremy.cowgar.com/euphoria/library.htm">http://jeremy.cowgar.com/euphoria/library.htm</a></font></i>
> > > > page.
> > >
> > > I looked but I am not sure what you want me to see.
> >
> > It's a broken link for me.
>
> Hm, works for me.
>
> --
> Jeremy Cowgar
> <a href="http://jeremy.cowgar.com">http://jeremy.cowgar.com</a>
The link http://jeremy.cowgar.com/euphoria/lib_pat.htm comes up 404. I think
that's what he's talking about.
--
A complex system that works is invariably found to have evolved from a simple
system that works.
--John Gall's 15th law of Systemantics.
"Premature optimization is the root of all evil in programming."
--C.A.R. Hoare
j.
34. Re: Yay or Nay? Framed reference manual
Jeremy Cowgar wrote:
>
> Mike777 wrote:
> >
> > How big did you make the font? Go bigger. Bigger still. And then bigger.
> > What do you get?
> >
>
> Wow, I had to go huge before it would start wrapping. I hope nobody ever reads
> web pages that large.
Uh, we do.
> <a
> href="http://jeremy.cowgar.com/snap/1210036625039796944.png">http://jeremy.cowgar.com/snap/1210036625039796944.png</a>
>
> It's not because of the PRE tag, it's because of the long link w/no spaces in
> it:
>
> <a
> href="http://www.rapideuphoria.com/cgi-bin/guru.exu?refDoc=on&libDoc=on&otherDoc=on&keywords=euinc">http://www.rapideuphoria.com/cgi-bin/guru.exu?refDoc=on&libDoc=on&otherDoc=on&keywords=euinc</a>
Yes, I can understand how a link will preclude wrapping. There seem to be other
messages in this thread indicating that a long link will CAUSE wrapping. I can't
"wrap" my head around that one.
Not that I feel the need to explain, but I frequently scroll a page very large
(should I say very, very large?) and then ratchet back until the text is just
visible on one line for a majority of the page. It is the outliers that are the
problem. If they wrap, great, I have learned to adjust. If they don't wrap, I
must, MUST, ratchet back until the longest line is just visible and, frankly,
that just isn't big enough for me to relax in my recliner. Oh, wait! Was I
supposed to admit that?
Mike
35. Re: Yay or Nay? Framed reference manual
Jason Gade wrote:
>
> The link <a
> href="http://jeremy.cowgar.com/euphoria/lib_pat.htm">http://jeremy.cowgar.com/euphoria/lib_pat.htm</a>
> comes
> up 404. I think that's what he's talking about.
Right. The link for wildcard_match() and wildcard_file() come up as broken
links.
http://jeremy.cowgar.com/euphoria/lib_pat.htm#wildcard_match
http://jeremy.cowgar.com/euphoria/lib_pat.htm#wildcard_file
36. Re: Yay or Nay? Framed reference manual
Euler German wrote:
>
> > On 5 May 2008 at 17:57, Mike777 wrote (maybe snipped):
>
> > How big did you make the font? Go bigger. Bigger still. And then
> > bigger. What do you get?
> >
> Mike, if I put THIS BIG, my neighbour two blocks away will be able to
> read my display without his glasses. This is beyond reasonable, IMO.
My specialty, I suppose.
Mike
37. Re: Yay or Nay? Framed reference manual
Marco Achury wrote:
>
> Mike777 wrote:
> >
> > While you are at it, can you take a look at the individual pages and ensure
> > that they wrap?
> > This one wraps:
> > <a
> > href="http://jeremy.cowgar.com/euphoria/overview.htm">http://jeremy.cowgar.com/euphoria/overview.htm</a>
> > This one doesn't:
> > <a
> > href="http://jeremy.cowgar.com/euphoria/install.htm">http://jeremy.cowgar.com/euphoria/install.htm</a>
> > Mike
>
> Checking the source:
> The reason why install.html don't wrap is because the section about
> autoexec.bat defines a table, and the section about Uninstall Euphoria uses
> <pre>
>
> We can change it this way:
>
> <b>How to manually edit autoexec.bat (WinME/98/95/3.1) </b></font>
>
> <p>
> <ol>
> <li>In the file <b>c:\autoexec.bat</b> add ... </li>
> <li>In the same <b>autoexec.bat</b> file ...
Marco,
Thanks much. It appears to me that the second link (install) has indeed been
changed as it seems to wrap now.
I concur with the conclusion to not change the /pre formatting if it will in any
way mess up things.
However, if a simple change can be made to accommodate wrapping, then I'm all
for it.
Mike
38. Re: Yay or Nay? Framed reference manual
c.k.lester wrote:
>
> Jason Gade wrote:
> >
> > The link <a
> > href="http://jeremy.cowgar.com/euphoria/lib_pat.htm">http://jeremy.cowgar.com/euphoria/lib_pat.htm</a>
> comes</font></i>
> > up 404. I think that's what he's talking about.
>
> Right. The link for wildcard_match() and wildcard_file() come up as broken
> links.
>
Ah! Ok. I was looking for spelling or formatting mistakes. Didn't even click the
link! I recently moved the detail of those functions from the pattern matching to
search category. I hated to have a category for two functions.
I fixed and updated the site. Thanks for catching that and taking the time to
explain it to my sleepy mind.
--
Jeremy Cowgar
http://jeremy.cowgar.com
39. Re: Yay or Nay? Framed reference manual
Mike777 wrote:
>
> Jeremy Cowgar wrote:
> >
> > Mike777 wrote:
> > >
> > > How big did you make the font? Go bigger. Bigger still. And then bigger.
> > >
> > > What do you get?
> > >
> >
> > Wow, I had to go huge before it would start wrapping. I hope nobody ever
> > reads
> > web pages that large.
>
> Uh, we do.
>
> > <a
> > href="http://jeremy.cowgar.com/snap/1210036625039796944.png">http://jeremy.cowgar.com/snap/1210036625039796944.png</a>
> >
> > It's not because of the PRE tag, it's because of the long link w/no spaces
> > in
> > it:
> >
> > <a
> > href="http://www.rapideuphoria.com/cgi-bin/guru.exu?refDoc=on&libDoc=on&otherDoc=on&keywords=euinc">http://www.rapideuphoria.com/cgi-bin/guru.exu?refDoc=on&libDoc=on&otherDoc=on&keywords=euinc</a>
>
> Yes, I can understand how a link will preclude wrapping. There seem to be
> other
> messages in this thread indicating that a long link will CAUSE wrapping. I
> can't "wrap" my head around that one.
>
> Not that I feel the need to explain, but I frequently scroll a page very large
> (should I say very, very large?) and then ratchet back until the text is just
> visible on one line for a majority of the page. It is the outliers that are
> the problem. If they wrap, great, I have learned to adjust. If they don't
> wrap, I must, MUST, ratchet back until the longest line is just visible and,
> frankly, that just isn't big enough for me to relax in my recliner. Oh, wait!
> Was I supposed to admit that?
>
> Mike
Well, i'm a bigger fool than i thought i was.
Kat
40. Re: Yay or Nay? Framed reference manual
I don't really see the need for frames for the manual, but once I found
that I could expand the left-hand "menu" to read it all, or diminish it so
that it took up only 1/4 inch blank space, I don't really mind it either.
BTW, the link in the menu "Language Manual", should be "Reference Manual".
Dan Moyer
41. Re: Yay or Nay? Framed reference manual
I vote Yay for the Framed reference manual.
42. Re: Yay or Nay? Framed reference manual
Jeremy Cowgar wrote:
>
> <a
> href="http://jeremy.cowgar.com/euphoria/index.htm">http://jeremy.cowgar.com/euphoria/index.htm</a>
>
> I have not committed this to SVN yet. Would like to have some feedback.
>
> --
> Jeremy Cowgar
> <a href="http://jeremy.cowgar.com">http://jeremy.cowgar.com</a>
Yay for frames.
Please remove any reference to ed, it will put many potential users, used to
Eclipse, Visual Studio, Notepa++ and such, off. We are no longer in 1993. Make it
part of the stanard librry if you wish.
Please review the "24 reasons" list. Again, we are no longer in 1993, and some
of the arguments there are outdated. As far as the debugger is concerned, anyone
who ever used a modern debugger will disagree with the statements. This list is a
credibility liability as it stands. Perhaps a third of it is still valid, hardly
more.
CChris
43. Re: Yay or Nay? Framed reference manual
I agree documentation with frames unsing <noframes>
This will give compatibility with any browser, even cell phones.
I don't want javascript code there.
+-+-+-+-+-+-+-+
Marco A. Achury
Caracas, Venezuela
44. Re: Yay or Nay? Framed reference manual
[snip all]
Jeremy,
The HTML looks really nice, regardless of whether you're using frames or
div. Having all the hyperlinks makes it easy to find what you're looking for,
too. But, is it possible to also have a plain text version of the docs?
When I'm using ed.ex, a lot of times it's easier to just ESC-C and ESC-F to
get the part of the document I'm looking for, and have both parts on the
screen at the same time without fussing over rearranging and aligning a
browser and text editor, or having the ALT-TAB and memorize for a few seconds
what I need. It's just a productivity thing. Every time I have to touch the
mouse, it goes down.
45. Re: Yay or Nay? Framed reference manual
Michael J. Sabal wrote:
>
> [snip all]
> Jeremy,
> The HTML looks really nice, regardless of whether you're using frames or
> div. Having all the hyperlinks makes it easy to find what you're looking for,
>
> too. But, is it possible to also have a plain text version of the docs?
> When I'm using ed.ex, a lot of times it's easier to just ESC-C and ESC-F to
> get the part of the document I'm looking for, and have both parts on the
> screen at the same time without fussing over rearranging and aligning a
> browser and text editor, or having the ALT-TAB and memorize for a few seconds
> what I need. It's just a productivity thing. Every time I have to touch the
>
> mouse, it goes down.
Yes, plain text docs are still generated w/no problem. I was just updating the
HTML organization and appearance.
--
Jeremy Cowgar
http://jeremy.cowgar.com
46. Re: Yay or Nay? Framed reference manual
Kat wrote:
>
> Mike777 wrote:
> >
> > Jeremy Cowgar wrote:
> > >
> > > Mike777 wrote:
> > > >
> > > > How big did you make the font? Go bigger. Bigger still. And then
> > > > bigger.
> > > > What do you get?
> > > >
> > >
> > > Wow, I had to go huge before it would start wrapping. I hope nobody ever
> > > reads
> > > web pages that large.
> >
> > Uh, we do.
> >
> > > <a
> > > href="http://jeremy.cowgar.com/snap/1210036625039796944.png">http://jeremy.cowgar.com/snap/1210036625039796944.png</a>
> > >
> > > It's not because of the PRE tag, it's because of the long link w/no spaces
> > > in
> > > it:
> > >
> > > <a
> > > href="http://www.rapideuphoria.com/cgi-bin/guru.exu?refDoc=on&libDoc=on&otherDoc=on&keywords=euinc">http://www.rapideuphoria.com/cgi-bin/guru.exu?refDoc=on&libDoc=on&otherDoc=on&keywords=euinc</a>
> >
> > Yes, I can understand how a link will preclude wrapping. There seem to be
> > other
> > messages in this thread indicating that a long link will CAUSE wrapping. I
> > can't "wrap" my head around that one.
> >
> > Not that I feel the need to explain, but I frequently scroll a page very
> > large
> > (should I say very, very large?) and then ratchet back until the text is
> > just
> > visible on one line for a majority of the page. It is the outliers that are
> > the problem. If they wrap, great, I have learned to adjust. If they don't
> > wrap, I must, MUST, ratchet back until the longest line is just visible and,
> > frankly, that just isn't big enough for me to relax in my recliner. Oh,
> > wait!
> > Was I supposed to admit that?
> >
> > Mike
>
> Well, i'm a bigger fool than i thought i was.
Aren't we all?
My point is and remains that accessibility is enough reason to traverse this
path. Any one individual's infirmities (or lack thereof) do not create the need
(or alleviate it).
Mike
