Hi folks,
Just a quick note to let you know that the Validacious repo on GitHub is now locked and loaded. In other words, it’s ready to go.
This repository represents the first edition of Trongate where everything is a module.
It is significantly more customisable than the current edition of Trongate. It will also be much easier to work with, particularly for those building multilingual websites or projects where English is not the first language. In addition, it should be far more accessible to AI models. Performance-wise, we are expecting around a 3% improvement over the current edition, placing clear daylight between Trongate’s benchmarks and Phalcon. Best of all (and let's all say it together) it comes with no breaking changes. Your existing modules will continue to work and you can continue working as you normally do.
The philosophy of “everything as a module” is unique in the world of PHP frameworks. Regardless of what one or two sceptics may suggest, we now have solid foundations on which to build a code-sharing ecosystem. You will begin to see that take shape very soon.
Hopefully, I can have an opportunity to hook up with Simon over the next few days, and we can have his CSS magic included in this new upcoming edition of Trongate.
Validacious has been a fantastic collaboration. It has demonstrated what can be achieved when we work together, and I’m keen for us to continue building great things as a community. 'Validacious' will become the new official edition of Trongate before the end of the month, possibly as early as Thursday.
Thanks again to everyone who contributed. Let’s do it again sometime.
The Validacious repo is available here:
https://github.com/trongate/validacious
DC
Validacious
2 days ago
2 days ago
#1
21 hrs ago
#2
Hi Dave, thank you for sharing the great news! I'm really excited about the "Validacious" update. The clean, fully modular architecture, the performance gains, and the expanded multi-language support are all massive improvements. It's fantastic to see what the community can achieve through this kind of teamwork. I can't wait to see it in action! Also, looking forward to hearing whether DaFa's CSS magic makes the final cut or not.
16 hrs ago
#3
I have a slight concern i want to hear opinions on and decide if it's a non-starter.
The *_tester modules, shouldn't they prevent access outside of DEV environment?
My primary concern is with document_tester, it could potentially lead to someone uploading a flood of files and effectively taking down the app via disk starvation.
The *_tester modules, shouldn't they prevent access outside of DEV environment?
My primary concern is with document_tester, it could potentially lead to someone uploading a flood of files and effectively taking down the app via disk starvation.
12 hrs ago
#4
Hi,
They won't be included in the framework.
They won't be included in the framework.
2 hrs ago
#5
I apologise for threatening to leave this forum more times than Trump has threatened to bomb Iran.
That said, this matters. We’ve got a major update coming up - let’s get it right.
THE CURRENT STATE OF VALIDACIOUS
I’ve removed all unwanted files and folders. What remains is essentially what we’ll be shipping with the new Trongate.
This site has been running Validacious for about a week. I’m monitoring the error logs closely and fixing issues as they arise. There have been quite a few, but none related to the framework - mostly documentation errors.
THE CURRENT STATE OF SIMON’S CSS
Simon and I have a long-standing dynamic when it comes to framework changes. I push back, we debate, and more often than not, he turns out to be right and we proceed.
From the outside, it might look heated. It isn’t. There’s mutual respect there - and frankly, that friction keeps things sharp.
Simon has recently worked on two areas:
1. Fixing an animation
2. Dark mode
My concerns are:
1. There are merge conflicts in the Validacious repo, making it difficult to pull in his changes.
2. Any new feature must be properly documented - that means full framework documentation.
3. I don’t fully understand the dark mode implementation. I’m sure it’s solid, but I need a walkthrough.
If Simon can demo it, I can document it. Without that, it’s unlikely to make this release. That said, there’s no reason it can’t follow later.
OUR BIGGEST CHALLENGE
As always, our biggest challenge is docs. I'm going to add the full docs to GitHub soon (four books!) and you'll be able to edit them. There are some cool features in this framework that nobody knows about! That's because they haven't been covered in the documentation yet. My attitude towards this can be summed up as follows: "if a feature is not in the docs then the feature doesn't exist".
I worry about the docs. Perhaps sorting out the docs could be the magical use case for Grady that I've been searching for.
WHAT NEXT?
This site gets around 25,000 visits per month - likely half are bots, but still a healthy number.
I’m watching the error logs closely and fixing issues as they appear.
Once we hit 24 hours with zero errors, I’ll announce a YouTube launch event for the following day.
That’s the current state of play.
ANYTHING ELSE?
This is not a monologue nor a dictatorship. If you have any questions, comments, suggestions or whatever then do let me know. Trongate is transitioning into more of a community driven framework. So, if you want involved then your help is always appreciated. Even if you're not a confident coder, I guarantee we can find something for you to do. We welcome any help that you have to offer.
Let's make Trongate magic!
DC
That said, this matters. We’ve got a major update coming up - let’s get it right.
THE CURRENT STATE OF VALIDACIOUS
I’ve removed all unwanted files and folders. What remains is essentially what we’ll be shipping with the new Trongate.
This site has been running Validacious for about a week. I’m monitoring the error logs closely and fixing issues as they arise. There have been quite a few, but none related to the framework - mostly documentation errors.
THE CURRENT STATE OF SIMON’S CSS
Simon and I have a long-standing dynamic when it comes to framework changes. I push back, we debate, and more often than not, he turns out to be right and we proceed.
From the outside, it might look heated. It isn’t. There’s mutual respect there - and frankly, that friction keeps things sharp.
Simon has recently worked on two areas:
1. Fixing an animation
2. Dark mode
My concerns are:
1. There are merge conflicts in the Validacious repo, making it difficult to pull in his changes.
2. Any new feature must be properly documented - that means full framework documentation.
3. I don’t fully understand the dark mode implementation. I’m sure it’s solid, but I need a walkthrough.
If Simon can demo it, I can document it. Without that, it’s unlikely to make this release. That said, there’s no reason it can’t follow later.
OUR BIGGEST CHALLENGE
As always, our biggest challenge is docs. I'm going to add the full docs to GitHub soon (four books!) and you'll be able to edit them. There are some cool features in this framework that nobody knows about! That's because they haven't been covered in the documentation yet. My attitude towards this can be summed up as follows: "if a feature is not in the docs then the feature doesn't exist".
I worry about the docs. Perhaps sorting out the docs could be the magical use case for Grady that I've been searching for.
WHAT NEXT?
This site gets around 25,000 visits per month - likely half are bots, but still a healthy number.
I’m watching the error logs closely and fixing issues as they appear.
Once we hit 24 hours with zero errors, I’ll announce a YouTube launch event for the following day.
That’s the current state of play.
ANYTHING ELSE?
This is not a monologue nor a dictatorship. If you have any questions, comments, suggestions or whatever then do let me know. Trongate is transitioning into more of a community driven framework. So, if you want involved then your help is always appreciated. Even if you're not a confident coder, I guarantee we can find something for you to do. We welcome any help that you have to offer.
Let's make Trongate magic!
DC