On 29 November 2017 at 07:50, Sean P. DeNigris <s...@clipperadams.com> wrote: > Stephan Eggermont-3 wrote >>> 2c) Code subdirectory: enter "src" here !!! >> Do we really need that? Why would I care about that? > > BTW in latest Iceberg this is automatically selected if it is one of the > standard names (e.g. src, repository)
That is cool to automate that, but these names seem a bit generic to take ownership across all domains in random projects. How does the system handle a "src" folder that is not an iceberg folder. What about having an "iceberg.conf" or ".iceberg.conf" file in the root folder? or maybe be more generic cross-platform friendly and use "tonel.conf". This file might also be a place to specify multiple folders containing different packages. A few other random thoughts... Maybe that "Clone repository by URL" dialog could be split in two. The "code subdirectory" field does not impact the cloning operation and is an extra cognitive load when someone new to Iceberg is not sure how it works, which breeds uncertainty about using the tool. After the clone completes, Iceberg could observe the directories in the working copy and present a list of them for user selection (if it wasn't already specified in iceberg.conf) Alternatively, rather than (or in addition to) the [Packages] tab, maybe have a [Working Copy] tab that shows a tree structure from the root directory. The user would then browse into the "src" file to see the packages. This could lead Iceberg in the direction of being a more generic tool to manage other project resources, and also facilitate having multiple packages within the one repo, although synchronising those packages to their own single package repo might get complicated. Directories specified in iceberg.conf could be listed at the top of the [Working Copy] tab for easy access. cheers -ben
