Weekly developers meetup

Hi developers,  I'm missing the video's, since July.  Any chance that you can record and post the video?

Sorry! We'll do best ... today we almost couldn't produce it for technical reasons. Will be published once tomorrow.

temporally back to zoom
https://us06web.zoom.us/rec/share/zmJZYS8AOT27JEFgbDUaG8QvN1zoQ8k4r3s8EeOlf4IWgvJ5tJJEt06Ct_n-qn9x.9m3xohqtdiQG8o-6

https://us06web.zoom.us/rec/share/dKbt08VbRJyjOc0wZtNc3DhSf889-augmwZBmutLE9pcG21FLKUGw7p3CLkr4kll.LpW5Nzqd1Ss3jUii

https://us06web.zoom.us/rec/share/8WlX6iXdBhFdX5FsZQ2MWGLXBdFs-Fo9424CoAi4gZ0WJqn1zyKZxcZ1bqdTz7ar.oGZ-CHIex4oSBIlo

https://us06web.zoom.us/rec/share/3ijWLzK7VY-XRRwkbmZ1phD5tJ-AXOeh58GL1QkVqoONzz2qKCOC7RdCkjxieRW9.6GmkjPhWgb8KANoh

https://us06web.zoom.us/rec/share/NiVPi2piXAQWONo2BaqSQh78umQtuXPGMIDdMX0PCJaRflLuqnD7IuQFSCz9CDFe.XHme_KEXKx0KsbZs

Meeting held, didn't record. It was just @Tearran and me discussing armbian-config related issues. Next week are vacations for many people, so I guess we could just skip it.

https://us06web.zoom.us/rec/share/2DAkFPOHf2H0SWr8XWi69DUqTSAcPVEEEJ83O2RVuk-At1fXnEpaAtIfeB8_yydt.99OHO2CS-yOsq_uy

On 11/16/2023 at 2:17 AM, schwar3kat said:

Winter, Spring, Summer, Autumn.
This can only apply in northern hemisphere countries.  Southern hemisphere is the opposite months.

First quarter, second quarter, third quarter, fourth quarter are possible alternate options.

We forgot on you guys down there   Good catch!

 

Also good task for those who complain they are not contribution as they are not software developers.
https://armbian.atlassian.net/browse/AR-1933 

We have skipped today's meeting. 

https://us06web.zoom.us/rec/share/5QtpKDSnoNj82IR5ZStwDNYIFM1-EHE2-vG8U3jrYkLm6bqcozclBREAuh4LIxFq.dpvHQSh4YzlNU1u8

https://us06web.zoom.us/rec/share/_KNgbricrEDvO4WdkZGrso82cCs7bUxb1uvaUOzni4zI1FELDBTVQ30d97Px7t1n.in4hFwQ6IQEu8pzf

7 hours ago, Igor said:

https://us06web.zoom.us/rec/share/_KNgbricrEDvO4WdkZGrso82cCs7bUxb1uvaUOzni4zI1FELDBTVQ30d97Px7t1n.in4hFwQ6IQEu8pzf

I watched this week's video, and have a question about Joey's configng presentation.
 

If my understanding is correct then the directory/folder that contains the script function determines the menu group, and the script header description determines the menu item wording.

How can we include/exclude a script in the menu based on a runtime condition, like it is possible in armbian config?  E.g. depending on a file or executable existing.

How can we include/exclude a script group in the menu based on a runtime condition like it is possible in armbian config?

@Tearran

 , Great point,  @Igor  Pointed out a probable solution to the concept, &  https://github.com/armbian/configng/blob/main/bin/armbian-configng#L25

On 12/6/2023 at 9:02 PM, schwar3kat said:

How can we include/exclude a script in the menu based on a runtime condition, like it is possible in armbian config?  E.g. depending on a file or executable existing.

How can we include/exclude a script group in the menu based on a runtime condition like it is possible in armbian config?

community direction is needed. Such as use cases for what to show or hide, and what to checks to make the determination.  @Igor  Pointed out a probable solution to the concept, Basic consept logic https://github.com/armbian/configng/blob/main/bin/armbian-configng#L25  

 

The current armbian-config has much of the said "runtime conditions" covered, To progress development, a generalized approach has been taken, keeping current armbian-config compatibility has been a priority.

As for general condition checking. There are a some working examples of approach. With some limitations. Arguably $args.  Sorry, I mean "options". 

To progress a more focused approach development. Community direction is needed.  GIven my choice alone I would continue Focus on Developing ... ,  More accurately playing with a text editor and flat file UI UX elements, svg, html etc. for the project   

On 12/8/2023 at 10:44 PM, Tearran said:

@Igor  Pointed out a probable solution to the concept, Basic consept logic https://github.com/armbian/configng/blob/main/bin/armbian-configng#L25  

 
@Tearran Bear in mind I'm not experienced with bash, so expect some ignorance 😄

Perhaps some kind of standard initialization function if it exists, could be triggered first as each script is parsed,  setting initialization variables could be included as a standard part of any function script.  And a similar menu folder initialization script could be included in any folder.

One of those variables could set visibility.  Another could set menu text, allowing dynamic menu text based on runtime requirements and possibly other options could be added if required.

Any logic could be used to set those variables.

To illustrate with an example of what I am imagining.  Maybe something like this:
(excuse my bash if it is bad or not feasible)
 

# @description Do something useless.
#
# @exitcode 0  If successful.
#
# @options none

# menu_init function triggered first by menu creation routines if it exists
function menu_init(){
    #
    # Only display menu option if internet connection is available
    #
    wget -q -t 1 --timeout=5 --spider http://github.com
    if [[ $? -ne 0 ]]; then
        menu_item=false
    else
        menu_item=true
    fi

    menu_text='Do something useful' # this could override the description as the menu text if it exists
}

function group::string() {s
    echo "Doing something"
    return 0
}

 

@schwar3kat  Bear in mind you have clearly the advantage of specialised knowledge here.
Clearly proven by that pattern  😅 , it is brilliant. For one its set context for🤯.... before I get distracted again 😅
This does not seem to be the place to continue expanding. I am unsure!  Do you have collaborative insight you could share? Could you suggest a better place to expand on this topic? 

 

14 hours ago, Tearran said:

Could you suggest a better place to expand on this topic? 

 

@Tearran I changed the function name in my example to menu_init (because that would be a more accurate description).

I have opened an issue on https://github.com/armbian/configng/issues/26 where the discussion could continue.

Also feel free to pm me.

Regards
Kat

On 12/8/2023 at 10:44 AM, Tearran said:

keeping current armbian-config compatibility

From user perspective - it should function approximately the same. We need to come up with better code (style) as existing one, then upgrade and move further.

 

On 12/8/2023 at 10:44 AM, Tearran said:

Community direction is needed. 

For now, this community its me and @schwar3kat I am sure more ideas will come on the way ...  Yeah, lets continue this directly at PR.

https://us06web.zoom.us/rec/share/_3tMfthlisbKR73mjF_q9x3NqvsIdjkQLidXw-efGXCLc_JoK__XejmMMfNZmgJ3.3RPXEpkatFRzaq1R

Skipped. Next week is holiday season and we are skipping it too. Next one, next year!

First meeting of the year:
https://us06web.zoom.us/rec/share/e-w3eQ5I1-mUoUzziUJWI9lAQyVy7z6H_PPJJ3d9HbUf51tUYuMwnHzlduHNTVb1.8_TlzRbNSc1SPFUP

Back in action:
https://us06web.zoom.us/rec/share/XBdGnLqdJoihDAeEZGv8hs1HCbHloYY9qbTvnfiTBignyodLQXH_aYh0xj7vpvrA.hmG3BztFBtbP26qF

https://us06web.zoom.us/rec/share/t-1WIQTlGjE9b9__fnSG3vxdFqr3axorjVea1vyzPaT_m9Pu3faLovs8MZ5dp3j4.V-KXtC_bdEaNI1QL