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.52.181.200 with SMTP id dy8mr43295903vdc.8.1412176263922; Wed, 01 Oct 2014 08:11:03 -0700 (PDT) X-Received: by 10.140.90.20 with SMTP id w20mr9575qgd.24.1412176263895; Wed, 01 Oct 2014 08:11:03 -0700 (PDT) Path: border1.nntp.dca1.giganews.com!nntp.giganews.com!dc16no265778qab.1!news-out.google.com!i10ni57qaf.0!nntp.google.com!s7no146997qap.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 1 Oct 2014 08:11:03 -0700 (PDT) In-Reply-To: <23555c8e-1746-4db4-ac07-ff0a6f9c0873@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=86.128.185.17; posting-account=28F2IwkAAACL1Z5nRC-dE7zuvWdbWC7P NNTP-Posting-Host: 86.128.185.17 References: <07383010-822f-4732-bb11-273f8876f4c7@googlegroups.com> <68a3d345-f716-465b-b740-4944a035fbc4@googlegroups.com> <_vHWv.296198$Q61.62547@fx13.iad> <36b0981f-d927-4255-a292-f119172e379d@googlegroups.com> <08c241d6-050d-41e7-80d1-1ff9687bea1a@googlegroups.com> <23555c8e-1746-4db4-ac07-ff0a6f9c0873@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Gnoga - The GNU Omnificent GUI for Ada From: tonyg Injection-Date: Wed, 01 Oct 2014 15:11:03 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xref: number.nntp.giganews.com comp.lang.ada:189280 Date: 2014-10-01T08:11:03-07:00 List-Id: On Wednesday, 1 October 2014 14:31:22 UTC+1, David Botton wrote: > > Is there a GUI tutorial coming soon >=20 >=20 >=20 > Everything so far are GUI tutorials, but I think you want something that = looks closer to a VB setup >=20 >=20 >=20 > >, I am very interested in making views appear and disappear with button = presses, data be updated in labels on the screen etc. and also for position= ing of widgets etc. Great, thanks for that.... >=20 >=20 >=20 > The next tutorial on forms will I am sure be what you are looking for. I = hope to have time to do it today. I've been working on binding some remaini= ng parts, for example last night I added the ability to create autocomplete= lists for inputs and fieldsets for group form elements. >=20 >=20 >=20 > The example will show you how to create and interact with form elements, = etc. >=20 >=20 >=20 > As for more about positioning, I think a full tutorial on that alone is v= ery called for and will add it to the list now and see if I can skip ahead = and do that sooner rather than later. >=20 >=20 >=20 > In the mean time, to "manually" position anything anywhere, after creatin= g your element do: >=20 >=20 >=20 > My_Button.Position (Fixed); >=20 > My_Button.Top (10); >=20 > My_Button.Left (10); >=20 >=20 >=20 > One you change the Position system to Fixed you can then place an element= any place you want. >=20 >=20 >=20 > The default is Position (Static). Which means elements are added on after= another at the bottom of the view as you add them. If they are block eleme= nts they take an entire row, if inline they are placed one after another fr= om left to right. >=20 >=20 >=20 > You can change the default Display of an element to be inline or block us= ing: My_Element.Display (block); or My_Element.Display (inline); >=20 >=20 >=20 > I realize this may be too much info for now :) I am adding View types tha= t allow for all sorts of automatic positioning, columns, etc. in the near f= uture. >=20 >=20 >=20 > When I get the positioning tutorial done it will all make more sense and = can see how simple it can be. >=20 >=20 >=20 > As for hiding and displaying Views. Views are like any other element and = can be placed in to other Views, styled, etc. The default create does make = it resize and take up the entire window if the window is the parent. So giv= en that you can have many views ( or any element) and display and hide each= as desired using: >=20 >=20 >=20 > My_View_or_Element.Hidden; or My_View_or_Element.Hidden (False); >=20 > This will make an element be completely hidden from view and take no spac= e on the page. >=20 >=20 >=20 > or >=20 >=20 >=20 > My_View_or_Element.Visible (False); or My_View_or_Element.Visible); >=20 > This will make an element not be visible but it will still take up the sa= me space it did before on page. >=20 >=20 >=20 > I'll make sure there are examples of all the above in coming tutorials. >=20 >=20 >=20 > David Botton