Hi Felix, thanks for all the information there's plently of food for thought for me to chew through.
Chibisi On Wed, Sep 3, 2008 at 3:36 PM, drflxms <[EMAIL PROTECTED]> wrote: > Hello Chibisi, > > you might be looking for something like "Rpad" > (http://www.rpad.org/Rpad/). There are some other systems like > SNetscape, Rserve, RSOAP, R.NET.Web as well. Unfortunately I have no > personal experience with these systems so far, so I can't give you any > real advice. I just know them to exist and surfed some testpages. > > To me Rpad looks as probably the most feasible system for the task you > describe (and from a cost vs. benefit point of view) . As far as I > understand/remember users need no unusual prerequisites to use Rpad. > > For a general overview of GUIs see i.e. http://www.sciviews.org/_rgui/. > > According to your latest description of the database associated with the > webpage, SQlite probably will suffice and might be easier to handle than > a whole MySQL server - as Hadley Wickham already proposed in his e-mail. > But this all of course depends on your resources as well (i.e. do you > have access to your own root-server, or just some megabytes of ordinary > webspace...?). > > Kind regards and greetings from Munich, > Felix. > > Chibisi Chima-Okereke schrieb: > > Dear Felix, > > > > Thanks for the reply, > > > > If you haven't already guessed I am new to web programming. > > > > The sort of webpage I want to build is one that presents quantitative > > information in graphs and charts, that people can interact with, e.g. > > select parts of charts to zoom into, highlight values, click buttons > > to do analysis on the data displayed, so yes some sort of interactive > > GUI. I initially thought of using flash as a front end but I don't > > know any actionscript, so learning that would to a suitable standard > > take alot of extra time, and I think it would be best if everything > > could be done in R as much as possible. > > > > If I used an RGUI I guess I would be using the playwith package? Do > > the consumers of the website need to have R to consume stuff displayed > > with an RGUI? > > > > The database itself would just be pretty static just being queried for > > information, unless some analysis was required in which case R would > > query the database do the analysis and write the analysis back to the > > database (I guessing that is the way it would be done), before it gets > > displayed on the web page. > > > > Kind Regards > > > > Chibisi > > > > On Wed, Sep 3, 2008 at 11:39 AM, drflxms <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > Hello Chibisi, > > > > I am not shore whether I completely understand your needs: Do you > want > > to build a webpage which relies on a content management system > > (cms)? Do > > you want to collect data (i.e. survey) which later on shall be > > analysed > > using R? Or shall it be a webpage with an interactive R GUI? What > > else? > > > > But personally I would prefer MySQL as backend for websites, as most > > professional (opensource) cms (i.e. typo3, wordpress etc.) are > created > > with MySQL in mind. > > There is a good interface between R and MySQL called RMySQL as well. > I > > use this on a daily basis, as all my data is stored in a local MySQL > > database (more flexible than always reading in text files - at > > least in > > my opinion). > > > > Hope this personal view might help a little bit. > > > > Cheers, > > Felix > > > > ______________________________________________ > > R-help@r-project.org <mailto:R-help@r-project.org> mailing list > > https://stat.ethz.ch/mailman/listinfo/r-help > > PLEASE do read the posting guide > > http://www.R-project.org/posting-guide.html > > and provide commented, minimal, self-contained, reproducible code. > > > > > > [[alternative HTML version deleted]] ______________________________________________ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.