SMF Development > Next SMF Discussion

My SMF 3.0 Dream

<< < (2/16) > >>

Kcmartz:
OK. What do you think about the others?

Kindred:
most of them are a toos-up for me.  I can see some of them being useful - many of them are already mods.

I have no specific argument with them and would leave it up to our developers to decide if they wanted to do it or not.

DoctorMalboro:
I don't agree in 17 and 18, mainly because people are not likely to use SQLite and PostgreSQL and for me, MySQL can work in both ways perfectly...

Then, Pretty URLs shouldn't be standar, because it's just a matter of the user, maybe as an option but disabled, kind of like many CMS do...

Then, in 21, I don't see the point of using SVG when they weight pretty much the same as PNG (in my experience using it, of course)...

I would add a better support to multimedia attachments (like videos with popcorn.js and multiple images with a slideshow) and if the use of CSS3 is likely to happen, create a basic color changer with JavaScript would look great (and remove all the default simple variations)...

Oldiesmann:

--- Quote from: Xarcell on October 06, 2011, 01:51:46 AM ---Personally I think 2.1 should be skipped and go straight into developing on 3.0.

My 3.0 Dream:

1.| Use HTML 5 especially with the use of microdata. The way I see it, but the time 3.0 comes out, there will be a lot more support for it.

2.| Go Object Oriented.

3.| Keep your ground on not supporting third party software. jQuery "might" being the only exception, as some don't consider it third party. However, it should be discussed publicly on whether to support it or not. The pros may out-weigh the cons greatly.

4.| Add a BBC manager and a Menu Manager.

5.| Rename "Default Theme" to "Master Theme", and use the term "Default Theme" when applying a theme to run as the site default. This makes things a little clearer for newcomers.

6.| Remove most of the profile fields in profiles and let the custom profile fields do the work. If the admin wants them, he can create them.

7.| Remove the Calendar. I actually have mixed feeling about this, because I use the Calendar. I think it should be an "official" mod.

8.| Permissions need a make-over. Current system is to complicated to understand for newcomers. Adding options like "Accept" "Deny" and "Revoke" can be a game changer and help people understand it better. Using "Deny" means no permission, but can get permission that allows you from another group. However, using "Revoke" means no permission, regardless if you get permission from another group.

9.| Full UTF8 support by default.

10.| Look at "PHP Speedy"(uses GZIP compression to reduce browser overhead), this idea has potential. Can SMF have something similar by default, that combines all JS files into one file and CSS files into one file(including additional JS/CSS files from mods), and removes white-space and comments. This will reduce HTTP requests and file sizes. Not speed up not only page loading by a little bit, but increase browser load speed greatly on slower computers.

11.| Make notification a numbered queue like facebook alerts, rather than sending an email.

12.| Add user tagging, meaning I can tag a user in a message(@Xarcell) and receive an notification that my name was tagged. It lets me know a comment was directed towards me. To cut down on abuse, you should only be able tag users that are participating within that topic. Also have an option to ignore those notifications for a particular topic.

13.| More CSS3 support, less IE6 support.

14.| Default theme(or "Master Theme" if you will), should have better smart-phone/tablet support out-of-box. Heck, look at windows 8.

15.| Eliminate as many images as you can. SMF uses way too many icons. Many of them can be created using pure CSS, like the "new" button. Reduce HTTP requests and page load.

16.| Eliminate post page, expand Quick Reply and use ajax.

17.| Continue support for multiple database types.

18.| URL's need to be prettier. Site domain followed by the category name, numeric topic id, and then numeric reply id if any. Example: "simplemachines.org/smf-development/feature-requests/topic=31689/". Each reply go in numeric order, example: "simplemachines.org/smf-development/feature-requests/topic=31689/reply=1/".

19.| For the love of GOD, don't add a sidebar, it won't be flexible enough. All or nothing. If you want to do such as thing, then do it properly. Allow blocks of content to be displayed around the forum. Much like your common portals. Top, bottom, left, and right.

20.| Option to apply any age, gender, or custom profile field into a membergroup, so that it can be given permissions. This would allow sites to restrict content by age, gender, or custom profile field. This is something I have not seen any software do, but is always asked for as a mod/add-on.

21.| No more gifs! SVG should be used with a PNG fallback(javascript needed to do this until it becomes fully supported) where applicable.

22.| Scrap karma system for users and add like/dislike system based on posts.

23.| Use overlays where applicable.

24.| Profiles need a make-over, add more information and ditch the old YaBB look. Be sure to add page views a profile, and show what the user is currently viewing.

25.| Full Litespeed support.

26.| Allow multiple polls per topic.

27.| Expand buddy system to include following their activity & posts.

28.| Add option to appoint a membergroup moderator, which add add/remove users from that particular membergroup.

29.| Option to use custom on/off images per board.

30.| Use jQuery as library of choice and/or jQuery mobile.

31.| Add "drag & drop" for arranging for categories/boards, and profile fields. Also any other areas where useful.

32.| Option to add attachments in PM's.

33.| phpinfo should be shown in admin section.

34.| Add default avatar, brings uniform to forum.


Help Forums Evolve!

1.| There should be an option to display a topic as an "article", "page", "file", "thread", or "blog". Really if you think about it, the only different between the four is HOW the information is displayed. Selecting between the five options merely changes which template can be used to display that information.

Membergroup permissions determine what type can be used, along with what code such as BBC, HTML, or PHP. An example of default restrictions would be Page & PHP is allowed by the admin only.

If your wondering what "file" type is, then it's nothing more than taking a post with an attachment and display to look like a item download page. All the information is there, it's just a manner of how to display it.

It would also make it easier to make an add-on for it. Someone might want a custom "reviews" add-on, that mainly just displays the information within the post to look like a review page.

2.| All content of any type can all be found within the forum. No need for separate sections. Actions(such as the calendar) show even be allowed to placed into a forum category. So there should be an option for every action to do this or not(Google doesn't like redirects). Either way though, everything that a forum has, should have an option be able to be found within the forum itself, including the member base. The forum index should be the sitemap!

3.| I'm not for third party support, but I think people should be able to login and post using their Facebook, Twitter, OpenID, Yahoo, Live, and Google login's without registering or creating a profile.



--- End quote ---

1. I agree.
2. Fine with me as well. Might make things more flexible.
3. I agree here as well. jQuery can be quite useful, and is very well supported, so I see no reason why we can't use it.
4. Not really sure on this one. Menu options are easy enough to add now - they just require a file edit. BBCode on the other hand would be nice, as our current system is much too confusing for those not familiar with PHP and such.
5. Agree here as well.
6. Agree, but we should have some standard fields defined by default, and let the admin change/remove them if they aren't wanted.
7. Mixed feelings on this as well. The biggest request in this area over the years has been to add more features (recurring events and the like), so removing it, even if it's kept as an official mod, might annoy people.
8. Agree. SMF's permissions system is quite powerful, but the current setup tends to confuse people more than anything.
9. Definitely. MySQL 4.0 is so ancient now that we should have no issues with dropping support for it in order to have full UTF8 support out of the box.
10. Interesting idea, but removing linebreaks, etc. from generated source might make it harder to debug things.
11. I agree as well. IPB has already moved in this direction and I love their current notifications system.
12. Agree, as long as it won't add a lot of overhead and can be disabled (not everyone wants to get notified when they're tagged)
13, 14 and 15: Agree
16. I would prefer to keep the post page. Adding more features to the Quick Reply is a good idea as long as we have control over it (some of us like the bare-bones quick reply :P).
17. Agreed. Just because Postgres and SQLite aren't as common as MySQL doesn't mean we shouldn't support them.
18. Disagree. Let's leave this one to mods.
19. Agree as well. Everytime I go to a forum which has a sidebar, the first thing I do is figure out how to get rid of it. There are portals for this if the admin really wants them.
20. Nice idea. Would definitely be popular. Question is whether it can be done without making things too complicated.
21. On the fence here. SVG is great for larger images that need to scale well, but I'm not sure how SVG would be better for the smaller images that we currently use GIFs for.
22. Like/dislike is all the rage these days, so go for it. Karma system never has been that useful since we never bothered to do anything with it, and very few mods actually use it for anything.
23. No idea what you mean here...
24. I agree as well.
25. Agree. Litespeed is becoming more and more popular, so we should do our best to support it.
26. Yes, especially if we can make dynamic polls (eg the second poll's options are based on what you voted for in the first poll)
27. Yes. Definitely.
28. Already exists :)
29. It's easy enough to replace the images now, so I don't know why we need to dumb it down any further...
30. Yes to jQuery. Don't know enough about the "mobile" version.
31. Yes, as long as it doesn't add a lot of overhead.
32. No, for the reasons already pointed out by others. There are plenty of file-sharing and image-hosting sites for this sort of thing.
33. Yes, as long as it's only available to admins (mainly to prevent whining about possible targeted attacks due to outdated server software :P)
34. Yes
1. Not sure about this. Might make things more confusing in the long run.
2. I think that would make things more confusing. A built-in XML sitemap might be good, but non-forum content should be kept out of the forum itself.
3. I agree here as well.

vbgamer45:
1. Use some html5 but not make the forum depend on it. Microdata is good.
2. No OOP there is no major gain and you will just end up rewriting all the code with the same bugs and that will take another couple years to get done. You can do parts that make sense.
3. jquery is nice as long as major parts of the code are not javascript based and depending on what you include does increase the page load time. Would like to see it optional.
4. Agree
5. Can go either way
6. Agree
7. We have the code already no need to remove it.
8. I think that is how it used to be in 1.1.x
9. Tables should be utf8 by default would help with some issues.
10. Looks nice I am big into reducing page loading time
11. Somewhat agree but I think it would be better have a summary either hourly or daily for certain events
12. Net idea
13. CSS3 on the fence it is not even completely defined yet. Would need to see the benefits and what browsers support what.
14. Agree mobile/tablet is needed.
15.Agree
16. Disagree maybe add a couple extra options to quickly
17. Disagree but keep the abstraction layer. Have hardly seen any posts in the other database type forums.
18. Agree.
19. Could go either way
20. Agree
21. Never seen a svg image with a web app. I would be in favor of PNG's over gifs. I don't even know what programs make svg files.
22. Not a big fan of scraping existing features but do like the idea of adding likes/dislikes to posts.

Navigation

[0] Message Index

[#] Next page

[*] Previous page