What are you working on?
What are you working on?
What extensions are you currently working on for phpBB? The community could use this topic as a means of sharing what they're currently developing, share ideas and moral support in cases of tricky bug fixes perhaps!
Re: What are you working on?
A lot of stuff. Most of it updating some of the phpBB Modders extensions to 3.3. Also working on a new style for the site. I like Revolution, but flip-flopping back and forth between it, the style I use here, or a completely custom one based on a old 3.0 style.
Re: What are you working on?
Hmm.. Currently I'm migrating everything from 3.3.x to pre-Triton (in other words master branch).
At the same time I'm working on my core extension (base for every addition). And there are a lot of additions for the core extension that need work as well.
+ I'm testing ITCSS and Chameleon style (Even though it seems to be collecting dust).
At the same time I'm working on my core extension (base for every addition). And there are a lot of additions for the core extension that need work as well.
+ I'm testing ITCSS and Chameleon style (Even though it seems to be collecting dust).
Usus est magister optimus! phpBB pre-Triton & latest php environment.
When answer lies in the question, question becomes redundant!
When answer lies in the question, question becomes redundant!
Re: What are you working on?
How are you getting on with Chameleon? Have you get any kind of working demo?GanstaZ wrote: Wed Jun 19, 2024 9:53 am [...]
+ I'm testing ITCSS and Chameleon style (Even though it seems to be collecting dust).
I'm working on a payment / shop extension for phpBB. Starting to think that I've not properly considered how big a project it is!
Re: What are you working on?
No demo yet, because I'm still working on improving the code. I haven't updated github in ages.
I'm working on a style for my core extension that is based on Chameleon (some of its components and core).
I decided to switch from scss to pure css, because it is improving fast and doesn't require any compiling (extra tasks).
+ Chameleon itself needs updating. It still has
To put it short, everything that is related to prosilver is no good for 2020+.
But everything that is submitted to CDB has to work with prosilver. + There are so many styles that either inherit from prosilver or are standalone.
What a dilemma. So many issues. "So why not use Chameleon and forget about everything else?" was my thought
About future of Chameleon itself.. Only team knows. I'm surprised that all those style designers are staying away from that project and are still hugging prosilver.
When I'm done with style, I can focus on components that need my attention. For example Legend system or in other words Achievements system.
I prefer to have one core and everything else will inherit from it.
I have seen some shop extensions.. Yeah, those projects are big.
I'm working on a style for my core extension that is based on Chameleon (some of its components and core).
I decided to switch from scss to pure css, because it is improving fast and doesn't require any compiling (extra tasks).
+ Chameleon itself needs updating. It still has
import
instead of use
and itcss seems to be over complicated system (not saying it's bad).To put it short, everything that is related to prosilver is no good for 2020+.
But everything that is submitted to CDB has to work with prosilver. + There are so many styles that either inherit from prosilver or are standalone.
What a dilemma. So many issues. "So why not use Chameleon and forget about everything else?" was my thought
About future of Chameleon itself.. Only team knows. I'm surprised that all those style designers are staying away from that project and are still hugging prosilver.
When I'm done with style, I can focus on components that need my attention. For example Legend system or in other words Achievements system.
I prefer to have one core and everything else will inherit from it.
I have seen some shop extensions.. Yeah, those projects are big.
Usus est magister optimus! phpBB pre-Triton & latest php environment.
When answer lies in the question, question becomes redundant!
When answer lies in the question, question becomes redundant!