#1

Car Dealer sample application

8/6 16:16 Car Dealer module is a sample car dealer application based on IBM tutorial for Object Rexx

This modules shows that you can implement in XOOPS any project, even as complex as these designed by IBM

DOWNLOAD/FORK: https://github.com/mambax7/cardealer

SAMPLE DATA: The module provides a sample data that was incl. in the book, and you can import the data from the Admin - there is a special import button for it. This should give you a better understanding for what the module does.

DEMO: XOOPS Demo Website

MIN REQUIREMENTS: XOOPS 2.5.9, PHP 5.6+

Please fork it, test it and let me know what you think.

Any bugs/issues: please submit them on GitHub, or here in this Forum

#2

Publisher 1.06 FINAL Released (PHP 5.6 - 7.2.8)

8/1 23:55

Publisher 1.06 FINAL is released

This module has been updated for XOOPS 2.5.9 and PHP 5.6 - 7.2.8 Also tested on the upcoming XOOPS 2.5.10 and PHP 7.3

The key changes in this release are internal, i.e. we've moved to namespaces and class autoloading. This should make future development faster and easier! Hopefully!

DOWNLOAD: https://github.com/XoopsModules25x/publisher/releases

FORK: https://github.com/XoopsModules25x/publisher

TUTORIAL: https://docu.xoops.org/mkdocs/modules/ ... /en/book/2administration/

#3

Re: Publisher 1.06 RC-1 for XOOPS 2.5.9 and PHP 5.6 - 7.2.7

7/30 6:08 You can always submit new features on GitHub: https://github.com/XoopsModules25x/publisher

Just fork it from there and submit it there. If we like it, we'll be glad to incorporate it into Publisher.

#4

Famous SAKILA database is coming soon to XOOPS as a Web Application

7/22 22:46 As a result of last "Open Source Friday", the famous SAKILA database is coming soon to XOOPS as a Web Application, showcasing how easy it is to develop complex Web applications with XOOPS! :)
More info about Sakila:
https://dev.mysql.com/doc/sakila/en/sakila-structure.html

#5

MyMenus 1.54 Beta 2 (XOOPS 2.5.9, PHP 5.6 - 7.2.8)

7/20 17:09

The MyMenus 1.54 Beta-2 is available for testing on XOOPS 2.5.9 and PHP 5.6 - 7.2.8

New in this version: conversion to namespaces and class autoloading.

You can download it from GitHub.

And you can fork it from GitHub as well, and submit your improvements or bug fixes there.

We encourage everybody to open an account on GitHub and get used to working with Git, as this is the current Industry Standard.

Please note:

a) This version is developed and tested ONLY on XOOPS 2.5.9

b) This is still in a development, so please be careful and don't use it on a production site.

TUTORIAL

We are also looking for help with the Tutorial for My Menus and for few other modules.

You can fork the MyMenus Tutorial in GitHub, and then use GitBook to modify it, or you can modify it manually, directly in GitHub, or on your local PC with your own editor.

The beauty of this approach is that once you learn how to use GitHub, you can use these skills for both source code and for Documentation

#6

Re: Test for edit Forum topic (y) (x becomes y)

7/20 4:32 In the preferences, you have the option:
Quote:

Here we give the users 60 minutes time to modify their post, after which the "Edit" button is not shown anymore.

Check the Preferences in your installation.

#7

Re: Test for edit Forum topic (y) (x becomes y)

7/19 16:04 The Edit button should be there.
Did you have it before? If yes, what have you changed in your configuration recently?

#8

Re: Test for edit Forum topic (y) (x becomes y)

7/18 10:37 Just open and edit the "Subject" of the first post, and in case of other people responding, also the "subjects" of other posts, if you need to.

We don't have such a function, because each user can change the subject in their response, i.e. the "topic" will change automatically in his response.

As a moderator, I've changed your original topic by adding the (x) to it.

In my response, I've changed the topic by changing the (x) to (y) and adding the "(x becomes y)"

This way people can adjust their topics, and if the discussion moved to something else, the message can reflect that.

#9

Publisher 1.06 RC-1 for XOOPS 2.5.9 and PHP 5.6 - 7.2.7

7/15 13:09

Publisher 1.06 RC-1 is available for testing on XOOPS 2.5.9 and PHP 5.6.+

Changes in 1.06:
- namespaces and autoloading
- added missing common traits (goffy/mamba)
- fix for page styling in categories (liomj/mamba)
- added Constants class
- added truncateHTML
- fixed active notifications
- responsive image
- blocks Admin

DOWNLOAD: https://github.com/XoopsModules25x/publisher/releases

FORK: https://github.com/XoopsModules25x/publisher

TUTORIAL: https://docu.xoops.org/mkdocs/modules/ ... /en/book/2administration/

Still afraid of GitHub? Maybe this will help?
https://try.github.io/

#10

Re: set class for form elements

7/12 2:20 What would be "use case" for it?

As I understand, the XoopsFormRenderer is basically a "factory" to create a consistent visual implementation for all elements of the XoopsForm

In XOOPS 2.5.9 Mage and Geekwright extracted it to an Interface, and added the Bootstrap implementation, so now you can call either the XoopsFormRendererLegacy or XoopsFormRendererBootstrap3.
And you could provide XoopsFormRendererXXX that would be specific to your "look & feel" by using some other CSS framework.

It's along the line: "Don't call us, we'll call you", i.e. you provide the implementation via XoopsFormRendererXXX , and XOOPS will call it and use it to render individual elements of your implementation as needed.

More about the Hollywood Principle using the Template Method:




So if I understand correctly, instead of going trough the XoopsFormRendererXXX and let it do the job for you, you would like to be able to provide implementation for individual element (like the FormButton) and then render it individually as needed, correct?

What would be the advantage of it?

Do you want to have an option that in case you don't like the implementation of XoopsFormRendererBootstrap3, instead of modifying the whole Renderer, you just want the option to change the FormButton? If yes, could you just subclass the Renderer and make the changes as needed there?

BTW - there was an interesting article about using "Inheritance of XoopsForms"