XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Modules Support forums / 
  3. Module usage questions 
  4.  / Repository Module
Register
41
Burning
Re: Repository Module

  • 2010/5/25 8:13

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


hi'

Thanks Ghia :)



--- About Php and Mysql version

If I do not create columns for Php and Mysql version, information will never appears in repository. I'm not developer, so if others are agree with you (the date is sufficient), I will not search further.



--- .ods file

1 • Module name
2 • Zip name
3 • Release date
4 • Compatibility
5 • Author name
6 • Module version
7 • Module folder name
8 • Download link
9 • Logo module *

* Column 9 is added and all logos are in a folder (logo name = archive name). Some has to be redesigned. The more easy way to proceed is only two colors :
• orange (old logo) for 2.0.x series
• bleu (new logo) for 2.3.x to 2.5.x series

Agree for two colors ?



--- Module description

Then, it will remain one column at least : module description. We have to create a "canvas" (html). Of course not all modules have a complete description...

Some ideas :
• short description
• long description
• blocks available
• language available
• changelog
• ... ????

Other suggestions ?

Still learning CSS and... english
42
Burning
Re: Repository Module

  • 2010/5/26 13:19

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


hi'

I'm "playing" with logos. How to say that... it is a huge mess !!

Just an example : for 164 modules published (Xoops 2.3.x), only 42 are compliant (I mean blue logo and with .png extension).

So if create new logos, I would have to edit 122 files xoops_version.php to declare the new logo. That's not a matter, we are in no hurry


Before I begin, no one against this change ? Good or bad idea ?

(I'm sorry for Bit3Rc0 and Tad who made very smart logos)


Thanks for response :)
Still learning CSS and... english
43
ghia
Re: Repository Module

  • 2010/5/26 13:40

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


As said before, I would use the module logo as the developer has created it, compliant or not.

It is not a shame to have an 'old' logo, it can also refer to a module with a long history of many versions, which resulted in a very mature module.
And of course also the graphics are the artwork of the developer and an integral part of the module.
44
belia
Re: Repository Module

  • 2010/5/26 14:05

  • belia

  • Just popping in

  • Posts: 83

  • Since: 2007/12/18


Quote:

As said before, I would use the module logo as the developer has created it, compliant or not.

It is not a shame to have an 'old' logo, it can also refer to a module with a long history of many versions, which resulted in a very mature module.
And of course also the graphics are the artwork of the developer and an integral part of the module.



+1

i support to keep the logo as it is
i like the logo by ed and tad...

what more important is the module works in latest xoops version

thanks for your work

may i know how will the module presented...is the old version of a module is download-able ...just in case..

or only latest version of module will be displayed... ?
45
Peekay
Re: Repository Module

  • 2010/5/26 15:27

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


Is there any chance in the future that developers could actually upload releases instead of linking to their own websites?

I know some devs want to host their modules during development, but I think it would help Xoops users enormously if devs were encouraged to commit final versions to the repository. Then at least the modules would always be available.

There was a time when you could upload files to the dev forge and create a link to the project page, but sadly this no longer works. Any downloads published there also have to be links.
A thread is for life. Not just for Christmas.
46
Burning
Re: Repository Module

  • 2010/5/26 17:19

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


@Peekay :
Quote:
Is there any chance in the future that developers could actually upload releases instead of linking to their own websites?

1. Direct submit should not be allowed

Before to release on xoops.org, must control
- archive content (virus scan for example
- archive format (not rar for example)
- archive name (XOOPS2 + mod + folder-name + version + author)

> in my opinion, we will need an upload form but with a moderation


2. Updates / creations of modules should all be reported on xoops.org

For moment we have to look for updates / creations of modules on various websites. Nobody can force developers to make regular anouncements : users have to report updates.

> repository comments could be used in this case
> ... and I hope when module repository will be cleaned, developers will be more """cooperative"""


Quote:
Then at least the modules would always be available.

Agree with you. I believe a good module repository should propose :
- link to developer's site if exist
- and, always, direct download to zip

I do not know how dev.xoops.org
works, but if needed, all zip are already prepared (more than 600 modules).



@belia :
Quote:
may i know how will the module presented...is the old version of a module is download-able ...just in case..
or only latest version of module will be displayed... ?

There are many particular cases.

Two mains :
• for more popular modules (eg. News), many developers propose their own version, less or more hacked. In such case, we provide all versions found
• for other modules, latest version will be available and if we can, original module (I mean last version released by original dev)

... there will be mistakes, but we hope dev or users help to correct it (comment function or anyway)
Still learning CSS and... english
47
Burning
Re: Repository Module

  • 2010/5/26 17:34

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


@Ghia
Quote:
As said before, I would use the module logo as the developer has created it, compliant or not.

It is not a shame to have an 'old' logo, it can also refer to a module with a long history of many versions, which resulted in a very mature module.

I believe we face two conflicting requirements :
• make repository more usable for newbies
• do not disturb old xoopsers with new logos

To make repository more usable, one idea is to ensure that the logos of the modules provide useful information.

If we use original logos, it will not the case

And more simply, if we choose to display modules logo, a graphic work is necessary (without any question logo orange / blue logo). See pdf :
- too various format / dimesions
- and in my opinion a lot are also too ugly

... even playing with the templates and the stylesheet, it will be difficult to use modules logo.



Quote:
And of course also the graphics are the artwork of the developer and an integral part of the module.

Agree, it is difficult to say we prefer a standard logo when developer has spent time on it

What we could do : when module logo is changed, display original one in module description.
Still learning CSS and... english
48
ghia
Re: Repository Module

  • 2010/5/26 20:28

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


Quote:
do not disturb old xoopsers with new logos
New XOOPSers don't know the difference!
If the logo differs in the module manager from the one in the repository, they may ask themselves questions and think they have done something wrong.

Quote:
even playing with the templates and the stylesheet, it will be difficult to use modules logo.

.modulelogo { width:92px ; height: 52px;}

I would not do more than that.

If you realy want to spend much time on it and do some special and useful graphics on the module, make a screen shot of a typical view for the module.
49
Peekay
Re: Repository Module

  • 2010/5/28 9:56

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


Quote:
ghia wrote:

If you realy want to spend much time on it and do some special and useful graphics on the module, make a screen shot of a typical view for the module.

I agree that would be very useful.

A 'Call for screenshots' campaign would save you a lot of work.
A thread is for life. Not just for Christmas.
50
Burning
Re: Repository Module

  • 2010/5/28 10:33

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


hi'

--- Screenshots ?

Quote:
A 'Call for screenshots' campaign would save you a lot of work.


If you think it is useful, why not ?
I will have no enough free time to do screenshots.



--- Where it is

1 • Module name
2 • Zip name
3 • Release date
4 • Compatibility
5 • Author name
6 • Module version
7 • Module folder name
8 • Download link
9 • Logo module original
10 • Logo module alternative (done, if we change our mind)

In progress :
11 • Profile developer url on xoops.org

Columns that remain to do :
12 • Category id
13 • Module description



--- 13 • Module description

Some ideas :
• short description
• main features
• blocks available
• language available
• installation notes
• changelog

Another informations to add ?
Still learning CSS and... english
« 1 2 3 4 (5) 6 7 8 9 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

359 user(s) are online (275 user(s) are browsing Support Forums)

Members: 0

Guests: 359

more...

Donat-O-Meter

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

Latest GitHub Commits