Where do I put that code? Can’t figure it out 
You mentioned that you had python knowledge. Your key error message in the screenshot says where the issue is.
If you are struggling with python then shout … I will have to find some time to help with coding. Just ensure your fork is up to date so that I can merge
it is up to date.
Look at this line:
if systemstate.codename in config['budgie-applets', 'development'][applet]['repos']:
What I’m saying is to find that line, I used the Find tool and searched for config. No results. If you can point me to the proper line, I’ll be happy to fix it ASAP
Look closely at the screenshot - it said line 237:
Stupid me. I was looking at the wrong file ALL ALONG!
@fossfreedom my code there:
for applet in config['budgie-applets', 'development']:
if systemstate.codename in config['budgie-applets', 'development'][applet]['repos']:
app.update_page("." + applet, 'show')
else:
app.update_page("." + applet, 'hide')
What do I change? Thanks…
No worries that you are finding it a bit complicated. Below is a diff that will get you going
thanks so much, will finish and then make a pr.
Side note, can budgie welcome install from DEB files instead of repos/ppas?
Also, is Welcome based on Ubuntu Mate’s Welcome? Saw the copyright notice, and looks similar
I wouldn’t want it to - all packages should be capable of being maintained - just installing the deb itself means it would never receive updates.
Yes - forked it a long time ago - so yes it shares some stuff - but does look and function differently now.
Thanks.
Few areas that really need to be considered:
zsh - really needs configuration such as plugins and theming options. Just installing the package doesnt add any value.
fish - i guess - never used it so can’t really comment how useful - nor do I know if the user has to-do anything else to make this useful after installing the package.
Other stuff that needs to be considered for this new development capability:
I am thinking of editors: vscode snap
may be atom as an option
pycharm snap
“Getting started with budgie applet development” : git + build-essential + dev packages for budgie-extras,
“Getting started with budgie desktop development”: git + build-essential + dev packages for budgie desktop.
Both of the above needs source packages enabled in /etc/apt/sources.list
“Create and maintain debian packages”: git, bzr, ubuntu-dev-tools, openssh-server
all true.
- I don’t know how to add snaps, guidance there would be appreciated, although for VSC the DEB might be a better idea, it auto updates as well via auto-adding a custom repo: https://code.visualstudio.com/updates/v1_10#_official-signed-repositories-for-linux
- Shell config; here, Fish works perfectly out of the box. On the other hand, ZSH requires going through a configuration wizard; I could counteract this by providing a minimal yet functional .zshrc file (although Oh My Zsh might be a good idea to install). They do have to be manually set as the default using
chsh, though. Don’t know how to run that OR add a .zshrc file to the user’s home. - All those packages could be great, if you want feel free to add them, otherwise I can update my PR when I have time.
Sorry, my keyboard is broken, so it’s harder to type. Getting a new one soon
thx, @fossfreedom
Any thoughts on the above?
thx
I have been interested in doing some sort of developer section (or app even). But here is why I sort of put it on hold (in what I was going to originally going to put together). The developer experience is pretty unique and special to each individual. And my concern is how do you provide something of real value? There are considerations based on which stack you are looking to install. IDE’s are a religious war at times. If you are installing an alternate shell like this and moving away from bash - there is usually a problem or behavior that person is trying to solve. What is it? For example, I personally moved to ZSH, BUT - to get it where it solved my problems/desires, I needed to add plugins, etc before it brought value (for me in this case). So I tend to agree that just putting the software is only a first step. I may almost argue that anyone who is advanced enough to “want” something like ZSH - likely has already ran the sudo apt install zsh and likely even installed oh-my-zsh (and done some initial config)
So again it comes back to what are we trying to accomplish, what are the goals and what is the value.
I myself was still trying to determine this (and why I paused my own progress and test code I had written). I went back to blueprint this out before I started putting together code and config.
So, if I understand you correctly, most people that would want those tools would have the knowledge to install and configure it from the terminal?
If not, please clarify 
I can’t say that for sure (no data). But I suspect. More the point I am attempting to make is that we need to identify the goal and the problem we are trying to solve. 
Hmmm.
I’ll add a couple more tools soon.