Dream Features For 5.0 Release Request

[labanex]

1. Mobile device capability: Install sometype of WAP, PocketPC, Sprint PCS Web Browser, and other mobile device browser adaptability. Basically, all content in the MAIN BODY section is compatible with most browsers, displaying it for mostly all mobile devices. As the formats of browsers grow, all future releases of Mambo can include the newest formats out there. The MAIN BODY info adapts automatically based upon the browsers capabilities. For instance, for WAP phones, the content is adjusted to display the limited memory that most phones can display, like NEXT PAGE, which displays the page as CARDS.

PocketPC and Smartphones are displayed in it's limitations. Other phone browsers and Palm Pilots browsers are adjusted as well to display the limitations of the browsers.

All images for WAP browsers are adjusted as well. Maybe an additional feature for Imagemagick can reconfigure all images from png, jpg or gif into wbmp files live. Also, Sprint PCS Web phones does not display png files. When a browser comes up againsts a png file, or even a gif file, the file is converted into a jpg file. Also, the size of the graphics file is adjusted to the size of the browser window on the mobile devices. For instance, a 400 width picture can be displayed at 80 width instead using Imagemagick, or any other web based image software. I am not saying that Mambo should do design Imagemagick, but I am thinking of a way for Mambo to access Imagemagick, JPEG, or any other image software and can be configured in the main settings.

2. Only server info in config file. All configurations are set in the mySQL database. The only thing that is in the config file is the database info, passwords, secret word and offline data. All other configuration is set in mySQL database. This will make Mambo a complete database based software.

3. Automatic database backup. This can be set in the configuration. Of course, we know that php is not a continuous running program. It is based on server's request. If the backup is set once a week, Sunday 12 noon, if someone makes a request on the web site at 12:10pm, it will make the database backup at that time as a tar.gz file. When the Mambo backend administrator logs in, in the module of the home page, there can be a link to the tar.gz file for the administrator to download the file from the database. Also, all configuration files are stored there too. THis will allow the administrator to backup the files in case the server crashes. The administrator can use the database file, install it. Install another Mambo with components and modules, then within Mambo backend, upload the config files all in one file. It will be that easy.

4. Multi-db and multi-site support is a great idea. The only thing I want is that the site can be hosted on several different servers. For instance, a local baseball league. One team hosts their web site on a Texas server with it's own database. Another team hosts their web site on a California server. Different databases, but one user log in and password accounts. Also, the extended info is also stored.

5. About NO. 4, anytime a component could use the one db info, the component tells Mambo that all sites tied together will be using the same info.

6. The main database is set on the MAIN SERVER, like the League's Headquarters web site. This can either be stored on a seperate server, or same server. The user and linked info database files can be stored on the MAIN SERVER. But here is the catcher. All local server db info is stored on the same server as the web site itself.

7. Outside MAMBO Static Page access: This will be a cool feature for an administrator to have access to all of the web site, with access rights to certain administrators and moderators. This can be accessed in the front end too, where the administrator can set which users have access to what feature. It is like Mambo having access to the entire site, CHMOD settings, upload files, etc. This feature can be more like an external component that anything.

8. Poll votes within the component, not just the module. It is also a setting that allows the administrator to turn off voting within the module, but component only. Also, the administrator may choose to turn off voting altogether, but allow the results to be shown for a limited time (setting the time of expiration) or forever.

9. Modules with time on and time off expirations, like the content, as well as, MENU links. Every link and module could benefit a creation date, time on data and time, and expiration date and time. This will allow for a more automated control, in case the administrator leaves town for a few days, but wants to not display a certain link or module during a certain time.

10. Whenever Gallery 2 comes out, a mambot would be needed to include searches of the Gallery component. This is be a third party mambot.

11. Integration or third party software linkage and sharing of user information: Not every software needs to be fully integrated. All I want is a way to apply a plug-in in the third party software to tell the software to log in under Mambo's user tables. Whether the user logs-in under Mambo site or the third party software site, all sites are logged in automatically. For instance: Mambo is installed. phpBB is also installed, but not integrated, Moodle (course management software) is not integrated, but installed. phprojekt (project management software), gForge (groupware) is also not integrated, but installed. All software has a new script or hack that will use the log-in and password screen to use the Mambo's usertables. Once logged in, the user can bounce back and forth between the softwares and the user is logged in. The multiple Mambo sites that are also tied in would also be logged in, even if on a different server.

No need for the user to log in everytime they enter a different site. If a user is using Moodle, the change password script links to the Mambo site change password screen. When the user press ENTER or SUBMIT, the screen returns to the home page site they came from. No matter which software they are using, when the user clicks LOG OFF or OUT, all software is logged out automatically. I believe that the header files of each software can be the hack for this along with a small php file within each software.

Like I said, I really do not care for integration, I just want to use these other softwares for my users, but not neccessarily have to have different user names and passwords either.

A good point and view: Imagine mamboserver.com, the vBullentin forums can have the same passwords as help.mamboserver.com, www.mamboserver.com and gForge that runs mamboforge.net.

In Mambo, each software can use a mambot and component, backend based only. The mambot will authenticate the users for all sites, other Mambo sites that are tied, other softwares and even if the different Mambo site and software is on a different server.

The component software is where the administrator sets it all up. Server settings, and determines which user has access.

12. Drupal has one good feature. It allows the administrator to set access to several users and not limited to three group settings. If I wanted one person to access Sporting events only, he can. Maybe even having different rates of members. One group has access to limited info. A paid member can access more features, meaning MENU links. A GOLD MEMBER can access even more features or if not all. The administrator can determine the class and names of these groups, and in the MENU settings, the group settings can also be set in the parameters.

13. Movable type and Greymatter are blog software. But I love how one can change the look of the site by going to the template settings. If anyone is familiar with Greymatter, you can basically design a site a piece at a time anyway you like. I know that Mambo wants to be more language sensitive. I believe that if Mambo uses the same kind of features that is used in Greymatter, but saving the data in the database instead as a language file, this can be a great feature for Mambo.

14. Accessing different links in the COMPONENT MENU is sometimes difficult, especially when having to go to the MORE COMPONENTS links. Every component setting in the backend should have the links on to top of the page, under the MAIN MENU, so that can be avoided. For instance, when an administrator goes to Remository settings, the links should be in the top menu if wants access to CATOGORY, CONFIGURATION, SHOW FILES, etc.

I am a BIG FAN of MAMBO, but I also noticed features in other CMS's that I love to see in MAMBO. I think Mambo is a very powerful.

My site is http://dragons.ymp.net/ - thanks for your time in my lengthy statement.

[swordhert]

is it posible to browse mambo site using wap phone?

[millarch]

Originally Posted by labanex

12. Drupal has one good feature. It allows the administrator to set access to several users and not limited to three group settings. If I wanted one person to access Sporting events only, he can. Maybe even having different rates of members. One group has access to limited info. A paid member can access more features, meaning MENU links. A GOLD MEMBER can access even more features or if not all. The administrator can determine the class and names of these groups, and in the MENU settings, the group settings can also be set in the parameters.

From everything you mentioned, the stuff I miss the most are Drupal's features. In a dremaland I'd like to see both projects merge into one...

Specifically: better categorization (taxonomy!); better ACL (user management); and the fantastic Template system and CSS based sites (Drupal sites can be done totally without Tables!).

Once this is achieved, there would be no need for any other CMS...

Any feedback from the developers on any of these features timeframe?

Thanks !

P.S. - Don't get me wrong: I think Mambo has MANY other features that are better than Drupal.

[labanex]

Though Drupal has a lot of functionality that Mambo doesn't, for what I need, Mambo is better. The problem is, I need a CMS that is for business with a blog like feel. Drupal is not really a business CMS, or at least, it does not feel like one. Drupal is more of a community CMS. Mambo is not. Though, both CMS can be configured for business and/or community. I think that Drupal and Miro can get together creating the best CMS available, along with the power of phpProjekt as well. Mambo 4.5.2.1 is awesome, but changing the goal of Mambo will be hard for Miro because their ultimate goal is to create the ultimate business CMS script. Which it is in my book...

Maybe if someone else took the framework of Drupal and Mambo, combined the frameworks together, along with the powerful engine of phpProjekt, I think that this CMS can be great. But, this new framework, of course, will need to give credit to the original frameworks author, Miro and Drupal. I do not think that Miro or Drupal would fuss if someone did take on this project.

I am soooooo new to php and in the process of reading books about php and mysql. But I am far from creating or redoing the framework of a CMS. I just have ideas like everyone else does here. But execution is not where I am at now. In the future, maybe.

Antonio - http://dragons.ymp.net/

[millarch]

Originally Posted by labanex

Maybe if someone else took the framework of Drupal and Mambo, combined the frameworks together, along with the powerful engine of phpProjekt, I think that this CMS can be great. But, this new framework, of course, will need to give credit to the original frameworks author, Miro and Drupal. I do not think that Miro or Drupal would fuss if someone did take on this project.

I had a similar thought in the past. Actually I did not consider someone creating a brand new CMS based on both Drupal and Mambo, but having the two teams actually joining forces. Of course it would be more a diplomacy issue, as naturally both development teams would be reluctant to the idea at first. It would be a merger, like it happens in the corporate world, of two great solution, totally complimentary to one another. The question is, who (with credentials) would make the first contact and et people together around this?

One reason for this is: in the mambo 5.0 roadmap, it is already identified the lack of taxonomy and ACL in mambo, and that's two of the features that have to be urgently builded. If developers from Drupal joined the team, they would come with their experience on this end, and would save mambo CMS a lot of time...

[Dreamlogic]

Personally what I would like to see the most in Mambo 5 is a clear separation of content, code and presentation. As it is now, the Mambo code is full of html tags, and thus it is quite clunky to build a 100% customized site.

Regards
Dreamlogic

[<--R O B-->]

I just checked out mambo 5 cvs - it looks like com_conent has been updated to use patTemplate - so a seperation of content, code and presentation. I guess that the other core components will also follow suit.

Also there appears to be quite a lot of work gone into ACL and a node structure for the content.

Really impressed with what I saw

[millarch]

Originally Posted by <--R O B-->

I just checked out mambo 5 cvs

Where can I find the version 5 cvs?

[Dreamlogic]

See this post;
http://forum.mamboserver.com/showpos...&postcount=6=6

Regards
Dreamlogic

[spignataro]

using this you can view mambo through wap

http://sakic.net/index.php?option=scripting&sub=wps

[MystaMax]

IMO, I like the way mambo is going with things. The best part for me is that i get come along for the ride. It'll be a good experience for a novice programmer like me. I feel we'll be pretty surprised and overwhelmed w/ the outcome. It'll be the best Christmas present I'll get! Unless I get a new house and car! That may just edge mambo 5 just a lil.

[myra]

12. Drupal has one good feature. It allows the administrator to set access to several users and not limited to three group settings. If I wanted one person to access Sporting events only, he can. Maybe even having different rates of members. One group has access to limited info. A paid member can access more features, meaning MENU links. A GOLD MEMBER can access even more features or if not all. The administrator can determine the class and names of these groups, and in the MENU settings, the group settings can also be set in the parameters.

That's very important feature for a CMS, it must, phpGACL is the best choice mambo currently used, but it must be implemented as soon as possible...

Especially for backend access people need different access levels, for example one can access only some component's management, others cannot...

It's hard work I know, currently I try to do this manually by hacking many files, it is to difficult...A backend module or something else is needed to configure ACL checks and access levels...

Before going more extra new features done, this must be done because it's about core, not side...

Yeah, the extended granular ACL in 5.0 CVS looks promising, although from a usability perspective, it's currently arranged in a mess

[myra]

Originally Posted by absalom

Yeah, the extended granular ACL in 5.0 CVS looks promising, although from a usability perspective, it's currently arranged in a mess

Yes,it can be massy for some mambers but it's a need to control component based access in backend...

Maybe an advanced control system can be stored in backend to control it with an attention for newbie mambers...

I'm thinking of doing some usability models just to get the 5.0 granular acl right.. (or at least the way I envision right to be)..