Tuomo Valkonen <[EMAIL PROTECTED]> writes: > Even if I decide to keep it all in one place, package > maintainers should probably create a pwm package that depends on the ion > package and includes such a script.
Another variant would be to place each module in a separate package, ie. ion-tilews and ion-floatws, that both provide a virtual package "ion-ws" which the ion package depends upon. The pwm package would then only have to depend on the ion-floatws package, thus not requiring floatws-only (PWM) users to have the ion workspace module installed. But perhaps this isn't really needed considering the small size of the modules. However, this raises another question. Now when ion is modularized, there's suddenly two things with the same name, the ion program (containing only wmcore now) and the ion workspace module. This is a bit confusing. Since PWM will now be renamed to "floatws", have you considered renaming ionws to something like "tilews"? Another solution would be to keep the name ionws and rename the executable, because ion isn't really a hack for tiled windows anymore, it is now a quite general window manager with support for multiple approaches to window management. Compared to other window managers, wmcore makes very little assumptions on how window management is supposed to be done. This allows unusual approaches such as ionws, but it certainly doesn't limit it to just that one. And currently, the name ion is very strongly associated with this particular way of window management. /Pelle
