Subject:*
<
Name/Email:*
<
Message Icon:*
<
Select*
<
Message:*
<



Click the Preview to see the content in action.
Options:*
<
Confirmation Code*
<
9 - 7 = ?  
Input the result from the expression
Maximum attempts you can try: 10
*
<
   

Re: XOOPS Module Admin GUI Guidelines
by mboyden on 2010/6/1 14:49:41

Yes, having a common methodology for administration would be great. There was a push for this some time back and a lot of the authors jumped on board with the tabs concept. However, we kinda moved away from it. We also started a Module Quality Team awhile back that rated modules on various things such as this as well as code (such as putting HTML into the functional layer, a no-no that still is done too much IMHO).

Maybe a revival of that along with the updated repository that is moving forward.

Personally, I started using Crystal Icons about 18 months ago and all deployed modules on the user side use a consistent set of these since then for all my installations. It could help all our users to do that. The next question becomes which size or having a configuration option that allows the user to choose, but the icons don't all exist at all sizes either.

But, it's the right thing for us to do -- to adopt a standard set of icons and use them throughout our modules and core.
Re: XOOPS Module Admin GUI Guidelines
by vamptrix on 2010/6/1 11:22:41

Very nice indeed - looks promising, but a lot of modules should get an update for it, but it's indeed very interesting..
Re: XOOPS Module Admin GUI Guidelines
by Mamba on 2010/6/1 7:44:06

The problem is that they are only in 16x16 size.

Crystal Icons have several different sizes.

But I hope, we'll evolve to a system where the icons will be stored centrally and each module will get them from there, and the user will be able to define in Preferences which set he wants to use: Crystal, FamFamFam, or yet something custom.

The key is that once the user selects the icon set, he'll have all modules using this particular set, and thus having a consistent look and feel. Currently, each module is pretty much using own set of icons.

Add to it a theme switch mechanism for Admin/Modules like the one ThemeRoller from jQueryUI , and then we have a very nice solution for our users.
Re: XOOPS Module Admin GUI Guidelines
by vamptrix on 2010/6/1 7:10:50

I'd prefer if we'd used the Silk icons from FamFamFam. They look awesome, are free and there are 1000 icons - more than enough.

http://www.famfamfam.com/archive/silk-icons-thats-your-lot/
Re: XOOPS Module Admin GUI Guidelines
by luciorota on 2010/5/31 21:28:01

we can improve XoopsSystemGui class, with some methods...

addIcon('icon name', ICON URL, ICON_DECSRIPTION, ICON_SIZE...)
renderIcon('icon name')
srcIcon('...')
...

sir Trabis on 2009-09-13 is the last who commits on this class... his wisdom could be useful

Who's Online

176 user(s) are online (124 user(s) are browsing Support Forums)


Members: 0


Guests: 176


more...

Donat-O-Meter

Stats
Goal: $15.00
Due Date: Jul 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $15.00
Make donations with PayPal!

Latest GitHub Commits