Xojo Conferences
XDCMay2019MiamiUSA

HTMLViewer Navigation (Real Studio network user group Mailinglist archive)

Back to the thread list
Previous thread: encoding
Next thread: inlining via external text processing


FW: Special Valentine's Offer for Valentina - Beat the Price Increase!   -   Lynn Fredricks
  HTMLViewer Navigation   -   Thom McGrath
   Re: HTMLViewer Navigation   -   Fargo Holiday
    Re: HTMLViewer Navigation   -   Tom Russell
     Re: HTMLViewer Navigation   -   Fargo Holiday
   Re: HTMLViewer Navigation   -   Thom McGrath
    Re: HTMLViewer Navigation   -   Steve Garman
     Re: HTMLViewer Navigation   -   Thom McGrath
      Re: HTMLViewer Navigation   -   Steve Garman
       Still having problems with large files   -   AP Work
      Re: Still having problems with large files   -   Kirk Gray
   Re: HTMLViewer Navigation   -   Emile Schwarz
   Re: HTMLViewer Navigation   -   Thomas Cunningham

HTMLViewer Navigation
Date: 25.11.07 07:34 (Sun, 25 Nov 2007 01:34:08 -0500)
From: Thom McGrath
Although I'm using 07r2, I think it's incredible that the HTMLViewer
does not have two extremely basic functions: Back() and Forward() -
how can we be without those?

Does a future version fix this?

Re: HTMLViewer Navigation
Date: 25.11.07 08:44 (Sat, 24 Nov 2007 23:44:26 -0800)
From: Fargo Holiday
Thom McGrath wrote:
> Although I'm using 07r2, I think it's incredible that the HTMLViewer
> does not have two extremely basic functions: Back() and Forward() -
> how can we be without those?
>
> Does a future version fix this?
>
> --
> Thom McGrath
> The ZAZ Studios
> <http://www.thezaz.com/> AIM: thezazstudios
>
Wouldn't that just be something to implement on your own? I mean, it
would just be an indexed list of URLs, or cached local copies should you
prefer to implement a cache. The viewer is just an html parsing engine,
not a browser. This strikes me as akin to asking it to have a built in
history or bookmark function. Which is to say easy, but not fitting
within the context of the item.

Might just be me though.

-Fargo

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Re: HTMLViewer Navigation
Date: 25.11.07 16:49 (Sun, 25 Nov 2007 10:49:59 -0500)
From: Tom Russell
Not trying to be rude, but from experience with other development
environments, typically a control has a lot of items baked in within
basic reason of its functionality.

What Thom says makes perfect sense regardless of whether its easy to
implement or not. The control acts as a browser as far as I can tell.

Even the LR states "Renders HTML and provides basic navigation
features." If it provides basic navigation features then that would
include the Back and Forward features. And as always the LR fails to
provide examples showing that basic functionality.

I think many of us are too quick to surmise that we need to implement
functionality that should be basic to the control itself. Time is
usually money and in this instance depending upon your rate, your losing
out because you have to spend some inordinate amount of time
implementing some basic feature that should be a given.

Just my opinion of course.

Tom

Fargo Holiday wrote:
> Thom McGrath wrote:
>
>> Although I'm using 07r2, I think it's incredible that the HTMLViewer
>> does not have two extremely basic functions: Back() and Forward() -
>> how can we be without those?
>>
>> Does a future version fix this?
>>
>> --
>> Thom McGrath
>> The ZAZ Studios
>> <http://www.thezaz.com/> AIM: thezazstudios
>>
> Wouldn't that just be something to implement on your own? I mean, it
> would just be an indexed list of URLs, or cached local copies should you
> prefer to implement a cache. The viewer is just an html parsing engine,
> not a browser. This strikes me as akin to asking it to have a built in
> history or bookmark function. Which is to say easy, but not fitting
> within the context of the item.
>
> Might just be me though.
>
> -Fargo
>
> _______________________________________________
> Unsubscribe or switch delivery mode:
> <http://www.realsoftware.com/support/listmanager/>
> Search the archives:
> <http://support.realsoftware.com/listarchives/lists.html>

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Re: HTMLViewer Navigation
Date: 25.11.07 20:00 (Sun, 25 Nov 2007 11:00:50 -0800)
From: Fargo Holiday
Debate is healthy, and you certainly won't offend me. =)
Anyway, I see where you're coming from, I just don't think it makes
sense in this case. "Basic navigation" is just the ability to load a url
or file, keeping any sort of index is up to you to implement, or at
least that's my take on it.

I don't think the control does act like a browser. It has no user
interface whatsoever, and is merely one component of a possible browser.
Adding anything beyond the bare minimum strikes me as undesirable, since
often I use the htmlviewer control to simply display some documentation,
and have absolutely no need for saving histories, keeping a cache,
allowing direct user input of a URL, or much of anything really. I use
it simply as it is intended, which is to render html.

All adding back/forward and other components of the ilk in would do is
unnecessarily bulk up a simple control, and for anyone that wants to
implement their own idea of how the various browser components should
work, it adds complexity to the control without any benefit at all. The
loading and rendering of html isn't something I'd ever want to
implement, as a lone programmer, but everything else I may decide to
change depending on the application.

For everyone that needs to use a more enriched htmlviewer, why not just
subclass it, add what you want, and export it for use in other projects?

-Fargo

Tom Russell wrote:
> Not trying to be rude, but from experience with other development
> environments, typically a control has a lot of items baked in within
> basic reason of its functionality.
>
> What Thom says makes perfect sense regardless of whether its easy to
> implement or not. The control acts as a browser as far as I can tell.
>
> Even the LR states "Renders HTML and provides basic navigation
> features." If it provides basic navigation features then that would
> include the Back and Forward features. And as always the LR fails to
> provide examples showing that basic functionality.
>
> I think many of us are too quick to surmise that we need to implement
> functionality that should be basic to the control itself. Time is
> usually money and in this instance depending upon your rate, your losing
> out because you have to spend some inordinate amount of time
> implementing some basic feature that should be a given.
>
> Just my opinion of course.
>
> Tom
>

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Re: HTMLViewer Navigation
Date: 25.11.07 16:49 (Sun, 25 Nov 2007 10:49:14 -0500)
From: Thom McGrath
History is not as simple as a list of URLs, and the HTMLViewer does
not provide us access to the cache. It's also already built into
WebKit, as well as the very simple function of reload.

Re: HTMLViewer Navigation
Date: 25.11.07 19:19 (Sun, 25 Nov 2007 18:19:47 +0000)
From: Steve Garman
In a message regarding Re: HTMLViewer Navigation dated Sun, 25 Nov 2007
10:49:14 -0500, Thom McGrath said that ...

> History is not as simple as a list of URLs
Really? What else is there?

I implemented a simple history class to store URLs back when the HTMLViewer
was first introduced and there is a sample at
http://rb.sgarman.net/browser/

Presumably this does not fulfill all your requirements but I'd be
interested to know what it's missing.

I apologise for the appearance on the Mac, I never got round to fixing it
in the sample.

Re: HTMLViewer Navigation
Date: 25.11.07 23:05 (Sun, 25 Nov 2007 17:05:10 -0500)
From: Thom McGrath
Usually, navigating would use a cache. Press back, and the browser...
well... just goes back. To keep a list of URLs would reload them,
which would also break some forms. It's hardly a desirable situation
when it's already built into WebKit, just not exposed to us.

Just feels like another half-baked feature to me.

Re: HTMLViewer Navigation
Date: 26.11.07 19:12 (Mon, 26 Nov 2007 18:12:05 +0000)
From: Steve Garman
In a message regarding Re: HTMLViewer Navigation dated Sun, 25 Nov 2007
17:05:10 -0500, Thom McGrath said that ...

> To keep a list of URLs would reload them,
> which would also break some forms.

Good point.

I wish I'd thought of that before standing on shaky ground while causing
offence on the forums.

Re: HTMLViewer Navigation
Date: 26.11.07 00:01 (Mon, 26 Nov 2007 00:01:23 +0100)
From: Emile Schwarz
Hi all,

there is one thing everyone forgot to say (except Steve: Windows I
think) is the running OS each of us use / run.

On Windows, there are many more entries on the contextual menu v/s on
the Macintosh side (sorry Fargo, I forget about Linux).

So, to be in tunes, it is a good idea to add the main running OS. Mine
is Macintosh (but I can run Windows and Linux) even if Internet is only
available (for me) thru the Windows box (Airport does not receive the WiFi
Box signal, the Pentium IV laptop LinkSys WiFi PCMCIA card is probably
more sensitive...

Cheers,

Emile

PS: because I stopped to watch my own Help system, can you remind me how
we can fill an array to implement Previous / Next / History ?
I mean, how to get and store the URL of the item.

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Re: HTMLViewer Navigation
Date: 26.11.07 03:04 (Sun, 25 Nov 2007 16:04:25 -1000)
From: Thomas Cunningham
HTML Viewer on a Mac is half baked and that is being very kind. There
are many feature requests to improve it, but so far they have fallen
upon deaf ears.

Module:
Init Routine that you pass the 'aHandle' of your instance.
Module properties:
Dim webView As Integer
Dim goBack, goForward As Integer

declare function sel_registerName lib "/usr/lib/libobjc.dylib" (name
as CString) as Integer
goBack = sel_registerName( "goBack:" )
goForward = sel_registerName( "goForward:" )
declare function HIWebViewGetWebView lib "WebKit" (hiview as
Integer) as Integer
webView = HIWebViewGetWebView( aHandle )

Sub GoBack(Extends htmls As HTMLViewer)
#if TargetMacOS then
declare sub objc_msgSend lib "/usr/lib/libobjc.dylib" (obj as
Integer, selector as Integer, agentName as CFStringRef)
declare sub objc_msgSend lib "/usr/lib/libobjc.dylib" (obj as
Integer, selector as Integer)

objc_msgSend( webView, goBack)
#endif

Sub GoForward(Extends htmls As HTMLViewer)
#if TargetMacOS then
declare sub objc_msgSend lib "/usr/lib/libobjc.dylib" (obj as
Integer, selector as Integer, agentName as CFStringRef)
declare sub objc_msgSend lib "/usr/lib/libobjc.dylib" (obj as
Integer, selector as Integer)

objc_msgSend( webView, goForward)
#endif

HTH. Most of what I have listed here is from Jon Johnson.