With that in mind it may be worthwhile to have a bit more data on the requirements of the app itself. If it's currently non-GUI Perl then it seems likely these limitations aren't really limitations at all. Posting data to a webapp is trivial, code that works across multiple browsers is fairly easy to create (and it's pretty easy to prove IE is a failure in all corner cases... just them them to the ACID 3 test and have them let you know when it looks right), and most professors probably have Internet more often than not. Making it web-enabled could let you store original data plus results from processing over time which may be a nice additional feature that is easy to add.
AB On Mon, Sep 13, 2010 at 19:33, Nicholas Blatter <[email protected]> wrote: > On Mon, Sep 13, 2010 at 6:31 PM, Joshua Lutes <[email protected]> wrote: >> +1 for using a browser to render your frontend. Way easier to program, much >> better looking (and consistent across platforms) and much more easily >> expandable. > > Just keep in mind the limitations of web applications so they don't > bite you later when the professor asks you to add feature n+1. > Generally, > > - You can't access the client filesystem directly > - Access to the GUI requires an active Internet (or at least network) > connection > - What you can display is dependent on the browser and its plugins. If > you want to display something like a pixmap you're out of luck > > and so on. Something to consider, anyway. > > Despite many claims to the contrary, reports of the death of the > desktop application are greatly exaggerated :) > > Nick > -------------------- > BYU Unix Users Group > http://uug.byu.edu/ > > The opinions expressed in this message are the responsibility of their > author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. > ___________________________________________________________________ > List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list > -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
