101
syrian_arab
Re: If we were to start a 2.6 Branch what would you like to see.

hi all

My request is the amendment to the comments:

1 - cancel button Add comment

2- And be added comment directly

3 - And to be beautifully

This is an example to add a comment in ( WordPress ) :

Resized Image


example link :
here

102
syrian_arab
Re: If we were to start a 2.6 Branch what would you like to see.

up ^_^

103
s3ra
Re: If we were to start a 2.6 Branch what would you like to see.
  • 2012/1/25 14:59

  • s3ra

  • Just popping in

  • Posts: 2

  • Since: 2011/10/11


Please take care to archiving + Seo + Button social sites ( facebook twiter tagged ....) + button google + Thank you

104
panwac
Re: If we were to start a 2.6 Branch what would you like to see.
  • 2012/1/25 18:15

  • panwac

  • Just popping in

  • Posts: 62

  • Since: 2005/11/12


Multidomain system!

Built in the core or in a separate module, but without having to make changes in the files of the core.
Thanks

105
timgno
Re: If we were to start a 2.6 Branch what would you like to see.
  • 2012/1/27 9:01

  • timgno

  • Module Developer

  • Posts: 1504

  • Since: 2007/6/21


I found a problem between the CSS and classes xoopsform, when I show a form submit or the same type register, the CSS class that should be on the top head is on the left of the form. For example, the class themeform.php, has this problem, we should improve the css and outer head another way. That's what causes all this comparing it with the original if I had to edit it:

Resized Image
Resized Image

106
voltan
Re: If we were to start a 2.6 Branch what would you like to see.
  • 2012/4/15 14:55

  • voltan

  • Theme Designer

  • Posts: 724

  • Since: 2006/12/5


Some idea :

1- comment system like WP
2- improve notifixtion system ( for example SMS notifiction )
3- new image/file manager
4- remove all pm and user functions from core and use PM and Preofile module for this part ( some files removed like : edituser.php, pmlite.php, readpmsg.php ,user.php ,userinfo.php ,viewpmsg.php
5- remove some old and unused files and functions from core like : misc.php / pda.php
6- multi feed system
7- improve search system and add better template
8- uncheck banner / rank / smile if that modules not installed
9- move some kernel class to module class ( for example banner codes )
10- improve URL system
11- have content module as core module
12- improve user functions in profile module

107
Anonymous
Re: If we were to start a 2.6 Branch what would you like to see.
  • 2012/4/15 15:20

  • Anonymous

  • Posts: 0

  • Since:


@ Voltan Particular having a content module as core module sounds like a great idea, in this way you can always be sure the content module is stable, up to date and translated. Many sites don't need any other modules...

108
demented
Re: If we were to start a 2.6 Branch what would you like to see.
  • 2012/4/16 2:49

  • demented

  • Just popping in

  • Posts: 40

  • Since: 2008/3/24


The ability to set experations on blocks

109
redheadedrod
Re: If we were to start a 2.6 Branch what would you like to see.

I don't know if calling them core modules is correct.

Perhaps calling them included modules would be better.

This would mean including them like how pm, profile and protector are now.

When I am able to devote more time to my projects I will be building a system that will make a lot of this discussion unnecessary. I have 3 more weeks of classes then I am done for the summer and one of my goals this summer is to revamp the whole installation system but it will require steps to get it accomplished. If I am successful you will see something more like the Drupal Install system along with the modules etc.
Attending College working towards Bachelors in Software Engineering and Network Security.

110
Anonymous
Re: If we were to start a 2.6 Branch what would you like to see.
  • 2012/4/16 9:57

  • Anonymous

  • Posts: 0

  • Since:


Revamping the install is good, but has nothing to do with a good content module. WP has one versatile build in and nobody complaints... Xoops has many content modules, all doing basically the same, and nobody really knows which of them will be developed further. So why not make the core development team responsible for one versatile content module? Current anarchy with half baken content modules is no good for xoops.

Login

Who's Online

226 user(s) are online (130 user(s) are browsing Support Forums)


Members: 0


Guests: 226


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Jun 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits