From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.224.66.70 with SMTP id m6mr11454653qai.6.1373615599754; Fri, 12 Jul 2013 00:53:19 -0700 (PDT) X-Received: by 10.49.18.193 with SMTP id y1mr52420qed.29.1373615599721; Fri, 12 Jul 2013 00:53:19 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!news.glorb.com!t19no1214441qam.0!news-out.google.com!f7ni2066qai.0!nntp.google.com!t19no1289196qam.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 12 Jul 2013 00:53:19 -0700 (PDT) In-Reply-To: <20130712075752.46e2cf01@atmarama.noip.me> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=195.182.34.201; posting-account=bMuEOQoAAACUUr_ghL3RBIi5neBZ5w_S NNTP-Posting-Host: 195.182.34.201 References: <20130712075752.46e2cf01@atmarama.noip.me> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <7619c730-b138-4bd9-a0e7-9c80d26f7f00@googlegroups.com> Subject: Re: Ada-Python demo From: Maciej Sobczak Injection-Date: Fri, 12 Jul 2013 07:53:19 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:16316 Date: 2013-07-12T00:53:19-07:00 List-Id: > Thank you. Read your article about calling Ada modules from within > Python and wonder, if you explored that idea further, what do you think > if it would be feasible to write the whole back-end/libraries of > application using Ada and then glue everything together in GUI app > written with PyQt? It makes perfect sense, especially if you take into account that GUI in Ada= is kind of shaky subject. This might be a valid idea also for teams where = some programmer(s) might be more Ada-oriented while other(s) might happen t= o be Python fans - problem solved, all programmers will be happy. :-) On the other hand, in the context of writing GUI I would consider even more= options. Extending Python interpreter with Ada modules means that there ex= ists a single process that does everything. Why not divide the whole applic= ation into separate processes: one (or many) handling the business logic an= d another for the UI. This can open some interesting options like having de= sktop GUI (Python? Java? etc.) *and* web-based interface (AWS? Java? etc.) = *and* perhaps even something else (mobile app?) for the same functionality. In this case, instead of investing into inter-language integration at the l= evel of Python interpreter (note that it basically binds you to a single sc= ripting language) I would consider going full distributed. No, I'm not trying to discourage you from the Ada-Python integration (what = would be the point of creating the demo? :-) ), but keeping alternatives in= the back of our minds is probably a good idea. --=20 Maciej Sobczak * http://www.msobczak.com * http://www.inspirel.com