I agree with most of what Robert said; just wanted to amplify a few points.
Robert Walker wrote: > Ralph Shnelvar wrote: >> I want to use Rails to >> >> (1) Download an executable. > > This part is trivial. > >> (2) Interact with a client to select a directory on the client side > > This happens automatically depending on what web browser the client > uses. > >> (3) do directory browsing and selecting > > Thank goodness this is not possible through standard web technologies. Sure it is, with a file input field. > >> (4) create an xml file of parameters, and write the xml file somewhere >> or pass it to the executable. > > Much effort has been put into web browser security to prevent this exact > process. Except that you *can* download a file that you expect the user to open in your application. You *may* even be able to write a browser plugin to make the file open in the browser (as Adobe has done with its PDF and -- yes -- Flash plugins). [...] >> Is this doable or am I better off having my client download a >> stand-alone Ruby application? It's hard to tell, at least for me. >> If a standalone Ruby application is >> better, can someone recommend a GUI that you might suggest? [...] You might like to look at Monkeybars or Limelight. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
