Discussion in 'Tomato Firmware' started by thor2002ro, Apr 6, 2009.

  1. thor2002ro

    thor2002ro Addicted to LI Member

    i'm making a tomato build...
    can anyone tell me how the web interface works?
  2. bogderpirat

    bogderpirat Network Guru Member

    it has those unicorns that pierce the websites onto their horns and deliver them to the browser of your choice
  3. fyellin

    fyellin LI Guru Member

    Since you're a new poster, it's hard for us to tell if you're asking a really easy question, which would best be answered by reading the FAQ, or a really hard question which would best be answered by looking at the source, particularly httpd.c.

    Are you asking how to access the UI (read the faq) or how is the UI implemented?
  4. thor2002ro

    thor2002ro Addicted to LI Member

    how is the ui implemented... ,
    i what to make a new page that will modify some nvram variables
    and what about debuging the site i see it needs some kind of debug.js

    sorry if i sound noobish but i'm not that familliar with ajax... but i do know linux stuff
  5. TVTV

    TVTV LI Guru Member

    In order to modify the UI, i reckon you must be familiar with AJAX.
  6. thor2002ro

    thor2002ro Addicted to LI Member

    if your not going to help DONT POST... whats the point :|

    PS: vad ca esti roman asa ca nam pretenti de la tine...
  7. fyellin

    fyellin LI Guru Member

    Your best bet is to look at the source. Unless you're planning on doing an interactive page, you don't really need AJAX, but you do need to be comfortable with JavaScript.

    All the web pages served are in the source code in the httpd/ directory, and in the image in the /www directory. These are .asp files, in which inline constructs in the file are expanded before being sent to the user. Changes are sent back using forms. These are not separate cgi scripts; rather there are a built in set of functions that the httpd calls directly

    If you feel like playing, create a directory /var/wwwext. But some .asp documents there. You can then browse them using http:<ip>/ext/foo.asp.
  8. thor2002ro

    thor2002ro Addicted to LI Member

    thank you , i'll give it a try...

    later edit: what about debuging the site?
  9. fyellin

    fyellin LI Guru Member

    Someone else will have to help you with that. I've just tried to figure out how things work. I haven't written any of my own.
  10. SgtPepperKSU

    SgtPepperKSU Network Guru Member

    I debug GUI changes by mounting CIFS and symlinking it at /var/wwwext. That way anything I have on my development computers network share is immediately available at http://router/ext/ . From there, it's regular web development debugging (I rely heavily on Firefox's DOM inspector and Error Console).
  11. thor2002ro

    thor2002ro Addicted to LI Member

    o i use firebug addon on firefox ... i thought that was something more special.... :tongue:
    ok thanks!!! :thumbup:
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice