{dialog.object}.getTopParentObject() and state variables

[madtowng]

Hi Everyone,
I'm putting this here because this is a combination of 2 topics.
My ultimate goal is to programatically update a viewbox/list control from
a child/grandchild/great grandchild component.

The code below is getting the value of state variable "refreshbutton" from the
main UX component.

// code on grandchild component button
var topObj = {dialog.object}.getTopParentObject();
//{dialog.Object}.getStateInfo();refreshbutton
var x = topObj.stateInfo['refreshbutton'];
alert(x);​

' Code from primary UX on-initialize event to set state variable
e._state.refreshbutton = "hotDOG"

[peteconway]

There seems to be a lot of embedded components here, so I assuming you you have a grid in there somewhere, anyhow - I would set an argument in the the object that has the button in it and get the value of the topObj.argument value.
- but its been a long time since I messed with embedded controls.

Pete

[madtowng]

Hey Pete,

I probably should've(could've) done embedded, but it's all done with control clicks.

[peteconway]

No, that's not what I mean, what are the controls - what type of control is the {dialog.object}.getTopParentObject() - it it in the same UX? or another parent UX.

[madtowng]

I think we are separated by the term "embedded". For example: I use a collapsing menu on the primary UX that has a list control (I really need to improve my viewbox skills) that displays upcoming events for a warehousing operation. Clicking the option to view the current active inbound transactions brings up a grid component. Clicking the ARRIVED button for a row brings up an UX to edit that row. If those changes alter the status of that transaction (it arrived) I want the change to be reflected in the list control on the primary UX.

[Lance Gurd]

sounds to me like it should all be in one UX with various viewboxes, I have stopped using cascading menu's and now use viewboxes instead, much more control and then if all on one simple UX no need for and topParent or parent stuff.

[mikeallenbrown]

Hi Everyone,
I'm putting this here because this is a combination of 2 topics.
My ultimate goal is to programatically update a viewbox/list control from
a child/grandchild/great grandchild component.

The code below is getting the value of state variable "refreshbutton" from the
main UX component.

// code on grandchild component button
var topObj = {dialog.object}.getTopParentObject();
//{dialog.Object}.getStateInfo();refreshbutton
var x = topObj.stateInfo['refreshbutton'];
alert(x);​

' Code from primary UX on-initialize event to set state variable
e._state.refreshbutton = "hotDOG"

What's your question?? ...I've read this post a couple times and I don't see one. Is the code not working or something else?

[madtowng]

Hi Lance,
I wanted to use viewboxes, but let's face it, viewboxes don't follow the low-code/no-code motto that brought many people to Alpha Software.
Combine this with a lack of documentation that cause developers to suffer from text overload.

There is a video from over a decade ago that shows the power of the grid (

)

I'm still not a fan of the list control, but it certainly is a lot easier to use now than it was the first time I used it.
I didn't have to use css to produce what I needed.

The image below shows the primary screen the user sees. This is meant for use on the desktop, but I will soon be creating a mobile version.
Each item uses grid, complete with multiple search controls to allow the end user to easily get to the data he needs.
The several of the columns in many of the data rows are click enabled, allowing the user to easily edit data or generate required documentation
including labels, checkin/pull sheets, and of course BOL's.

The viewbox is a great tool, but it takes a lot more to design it to do what this project does.

Don't get me wrong, I really do appreciate the assistance and knowledge I've gained from you and Peter and everyone that has shared information
and ideas with me, and I will continue to seek this information as I continue trying to "create a better mousetrap".


2022-10-27_9-45-19.png

[madtowng]

What's your question?? ...I've read this post a couple times and I don't see one. Is the code not working or something else?

This didn't start as a question...it started as sharing information, not to mention a place to easily recall how to do something instead
of trying to remember which project I created it.

[Lance Gurd]

Hi Gregg,

I know what you mean about the low code and lack of documentation, but a little perseverance is well worth it.

When you first put a viewbox on a UX you can load a sample viewbox from the home page of the viewbox builder, there are a few and they are all worth an experiment with. The menu in your panel card 1 could easily be replaced with one of the samples and the grid in panel card 2 with a list style viewbox. For a really good example have a look at 'Advance: List of orders for a customer', this has been the basis for many of my viewboxes

[peteconway]

There is a video from over a decade ago that shows the power of the grid

I wrote that application and did the video - at the time the iPhone was being born. - Times and needs change, the Grid in the right hands could do wonders - but developers wanting to be serious about developing in the now, need to plan without it.
Having your data bound to a preconceived control in general methods will not cut it in todays world - you never know what device your client will end up using now or in the future - that control just wont survive in anything other than a desktop browser, just like tabbed UI - make the jump, I stopped using grid the day the List Control arrived an stopped using List Controls the year the Viewbox arrived and have never looked back,
Pete

[madtowng]

Pete,
Please don't misunderstand what I was saying.
I would absolutely LOVE to use the viewbox for my project, but until I actually understand what I'm doing,
I have to work with what I know.

For this particular project, the end user is using a desktop computer. I was able to get him off the spreadsheet
his predecessors created before he considered joining the team. We now have a system that actually keeps
track of inventory, and charges the correct amount.

Up next is an app for a mobile device for the people working the dock to use.

Last but certainly not least, I was pointing out that Alpha seems to be drifting away from the low-code/no-code mantra,
and the documentation for those of us without computer degrees quite often leaves us frustrated.

[WindForce]

Hi Lance,
I wanted to use viewboxes, but let's face it, viewboxes don't follow the low-code/no-code motto that brought many people to Alpha Software.
Combine this with a lack of documentation that cause developers to suffer from text overload.

There is a video from over a decade ago that shows the power of the grid (

)

I'm still not a fan of the list control, but it certainly is a lot easier to use now than it was the first time I used it.
I didn't have to use css to produce what I needed.

The image below shows the primary screen the user sees. This is meant for use on the desktop, but I will soon be creating a mobile version.
Each item uses grid, complete with multiple search controls to allow the end user to easily get to the data he needs.
The several of the columns in many of the data rows are click enabled, allowing the user to easily edit data or generate required documentation
including labels, checkin/pull sheets, and of course BOL's.

The viewbox is a great tool, but it takes a lot more to design it to do what this project does.

Don't get me wrong, I really do appreciate the assistance and knowledge I've gained from you and Peter and everyone that has shared information
and ideas with me, and I will continue to seek this information as I continue trying to "create a better mousetrap".


2022-10-27_9-45-19.png

Hi
In your grandparent UX create a javascript function that returns the value of the needed state variable, for instance getMyState()
In your child or grandchild just call getMyState() to get that value.
It's a mesmerizing fact i learnt from one of the weekly webinars, calling a javascript function in a ux will drill back up to parents and grand parents until found !

Jaime

[CharlesParker]

It's a mesmerizing fact i learnt from one of the weekly webinars

I just wanted to chime in and say the team does an excellent job of putting these things together - if your not there be sure to visit the youtube page and catch up - I just cannot say enough about them.

[Lance Gurd]

I am often busy when they go live, so catch up on YouTube often and have learned a lot. My only gripe is the links are often posted in the chat window and therefore not available on YouTube. I have asked for them to be published with the videos but still seems to be missing