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 autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.107.38.11 with SMTP id m11mr33703368iom.15.1437524259353; Tue, 21 Jul 2015 17:17:39 -0700 (PDT) X-Received: by 10.140.91.182 with SMTP id z51mr215423qgd.5.1437524259206; Tue, 21 Jul 2015 17:17:39 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!news.glorb.com!f3no1097358igg.0!news-out.google.com!4ni81731qgh.1!nntp.google.com!69no1146877qgl.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 21 Jul 2015 17:17:38 -0700 (PDT) In-Reply-To: <1npnbotrqohbb$.cj0by0oyo31r$.dlg@40tude.net> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=73.138.95.40; posting-account=wEPvUgoAAABrLeiz_LRhQ3jeEhyfWVMH NNTP-Posting-Host: 73.138.95.40 References: <084c0dc7-ae74-4cb8-b1fe-78f42de94291@googlegroups.com> <5IidnWtEWowowjHInZ2dnUVZ5v6dnZ2d@giganews.com> <61db6272-72a4-47d7-b0e5-e870ac8a0432@googlegroups.com> <9078db18-03ef-4724-9818-e9ae37e3d7a8@googlegroups.com> <1opmyg48btl6a$.1pgzq9yrcmv6t$.dlg@40tude.net> <3922d054-290f-4a7d-8660-85eeac6072e9@googlegroups.com> <9daa54dc-338a-4a78-b553-5609623ff061@googlegroups.com> <1npnbotrqohbb$.cj0by0oyo31r$.dlg@40tude.net> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Weakness of Ada is expensive / security / etc. ? Anything else? From: NiGHTS Injection-Date: Wed, 22 Jul 2015 00:17:39 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:26950 Date: 2015-07-21T17:17:38-07:00 List-Id: > Label text wrapping may depend on the widget size requisition. So you > should set the label size explicitly. It could be a GTK bug as well, > because it is highly unlikely that anybody would use that for text > rendering, there is Gtk_Text_View for that. And because GTK 3 reworked mo= st > of widget sizing. It affects things like tooltips (built in) and various other things that in= herently use labels. I've explicitly set widths to all inherited widgets in= cluding the label itself and this had no effect. I made sure Word wrapping = was enabled and followed all correct guidelines on the subject. Again it wo= rks in Windows, just not in Linux. > GTK is full of bugs, especially GTK 3. But that has nothing to do with Ad= a. I am not blaming Ada. Its a beautiful language. I merely suspect that GtkAd= a's thick bindings have something to do with it. I am not dismissing the po= ssibility that GTK 3 is also at fault, but in my mind I feel that the GTK c= ore library is probably more tested than GTKAda (A misconception maybe? I w= ould love to be wrong about this.) > Style is much more than colors. All widget style properties can be change= d. >=20 Well you were talking about "themes", and no doubt styles involve both colo= r and structure. On that note I am quite disappointed by how limited the GT= K CSS support is with regards to things like setting margins and other stru= ctural parameters. They simply don't work. I can only use the CSS to define= colors, fonts, and backgrounds. I've been forced to hard code structural t= hings like margins which I feel is bad form as it should belong in the styl= e sheet. > There is GtkAda mail list. >=20 I've looked and couldn't find it. I would love to know what the address is = if you don't mind me asking. > I cannot tell anything for that, I never used it. I dropped using > DB-specific bindings a decade ago. ODBC does the job. There is no serious > reasons to use DB-specific bindings. GNATCOLL's database library was not designed to be DB-Specific. From what I= understand of their design philosophy is that they are offering an strongl= y-typed Ada-esque approach to work with SQL queries and other common databa= se tasks using a common seamless API. They only support two databases curre= ntly but it was designed to support whatever database is needed for the job= . If done correctly you should be able to switch databases without changing= code in GNATCOLL. It would have been nice to have added support for ODBC, = but the GNATCOLL is designed to facilitate interfacing to anything includin= g ODBC. I fell in love with the GNATCOLL SQL philosophy. Unfortunately the designer= s have not done a good job of generating interest in the project. In my cas= e I can't get any support whatsoever with using that library and it seems l= ike no one here takes it seriously. Its a shame.