702
Done... in french ! 
14 pages with a very full explanation:
Introduction
Setting up
General structure
List of variants
Choice of variants
Template theme.tpl - Requirements
Positioning of blocks
Template theme.tpl - Header
Template theme.tpl - Body - Start
Template theme.tpl - maincontainer
Template theme.tpl - Body - End
Customisation of the CSS file
Direct access to block management
Module template overloads
14 pages with a very full explanation:
Introduction
Setting up
General structure
List of variants
Choice of variants
Template theme.tpl - Requirements
Positioning of blocks
Template theme.tpl - Header
Template theme.tpl - Body - Start
Template theme.tpl - maincontainer
Template theme.tpl - Body - End
Customisation of the CSS file
Direct access to block management
Module template overloads
704
Hey,
I'm working on a really comprehensive tutorial on xSwatch4 (english and french language).
Take a look at what you will find in the ten or so pages of the tutorial.
CodePen link : https://codepen.io/alain01/full/ExXPJYy
(To understand the theme, I invite you to change the width of your browser window)
I'm working on a really comprehensive tutorial on xSwatch4 (english and french language).
Take a look at what you will find in the ten or so pages of the tutorial.
CodePen link : https://codepen.io/alain01/full/ExXPJYy
(To understand the theme, I invite you to change the width of your browser window)
705
XOOPS AdsLight 2.4.0 Alpha 2 released for testing/contributions!
DOWNLOAD: https://github.com/mambax7/adslight/releases
FORK: https://github.com/mambax7/adslight/
ISSUES/BUGS: Please report all issues on GitHub
REQUIREMENTS:
- XOOPS 2.5.10+
- PHP 7.3+
Tested on PHP 7.4.23 and PHP 8.0.10
XOOPS AdsLight 2.4.0 Alpha 2 released for testing/contributions!
DOWNLOAD: https://github.com/mambax7/adslight/releases
FORK: https://github.com/mambax7/adslight/
ISSUES/BUGS: Please report all issues on GitHub
REQUIREMENTS:
- XOOPS 2.5.10+
- PHP 7.3+
Tested on PHP 7.4.23 and PHP 8.0.10
706
XOOPS Publisher 1.08 Alpha 5 released for testing/contributions!
DOWNLOAD: https://github.com/XoopsModules25x/publisher/releases
FORK: https://github.com/XoopsModules25x/publisher/
ISSUES/BUGS: Please report all issues on GitHub
REQUIREMENTS:
- XOOPS 2.5.10+
- PHP 7.3+
Tested on PHP 7.4.22 and PHP 8.0.9
DOWNLOAD: https://github.com/XoopsModules25x/publisher/releases
FORK: https://github.com/XoopsModules25x/publisher/
ISSUES/BUGS: Please report all issues on GitHub
REQUIREMENTS:
- XOOPS 2.5.10+
- PHP 7.3+
Tested on PHP 7.4.22 and PHP 8.0.9
708
Quote:
Yes, you absolutely should use something like Scrutinizer!
This is a great video showing the need to use static analyzers like PhpStan and PhpInsights:
Ok. may be I should add a static analysis on 1 of my repositories to test and understand.
Yes, you absolutely should use something like Scrutinizer!
This is a great video showing the need to use static analyzers like PhpStan and PhpInsights:
709
Ok, Thank you for your answer.
So, for us, it uses XoopsCore25/.scrutinizer.yml.
Ok. may be I should add a static analysis on 1 of my repositories to test and understand.
So, for us, it uses XoopsCore25/.scrutinizer.yml.
Ok. may be I should add a static analysis on 1 of my repositories to test and understand.
710
Quote:
Scrutinizer is a static analysis tool that helps with code quality by doing Automated Code Reviews
It is highly recommended to run your code through such tools, as they point out issues that sometimes are missed or overlooked by developers.
Quote:
You go to Scrutinizer and start a test on a particular Github repository. Scrutinizer will then add itself to that repository via Webhooks, so next time when a PR is added, it will run the tests automatically (see here).
Quote:
You can list the tests that you want to run in the configuration file .scrutinizer.yml file (see here).
Quote:
We use the tests provided by Scrutinizer
There are other Static Analysis Tools as well - a good list is here
What is Scrutinizer
Scrutinizer is a static analysis tool that helps with code quality by doing Automated Code Reviews
It is highly recommended to run your code through such tools, as they point out issues that sometimes are missed or overlooked by developers.
Quote:
what you did to add tests,
You go to Scrutinizer and start a test on a particular Github repository. Scrutinizer will then add itself to that repository via Webhooks, so next time when a PR is added, it will run the tests automatically (see here).
Quote:
what kind of tests you added.
You can list the tests that you want to run in the configuration file .scrutinizer.yml file (see here).
Quote:
Did you use your own scripts or did you use tools inside the Scrutinizer?
We use the tests provided by Scrutinizer
There are other Static Analysis Tools as well - a good list is here
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|