The same for network page if the module is already loaded as global/user module.
Reason: When adding new network, I don't know which modules I need to load. E. g. chansaver is useful... but it's already loaded for me at user level, so no need to load it twice.
The same for network page if the module is already loaded as global/user module.
Reason: When adding new network, I don't know which modules I need to load. E. g. chansaver is useful... but it's already loaded for me at user level, so no need to load it twice.
##
<bountysource-plugin>
---
The **[$5 bounty](https://www.bountysource.com/issues/658-webadmin-show-in-user-page-if-the-module-is-already-loaded-as-global-module?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** on this issue has been claimed at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:5477101 -->
Hi,
How should it look like and how should it behave? Should we disable checkbox and show some hint why it's disabled? In the attached file you can see one of the possible design proposals, what do you think?
Hi,
How should it look like and how should it behave? Should we disable checkbox and show some hint why it's disabled? In the attached file you can see one of the possible design proposals, what do you think?

<!-- github-comment-id:30609251 -->
Probably rows for modules, which can't be loaded as user module, should
have that cell empty? The similar column for global? But looks good
Probably rows for modules, which can't be loaded as user module, should
have that cell empty? The similar column for global? But looks good
<!-- github-comment-id:30618107 -->
Hi,
What do you think about the following design?

<!-- github-comment-id:30873486 -->
Hi, this one is bad: you are allowed to load a module, even if it's
already loaded on another level. This feature needs only to show hint
for user that probably you don't need to load the module again.
I was talking about empty cell on your added column, not about inability
to load the module at all.
Hi, this one is bad: you are allowed to load a module, even if it's
already loaded on another level. This feature needs only to show hint
for user that probably you don't need to load the module again.
I was talking about empty cell on your added column, not about inability
to load the module at all.
On 18.12.2013 19:41, Vasily wrote:
> Hi,
> What do you think about the following design?
> design_proposal_2
> https://f.cloud.github.com/assets/923963/1776856/4ad6dfea-681c-11e3-8cf2-6070ceebe79b.png
>
> —
> Reply to this email directly or view it on GitHub
> https://github.com/znc/znc/issues/189#issuecomment-30873486.
<!-- github-comment-id:30899273 -->
I have a crude idea (I used paint instead of fighting with CSS/HTML).
Network modules:
Allow users to see if a network module is also loaded as a user or global.
User modules:
Allow users to see if a user module is also loaded as a global or network. In this example, the log module is loaded as a user module while its also loaded as a network module for some, but not all the networks. Maybe if its loaded for all networks, use the block_motd check color?
Global modules:
I think we get the idea.
Maybe remove the left check/uncheck row and just use the right side one?
or..
Maybe just move the entire right side over to the left?
I have a crude idea (I used paint instead of fighting with CSS/HTML).
Network modules:
Allow users to see if a network module is also loaded as a user or global.

User modules:
Allow users to see if a user module is also loaded as a global or network. In this example, the log module is loaded as a user module while its also loaded as a network module for some, but not all the networks. Maybe if its loaded for all networks, use the block_motd check color?

Global modules:
I think we get the idea.
Maybe remove the left check/uncheck row and just use the right side one?
or..
Maybe just move the entire right side over to the left?
<!-- github-comment-id:30905033 -->
It would be amazing to see what modules are loaded in other contexts this way, as @KindOne- mocked. Even if the interface isn't exactly like that, it would still be incredibly useful.
I would support being able to change at least user & network mod status from the network screen. Being able to load a module for all networks from the user settings would be an added bonus as well.
It would be amazing to see what modules are loaded in other contexts this way, as @KindOne- mocked. Even if the interface isn't exactly like that, it would still be incredibly useful.
I would support being able to change at least user & network mod status from the network screen. Being able to load a module for all networks from the user settings would be an added bonus as well.
<!-- github-comment-id:30905415 -->
Supporting loading modules this way would be tricky, because they can be
loaded with different arguments... Probably need some bigger redesign of
the table for that.
On 19.12.2013 05:01, dgw wrote:
It would be amazing to see what modules are loaded in other contexts
this way, as @KindOne- https://github.com/KindOne- mocked. Even if
the interface isn't exactly like that, it would still be incredibly
useful.
I would support being able to change at least user & network mod
status from the network screen. Being able to load a module for all
networks from the user settings would be an added bonus as well.
Supporting loading modules this way would be tricky, because they can be
loaded with different arguments... Probably need some bigger redesign of
the table for that.
On 19.12.2013 05:01, dgw wrote:
> It would be amazing to see what modules are loaded in other contexts
> this way, as @KindOne- https://github.com/KindOne- mocked. Even if
> the interface isn't exactly like that, it would still be incredibly
> useful.
>
> I would support being able to change at least user & network mod
> status from the network screen. Being able to load a module for all
> networks from the user settings would be an added bonus as well.
>
> —
> Reply to this email directly or view it on GitHub
> https://github.com/znc/znc/issues/189#issuecomment-30905415.
<!-- github-comment-id:30912076 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The same for network page if the module is already loaded as global/user module.
Reason: When adding new network, I don't know which modules I need to load. E. g. chansaver is useful... but it's already loaded for me at user level, so no need to load it twice.
--- The **[$5 bounty](https://www.bountysource.com/issues/658-webadmin-show-in-user-page-if-the-module-is-already-loaded-as-global-module?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** on this issue has been claimed at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).Hi,

How should it look like and how should it behave? Should we disable checkbox and show some hint why it's disabled? In the attached file you can see one of the possible design proposals, what do you think?
Probably rows for modules, which can't be loaded as user module, should
have that cell empty? The similar column for global? But looks good
Hi,

What do you think about the following design?
Hi, this one is bad: you are allowed to load a module, even if it's
already loaded on another level. This feature needs only to show hint
for user that probably you don't need to load the module again.
I was talking about empty cell on your added column, not about inability
to load the module at all.
On 18.12.2013 19:41, Vasily wrote:
I have a crude idea (I used paint instead of fighting with CSS/HTML).
Network modules:
Allow users to see if a network module is also loaded as a user or global.
User modules:

Allow users to see if a user module is also loaded as a global or network. In this example, the log module is loaded as a user module while its also loaded as a network module for some, but not all the networks. Maybe if its loaded for all networks, use the block_motd check color?
Global modules:
I think we get the idea.
Maybe remove the left check/uncheck row and just use the right side one?
or..
Maybe just move the entire right side over to the left?
It would be amazing to see what modules are loaded in other contexts this way, as @KindOne- mocked. Even if the interface isn't exactly like that, it would still be incredibly useful.
I would support being able to change at least user & network mod status from the network screen. Being able to load a module for all networks from the user settings would be an added bonus as well.
Supporting loading modules this way would be tricky, because they can be
loaded with different arguments... Probably need some bigger redesign of
the table for that.
On 19.12.2013 05:01, dgw wrote:
Leaving loading other levels from here aside, then, probably. I get ahead of things sometimes.
Great, thanks!