Re: O$: adding column to complex grid

Ken

Also interested in a sample lib if one is available

Nigel

> On 11 Aug 2017, at 16:59, Alan Schmidt <alan@goconnected.com> wrote:
>
> Hi Ken,
>
> That sounds cool.
>
> I’m interested in a sample lib.
>
> -Alan
>
>
> On 8/10/17, 7:13 PM, “omnisdev-en on behalf of Ken Dimson” <omnisdev-en-bounces@lists.omnis-dev.com on behalf of ken@dimson.com> wrote:
>
> For me its always valuable to read words from the experts and Doug is one of the many on this list. I will now need to explore and compare headed lists again.
>
> In our app I wanted one list that could serve all purposes some of which are the same as Doug describes.
>
> 1 – display and look like an ordinary list
>
> 2 – allow an individual cell to appear as a link (blue txt etc) and be clicked on from which we would then open some other say detail window or display detail in same window below etc
>
> 3 – become a fully enterable list for data entry
>
> 4 – allow the user to customize by changing the order and selection of columns to display
>
> 5 – allow the user to change size of columns
>
> 6 – allow the user to change the text color of entire rows or individual cells
>
> etc
>
> Also our app is 25 libs + so I was also concerned about the number of window classed that might be created to achieve a complex grid
>
> To achieve all of the above I decided that I wanted a controller class to dynamically create a complex grid and therefore decided on one window class and one controller class.
>
> Objects that need a complex grid pass parms to this grid controller and it builds on the fly a complex grid. We thus reuse that same window class for complex grid throughout our app many times most often as a subwindow etc. Because the same controller builds complex grids throughout our app we were able to expand its use to include things like add or removing columns by the user and colors etc.
>
> This means to answer the original question, for a developer to add a column between column 3 and 4 the developer adjusts the parm string sent to the controller.
>
> I can prepare a sample lib if interested.
>
> With that now I am going to review Doug’s comments and explore options for headed lists.
>
>
>
> Ken Dimson
> ken@dimson.com <mailto:ken@dimson.com>
>
> That you are here — that life exists, and identity; that the powerful play goes on and you may contribute a verse. — Whitman
>
> What will your verse be?
>
>
>
>
>
>>
>>
>> On 7 Aug 2017, at 16:06, Doug Easterbrook wrote:
>>
>>> hi nick.
>>>
>>> you said two dirty words as far as your question went. Complex Grid.
>>>
>>>
>>> so be sure, complex grids are useful in any application and we have 4 places that we use them. They are fantastic for a complicated multi line display with large icons and entry fields — however the limitation about them is .. changing them involved work.
>>>
>>>
>>> on the other hand, a headed list box offers a whole lot of good so we use it in about 99% of our application. things such as:
>>> easily hiding and showing columns
>>> easily dragging columns from one place to another
>>> easily extending the application if you add one more column to your list
>>> ability to fix the first few columns in a list so that they can’t be scrolled off window
>>> some ability to do entry into some columns
>>> you can display small icons and change colours on list lines to highlight important features
>>>
>>> we have all our headed lists composed from a table class so that we save the last look of the list for each user and restore that when they next log in. adding a new column to the list for is simply:
>>> add the field to the query class
>>> update the fields visibility in our data dictionary
>>> done — there are no further coding changes, or window changes at all
>>>
>>>
>>> I find that a headed list is pretty easy for our customers to grasp and they like the ability to move columns. it far outweighs complex grid — which we have to program everything for.
>>>
>>>
>>> when we converted from the classic world, we started off thinking everything was a complex grid, simply because thats what we were used to…
>>>
>>> until we discovered the sheer joy and simplicity of the headed list. its my favourite studio interface object.
>>>
>>>
>>>
>>>
>>>
>>>
>>> Doug Easterbrook
>>> Arts Management Systems Ltd.
>>> mailto:doug@artsman.com
>>> www.artsman.com
>>> Phone (403) 650-1978
>>>
>>>> On Aug 4, 2017, at 1:54 AM, Nick Renders <omnis1@arcict.com> wrote:
>>>>
>>>> Hi *
>>>>
>>>> I have a newbie question about the complex grid.
>>>>
>>>> Whenever I want to add an extra column in design mode,
>>>> I update the $columns property of the object. Omnis
>>>> adds a divider at the end, and I can start adding objects
>>>> in the new column.
>>>>
>>>> But how do I add a column in between 2 other columns?
>>>> Is there perhaps some way to re-order the columns in a
>>>> complex grid?
>>>>
>>>> The only way I have found is to drag fields from one
>>>> column to another, but that is really tedious work.
>>>> Am I missing something obvious?
>>>>
>>>> Best regards,
>>>>
>>>> Nick Renders
>>>>
>>>> _____________________________________________________________
>>>> Manage your list subscriptions at lists.omnis-dev.com
>>
>>
>> _____________________________________________________________
>> Manage your list subscriptions at lists.omnis-dev.com
>
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com
>
>
>
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com

_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com