Cross-browser Ajax-ified online docs

I spent a little bit of time today and got my documentation system running again. I also updated it with the very latest GTK# 2.7.1 and Mono 1.1.10 class library documentation.

Announcing: http://docs.gotmono.net/ !

Thanks to the AJAX.net library, you will never see the entire page reload, yet the contents tree will always stay in sync with what you are looking at. I have also implemented a live index search making it extremely quick and easy to find what you are looking for.

I find it amusing that my very first javascript project is several magnitudes better than what Microsoft managed to scrap together, which only works properly when used with Internet Explorer.

I have tested the site in Firefox, Opera, and Internet Explorer, and other than IE’s usual CSS problems (and it looks like some of which might already be fixed in IE7), it works almost perfectly in every one.

Please let me know if you find any bugs or have any suggestions…or even if you just find it useful! If there is an open-source mono library you would like to see added to the site let me know about that as well.

UPDATE: It looks like the site was erroring a bit… its working now.

9 Comments

  1. Foole
    Posted November 19, 2005 at 10:09 pm | Permalink

    That absolutely rocks.

    I was about to say it needed a way to direct someone else to whatever page I was looking at, but then I saw the “Link to this document” button. Excellent work.

    This computer is kinda slow, so the ajax version will probably be faster than monodoc for me.

  2. reflog
    Posted November 20, 2005 at 1:06 am | Permalink

    hi.
    looks great, but seems like some pages are missing?
    GLib->Argv->Members brings:

    Server error in ‘/’ application
    Not found
    Description: Error processing request.

    Error Message: HTTP 404. Not found

  3. reflog
    Posted November 20, 2005 at 12:10 pm | Permalink

    getting it, still…
    http://docs.gotmono.net/display.aspx?url=ecma%3a%2f%2fgo%3flink%3dM%253aIPod.Playlist.InsertSong%2528int%252cIPod.Song%2529
    Server error in ‘/’ application
    Not found
    Description: Error processing request.

    Error Message: HTTP 404. Not found

  4. KillerKiwi
    Posted November 20, 2005 at 12:27 pm | Permalink

    Some Components that I find come in handy

    DotNetOpenMail
    http://dotnetopenmail.sourceforge.net/

    Ajax.Net
    http://ajax.schwarz-interactive.de/csharpsample/default.aspx

    Neat Upload
    http://www.brettle.com/neatupload

    Log4Net
    http://logging.apache.org/log4net/

    SharpMimeTools
    http://anmar.eu.org/projects/sharpmimetools/

    A library of where to find controls like this would be very cool

  5. Josh Tauberer
    Posted November 20, 2005 at 12:27 pm | Permalink

    Wow, excellent. Can we get this running on go-mono.com, or else can we direct the Mono website’s link to docs to your site?

  6. Posted November 20, 2005 at 12:42 pm | Permalink

    reflog - Hey, looks like its erroring for me too. I’ll try to have it fixed by
    the end of the day.
    Fixed!

  7. chris
    Posted November 21, 2005 at 12:33 am | Permalink

    That really does look slick. Great work Eric!

  8. Posted November 21, 2005 at 1:30 am | Permalink

    Now if only we could edit the missing documentation and do a postback to the server to have it updated.
    And then abstract the whole thing so we can reuse this for our own libraries…

  9. Posted December 5, 2005 at 2:56 am | Permalink

    Although I like AJAX a lot, I do not particularly appreciate how it works (or rather; doesn’t) without JavaScript enabled. AJAX shouldn’t be an excuse lazy web developers can hide behind because they don’t want to, or don’t know how to, create web pages truly accessible, regardless of the technology used to view them and regardless of the person who views them and their handicap (if any).

    Google, for example, will have major problems accessing a web page that has links with href’s that point to JavaScript functions. That is not good accessibility. And it’s not necessary either. If this is how the AJAX.NET framework is built, I don’t think it’s good to build anything on it, since it won’t be accessible without a highly modern web browser with JavaScript enabled.

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*