Guille wrote
Just a thought, maybe offtopic,
but that goes in the modularity path...
What about adding also a new ´moose´ tab
to the configuration browser showing only
moose sub-products?
configuration browser first needs something to be able to load Seaside with Magritte. We regularly get complaints about that. A separate tab for Moose doesn't make much sense. Configuration browser is for ease of use, so configurations should provide a list of sensible (to an end user) groups that the browser can use.
Stephan
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I'd like to see the Configuration Browser having a tree interface
and/or a context menu providing a list of groups & versions that
can be installed. This would probably be dependent on some process like
the PharoProjectCatalog CI scraping and compiling the packages