11
alain01
Re: xswatch
  • 2019/11/19 7:03

  • alain01

  • Just can't stay away

  • Posts: 528

  • Since: 2003/6/20


OK, i will come back next days to get a full answer for you,
but quick answer here :

1- Read the file here README

2- sources are here https://bootswatch.com/ (buttons Download)

3 - Here you get custumize b4 but xswatch was created with b3, so you need to modify some little things in files *.tpl.

12
Lupin
Re: xswatch
  • 2019/11/19 11:10

  • Lupin

  • Just popping in

  • Posts: 92

  • Since: 2007/6/1 2


Ok
tyvm : now I started to understand connections ...

Yesterday I found those pages ... but I was missing the connection with xswatch ... now I can get busy with less fear

Pino

13
Lupin
Re: xswatch
  • 2019/11/27 9:24

  • Lupin

  • Just popping in

  • Posts: 92

  • Since: 2007/6/1 2


OK ...

As I wrote , to read suggested docs , was a good thing.

I saw in both version of bootstrap the data lines for the customization of the "container-maincontainer" zone are identical ... so, probably, switching to the most recent bootstrap version would not have changed anything for me.

But this reading also made me reflect on the detail also the navmenu is contained in the same CSS class ... and what could be in the menu that could create that problem for me? One thing: the logo!

In fact the customization of the logo had led to larger sizes than those of the original Xoops logo ... in particular returning to the width of the logo within the previous measure, the problem has disappeared!
So it was my (unconscious) mistake to create this problem.

Now, the changes to the CSS that I had hypothesized are giving their result and the images are seen full screen even on mobile phones, without any problems!

Thank you everyone for the support.

Pino

14
alain01
Re: xswatch
  • 2019/11/27 9:37

  • alain01

  • Just can't stay away

  • Posts: 528

  • Since: 2003/6/20


Ok, good news !

Do you use smarty variables with the tag active, with the navmenu elements ?
Like $xoops_page, $xoops_startpage and $xoops_modulepage.

It's a very usefull !

15
alain01
Re: xswatch
  • 2020/2/2 8:54

  • alain01

  • Just can't stay away

  • Posts: 528

  • Since: 2003/6/20


Thank you Richard with this new idea here :

<div class="jumbotron<{if $xoops_banner != "&nbsp;"}> xo-jumbotron<{/if}>">


I didnt think use smarty tests in in class !
You show us the way to do the best with themes !

16
Mamba
Re: xswatch
  • 2020/2/2 17:00

  • Mamba

  • Moderator

  • Posts: 11366

  • Since: 2004/4/23


Support XOOPS => DONATE
Use 2.5.10 | Docs | Modules | Bugs

17
alain01
Re: xswatch
  • 2020/2/7 14:46

  • alain01

  • Just can't stay away

  • Posts: 528

  • Since: 2003/6/20


Quote:
<div class="jumbotron<{if $xoops_banner != "&nbsp;"}> xo-jumbotron<{/if}>">

Now, i used this to show my news (module xmnews) with border-color/ title/background-color with a color per category.
i like it, very clear !

<div class="row no-gutters 
    <{if 
$news.cid == 2}> xoopscore-border
    <{elseif 
$news.cid == 3}> xoopsmodules-border
    <{elseif 
$news.cid == 4}> xoopsthemes-border
    <{else}>border
    <{/if}>
     rounded overflow-hidden flex-md-row mb-4 shadow-sm h-md-250 position-relative"
>

You will see that soon at https://www.monxoops.fr/

Login

Who's Online

219 user(s) are online (66 user(s) are browsing Support Forums)


Members: 0


Guests: 219


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Mar 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits