Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: Guy on May 07, 2011, 08:10:28 AM
-
Here is an idea which I think would be good to implement sometime in the future - not urgent, just whenever it is practical.
At the present time, when you open the App Browser, you get a list of extensions. Some of these are apps, and others are dependencies.
I suggest, have some way to differentiate between apps and dependencies, and have only apps listed in the App Browser, not dependencies. (Still have dependencies listed in the Depends and Size tabs)
That would make it simpler to find apps.
The same thing could be used with removing apps.
You may include the option to list all extensions, for those who want that option.
-
There is a plethora of extensions which could as well serve as apps and deps of other apps.
Also there are extensions which are apps but could be dependencies of 3rd party apps.
-
There is a plethora of extensions which could as well serve as apps and deps of other apps.
Also there are extensions which are apps but could be dependencies of 3rd party apps.
They could be included, but there are some extensions which are only ever dependencies. When looking for apps, it is necessary to search through these as well.
-
That classification would still be an opinion, really. What if I specifically want to load libfoo to develop for it, and don't want to search for an app that needs it first?
I do think some simple filters would be ok, ie checkboxes for both libs (^lib) and modules (.*2\.6\..*). These wouldn't need any changes in the data, they'd work just on the names.
-
or/and a exclude filter to choose arbitrary patterns could be useful to filter undesirable results
-
Most still do not use the Search or Provides area of appbrowser, which I find much quicker and much more targeted than having to click a check box to get a less targeted list for me to scan.
But the definition of an application versus an extension is still an interesting topic. I would say an application is something that a user would launch (run). Typically this would imply an embedded menu and/or an icon for system launchers.
Because our current structure has the menu/icon embedded is the reason I have the OnBoot and OnDemand being a user initiated functions.
I am actually pondering this area for possibly a new feature.