| Re: Idea : Norme for XOOPS tables |
| by Mamba on 2012/8/8 22:51:39 News 1.68 Beta with normalized table names and updated makepdf.php file for TCPDF is ready for testing. Download: XOOPS SVN Follow-up: please use this thread |
| Re: Idea : Norme for XOOPS tables |
| by irmtfan on 2012/7/15 4:30:33 Mamba: I mean core team (and not community) should set priorities for features because as you and ForMuss said there are limited times and resources for core team. Also when i told everybody can bombard the xoops.org forums for a feature i mean they can show their support and feed back for a mentioned feature even when they dont have anything to add or could not wrote in English. (so they just can send a single word or two) eg: I told somebody in our local community to support the "Thank you button" feature in xoops.org when i said it is up to the core team technically it will be interpreted to the below action: community can send features in sf.net and core team can go to the sourceforge feature tracker and set priorities. This feature to rename the xoops tables in more comprehensive way is good one but I mean there are many features already submitted that have higher priority. Also you just said this feature is not a simple renaming tables because then it will break the backward compatiblities. |
| Re: Idea : Norme for XOOPS tables |
| by Mamba on 2012/7/15 1:22:19 Quote: I repeat IMO core team should do what they intend to do. Just community can put pressure on them for a feature. eg: bombard the xoops.org forums for one needed feature and write the reasons and keep posting and ... I think, it's better to cooperate and work together as a one "XOOPS Community" instead of bombarding each other with features request, and getting on each other nerves. We have now Roadmap for XOOPS 2.6.0 and the community can discuss it and provide feedback in this thread. As Nicolas said, the Core team is open for suggestions, and if possible within given time and resources, they will try to accommodate them. The most successful products are those that are "customer focused". There are too many products that while technically superior, have failed because they missed what the customers wanted (for example, see Betamax vs. VHS). But that's only my view, so I would be curious what the rest of the community thinks about your comments... |
| Re: Idea : Norme for XOOPS tables |
| by Mamba on 2012/7/15 1:09:17 Quote: Moreover, Is it possible to get clean table for the next "news module" version: I've done it on my local installation. It seems to work OK, so once I'm done with some more testing, I'll release it as a new version 1.68 Beta for your testing. |
| Re: Idea : Norme for XOOPS tables |
| by irmtfan on 2012/7/14 6:00:11 +1 But IMO these are just some "Cosmetics features". XOOPS have more important "bugs" that should be solved and there are some very very important requested "features" that should be implemented in the next versions. IMO Core team should set the priority for features based on their technical ideas. a sidenote: Mamba: AFAIK You are a full democratic man and like to choose features based on the number of community requests (for example set a poll for each of them to find the priority. is there any?) but IMO it is up to current core developers to set the priorities. Your way of choosing is very time consuming and finally Xoops will not reach to anywhere. Also all of us in the community is not equal because our websites is not equal in visits, features, revenue and ... I repeat IMO core team should do what they intend to do. Just community can put pressure on them for a feature. eg: bombard the xoops.org forums for one needed feature and write the reasons and keep posting and ... |
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|