Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!news1.tnib.de!feed.news.tnib.de!news.tnib.de!newsfeed.freenet.ag!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.017 X-Spam-Evidence: '*H*': 0.97; '*S*': 0.00; 'javascript,': 0.07; 'api': 0.09; 'already.': 0.09; 'gurus,': 0.09; 'though...': 0.09; 'looked': 0.10; 'volunteer': 0.11; 'bonus': 0.13; 'server,': 0.15; 'client,': 0.16; 'fluent': 0.16; 'from:addr:torriem': 0.16; 'from:name:michael torrie': 0.16; 'pov,': 0.16; 'reasonably': 0.16; 'require.': 0.16; 'wrote:': 0.17; 'examples': 0.18; 'handles': 0.18; 'app': 0.19; 'fairly': 0.21; 'stick': 0.22; 'apps': 0.23; 'flexibility': 0.23; 'nearly': 0.23; "i've": 0.23; 'seems': 0.23; 'idea': 0.24; 'header:In-Reply-To:1': 0.25; 'header :User-Agent:1': 0.26; 'looks': 0.26; 'css': 0.27; 'interface': 0.27; 'run': 0.28; 'environment': 0.29; 'end,': 0.29; 'restricted': 0.29; 'stuff': 0.30; 'implement': 0.32; 'running': 0.32; 'to:addr:python-list': 0.33; 'front': 0.33; 'doing': 0.35; 'pm,': 0.35; 'remote': 0.35; 'too.': 0.35; 'subject:?': 0.35; 'something': 0.35; 'received:org': 0.36; 'but': 0.36; 'message- id:@gmail.com': 0.36; 'client': 0.36; 'should': 0.36; 'too': 0.36; 'itself': 0.37; 'does': 0.37; 'level': 0.37; 'being': 0.37; 'far': 0.37; 'well.': 0.37; 'subject:: ': 0.38; 'some': 0.38; 'talk': 0.38; 'to:addr:python.org': 0.39; 'received:192': 0.39; 'where': 0.40; 'received:192.168': 0.40; 'header:Received:5': 0.40; 'end': 0.40; 'think': 0.40; 'your': 0.60; 'easy': 0.60; "you'll": 0.62; 'necessarily': 0.63; 'more': 0.63; 'services': 0.64; 'to,': 0.65; 'business': 0.70; 'attractive': 0.78; 'directors': 0.81; 'dal': 0.84; 'demos': 0.84; 'monte': 0.84; 'subject:over': 0.84; 'top.': 0.84 X-Virus-Scanned: amavisd-new at torriefamily.org Date: Fri, 22 Feb 2013 16:37:08 -0700 From: Michael Torrie User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.12) Gecko/20130105 Thunderbird/10.0.12 MIME-Version: 1.0 To: python-list@python.org Subject: Re: PyQT app accessible over network? References: <20130222164513.9377097f0cf2add2a6d16204@gmx.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 28 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1361576247 news.xs4all.nl 6921 [2001:888:2000:d::a6]:60080 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:39626 On 02/22/2013 02:49 PM, Monte Milanuk wrote: > Web2py does seem pretty attractive in that it seems to come with a lot > of functionality rolled in already. It seems to be pretty easy to > deploy... since this would be more of a case where the volunteer match > directors are not necessarily computer gurus, and something that can > literally run from a USB stick on nearly any computer has its benefits. > I've seen some examples (I think) of twitter-bootstrap in some other > demos of flask, and it looked reasonably attractive without being too > over the top. web2py's DAL seems fairly straight-forward too. Looks > like I may have to get more fluent in CSS & javascript, though... If you just use web2py to implement the database calls and business logic, and to implement a simple, clean API (RPC really) for the clients to talk to, then you can still use your non-web UI tools like PyQt. But as an added bonus you can do a web interface as well. You'll have flexibility either way. A client is a client, whether it's web-bases and running on the same server, or a remote app using RPC over HTTP. I think all web-based apps should expose a web service (an API). that way you have flexibility to do a variety of front-ends. Normal web browser, mobile browser, a standalone app (think android or iphone). As far as doing client/server stuff with just a database engine, unless you have tight control over the environment end to end, from a security pov, it's not a good idea to expose the database engine itself to the internet. Better to put a restricted web services API in front of it that handles all the authorization needs (access-control) on the detailed level that you require.