| tsquez wrote: |
|
My statement was directed to Duster about his comment on “Communication with the community.” I was simply stating that after I read his article, I found the Team to be “LACKING” in this department. |
| Quote: |
|
PN does as well…..lol! If you are unable to provide help, then I do not expect you to, but if you are part of the TEAM then I do, and as of yet they haven’t. |
| Quote: |
|
Telling someone to do search in the forums is not providing any kind of help, especially after the person has clearly stated they have looked and found nothing that helps. That is called “passing the buck.” |
| Quote: |
|
So I leave you with this to consider: “Think before you speak, speak half of what you think.” ![]() |
| Quote: |
|
P.S. Duster, next time you try to write something that is free of "bias" look the word up and understand what it means. Your article is filled with bias. |
| Nixon68 wrote: |
|
Xanthia is the superior templating system because it can and will be used in all modules. So the admin is not dependend on the layout some developer designed. He can adjust everything to his own needs and can even include personal addons without hacking files only by smarty plugins and it also supports short URLs. |
| Nixon68 wrote: |
|
MDPro does not offer anything like Pagesetter. Pagesetter is a flexible meta-module that anables the admin to point&click types of publications, design the output via simple HTML and Smarty and can even implement workflows the way he wants. Together with Smarty Plugins and Postnuke this is a mighty combination. |
| Nixon68 wrote: |
|
Check out my testing site: http://v088405.dd1724.kasserver.com/gis/ It you click on "Das Team" you see a list of Pagesetter items together with images stored in the Photoshare gallery. If you click on the names of the first 3 persons you get the details. That is again the name from the Pagesetter publication, the image from Photoshare and the address that is fetched by my personal module pnInternutz that in turned gets the data directly from the XML-output of our universities information system, included in the pagesetter item via Smarty Plugin. Now explain how you do that in MDPro. |
| Nixon68 wrote: |
|
MDPro is a nice packet for admins how don't want to know much about the underlying system. They want a running system and a few colorful themes. Postnuke aims more at the professional segment. That doesn't mean that it doesn't run the way I described for MDPro but it has a bigger potential for professionals. |
| Nixon68 wrote: |
|
And I don't understand why MDPro-Devs decided not to contribute their knowledge to Postnuke development. |
| Nixon68 wrote: |
| You chose to compare Postnuke 726 with the latest MD-Pro-version in a time when Postnuke .750 was already available in a well developed release candidate which offered a number of great new features. |
| Quote: |
| Xanthia is the superior templating system because it can and will be used in all modules. |
| Quote: |
|
MD Pro does not offer anything like Pagesetter. |
| Quote: |
|
Postnuke aims more at the professional segment. That doesn't mean that it doesn't run the way I described for MDPro but it has a bigger potential for professionals. |
| Quote: |
|
And I don't understand why MDPro-Devs decided not to contribute their knowledge to Postnuke development. |
| Nixon68 wrote: |
| What is easier in Autotheme and what does it offer extra that XTE can't do? |
| Quote: |
|
There are 2 modules available for the conversion of Autothemes and classic themes into XTE-Themes - And it works with most themes that I tried. So there are as many Xanthia themes as MD-Pro themes. |
| Quote: |
|
I know there isn't a real roadmap for Postnuke but is there one for MD-Pro? What is the future of MD-Pro? |
| Quote: |
|
AFAIK understand MD-Pro it started as a distribution of Postnuke that included several hacks and 3rd party modules |
| Quote: |
|
- a package that gets bigger and bigger. Postnuke .8 will be the opposite: a lean core with all the basic layer of db abstraction, API, templating, permissions, security hook aso. |
| Quote: |
|
Is there some kind of comparable vision for MD Pro as well - I really am intered in that. I didn't ask that for provocation. I didn't follow MD-Pro's history. |
| Quote: |
|
BTW: I don't really like the religions tone of your last paragraph - I expected a discussion and not the Spanish inquisition!? |
| Duster wrote: |
| For this comparison, we will use the MD Pro 1.07 RC1 and PostNuke 0.726 releases. These are the two versions the author of this article (Duster) is familiar with. Further, only the official packages are used in this comparison. Hacks and third party resources are not considered for either program. The purpose of this comparison is to determine which is the better choice as it comes distributed. For many people, better will mean the easiest choice to both install and administer. |
| Duster wrote: |
| A program is only as good as the people behind it. |
| Duster wrote: |
| Compare the two websites. Look up comments on this subject on the PN forums. Look up the same thing on MDP's site. Which do you feel places a greater importance on communicating with its community, including the end users, on a regular basis? Do you know who the project manager is for each CMS? How often do they communicate with the community? |
| Duster wrote: |
| Compare documentation for the two programs. Which do you feel is more abundant and better able to help you with your concerns as a beginner? Is the documentation for either program adequate in addressing your installation and usage questions? Is there an ongoing effort to add to it and improve it? |
| Duster wrote: |
| How easy can you find your way around the respective sites? Is the site cluttered? Can you find documentation easily? Can you find third party blocks and modules easily? Do you spend more time looking than finding? |
| Duster wrote: |
| How long does it take for the next release? How long does it take for good suggestions to be added? |
| Duster wrote: |
| Is there a projected next release date? Do the developers have a good record of keeping their projections? Is the next release weeks away or years? |
| Duster wrote: |
| Do you know what features will be in the next version? Has there been any feedback on previously suggested features and any indication if they will be included? Are feature suggestions just generally ignored or commented on with no indication of future inclusion? |
| Duster wrote: |
| How many active developers are there for each CMS? The answer to this one may surprise you and teach you a lesson about making assumptions based on appearances. |
| Duster wrote: |
| Only MDP has the following features and refinement. PN does not[list] The ephemerid block does not show on days with no ephemerid
Ephemerids are sorted by month, date and year and displayed in that manner (to the admin) |
| Duster wrote: |
| The user points feature is included |
| Duster wrote: |
| Moderated registration is possible |
| Duster wrote: |
| MDP is search engine friendly. You can customize page names and descriptions for your entire site. |
| Duster wrote: |
| MDP allows for customizable meta tags for each page |
| Duster wrote: |
| MDP comes with built in short URL support (with a choice of extensions){/url] |
| Duster wrote: |
| Admin section has option of all sections together or separated by tabs |
| Duster wrote: |
| Dynamic menu with multiple levels |
| Duster wrote: |
| Compare Subjects (MDP) to Sections (PN). The former allows you to enter search engine terms on the same screen where you enter an article. The latter is oblivious to search engines. Furthermore, it allows you to separate articles into multiple pages. Which would you rather use?p |
| Duster wrote: |
| MDP has built in database support and is shown on the admin menu because regular backups are important and we understand the concept of "out of sight out of mind". We think regular backups are so important that you should be able to perform them from within your CMS. How does PN handle db backups? Are external programs such as phpMyAdmin necessary? |
| Duster wrote: |
| MDP uses the popular HTML based AutoTheme program for its theme engine, although all types of themes are supported. There are hundreds of themes available for it. If you know it already, you don't have to learn something new. Since it is HTML based, it is easier to use than other systems and you can use Dreamweaver and other popular HTML editors to create and modify your themes. |
| Duster wrote: |
| Speaking of themes, MDP includes logo blanks so you may rapidly replace our logo with yours and make use of existing themes within minutes. Can that be said of PN's themes? |
| Duster wrote: |
| MDP has a more refined look which makes data entry easier. |
| Duster wrote: |
| The refinement doesn't stop there though. We are examining every part of MDP and how it functions to eliminate confusion and deficiencies passed on from parent sources PostNuke and Envolution. This is why our ephemerids block functions properly, and why you will see many refinements in MDP that you will not find elsewhere. |
| Duster wrote: |
| Using a concept named zero based functionality, we examine how every part of MDP should work and then go about making sure it works that way. We pay attention to small details as well as major functions. |
| Duster wrote: |
| Doing little things well leads to doing bigger things better. |
| Duster wrote: |
| Look at the modules section of the two. The MDP modules section more easily conveys the status of the module, whether it is active, disabled or not initialized. |
| Duster wrote: |
| PN Hacks I DON'T need with MD-Pro
[list] Title Hack, which allows module titles to be displayed in the browser title area |
| Duster wrote: |
| pnMeta to allow editing of meta keyword tags for each module |
| Duster wrote: |
| pncUserHack to moderate user registration (very helpful at thwarting spammers from registering). |
| Duster wrote: |
| A simple editing hack to the login/registration block to make login information more direct and straighforward. |
| Duster wrote: |
| A hack to make Web Links balanced (it allows specifying the number of subcategory levels to be specified). |
| Duster wrote: |
| Another hack to Web Links that enables a different folder icon to be used for the subcategories, creating a greater visual distinction between category and subcategory. |
| Duster wrote: |
| Another hack to Web Links that requests a reciprocal link of anyone placing a link. |
| Duster wrote: |
| A hack to add subcategories to Sections |
| Duster wrote: |
| A hack to prevent the ephemerids block from being displayed on days for which there are no ephemerids |
| Duster wrote: |
| Another hack to ephemerids to have the dates sorted by month and day and then year in the admin section |
| Duster wrote: |
| The main menu has been organized and titles changed to make it more user friendly and intelligible. |
| Duster wrote: |
| A hack to the main menu to make long listings line up below the first line. |
| Duster wrote: |
| The future of MDP is smaller than PN's, while larger at the same time. MDP 1.1 will have a smaller, leaner core. Only components considered essential for most any site will be included in its core. All the remaining modules and blocks will be optional add-ons during the installation process or later. This will include such features as ephemerids, quotes and many others. This will make it easier for people who install MDP for the first time as they won't have a lot of unused features to disable and delete. |
| Duster wrote: |
| It will be much like installing Linux where you choose what you want installed. Even for the modules you do want to install, you will be able to choose from any on the same subject. Some site admins will require only lightly featured modules while others will prefer more robust modules for commercial purposes. |
| Duster wrote: |
| Our add-ons though, will carry the same commitment to make them the best that the core modules have. They will also enjoy the benefit of support as our core modules do. Note that this does not apply to third party add-ons. |
| Duster wrote: |
| We are in the process of setting up the MaxDev Association, a not-for profit organization to secure the future of MD- Pro. All assets of the Maxdev Project will be transferred to it and it will oversee global marketing and several other activities. |
| Duster wrote: |
| Of course, it helps to have over fifty developers in various countries also, with more joining our team periodically. MDP is not dependent on the efforts of a very small number of developers whose departure or loss could stall, cripple or halt development altogether. |
| Duster wrote: |
| PN has chosen to incorporate pnRender ( a version of Smarty) in future releases of PN. This can cause incompatibility with many modules. Check their forums for more on this. |
| Duster wrote: |
| PN may look bigger but MDP has many more developers. PN has a few, but most of the work is done by just one developer, Mark West. |
| Duster wrote: |
| Consequently, MDP is advanced faster than PN. MDP is a multi national collaboration with multiple sites (more than a dozen). That gives it built in redundancy and backup. PN is centralized with all functions controlled from one site. it has all it eggs in one basket. PN .8 will be using the Xanthia templating engine because a PN developer lost their intended Phoenix rendering engine in a hard drive crash. He had no backup for it.
|
| Duster wrote: |
| MD Pro is a more refined and polished product than PostNuke (that's less subjective though than you might think). A long list of hacks and other improvements was not needed with MDP. Most were already included. It only took suggesting the remaining ones to have them added as well. The differences between MDP and other CMS will grow considerably and the gap between them will widen to a chasm. We have an imaginative and very responsive group of developers and it's a real pleasure (not to mention a lot of fun) working with them.
|
| Duster wrote: |
| As an admin, I like the fact that MDP has built in search engine friendly features and I don't have to add third party hacks to address this severe shortcoming. I like that it has the capability for moderated registration now. It's a feature I need. I had just gotten through adding pncUserPoints to my last PN site when I moved to MDP and discovered they too were built in. I like the fact that the people behind MD Pro think of al these details and how their product will be used in the real world. Unlike PN, there is nothing in MD Pro I need to fix. |
| Duster wrote: |
| If you are still using PN, you should give some serious thought to changing to MD Pro, or just do it. You'll be glad you did and that's an understatement. |
| Duster wrote: |
| Programs fork for many reasons. Often, emphasis is on the code, which explains why so many deficiencies are passed on from one Nuke fork to another and nothing is done about them. Many developers don't think of how a module or block functions. They only think of how it is coded. At MD Pro, we have taken a different path. While our programmers are optimizing the code, they are also improving the functionality of all the parts and make them function as they should. We have an imaginative and highly responsive group of developers. They strive for excellence on a continual basis. Some improvements are made in as little as a few minutes. We employ the talents of many people, from programmers to document writers, wherever they live in the world. Their combined efforts can be found in an excellent product destined to be even better. We invite you to install MD Pro and see for yourself. |
| Quote: |
|
That said, no analysis of PostNuke as a Content Management System would be replete without analysis that takes into the range and variety of 3rd party modules and blocks available for it. |
| Quote: |
|
If I judge them by their respective front pages of both sites, I would rate the PostNuke.com site as being easier to navigate. I am looking at both sites' front pages right now in separate windows, and MD-Pro's front page is more cluttered. PostNuke's site makes better use of distinctive colors to provide a visual breakdown of modules, blocks, security, themes, etc., whereas the www.maxdev.com site (which is what I am referring to when I refer to MD-Pro's site - correct me if I am wrong) is more focused on making announcements than on making navigation better for me, the end user/visitor of the site. |
| Duster wrote: |
| How long does it take for the next release? How long does it take for good suggestions to be added? |
| Quote: |
|
A projected release date is nothing more than a target date, but all-too-often with many software companies, projected release dates are missed. Projected release dates mean nothing to me, individually and personally, since they aren't anything written in stone. The developers could be killed in an automobile accident or sometheing, and a project might never reach fruitition. |
| Quote: |
|
If you know the answer to the question, though, then you should have provided the respective numbers of developers for both PostNuke and MD-Pro. Otherwise, you are merely engaged in an exercise of oratorical sabre-rattling. |
| Duster wrote: |
| MDP is search engine friendly. You can customize page names and descriptions for your entire site. |
| Quote: |
|
That is merely a statement of personal opinion. |
| Quote: |
| I know that this item is a big concern for many web masters, and rightly so, but [sic]for myself, it is not a crucial item. The number of users for my site is not really a concern for me. I do recognize, however, that this is a big consideration for many, if not most, web masters. I use my web site primarily as a test bed for me to learn with. |
| Quote: |
| Being new to being a web master, absent an explanation in your analysis, your statement simply falls with no impact. If you seek to persuade people to go with MD-Pro, instead of PostNuke, your comparisons are not written with the new web master in mind. |
| Quote: |
|
Well, there is no reason that PostNuke sites can't have multiple pages with news on them. Flexibility in display options is of more concern to me as a web master than sheer quantity of pages which the core news module can have. |
| Quote: |
|
I have played with a number of different menu systems for my site. A variety of DHTML menus work with PostNuke 0.726, based upon my own prior experimentations with my site over the last few months. |
| Quote: |
|
If one does not wish to use Auto-Themes, what other options are available for theme, where themes are concerned, for MD-Pro? |
| Duster wrote: |
| Speaking of themes, MDP includes logo blanks so you may rapidly replace our logo with yours and make use of existing themes within minutes. Can that be said of PN's themes? |
| Quote: |
| Is there any problem with eliminating the MD-Pro logos, since those type logos are amongst the most unattractive of things, where aesthetics are concerned, for CMS sites that I visit. |
| Duster wrote: |
| MDP has a more refined look which makes data entry easier. |
| Quote: |
|
Again, I don't use ephemerids, so it is irrelevant to me, |
| Quote: |
| Your choice of wording, however, leaves one questioning whether MD-Pro is so great, after all, if, as you state, it has confusion and deficiencies passed on from parent sources PostNuke and Envolution. You fail to state what those specific confusions or deficiencies are, so there is no way to ascertain the veracity of the statement. |
| Duster wrote: |
| Using a concept named zero based functionality, we examine how every part of MDP should work and then go about making sure it works that way. We pay attention to small details as well as major functions. |
| Quote: |
| If that is the case, then why does MD-Pro still contain confusion and deficiencies from parent sources? |
| Duster wrote: |
| Doing little things well leads to doing bigger things better. |
| Quote: |
| Attention-to-detail is, indeed, an important part of product development. |
| Quote: |
|
I dislike PostNuke's Articles/Categories/Topics framework. Here, are you referring to sections for web links modules? It is difficult to follow your posting, when specificity is lacking. |
| Duster wrote: |
| The main menu has been organized and titles changed to make it more user friendly and intelligible. |
| Quote: |
|
I certainly cannot tellt hat by looking at the www.maxdev.com home page. |
| Duster wrote: |
| A hack to the main menu to make long listings line up below the first line. |
| Quote: |
|
Line up in what way? |
| Duster wrote: |
| It will be much like installing Linux where you choose what you want installed. Even for the modules you do want to install, you will be able to choose from any on the same subject. Some site admins will require only lightly featured modules while others will prefer more robust modules for commercial purposes. |
| Quote: |
|
I have never installed Linux, so that tells me nothing. |
| Quote: |
|
Well, the 3rd party add-ons for various CMSs are what excite me more than the core modules offered by any CMS that I have looked at, so far. |
| Duster wrote: |
| We are in the process of setting up the MaxDev Association, a not-for profit organization to secure the future of MD- Pro. All assets of the Maxdev Project will be transferred to it and it will oversee global marketing and several other activities. |
| Quote: |
|
How, exactly, will this MaxDev Association secure the future of MD-Pro? |
| Quote: |
|
First, you didn't list any of the developers, so it is just a number. |
| Quote: |
| That they are in various countries raises the potential for communication problems within the development core. |
| Quote: |
|
Furthermore, if the intent is to frame the PostNuke development community in a bad light |
| Quote: |
|
People can always die. But, people can be replaced. |
| Quote: |
|
Just because Albert Einstein died, the world was not left without any geniuses amongst us. |
| Duster wrote: |
| PN has chosen to incorporate pnRender ( a version of Smarty) in future releases of PN. This can cause incompatibility with many modules. Check their forums for more on this. |
| Quote: |
|
Simultaneously, though, you fail to state what the potential advantages of incorporating Smarty into the PostNuke development strategy might be. |
| Quote: |
|
As such, your comparison is not balanced, where this particular item is concerned. |
| Quote: |
|
If MD-Pro has so many developers, list them. |
| Duster wrote: |
| PN .8 will be using the Xanthia templating engine because a PN developer lost their intended Phoenix rendering engine in a hard drive crash. He had no backup for it.
|
| Quote: |
|
Well, if this is true, then it certainly would explain something to me about why the transition to Xanthia was made. |
| Duster wrote: |
| MD Pro is a more refined and polished product than PostNuke (that's less subjective though than you might think). A long list of hacks and other improvements was not needed with MDP. Most were already included. It only took suggesting the remaining ones to have them added as well. The differences between MDP and other CMS will grow considerably and the gap between them will widen to a chasm. We have an imaginative and very responsive group of developers and it's a real pleasure (not to mention a lot of fun) working with them.
|
| Quote: |
|
Stating that MD-Pro is, and I quote, "a more refined and polished product than PostNuke," is entirely subjective, |
| Quote: |
|
you fail to specifically define what constitutes the basis for establishing something as refined. |
| Quote: |
|
That something is a "hack" is not necessarily a bad thing. I change my theme by "hacking" it. Not all hacks are hatchet jobs. |
| Quote: |
|
You state that the differences between MDP and other CMSs will grow considerably and that the gap between them will widen to a chasm. This is nothing more than speculation and conjecture on your part. That may be a desired objective, but at this stage, it is simply speculation. |
| Quote: |
| I don't mind considering switching. Your article/posting, however, lacks persuasive power to convince me to switch. You should expound upon the strong points of MD-Pro, if possible and where possible, and try to do so with newbies to Content Management Systems and web mastering in mind. |
| Quote: |
|
I would be especially interested in hearing about MD-Pro, as it provides flexibility to the web master who does not desire to use AutoThemes. |
| Quote: |
|
I would also be interested in learning how MD-Pro's core development team will enable theme designers to have more control over the output and display of specific information which is output by various modules and blocks, as distinguished from the entireity of information output by such modules and blocks. |
| Duster wrote: |
| While it is mostly neutral or non applicable, it does demonstrate the purpose of my post, to ask questions and let each person find the answers and determine the value of them. |
| Quote: |
| And that's why I won't comment on Dusters post - he starts out by saying that it's un-biased and then fills the post with as much bias as one can cram into an article. I feel no need to comment on that kind of writing. Each person can make thier own mind up there. When the mind of the person writing a comparison is already made up there is only one outcome.....
In this thread i've added some links to some (very simple) testing comparing the speed of PN to MD-Pro. In addition PN has features that MDPro doesn't (like mdpro has features pn doesn't) e.g. Support for a variety of mail solutions (mailer module), capability of generating XHTML compliant out. The roadmap of md-pro seems to suggest that the next step for modue development in mdpro is to use pnHTML as it's output method. This output methodlogy has been made deprecated in PN by the advent of pnRender and having worked with pnRender for about a year now could not imagine myself working with pnHTML again. pnHTML is completely designer unfriendly making it virtually impossible for any designer to modify the layout of a module. Standards support is absolutely key for expanding the usage into the business, public sector and academic environemnts (in particular the latter two). With accessibility laws and guidelines requiring site adminstrators create fully standards compliant, acessable sites it key that a CMS delivers these standards to be considered a professional grade solution. Neither PN .72x or MDPro deliver on these so I don't, personally, think either of these products can be considered professional grade. .750 moves a step in the right direction here delivering XHTML compliance and, in some areas of the code, a basic level of accessibility. .8x moves much further removing virtually all tables (apart from those used for tabular data), making full use of the power of css and making all markup semantically correct. While this product is not finished yet the code can be checked out from cvs and people can take it for a spin now. Does maxdev pro really have more developmers - I personally don't know. MDpro has a closed cvs so you can't be certain whose making contributions. There's an often quoted by the mdpro people of 50 developers. I can only guess that this comes from this staff page. If this is the case then 50 'developers' is a bit of a misleading figure. I'd encourage mdpro to become a truly open source project and open up it's cvs for anonymous checkout like PN and virtually all other open source projects do. I'm confident that we've the quality (more important in my mind than quanity) of people to deliver on those goals. .750 and the changes on postnuke.com (xanthia themes, xhtml compliance) are a reflection of this. Simply it's not effective to be drawn in to a game of 'my cms is bigger, better etc.' than yours. I believe that postnuke as product, a site and a group of people stands on it's own. I encourage every user to look at all other cms's prior to selecting PN - I did... and i'm happy I made the right choice (at least for me). -Mark |
| Quote: |
| http://forums.postnuke.com/index.php?name=MDForum&file=viewtopic&t=31910 |
| Nixon68 wrote: |
| Hey! Chill! I didn't defame you you shouldn't to do that either. |
| Quote: |
|
1. You only ask questions in the first quarter of your text - beginning with "Features" a long list of answers follows. |
| Quote: |
|
2. Asking questions doesn't mean it's not propaganda. |
| Quote: |
|
3. I don't contradict myself, I change my mind. A feature of open minded people. |
| Quote: |
|
If Autotheme or Xanthia, which I must admit is the biggest difference in both systems, newbies won't really see the other differences. |
| ics wrote: |
| Umm... http://www.cmsmatrix.org/
Do a compare, I'd love to know if it accurate because I didn't know some of these features were available ![]() |
| jamesko20 wrote: |
| Quote from markwest : |
| Quote: |
| And that's why I won't comment on Dusters post - he starts out by saying that it's un-biased and then fills the post with as much bias as one can cram into an article. |
| Quote: |
| Each person can make thier own mind up there. When the mind of the person writing a comparison is already made up there is only one outcome..... |
| Quote: |
|
In this thread i've added some links to some (very simple) testing comparing the speed of PN to MD-Pro. |
| Quote: |
|
. pnHTML is completely designer unfriendly making it virtually impossible for any designer to modify the layout of a module. |
| Quote: |
|
Does maxdev pro really have more developmers - I personally don't know. MDpro has a closed cvs so you can't be certain whose making contributions. There's an often quoted by the mdpro people of 50 developers. I can only guess that this comes from this staff page. If this is the case then 50 'developers' is a bit of a misleading figure. |
| Quote: |
|
I'm confident that we've the quality (more important in my mind than quanity) of people to deliver on those goals. .750 and the changes on postnuke.com (xanthia themes, xhtml compliance) are a reflection of this. |
| Quote: |
|
Simply it's not effective to be drawn in to a game of 'my cms is bigger, better etc.' than yours. I believe that postnuke as product, a site and a group of people stands on it's own. |
| Nixon68 wrote: |
| Okay, let's leave it to this. This discussion helps no one - perhaps we should better compare Postnuke or MD-Pro to something non-Nuke. Mambo for instance. I checked out Mambo and the content handling really kicks ass while the templating seemed sad. What do you think? |
| markwest wrote: |
| And that's why I won't comment on Dusters post - he starts out by saying that it's un-biased and then fills the post with as much bias as one can cram into an article. I feel no need to comment on that kind of writing. Each person can make thier own mind up there. When the mind of the person writing a
comparison is already made up there is only one outcome..... |
| markwest wrote: |
| In this thread i've added some links to some
(very simple) testing comparing the speed of PN to MD-Pro. In addition PN has features that MDPro doesn't (like mdpro has features pn doesn't) e.g. Support for a variety of mail solutions (mailer module), capability of generating XHTML compliant out. |
| markwest wrote: |
| The roadmap of md-pro seems to suggest that
the next step for modue development in mdpro is to use pnHTML as it's output method. This output methodlogy has been made deprecated in PN by the advent of pnRender and having worked with pnRender for about a year now could not imagine myself working with pnHTML again. pnHTML is completely designer unfriendly making it virtually impossible for any designer to modify the layout of a module. |
| markwest wrote: |
| Standards support is absolutely key for expanding the usage into the business, public sector and academic environemnts (in particular the latter
two). With accessibility laws and guidelines requiring site adminstrators create fully standards compliant, acessable sites it key that a CMS delivers these standards to be considered a professional grade solution. Neither PN .72x or MDPro deliver on these so I don't, personally, think either of these products can be considered professional grade. .750 moves a step in the right direction here delivering XHTML compliance and, in some areas of the code, a basic level of accessibility. .8x moves much further removing virtually all tables (apart from those used for tabular data), making full use of the power of css and making all markup semantically correct. While this product is not finished yet the code can be checked out from cvs and people can take it for a spin now. |
| markwest wrote: |
| Does maxdev pro really have more developmers - I personally don't know. MDpro has a closed cvs so you can't be certain whose making
contributions. There's an often quoted by the mdpro people of 50 developers. I can only guess that this comes from this staff page. If this is the case then 50 'developers' is a bit of a misleading figure. |
| markwest wrote: |
| I'd encourage mdpro to become a truly open source project and open up it's cvs for anonymous checkout like PN and virtually all other open
source projects do. |
| markwest wrote: |
| I'm confident that we've the quality (more important in my mind than quanity) of people to deliver on those goals. .750 and the changes on
postnuke.com (xanthia themes, xhtml compliance) are a reflection of this. |
| markwest wrote: |
| Simply it's not effective to be drawn in to a game of 'my cms is bigger, better etc.' than yours. I believe that postnuke as product, a site and a group of people stands on it's own. I encourage every user to look at all other cms's prior to selecting PN - I did... and i'm happy I made the right choice (at least
for me). -Mark |
| Speedman wrote: |
| Thanks Duster.
Vanessa, the project manager, is incompetent. Nothing more needs to be said except that the very life of Postnuke depends on her getting out of the way. It's sad to see Postnuke drying up like this. Notice how new develoment has slowed to a crawl. Why is that? I think its because Postnuke has no direction and it's impossible (or a waste of time) to think long-term in developing something Postnuke. Poor Mark West. He's a good guy carrying more weight than he should have to. It's a bad deal all around. There's a lot of talent there but, and I might be wrong, I think they are holding their collective noses and waiting for something positive to happen. I take no satisfaction seeing that it's not happening. I'd like to see it happen, but it's just not. I don't think it's going to. I don't dislike them, in fact, I'm rooting for them. But for now, I'm just sad. I'm very sad. Speed |
| Duster wrote: |
| I did delete one inappropriate post from another PN user with low comprehension. I've been tolerant of the other such posts here, and that one was one too many. There was no value in this person's post.
|
| Quote: |
|
I would probably understand you have something against how the PNTeam treated you in the past (won't blabla on my opinion on this one either), but attacking an individual like you do... |
| Quote: |
|
Thanks to TiMax stating that this is not MaxDev post... but yours. |
| Quote: |
| Since PN was not being attacked and still is not, his post jsut anoither stupiod post by someone who does not understnad what he reads. Furhtreremoire, since he is a PN siteadministrator, posting as a sockpuppet (a false identity) in support of his site amounts to skullduggery, it is an unethical thing to do. |
| Zoom. wrote: | ||
Oh my god!!! It’s like an irony buffet! |
| Quote: |
|
I am not currently and have never been part of the postnuke team. My only connection to postnuke is as a user and a co-developer of some postnuke modules. I was made admin at the postnuke forum long ago ... |
| ics wrote: |
| I'd venture to say that any value this topic had was lost somewhere on page one. As an outsider, nobody is looking that professional right now. Delete this topic or the entire image is tarnished.
|
| ics wrote: |
| I also don't believe that "this is not the official position of maxdev" disclaimer removes responsibility from Timax. You must set standards of behaviour and team members must follow them. |
| SimMayor wrote: |
| Interesting comparison, but it is too much like an advertisement speech, to be taken too serious.
I don't see the differences as a comparison between two CMS, but more like a comparison between the needs of an user and the features of different CMS. |
| Quote: |
|
It looks like PN and MD PRO are taking different routes and it really means suitability for different purposes. |
| TiMax wrote: |
| I think is not your problem to decide if delete or not this post
|
| TiMax wrote: |
| I don't care if you beleive or not, |
| ics wrote: | ||||
Nice. I was voicing a perception not an instruction. You will do as you see fit and it's up to you. On the other hand, you should care what public perception is. I'm not associated with any project, I've tried to be a helpful member of the community (search my posts), I've offered to pay for and donate to public domain a custom module that I need (one that Duster said may have features that will be included in future releases of MDPro). Hostility is uncalled for and it's sad that it was resorted to. Remember, perception is reality. Take it as an observation not an attack. |
| ics wrote: |
| Delete this topic or the entire image is tarnished. |
| ics wrote: |
| With all due respect, this topic weakens the perception that MDPro is a serious contender for the CMS Crown. |
| Quote: |
| I also don't believe that "this is not the official position of maxdev" disclaimer removes responsibility from Timax. You must set standards of behaviour and team members must follow them. |
| Quote: |
|
I'd venture to say that any value this topic had was lost somewhere on page one. |
| Quote: |
|
Delete this topic or the entire image is tarnished. |
| TiMax wrote: |
| We have standards of behaviour and all team members follow them, this post not break them. |
| Duster wrote: |
| One can go to opensourcecms.com and see a slew of CMS programs that look like each other and may offer very few differences. With so many of them looking alike, how do you decide which one is for you? If you are considering PostNuke or are already using it, there are several reasons why we think you will find MD Pro to be a superior choice. You can download both programs or just the one you lack, but it takes time to study a program and you may overlook some important and even critical factors. You may be deceived by appearances. This guide is intended to help you in your selection not by giving you answers, but by giving you questions and letting you find your answers. Thus, the issue of bias is eliminated as you arrive at your own conclusions finding answers to questions that apply to both CMS programs.
For this comparison, we will use the MD Pro 1.07 RC1 and PostNuke 0.726 releases. These are the two versions the author of this article (Duster) is familiar with. Further, only the official packages are used in this comparison. Hacks and third party resources are not considered for either program. The purpose of this guide is to help you determine which is the better choice as it comes distributed. For many people, better will mean the easiest choice to both install and administer. The Sites and Communities A program is only as good as the people behind it. Consider the following in conjunction with features as you consider the options. Communication with the community Compare the two websites. Look up comments on this subject on the PN forums. Look up the same thing on MDP's site. Which do you feel places a greater importance on communicating with its community, including the end users, on a regular basis? Do you know who the project manager is for each CMS? How often do they communicate with the community? Which tells you of its history? Documentation Compare documentation for the two programs. Which do you feel is more abundant and better able to help you with your concerns as a beginner? Is the documentation for either program adequate in addressing your installation and usage questions? Is there an ongoing effort to add to it and improve it? Site navigation How easy can you find your way around the respective sites? Is the site cluttered? Can you find documentation easily? Can you find third party blocks and modules easily? Do you spend more time looking than finding? Development time How long does it take for the next release? How long does it take for good suggestions to be added? Next release date Is there a projected next release date? Do the developers have a good record of keeping their projections? Is the next release weeks away or years? Forthcoming Features Do you know what features will be in the next version? Has there been any feedback on previously suggested features and any indication if they will be included? Are feature suggestions just generally ignored or commented on with no indication of future inclusion? Number of developers How many active developers are there for each CMS? The answer to this one may surprise you and teach you a lesson about making assumptions based on appearances. Features Only MDP has the following features and refinement. PN does not The ephemerid block does not show on days with no ephemerid Ephemerids are sorted by month, date and year and displayed in that manner (to the admin) The user points feature is included Moderated registration is possible MDP is search engine friendly. You can customize page names and descriptions for your entire site MDP allows for customizable meta tags for each page MDP comes with built in short URL support (with a choice of extensions) Admin section has option of all sections together or separated by tabs News module can have multiple pages and columns Dynamic menu with multiple levels and a whole lot more Compare Subjects (MDP) to Sections (PN). The former allows you to enter search engine terms on the same screen where you enter an article. The latter is oblivious to search engines. Furthermore, it allows you to separate articles into multiple pages. Which would you rather use? Built in database backup MDP has built in database support and is shown on the admin menu because regular backups are important and we understand the concept of "out of sight out of mind". We think regular backups are so important that you should be able to perform them from within your CMS. How does PN handle db backups? Are external programs such as phpMyAdmin necessary? Theme engine MDP uses the popular HTML based AutoTheme program for its theme engine, although all types of themes are supported. There are hundreds of themes available for it. If you know it already, you don't have to learn something new. Since it is HTML based, it is easier to use than other systems and you can use Dreamweaver and other popular HTML editors to create and modify your themes. Speaking of themes, MDP includes logo blanks so you may rapidly replace our logo with yours and make use of existing themes within minutes. Can that be said of PN's themes? Refinement MDP has a more refined look which makes data entry easier. The refinement doesn't stop there though. We are examining every part of MDP and how it functions to eliminate confusion and deficiencies passed on from parent sources PostNuke and Envolution. This is why our ephemerids block functions properly, and why you will see many refinements in MDP that you will not find elsewhere. Using a concept named zero based functionality, we examine how every part of MDP should work and then go about making sure it works that way. We pay attention to small details as well as major functions. Doing little things well leads to doing bigger things better. Look at the modules section of the two. The MDP modules section more easily conveys the status of the module, whether it is active, disabled or not initialized. PN Hacks I DON'T need with MD-Pro Title Hack, which allows module titles to be displayed in the browser title area pnMeta to allow editing of meta keyword tags for each module pncUserHack to moderate user registration (very helpful at thwarting spammers from registering). A simple editing hack to the login/registration block to make login information more direct and straighforward. A hack to make Web Links balanced (it allows specifying the number of subcategory levels to be specified). Another hack to Web Links that enables a different folder icon to be used for the subcategories, creating a greater visual distinction between category and subcategory. Another hack to Web Links that requests a reciprocal link of anyone placing a link. A hack to add subcategories to Sections A hack to prevent the ephemerids block from being displayed on days for which there are no ephemerids Another hack to ephemerids to have the dates sorted by month and day and then year in the admin section The main menu has been organized and titles changed to make it more user friendly and intelligible. A hack to the main menu to make long listings line up below the first line. Looking ahead MDP The future of MDP is smaller than PN's, while larger at the same time. MDP 1.1 will have a smaller, leaner core. Only components considered essential for most any site will be included in its core. All the remaining modules and blocks will be optional add-ons during the installation process or later. This will include such features as ephemerids, quotes and many others. This will make it easier for people who install MDP for the first time as they won't have a lot of unused features to disable and delete. It will be much like installing Linux where you choose what you want installed. Even for the modules you do want to install, you will be able to choose from any on the same subject. Some site admins will require only lightly featured modules while others will prefer more robust modules for commercial purposes. Our add-ons though, will carry the same commitment to make them the best that the core modules have. They will also enjoy the benefit of support as our core modules do. Note that this does not apply to third party add-ons. The MaxDev Association We are in the process of setting up the MaxDev Association, a not-for profit organization to secure the future of MD- Pro. All assets of the Maxdev Project will be transferred to it and it will oversee global marketing and several other activities. Of course, it helps to have over fifty developers in various countries also, with more joining our team periodically. MDP is not dependent on the efforts of a very small number of developers whose departure or loss could stall, cripple or halt development altogether. PN PN has chosen to incorporate pnRender ( a version of Smarty) in future releases of PN. This can cause incompatibility with many modules. Check their forums for more on this. MDP is advanced faster PN may look bigger but MDP has many more developers. PN has a few, but most of the work is done by just one developer, Mark West. Consequently, MDP is advanced faster than PN. MDP is a multi national collaboration with multiple sites (more than a dozen). That gives it built in redundancy and backup. PN is centralized with all functions controlled from one site. it has all it eggs in one basket. PN .8 will be using the Xanthia templating engine because a PN developer lost their intended Phoenix rendering engine in a hard drive crash. He had no backup for it. Subjective part MD Pro is a more refined and polished product than PostNuke (that's less subjective though than you might think). A long list of hacks and other improvements was not needed with MDP. Most were already included. It only took suggesting the remaining ones to have them added as well. The differences between MDP and other CMS will grow considerably and the gap between them will widen to a chasm. We have an imaginative and very responsive group of developers and it's a real pleasure (not to mention a lot of fun) working with them. As an admin, I like the fact that MDP has built in search engine friendly features and I don't have to add third party hacks to address this severe shortcoming. I like that it has the capability for moderated registration now. It's a feature I need. I had just gotten through adding pncUserPoints to my last PN site when I moved to MDP and discovered they too were built in. I like the fact that the people behind MD Pro think of al these details and how their product will be used in the real world. Unlike PN, there is nothing in MD Pro I need to fix. If you are still using PN, you should give some serious thought to changing to MD Pro, or just do it. You'll be glad you did and that's an understatement. About the author This article was written by Duster. He began following PostNuke in May 2002 and began using it in January 2003. He moved to MD Pro in June 2004. The intent of this article is to help other people using or considering PN based on my experiences with both products and with both organizations. Furthermore, this article reflects my personal experiences and is not a part of any official MD-Pro stance. Summary Programs fork for many reasons. Often, emphasis is on the code, which explains why so many deficiencies are passed on from one Nuke fork to another and nothing is done about them. Many developers don't think of how a module or block functions. They only think of how it is coded. At MD Pro, we have taken a different path. While our programmers are optimizing the code, they are also improving the functionality of all the parts and make them function as they should. We have an imaginative and highly responsive group of developers. They strive for excellence on a continual basis. Some improvements are made in as little as a few minutes. We employ the talents of many people, from programmers to document writers, wherever they live in the world. Their combined efforts can be found in an excellent product destined to be even better. We invite you to install MD Pro and see for yourself. |
| Chestnut wrote: |
|
I wasn't talking about the initial post but about the overall answers we can find in this thread (wich means that if you are serious with your question, you probably didn't read it all). |
| Chestnut wrote: |
Even if I give fact and views, it is clear that it would be pointless... |
| Duster wrote: |
| You claim I insulted someone but you can't provide any proof.
|
| Duster wrote: |
| You PN people seem to be fond of doing that. |
| Nixon68 wrote: |
| I felt insulted - or at least attacked. That's what I meant when I said I didn't expect the Spanish inquisition. |
| Quote: |
|
If nobody got the point of the original post, there are two solutions: Everybody is stupid or it's poorly written. |
| Quote: |
|
Maybe Duster wasn't banned without reason... |
| Duster wrote: |
| Some people just don't know when to remain quiet. |
| Quote: |
| Compare Subjects (MDP) to Sections (PN). |
| Quote: |
|
I concur. Simple Machines looks pretty nice. |
| ifteba wrote: |
|
One thing I am concerned is about the attachment mod for PNphpbb and Quick reply mod it will be really nice to have on any of the forum MD team decide to go with. Thank you. |