Description

Some apps aren't available on the web, such as the Terminal and Files Manager. This PR adds a property that enable apps to tell if they can run on the web or not. If not, they won't show up

Depends on https://github.com/dahliaOS/backend/pull/5 to be landed first

Type of change

Please tick the relevant option by putting an X inside the bracket

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

Checklist:

• [x] My code follows the guidelines of this project
• [x] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] All current GitHub actions pass
• [ ] Any dependent changes have been merged and published in downstream modules
• [x] I have checked my code and corrected any misspellings
• [x] I have read the CONTRIBUTING document

• Adds: xml, easy_locale as dependences

• Replace locale delegates for delegates provided by easy_locale pkg

• [x] New feature (non-breaking change which adds functionality)

• [x] This change requires a documentation update

How was this tested?

Test Configuration:

• dahliaOS Build number: 201004
• Hardware:
• VM:

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have checked my code and corrected any misspellings

Hi, I tried to improve the look and feel of the quicksettings.

I added a bit padding on the sides, increased the border radius, height and grid size and added bouncing physics. I also moved the featureNotImplemented dialog into its own function to recude unnecessary code. I changed the slider to two sliders, one for brightness and one for volume and made them slidable (but not actually working)

And btw it looks like I changed much in main.dart but thats only because I auto formatted the code

Preview:

Can someone let me know if this is useful.

I was curious what the UX experience is to run it on a Desktop. Its actually very useful, because you can run it in full screen, and just use the apps and forget about the real desktop behind it.

also its quick for working on the app because go-flutter has hot reload.

I only had to make minor mods to the main.dart file and add a main_desktop.dart file and break out the "MyApp" class to a new file called mainapp.dart, and get the new main.dart and main_desktop.dart to call it.

https://www.youtube.com/watch?v=epoNDPnGjU0&feature=youtu.be

• its funny how the Text Editor gets a bit confused when i try to select text.

Makefile:

# https://github.com/dahlia-os/pangolin-desktop

# The main dev
# [email protected]

# wow it works on Mobiles

LIB_NAME=pangolin-desktop
LIB=github.com/dahlia-os/$(LIB_NAME)
LIB_BRANCH=master
LIB_FSPATH=$(GOPATH)/src/$(LIB)

print:
	@echo $(LIB_NAME)
	@echo $(LIB)
	@echo $(LIB_BRANCH)
	@echo $(LIB_FSPATH)

dep:
	# git clone
	mkdir -p $(LIB_FSPATH)
	cd $(LIB_FSPATH) && cd .. && rm -rf $(NAME) && git clone https://$(LIB).git
	cd $(LIB_FSPATH) && git checkout $(LIB_BRANCH)
dep-clean:
	rm -rf $(LIB_FSPATH)
code:
	code $(LIB_FSPATH)
flu-dep:
	cd $(LIB_FSPATH) && flutter packages get
hov-dep:
	go get -u github.com/go-flutter-desktop/hover
	go get -u github.com/go-flutter-desktop/go-flutter

mob-run:
	cd $(LIB_FSPATH) && flutter run -d all
desk-init:
	# need to manually fix main.dart first DONE
	cd $(LIB_FSPATH) && hover init $(LIB)
desk-init-clean:
	rm -rf $(LIB_FSPATH)/desktop
desk-buildrun:
	cd $(LIB_FSPATH) && hover build
	open $(LIB_FSPATH)/desktop/build/outputs/darwin/Pangolin
desk-run:
	cd $(LIB_FSPATH) && hover run

This is to show what the current desktop looks like, as the UI overhaul has drastically changed the overall appearance. So it would be a good idea to update the readme images to show the current state of the desktop.\

Images come from the dahlia documentation website, it just links to them.

Using a custom Xlib binding (with the help of ffigen), I've been able to communicate (somewhat oddly) with Xlib and thus the X-server. Here's what's happening and what needs to be done.

• [x] Communication with X-server
• [x] Window Manager Registration
• [x] Window Management
• [ ] and finally, making it look pretty.

Use power off instead of shutdown to completely shutdown kernel and device itself. Also include Bourne shell /bin/sh for making the is even more lightweight.

This will implement a CI system for web demos. AFAIK you have to be on Chrome and a somewhat fast device to use it. I don't know, it's just the way Flutter's set up for some reason.

• Moved all applications to application/ directory.
• Added fonts for system wide use. (Not implemented)
• Created an Inherited Widget for referencing to constants.
• Developing Application Manager and component widgets.
• Added Palette Generator (modified to extract colors from ByteArrays)

https://github.com/flutter/flutter/commit/4218c0bc38bc74a97b1b03d7b8b7f0ce32e29468

it was commited on 22 april it must have got to stable flutter channel now

we'll be having a lot of such situations as @nmcain said it'd be nice to have someone on dev channel of flutter to fix bugs before they even happen

Pull request template

• Please make sure you read and fill this template out entirely
• PRs that don't have the template filled out will be ignored

Description

This fixes the terminal code in this file by removing it completely because pangolin would not build otherwise

• Please include a summary of the change and which issue is fixed
• Please also include relevant motivation and context (Why is this change required? What problem does it solve?)
• List any dependencies that are required for this change
• If it fixes an open issue, plase link to the issue here

Fixes #(issue)

Screenshots (if appropriate):

Type of change

Please tick the relevant option by putting an X inside the bracket

• [ X] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

Checklist:

• [ X] My code follows the guidelines of this project
• [ X] I have performed a self-review of my own code
• [ X] I have commented my code, particularly in hard-to-understand areas
• [ X] I have made corresponding changes to the documentation
• [ X] My changes generate no new warnings
• [ X] All current GitHub actions pass
• [ X] Any dependent changes have been merged and published in downstream modules
• [ X] I have checked my code and corrected any misspellings
• [ X] I have read the CONTRIBUTING document

Bumps lint from 1.10.0 to 2.0.1.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps battery_plus from 2.2.2 to 3.0.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Description

• This isn't much of an issue more of an improvement, on your website it shows the zenit UI slider for the quick settings, so I added it!
• new dependencies zenit_ui

Screenshot

Type of change

Please tick the relevant option by putting an X inside the bracket

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

Checklist:

• [x] My code follows the guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] All current GitHub actions pass
• [x] Any dependent changes have been merged and published in downstream modules
• [x] I have checked my code and corrected any misspellings
• [x] I have read the CONTRIBUTING document

Description

To promote a higher quality and readable code, I am trying to introduce strict linting rules. The rules applied were based on Very Good Ventures' rules from the very_good_analysis package repo.

This is their article about the package.

First, I removed the lint package from the pubspec.yaml file. Then I took their rules and added them to the analysis_options.yaml file. After running dart fix --apply, I manually fixed other warnings, and removed the rules that would introduce somewhat significant changes to the code.

No dependencies are required for this change.

Type of change

Please tick the relevant option by putting an X inside the bracket

I am really not sure what to check here for this.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

Checklist:

• [x] My code follows the guidelines of this project
• [x] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] All current GitHub actions pass
• [ ] Any dependent changes have been merged and published in downstream modules
• [x] I have checked my code and corrected any misspellings
• [x] I have read the CONTRIBUTING document

Description

• Makes Customisation screen responsive.
  • Makes Theme Section horizontally scrollable
  • Makes Taskbar Section resizable (Changed the widget from Stack > Row)

Screenshots (if appropriate):

• Previously

• Now

Type of change

Please tick the relevant option by putting an X inside the bracket

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

Checklist:

• [x] My code follows the guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] All current GitHub actions pass
• [x] Any dependent changes have been merged and published in downstream modules
• [x] I have checked my code and corrected any misspellings
• [x] I have read the CONTRIBUTING document

Centers search bar hint text by increasing it to 46 pixels high. Will submit an issue to the flutter repo.

Also fixes some padding to make the search bar more symmetric.