Hi,

Please be specific about which pages and which links you think should be buttons.

Please be specific about what files you think are not needed.

Don't you think that MojoPortal needs a thorough Cleanup at least for couple of releases instead of continuously adding feature in each release?

Not really, this is hardly a hot topic, you are the only one really complaining about some needed cleanup. Most people want and ask for more functionality and I want to make a living so I continue to improve my product as fast as I can. In this day and age disk space is cheap so a few extra files or minimizing disk space are not my biggest concern (I'm not saying it is unimportant, just relatively unimportant compared to other concerns), providing a comprehensive set of features to meet most web site needs and including a lot of good looking skins to make my product more appealing is more important to me.

For the 2.3.3.2 release I did exclude a lot of sql scripts for other dbs, previously I included scripts for all dbs in all packages. Now each package has only the scripts for one db platform except the package for MS SQL which also includes the scripts for MySql because I can't make a pre-configured package for MySql so users have to download the MS SQL version and the MySql data layer separately. Maybe next release I will move the MySql scripts out of the MS SQL package and just include them in the MySql data layer package.

If you point out un-needed files and I agree they are un-needed I will exclude them and it certainly will not require a few release cycles to do cleanup, it would take me one afternoon at most. But you must be very specific about which files you think are not needed and I suspect I will not agree with you on all the ones you may think are not needed.

Best,

Joe

Hi,

1. Regarding links vs buttons, the irony for me is that we used to use buttons for Cancel but changed them to links as a recommended usability improvement. I still agree with the idea that links and buttons convey different things, links are more appropriate for things like cancel/go back. I am not going to change them back to buttons at this time, sorry.
2. I will remove the legacy .ascx files from the admin folder since that changed so long ago and also there is error handling for those missing items even if someone upgrades from a very old version.
3. Regarding the files in the root like BlogView.aspx etc, it was not that long ago when we moved the features out of the core project and into the "Features" set of projects and this required moving files. The old files still need to be there to avoid 404s for users who upgrade. The files are not very large and therefore there is very little affect on the package size by removing those, so they will stay a while longer.
4. I went through this morning and deleted some images from /Data/SiteImages and I also wen through each of the included skins and deleted files that are not used.
5. I will exclude WebStore from unsupported db packages going forward.
6. ClientScript - we do not include YUI nor do we include jQuery, those are loaded by default from the google CDN. The bulk of size in ClientScript comes from the fact that we include CKeditor, FCKeditor, TinyMCE, editarea, and XStandard. I am leaning towards removing XStandard which is about 2MB, but I do not want to eliminate any others at this time.

So maybe I reduced the size some today, however the only way to make major reductions in package size are to remove skins (accounting for about 9MB of size) and make them separate downloads, to remove editors (about 10MB combined) and make them separate downloads, to remove localization files and make them separate downloads. None of these steps seems like a good strategy at this time, i think we need to keep them in the box.

Note however that any competent developer can produce their own deployment packages from source code leaving out whatever they see fit to reduce the size.

Best,

Joe