Change Details

Ni! This follows the brief discussion here, which I restate below: <https://www.mediawiki.org/w/index.php?title=Topic:Vn7gb2xuqsnf3l43&topic_showPostId=vn88mhgjrdr8b0f6&fromnotif=1#flow-post-vn88mhgjrdr8b0f6> Hello, I'm a happy addicted user of this extension. From my experience, I feel it would be very useful, especially for page creation, if there was a parameter to launch the editor/action in a new tab or window. Quite often, a page will have a button to create or edit another page, while the documentation pertaining to the activity to be developed on the next page is to be found in the original page where the inputbox is. We all know from practice that there's a (very low) limit to what we can do to help users with only preloaded comments. I deal with this problem very frequently in my Wikiversity courses, but also in the organization of wikiprojects and editathons/workshops. Here's an exemple of a Wikiversity page from one of my courses, that uses <inputbox> with <dynamicpagelist> and some template fun to provide a nice "modern" experience to students. https://fr.wikiversity.org/wiki/Mod%C3%A9lisation_des_R%C3%A9seaux_(M1_SIREN,_2020)/Activit%C3%A9_D If you don't French, the button says "Create or access my page for this activity". (Although what it actually does in case the page exists is to directly open it for editing, not reading, but let's deal with one feature at a time, eheh.) I assume it is quite clear to anyone that the student will want to have the new page open in a new tab, not replace the page, so he can consult the instructions which involve <math> rendered formulas, and could also include graphics, in the original page containing the <inputbox>. Still, even Ctrl+clicking is not allowed with the button, so they end up with quite a clumsy experience. And again, I don't think this is a problem exclusively of this kind of usage. This could easily be the case with editathons or other typical <inputbox> uses for wikiproject organization. And it is, indeed, at least in my experience. This seems to me like a low hanging (and tasty) fruit. Hopefully maintainers will feel alike ! Let me know if I can help. Abraços!

Ni! This follows the brief discussion here, which I restate below: <https://www.mediawiki.org/w/index.php?title=Topic:Vn7gb2xuqsnf3l43&topic_showPostId=vn88mhgjrdr8b0f6&fromnotif=1#flow-post-vn88mhgjrdr8b0f6> Hello, I'm a happy addicted user of this extension. From my experience, I feel it would be very useful, especially for page creation, if there was a parameter to launch the editor/action in a new tab or window. Quite often, a page will have a button to create or edit another page, while the documentation pertaining to the activity to be developed on the next page is to be found in the original page where the inputbox is. We all know from practice that there's a (very low) limit to what we can do to help users with only preloaded comments. I deal with this problem very frequently in my Wikiversity courses, but also in the organization of wikiprojects and editathons/workshops. Here's an exemple of a Wikiversity page from one of my courses, that uses <inputbox> with <dynamicpagelist> and some template fun to provide a nice "modern" experience to students. https://fr.wikiversity.org/wiki/Mod%C3%A9lisation_des_R%C3%A9seaux_(M1_SIREN,_2020)/Activit%C3%A9_D If you don't French, the button says "Create or access my page for this activity". (Although what it actually does in case the page exists is to directly open it for editing, not reading, but let's deal with one feature at a time, eheh.) I assume it is quite clear to anyone that the student will want to have the new page open in a new tab, not replace the page, so they can consult the instructions which involve <math> rendered formulas, and could also include graphics, in the original page containing the <inputbox>. Still, even Ctrl+clicking is not allowed with the button, so they end up with quite a clumsy experience. And again, I don't think this is a problem exclusively of this kind of usage. This could easily be the case with editathons or other typical <inputbox> uses for wikiproject organization. And it is, indeed, at least in my experience. This seems to me like a low hanging (and tasty) fruit. Hopefully maintainers will feel alike ! Let me know if I can help. Abraços!

Ni! This follows the brief discussion here, which I restate below: <https://www.mediawiki.org/w/index.php?title=Topic:Vn7gb2xuqsnf3l43&topic_showPostId=vn88mhgjrdr8b0f6&fromnotif=1#flow-post-vn88mhgjrdr8b0f6> Hello, I'm a happy addicted user of this extension. From my experience, I feel it would be very useful, especially for page creation, if there was a parameter to launch the editor/action in a new tab or window. Quite often, a page will have a button to create or edit another page, while the documentation pertaining to the activity to be developed on the next page is to be found in the original page where the inputbox is. We all know from practice that there's a (very low) limit to what we can do to help users with only preloaded comments. I deal with this problem very frequently in my Wikiversity courses, but also in the organization of wikiprojects and editathons/workshops. Here's an exemple of a Wikiversity page from one of my courses, that uses <inputbox> with <dynamicpagelist> and some template fun to provide a nice "modern" experience to students. https://fr.wikiversity.org/wiki/Mod%C3%A9lisation_des_R%C3%A9seaux_(M1_SIREN,_2020)/Activit%C3%A9_D If you don't French, the button says "Create or access my page for this activity". (Although what it actually does in case the page exists is to directly open it for editing, not reading, but let's deal with one feature at a time, eheh.) I assume it is quite clear to anyone that the student will want to have the new page open in a new tab, not replace the page, so heso they can consult the instructions which involve <math> rendered formulas, and could also include graphics, in the original page containing the <inputbox>. Still, even Ctrl+clicking is not allowed with the button, so they end up with quite a clumsy experience. And again, I don't think this is a problem exclusively of this kind of usage. This could easily be the case with editathons or other typical <inputbox> uses for wikiproject organization. And it is, indeed, at least in my experience. This seems to me like a low hanging (and tasty) fruit. Hopefully maintainers will feel alike ! Let me know if I can help. Abraços!