Create a server component to accept icon requests and generate the xml files. about frost HOT 17 CLOSED

I am interested!

from frost.

from frost.

I use the icon requests for Turtl, in my experience, it might seem that it would make things easier, but it has some design problems although the fundamental problem I find is when discriminating between requests that include FLOSS or non-free apps. It could be solved by crossing the packageid of the requests with the packageid of the apps hosted on fdroid https://gitlab.com/fdroid/fdroiddata/blob/master/stats/known_apks.txt
I have definitely stopped using Turtl for this.

The idea of @conrad-heimbold in my opinion is the best way to go, so that we have the updated appfilter scraping the data directly from fdroid and the apps. So we would only have to deal with the icons, mounting the xml from the list of icons with the scripts that we currently have.

What type of server are you thinking of?

from frost.

from frost.

Scraping F-Droid is one option but an issue arises when someone uses default apps or sideloaded apps. I definitely want to include icons for certain other apps like the Lineage camera, FastHub, or Magisk, but I am still not sure where to draw the line for support, and this is a huge factor in the server design.

I am familiar with PHP and node so I was thinking of using one of those. I don't think submitting the requests over github is very useful, so I would rather add the requests to a database and include a web interface to view and manage the requests.

from frost.

from frost.

I definitely want to include icons for certain other apps like the Lineage camera, FastHub, or Magisk, but I am still not sure where to draw the line for support

I agree. For me a FLOSS license is enought. What about 2 appfilter parts? A main part with fdroid scraped lines and another one with other floss apps lines, manually updated.

What you think about modi the turtl APP

I can grant permissions inthe gitlab repo to who wants, for modifiying Turl in the direction needed. I have not the skills for writing that code.

from frost.

@xphnx I was actually planning on adding the code to the icon pack so users wouldn't need a separate app. I will probably be using a lot of the code from turtl for this. I am unsure about using two appfilter files because there is no easy way to combine them from the code, it would have to be done with a script. I ran into a similar issue when I was trying to figure out a way to keep the icon packs updated.

@beli3ver alright, PHP will work fine.

from frost.

Any progress with this?

from frost.

None so far, I spent winter break making a Chip8 emulator instead. I am adding it to F-Droid soon, just have a few tasks to finish first. This is still on my radar though, it's so annoying to add icons manually.

from frost.

I stay tuned.

from frost.

Okay, I am working on the database design and have a couple of questions for all of you.

1. Can you think of examples where one icon would be used by two different packages? Maybe something like FastHub and FastHub-Libre. Do you think this would be a good idea?

2. Do you think it would be a good idea to include "default" icons for some apps? I am talking about the generic icons being used if no icon is found for a certain app. For example, if the icon pack doesn't have an icon for Google Calendar, the generic calendar icon would be used instead.

3. Should the service allow for custom icon filenames or use a default schema? So FastHub would have to be named fasthub.svg every time. Not sure if this would make things easier or harder, I am on the fence about this right now.

4. Should we modify Turtl or just include the code in the icon pack. I am leaning towards the icon pack since it will not be that much code in the first place, an users wouldn't have to download a different app.

Lastly, does anyone have experience with frontend work and have any free time to help with the project? I can use whatever works best but help would be appreciated. I will make a repository if anyone can contribute code. I have worked with databases before but good CSS is a mystery to me.

from frost.

Here is a basic outline of what the website would do. It would have a list of every icon in the database. Icon pack creaters would check a box for every icon they have and the server would generate an appfilter.xml for every icon in that pack.

Positives:

• It would include every version of the class name in the database automatically, so no more work trying to update the component name for each app on every project
• Could add support for icons that wouldn't have been there before, in the case of "defaults" or several apps being able to use one icon

Negatives:

• Have to run a server, that costs money and adds complexity to the icon pack projects we have plus requires problem solving on this project to get it working
• Still requires quite a bit of work to get icons added to an icon pack, doesn't reduce effort that much
• I personally hate adding server components to something as simple as an icon pack, maybe this could be accomplished with scripts somehow instead of adding so much complexity to the project

from frost.

I personally hate adding server components to something as simple as an icon pack, maybe this could be accomplished with scripts somehow instead of adding so much complexity to the project

This.

from frost.

I think the icon packs have lost a bit of interest from users, and it is likely that the adaptive icons will definitely end with the need to customize icons in the future ...
For my part, I have the icon pack quite unattended.
My opinion is that mounting a server would involve too much complexity

from frost.

Same here.

from frost.

Sounds good, no worries. Closing this issue then. I will see if I can think of a better way to organize the app filter xml though, I hate how difficult the process is for adding the component names.

from frost.