New Gnoga Website and Its Source

New Gnoga Website and Its Source

[David Botton]

I've updated the Gnoga Website and started adding content towards the business plan (I'm working hard on all parts ;)

The site requires JavaScript and web sockets. If you have issues getting to the site, please e-mail me, as I am working through various proxy issues, etc. and collecting data.

http://www.gnoga.com

to see the source http://www.gnoga.com/source

David Botton

Re: New Gnoga Website and Its Source

[Simon Clubley]

On 2014-11-17, David Botton <david@botton.com> wrote:
> I've updated the Gnoga Website and started adding content towards the business plan (I'm working hard on all parts ;)
>
> The site requires JavaScript and web sockets. If you have issues
> getting to the site, please e-mail me, as I am working through various
> proxy issues, etc. and collecting data.
>
> http://www.gnoga.com
>
> to see the source http://www.gnoga.com/source
>

First off, well done for enabling a home page which has text explaining
Gnoga to Javascript disabled users.

Second, when I go to the above source link, I get redirected (after
enabling Javascript) to http://www.gnoga.com:8889/source, but while
I get a list of files, clicking on them does nothing other than
highlighting the filename.

Firefox on Linux, BTW and web sockets are enabled according to about:config.

Simon.

PS: BTW, As an Ada person, how do you find Javascript ?

I now know a lot more about it than I did a couple of weeks ago, and
I must say the impression I've developed is that it makes C++ look like
a nice robust, well engineered, safe language by comparison.

Some people judge a language's popularity by how active it's discussed
on line. In the case of Javascript I wonder if that online activity is
due to how much is left unsaid in the documentation and how scattered
the various documentation resources you need seem to be.

-- 
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world

Re: New Gnoga Website and Its Source

[David Botton]

> Second, when I go to the above source link, I get redirected (after
> enabling Javascript) to http://www.gnoga.com:8889/source, but while
> I get a list of files, clicking on them does nothing other than
> highlighting the filename.

My fault for not testing... I got lazy on the lay out and it bit me, since not working with FireFox, I'll fix that now check again in 20minutes.

> PS: BTW, As an Ada person, how do you find Javascript ?

I don't care much for it. I have an allergy to braces :)

With Gnoga you don't have to see it.

David Botton

Re: New Gnoga Website and Its Source

[David Botton]

> My fault for not testing... I got lazy on the lay out and it bit me, since not working with FireFox, I'll fix that now check again in 20minutes.

Ok, fixed up and looking better too.

David Botton

Re: New Gnoga Website and Its Source

[Simon Clubley]

On 2014-11-17, David Botton <david@botton.com> wrote:
>> Second, when I go to the above source link, I get redirected (after
>> enabling Javascript) to http://www.gnoga.com:8889/source, but while
>> I get a list of files, clicking on them does nothing other than
>> highlighting the filename.
>
> My fault for not testing... I got lazy on the lay out and it bit me, since not working with FireFox, I'll fix that now check again in 20minutes.
>

Yes, that's working ok now.

>> PS: BTW, As an Ada person, how do you find Javascript ?
>
> I don't care much for it. I have an allergy to braces :)
>
> With Gnoga you don't have to see it.
>

Yes, but you do if you are writing a Firefox Android extension... :-)

Simon.

-- 
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world

Re: New Gnoga Website and Its Source

[Jacob Sparre Andersen]

David Botton wrote:

> http://www.gnoga.com

The first two times I tried to load it, I just got a white page.

> to see the source http://www.gnoga.com/source

Then I took a look at the source browser, and it seems to work
reasonably well.

When I then tried to load the frontpage again, it came up fine.

(Using Iceweasel on Debian/stable.)

Greetings,

Jacob
-- 
A: Yes.
>Q: Are you sure?
>>A: Because it reverses the logical flow of conversation.
>>>Q: Why is top posting frowned upon?

Re: New Gnoga Website and Its Source

[Randy Brukardt]

"David Botton" <david@botton.com> wrote in message 
news:98d79d97-3481-432e-b21f-dd26b9f757dd@googlegroups.com...
> I've updated the Gnoga Website and started adding content towards the 
> business plan (I'm working hard on all parts ;)
>
> The site requires JavaScript and web sockets. If you have issues getting 
> to the site, please e-mail me, as I am working through various proxy 
> issues, etc. and collecting data.

Are you going to make some static pages available for search engines? One 
would like your project to show up in the various search engines, and I 
doubt that anything using web sockets will show up there. (For the Ada 
search engine, we ignore Javascript, too, but I think Google et. al. do some 
Javascript emulation.)

                                             Randy.

Re: New Gnoga Website and Its Source

[David Botton]

> Are you going to make some static pages available for search engines?

For the moment there is a <noscript> tag with a description of the site that addresses that until the site is done. Not ideal but works for now.

There is a way currently in Gnoga to dump the site to plain html and attach to elements for interactivity on connection that I could use to address the crawler issues and I may end up using that method.

I am also considering adding a fallback mechanism using http and ajax for Gnoga, although it seems, so far, that there is little need. After a few tweaks it seems that most firewalls and proxies are working today with websockets so the need may not be there.

In general the web has moved to more dynamic content and "comet" programming. So Google provides a way to allow you to present static content in an alternate crawler only URL scheme. I likely will add a way to automate Gnoga to provide the HTML snapshots with the proper URL scheme. (https://developers.google.com/webmasters/ajax-crawling/ and https://developers.google.com/webmasters/ajax-crawling/docs/specification)

For now though, I am mostly experimenting with possible "patterns" for writing websites with Gnoga.

Gnoga's design is "app" centric and more about GUIs than sites, so far a very refreshing and enjoyable way of writing a web site, i.e. as an application. Once I've got a good feel for it I'll add to Gnoga the needed parts to address the crawler issues in one form or another.

David Botton

Re: New Gnoga Website and Its Source

[johannes falcone]

On Sunday, November 16, 2014 8:24:37 PM UTC-5, David Botton wrote:
> I've updated the Gnoga Website and started adding content towards the business plan (I'm working hard on all parts ;)
> 
> The site requires JavaScript and web sockets. If you have issues getting to the site, please e-mail me, as I am working through various proxy issues, etc. and collecting data.
> 
> http://www.gnoga.com
> 
> to see the source http://www.gnoga.com/source
> 
> David Botton

Great work!

Re: New Gnoga Website and Its Source

[Markus Schöpflin]

Am 17.11.2014 um 02:24 schrieb David Botton:

> The site requires JavaScript and web sockets. If you have issues getting to
> the site, please e-mail me, as I am working through various proxy issues,
> etc. and collecting data.

FWIW, when not allowing scripts I'm seeing you noscript replacement text. When 
allowing gnoga.com and googleapis.com I get a completely blank page.

This is using FF 32.0.3 on Win7.

Markus

Re: New Gnoga Website and Its Source

[Markus Schöpflin]

Am 18.11.2014 um 09:08 schrieb Markus Schöpflin:
> Am 17.11.2014 um 02:24 schrieb David Botton:
>
>> The site requires JavaScript and web sockets. If you have issues getting to
>> the site, please e-mail me, as I am working through various proxy issues,
>> etc. and collecting data.
>
> FWIW, when not allowing scripts I'm seeing you noscript replacement text. When
> allowing gnoga.com and googleapis.com I get a completely blank page.
>
> This is using FF 32.0.3 on Win7.

Using FF 33.1.1 doesn't improve the situation, nor does additionally allowing 
bootstrapcdn.com for JS.

Markus