5992
Vamptrix, you are speaking right of my soul.
The situation right now is really a mess.
Behind closed doors I have already spoken to mamba and asked for changes that needs to be done.
What I think should happen:
- get the 2.5.x core boostrap ready
- take the main 10 - 12 Modules and make bootstrap templates
- only support bootstrap theme / template development, which means break dependencies with old themes
- put all old themes and modules in a archive. offer only the main modules for download
- get the main modules to the final version
- set up one place for the module / core development (GitHub)
- with xoops 2.6 we should break all dependecies with the old core! let us start from 0. with a new core, new features without losing time with old stuff.
Right now I am setting up a new german xoops website, with which I am trying to meet all the above named points. I have to say that this is really really hard job.
But there is a light at the end of the tunnel. Right now we are working on testing / getting the main modules to the final version. Also there is effort to get all modules to the github where the development will be supported.
Everyone is welcome to test the mymenus RC version which is published in the forums. New modules will be published for testing.
But I have no hope that all this points will be done very fast.
The situation right now is really a mess.
Behind closed doors I have already spoken to mamba and asked for changes that needs to be done.
What I think should happen:
- get the 2.5.x core boostrap ready
- take the main 10 - 12 Modules and make bootstrap templates
- only support bootstrap theme / template development, which means break dependencies with old themes
- put all old themes and modules in a archive. offer only the main modules for download
- get the main modules to the final version
- set up one place for the module / core development (GitHub)
- with xoops 2.6 we should break all dependecies with the old core! let us start from 0. with a new core, new features without losing time with old stuff.
Right now I am setting up a new german xoops website, with which I am trying to meet all the above named points. I have to say that this is really really hard job.
But there is a light at the end of the tunnel. Right now we are working on testing / getting the main modules to the final version. Also there is effort to get all modules to the github where the development will be supported.
Everyone is welcome to test the mymenus RC version which is published in the forums. New modules will be published for testing.
But I have no hope that all this points will be done very fast.
5993
Hello all, in this (way too long) post I'm talking about my personal opinion about XOOPS and where we need to take the project. It's all my opinion ;).
XOOPS has been standing too long at a standstill.
It breaks my heart, but XOOPS hasn't really seen any progress in a long while. Everything seems to have come to a standstill, even though work is being done working on XOOPS.
It all looks however like nothing is happening: check the website and you barely see anything new. Exciting things are being worked on in the kitchen however:
* xBootstrap
* xThemes and the possibilities it adds
* XOOPS 2.6
However, even more things have grounded to a halt or have simply dropped dead. Examples of this are abundant:
* Module development is nearly dead. New modules have stopped coming for a long while, mostly small updates of a few modules occur. Old modules aren't really maintained.
* Theme development is also nearly dead. The last new theme by someone else than angelorocha and Bitcero dates from 30 August 2014 by Sinnedesign.
* A World of XOOPS hasn't been done since October 2013, more than a year ago. And in that release there is being spoken about XOOPS 2.6, but it still isn't out.
* A lot of developers have simply stopped working and moved on to other projects, including some of the biggest contributers I've known.
Generally, it looks like a ton of things are dead, which is truly a shame.
What are the causes of this?
In my opinion, the things that cause this are:
1) A really big lack of information and documentation.
A lot of things or documentation offered by XOOPS is either outdated or simply incorrect. Many of it's links are dead or point to wrong information. (Example: https://xoops.org/modules/smartfaq/faq.php?faqid=331).
The official XOOPS Documentation (https://xoops.org/modules/mediawiki/index.php?title=Main_Page) is chaotic and incomplete. It's not really welcoming for new users and just fulled with incomplete and incorrect info.
For developers, the amount of information is almost non-excistant, and it's all hosted on third-party sites. I have tried to get into module development, but I never found a starting point and reliable information/documentation to support me.
Should there be good documentation available, I would have continued, but right now I don't even know where to start.
2) The official site is a mess.
Yes, I said it. XOOPS.org is a mess.
XOOPS.org isn't following a clear visual style, which really is an issue in XOOPS itself. Check the Theme gallery, compare it to the Module repository. Both look completely different and feel different.
The Repository is bugged and doesn't show sub-categories on the frontpage, but simply says Array. Many downloads don't work at all and you get redirected to the XOOPS Sourceforge page. Some categories don't display anything at all.
Basicly, the module Repository is useless and doesn't do what it's supposed to do.
The theme gallery is huge, has a ton of themes that aren't from this age and really should be either updated or dropped. Examples of this? Just check the theme gallery. Themes are by default sorted by Date, and the newest ones are shown first, but no themes were added in the gallery after 2010. It's just not user-friendly and it doesn't work like it should in my opinion.
A nice example of what I think is a great theme gallery (though it isn't perfect at all) is the Ghost Marketplace (http://marketplace.ghost.org/). Simplicity is bliss.
Another big issue for me is the Forum, like it currently is. It's a mess, which should be changed/restructured in my opinion. An example is that we have support threads for 2.3, 2.4, 2.5, 2.6.
In my opinion these should be merged into 1 main Support category, with sub-forums for versions.
As far as I was able to Google, 2.3 was released in 2008, so I really think this should be archived so it doesn't pollute the main (most important) threads.
I'd like to see all of the "old" boards archived in a special category. It'll be much more clean and easier to use!
3) Isn't it time to move on and drop older versions?
On the XOOPS website, we support a lot of things. Many of these shouldn't be there anymore. For example, the theme gallery seperates between old and new themes. This was for version 2.0.14.
XOOPS 2.0.14 was released in 2006, nearly 10 years ago. Shouldn't we simply drop these themes, or put them on an archive? It doesn't make any sense at all to still offer these on our site after all these years. You've had time enough to upgrade ;). This will also clean the servers and maybe allow to save some money.
Same thing applies to the Module Repository, documentation and the forums. When it's too old, archive it or delete it. It just costs a lot of effort to keep and maintain these things.
Okay, that was about everything I could think about right now. Ofcourse, I wouldn't rant about things and not do anything myself.
Recently, I've decided to help with the development of XOOPS, so I'll try to help with that. My PHP isn't that excellent yet, so it might be slow.
I'm also willing to help with the documentation or even start working on it right away, to ensure that we can start XOOPS 2.6 with a really well backed documentation.
I would also like to help moderating the forums and help restructuring the site as needed.
Name any area that needs to be improved, and if I can change it and help, I will.
Right now, I'd like to ask you guys your opinion about what I just typed (thanks for reading this :P) and I'm awaiting the feedback you guys might have.
Our time is now, let us not waste it!
Kevin
XOOPS has been standing too long at a standstill.
It breaks my heart, but XOOPS hasn't really seen any progress in a long while. Everything seems to have come to a standstill, even though work is being done working on XOOPS.
It all looks however like nothing is happening: check the website and you barely see anything new. Exciting things are being worked on in the kitchen however:
* xBootstrap
* xThemes and the possibilities it adds
* XOOPS 2.6
However, even more things have grounded to a halt or have simply dropped dead. Examples of this are abundant:
* Module development is nearly dead. New modules have stopped coming for a long while, mostly small updates of a few modules occur. Old modules aren't really maintained.
* Theme development is also nearly dead. The last new theme by someone else than angelorocha and Bitcero dates from 30 August 2014 by Sinnedesign.
* A World of XOOPS hasn't been done since October 2013, more than a year ago. And in that release there is being spoken about XOOPS 2.6, but it still isn't out.
* A lot of developers have simply stopped working and moved on to other projects, including some of the biggest contributers I've known.
Generally, it looks like a ton of things are dead, which is truly a shame.
What are the causes of this?
In my opinion, the things that cause this are:
1) A really big lack of information and documentation.
A lot of things or documentation offered by XOOPS is either outdated or simply incorrect. Many of it's links are dead or point to wrong information. (Example: https://xoops.org/modules/smartfaq/faq.php?faqid=331).
The official XOOPS Documentation (https://xoops.org/modules/mediawiki/index.php?title=Main_Page) is chaotic and incomplete. It's not really welcoming for new users and just fulled with incomplete and incorrect info.
For developers, the amount of information is almost non-excistant, and it's all hosted on third-party sites. I have tried to get into module development, but I never found a starting point and reliable information/documentation to support me.
Should there be good documentation available, I would have continued, but right now I don't even know where to start.
2) The official site is a mess.
Yes, I said it. XOOPS.org is a mess.
XOOPS.org isn't following a clear visual style, which really is an issue in XOOPS itself. Check the Theme gallery, compare it to the Module repository. Both look completely different and feel different.
The Repository is bugged and doesn't show sub-categories on the frontpage, but simply says Array. Many downloads don't work at all and you get redirected to the XOOPS Sourceforge page. Some categories don't display anything at all.
Basicly, the module Repository is useless and doesn't do what it's supposed to do.
The theme gallery is huge, has a ton of themes that aren't from this age and really should be either updated or dropped. Examples of this? Just check the theme gallery. Themes are by default sorted by Date, and the newest ones are shown first, but no themes were added in the gallery after 2010. It's just not user-friendly and it doesn't work like it should in my opinion.
A nice example of what I think is a great theme gallery (though it isn't perfect at all) is the Ghost Marketplace (http://marketplace.ghost.org/). Simplicity is bliss.
Another big issue for me is the Forum, like it currently is. It's a mess, which should be changed/restructured in my opinion. An example is that we have support threads for 2.3, 2.4, 2.5, 2.6.
In my opinion these should be merged into 1 main Support category, with sub-forums for versions.
As far as I was able to Google, 2.3 was released in 2008, so I really think this should be archived so it doesn't pollute the main (most important) threads.
I'd like to see all of the "old" boards archived in a special category. It'll be much more clean and easier to use!
3) Isn't it time to move on and drop older versions?
On the XOOPS website, we support a lot of things. Many of these shouldn't be there anymore. For example, the theme gallery seperates between old and new themes. This was for version 2.0.14.
XOOPS 2.0.14 was released in 2006, nearly 10 years ago. Shouldn't we simply drop these themes, or put them on an archive? It doesn't make any sense at all to still offer these on our site after all these years. You've had time enough to upgrade ;). This will also clean the servers and maybe allow to save some money.
Same thing applies to the Module Repository, documentation and the forums. When it's too old, archive it or delete it. It just costs a lot of effort to keep and maintain these things.
Okay, that was about everything I could think about right now. Ofcourse, I wouldn't rant about things and not do anything myself.
Recently, I've decided to help with the development of XOOPS, so I'll try to help with that. My PHP isn't that excellent yet, so it might be slow.
I'm also willing to help with the documentation or even start working on it right away, to ensure that we can start XOOPS 2.6 with a really well backed documentation.
I would also like to help moderating the forums and help restructuring the site as needed.
Name any area that needs to be improved, and if I can change it and help, I will.
Right now, I'd like to ask you guys your opinion about what I just typed (thanks for reading this :P) and I'm awaiting the feedback you guys might have.
Our time is now, let us not waste it!
Kevin
5994
Thanks to a very hard and dedicated work by Zyspec and Luciorota, and contributions from LioMJ and our UI/UX team, we're happy to release for testing MyMenus 1.51 RC-1!
You can download it from GitHub:
https://github.com/XoopsModules25x/mymenus/releases
Please help us with testing, and most importantly, go ahead and fork it, and help us with development. This will be also a good practice for you on how to work with GitHub!
The MyMenus 1.51 RC-1 is entering testing and bug fixing phase, i.e. we don't anticipate any new features being added. But we would like to make it as solid as possible.
This release, as well as upcoming releases for all other modules, are focusing on and will be certified for XOOPS 2.5.7.1.
We also recommend at least PHP 5.4
You can download it from GitHub:
https://github.com/XoopsModules25x/mymenus/releases
Please help us with testing, and most importantly, go ahead and fork it, and help us with development. This will be also a good practice for you on how to work with GitHub!
The MyMenus 1.51 RC-1 is entering testing and bug fixing phase, i.e. we don't anticipate any new features being added. But we would like to make it as solid as possible.
This release, as well as upcoming releases for all other modules, are focusing on and will be certified for XOOPS 2.5.7.1.
We also recommend at least PHP 5.4
5995
Hi,
Please wait for mamba before you do any further develpment.
I am not sure if you are working on the latest version.
I am very happy to see you working on this module. Maybe it is better not to add new features and instead get from beta to a final version.
Please wait for mamba before you do any further develpment.
I am not sure if you are working on the latest version.
I am very happy to see you working on this module. Maybe it is better not to add new features and instead get from beta to a final version.
5996
Committed last changes
https://github.com/luciorota/mymenus
changelog
Version 1.51 Beta 3 (2015-02-23)
- TODO: use Xmf libraries
- TODO: reintroduce hooks ...
- TODO: create infinite levels menu
- TODO: inline edit link vars
- fixed bug in update procedure (luciorota)
- added treemenu (LioMJ)
- standardize module to latest code style standards (luciorota)
- merged @zyspec and @luciorota code (luciorota)
what about working from this point?
https://github.com/luciorota/mymenus
changelog
Version 1.51 Beta 3 (2015-02-23)
- TODO: use Xmf libraries
- TODO: reintroduce hooks ...
- TODO: create infinite levels menu
- TODO: inline edit link vars
- fixed bug in update procedure (luciorota)
- added treemenu (LioMJ)
- standardize module to latest code style standards (luciorota)
- merged @zyspec and @luciorota code (luciorota)
what about working from this point?
5997
Thanks -
Ok they are two very different sites...
The main thing I think one of them uses the xoops method for storing password...
that one iI think is the one Ill start with.
Ill be curious to see how much I can import and I'll basically do anew xoops install locally and import data and see what happens. Will share what I learn.
Thanks!
Ok they are two very different sites...
The main thing I think one of them uses the xoops method for storing password...
that one iI think is the one Ill start with.
Ill be curious to see how much I can import and I'll basically do anew xoops install locally and import data and see what happens. Will share what I learn.
Thanks!
5999
Maybe you can update the existing template to use dropdown classes without having to set the classes manually
6000
Sorry.. ignore my attempt to create the bootstrap skin.
Ive been using the old version of mymenus in my new project...
.actually there is already bootstrap skin in mymenu 1.50
Refer the comment by bleek in this news
https://xoops.org/modules/news/article.php?storyid=6570
Keep up the good work with this module
Ive been using the old version of mymenus in my new project...
.actually there is already bootstrap skin in mymenu 1.50
Refer the comment by bleek in this news
https://xoops.org/modules/news/article.php?storyid=6570
Keep up the good work with this module
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|