The Fruml Forums are open!
You can use these forums to ask questions about Fruml or to get help installing or using it.
There's also a Chat forum for all other topics.
Page 1 of 1
Forums Opened
#5
Posted 04 February 2010 - 12:04 PM
I mean, Immerse was my first cms that pushed my to learn web app developing(php and dbs), and most of the code you wrote there is still perfect samples for me. Fruml is greater, though it is raw, its code looks so simple and DWOO is also great, it lets render tpls from string. I think Fruml has a good future.
#6
Posted 08 February 2010 - 12:11 PM
Thanks!
I've tried to keep the code in Fruml as simple as possible. It uses a simple but powerful MVC structure, and I chose to use Dwoo for the back end instead of writing my own template engine for that. For the front-end it uses a custom renderer.
Fruml still needs a lot of work, but it's coming along nicely. I'll probably be doing another large commit this weekend which should add some more of the still missing functionality to the system.
I've tried to keep the code in Fruml as simple as possible. It uses a simple but powerful MVC structure, and I chose to use Dwoo for the back end instead of writing my own template engine for that. For the front-end it uses a custom renderer.
Fruml still needs a lot of work, but it's coming along nicely. I'll probably be doing another large commit this weekend which should add some more of the still missing functionality to the system.
#8
Posted 17 March 2010 - 10:46 PM
Fruml is currently still very much in an alpha stage.
Most things work as they should, but a lot of functionality is still missing or only partially implemented, and there are no plugins yet (or even functionality to install plugins). Some of the functionality already written may also change in future alphas and betas.
Having said that, the Fruml site itself already runs on Fruml (and it runs very well
), and very simple sites should be fine as long as you don't mind getting stuck in to do a bit of PHP coding for components etc.
Most things work as they should, but a lot of functionality is still missing or only partially implemented, and there are no plugins yet (or even functionality to install plugins). Some of the functionality already written may also change in future alphas and betas.
Having said that, the Fruml site itself already runs on Fruml (and it runs very well
#9
Posted 01 May 2010 - 11:47 PM
Hey Alex,
I'm glad that idea of Immerse CMS is still alive. I do like the approach of backend interface that Immerse had in the past and some unique features, I think it was very intuitive for end user comparing to joomla. I'm wondering how do you position your cms and what are the targets that would make it stand out from other systems like joomla, typolight or MODx?
I'm glad that idea of Immerse CMS is still alive. I do like the approach of backend interface that Immerse had in the past and some unique features, I think it was very intuitive for end user comparing to joomla. I'm wondering how do you position your cms and what are the targets that would make it stand out from other systems like joomla, typolight or MODx?
#10
Posted 02 May 2010 - 01:29 PM
Hi Nazariy,
Good questions!
Fruml is aimed for small and medium sized websites, which can have from one to hundreds of editors, from one to thousands of pages.
Whilst the system is very extensible and developer-friendly (with an extended and extensible event system and plugin functionality which will let developers add whatever functionality they need), I am aiming to keep it as simple and consistent as possible. Currently the system is pretty much in 'full-blown developer-mode' in which all functionality is exposed. Once the system starts nearing a production-ready state, and I roll-out the permissions-checking in full force the interface will reflect that (e.g. if you have no permission to edit Content Providers you will not see the corresponding menu entry). This will mean that editors with limited permissions and possibly limited technical skills will have a much simpler interface to work with.
The intended audience of Fruml is web developers and designers, who want to use a powerful, feature rich CMS for their clients' sites, and to offer those clients are also able to use the system to manage their own content. Too often do I see CMS' which are geared to one end of that scale, making it more troublesome to use for users on the other end of the scale.
As for comparisons to other content management systems, I've learned in the past that such comparisons don't really lead anywhere, so I'll refrain from making any comparisons about why system x is better than system y for doing z. As for my thoughts on the other systems, sure:
- Joomla is a nice enough system with a huge library of add-ons and extensions available for it. I found it hard to get the system to work exactly the way I wanted it to though. Maybe that's more my problem (in that I should have changed the way I work, not the system).
- Typolight I've never used not investigated. I shall have to check it out. I've played with Typo3, and found it quite cumbersome and very slow to load (hopefully the 'light' in TypoLight fixes that). I didn't spend a lot of time with it though, so I can't really say much about it.
- MODx is a nice fork/ evolution of Etomite and has developed much in line with what I originally had in mind for Etomite's future when I was still active on that project. The new release seems very developer-centric and I wonder if that and the used terminology might not scare end-users/ editors away. I've only used the beta version of the new MODx though, so it's possible that it was in the same 'full-blown developer-mode' that Fruml is in now.
Eventually though, each system has it's own benefits and disadvantages, it's up to the users themselves to pick the system they feel most comfortable with
Good questions!
Fruml is aimed for small and medium sized websites, which can have from one to hundreds of editors, from one to thousands of pages.
Whilst the system is very extensible and developer-friendly (with an extended and extensible event system and plugin functionality which will let developers add whatever functionality they need), I am aiming to keep it as simple and consistent as possible. Currently the system is pretty much in 'full-blown developer-mode' in which all functionality is exposed. Once the system starts nearing a production-ready state, and I roll-out the permissions-checking in full force the interface will reflect that (e.g. if you have no permission to edit Content Providers you will not see the corresponding menu entry). This will mean that editors with limited permissions and possibly limited technical skills will have a much simpler interface to work with.
The intended audience of Fruml is web developers and designers, who want to use a powerful, feature rich CMS for their clients' sites, and to offer those clients are also able to use the system to manage their own content. Too often do I see CMS' which are geared to one end of that scale, making it more troublesome to use for users on the other end of the scale.
As for comparisons to other content management systems, I've learned in the past that such comparisons don't really lead anywhere, so I'll refrain from making any comparisons about why system x is better than system y for doing z. As for my thoughts on the other systems, sure:
- Joomla is a nice enough system with a huge library of add-ons and extensions available for it. I found it hard to get the system to work exactly the way I wanted it to though. Maybe that's more my problem (in that I should have changed the way I work, not the system).
- Typolight I've never used not investigated. I shall have to check it out. I've played with Typo3, and found it quite cumbersome and very slow to load (hopefully the 'light' in TypoLight fixes that). I didn't spend a lot of time with it though, so I can't really say much about it.
- MODx is a nice fork/ evolution of Etomite and has developed much in line with what I originally had in mind for Etomite's future when I was still active on that project. The new release seems very developer-centric and I wonder if that and the used terminology might not scare end-users/ editors away. I've only used the beta version of the new MODx though, so it's possible that it was in the same 'full-blown developer-mode' that Fruml is in now.
Eventually though, each system has it's own benefits and disadvantages, it's up to the users themselves to pick the system they feel most comfortable with
Page 1 of 1

Sign In
Register
Help


MultiQuote
