41
Burning
Re: Roadmap 2.6.0 Discussion
  • 2012/8/15 13:31

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


@Mariane about a Xoops form inside a custom block : quite esay to do with this module http://myht.org/modules/mydownloads/singlefile.php?lid=21

42
Roby73
Re: Roadmap 2.6.0 Discussion
  • 2012/8/15 22:53

  • Roby73

  • Friend of XOOPS

  • Posts: 262

  • Since: 2011/6/15


Many modules use social network...
An example:
<script src="http://connect.facebook.net/en_US/all.js#xfbml=1">


en_US there is in template for all languages.
If define a constant in global languages, each country has its.

43
mariane
Re: Roadmap 2.6.0 Discussion
  • 2012/8/16 8:35

  • mariane

  • Theme Designer

  • Posts: 649

  • Since: 2008/1/11


@ Burning : thanks for the module, but I think we have to find a technic to show any module in block : contact, liaise, ...etc

44
Burning
Re: Roadmap 2.6.0 Discussion
  • 2012/8/16 21:33

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


@Mariane, it is an heavy change ....

If I well understand, you would like many (at least two) $xoops_content variables on the same page. I'm not sure such feature will be easy :
• to develop (core = 1 $xoops_content, theme = 1 $xoops_content, ...)
• to keep an admin area easy to use

It would be more logical :
• to deliver modules with more blocks, to activate / desactivate
• and if all blocks available are not enough, to create a tool / a wizard to create your own sql requests, with a live preview

... simplicity first :) !

45
tatane
Re: Roadmap 2.6.0 Discussion
  • 2012/8/17 7:04

  • tatane

  • Just can't stay away

  • Posts: 649

  • Since: 2008/5/6 1


Quote:

mariane wrote:
Quote:
What do you mean?
You can do this now with the "blocks anywhere" hack.
(May need to update it for 2.5.5 if you are using the newest stable xoops)
You can go further with this with the block permissions to show a block or not on a page.

Block anywhere allows you to place a block anywhere in your theme, but what you can do if the module dosnt have a block? for example if you wish to show a quick contact us form in your footer, what is the best solution to do it with xoops? the module contact dosnt have a block.


it's exactly like me https://xoops.org/modules/newbb/viewto ... id=348764#forumpost348764

46
deka87
Re: Roadmap 2.6.0 Discussion
  • 2012/8/17 8:13

  • deka87

  • Friend of XOOPS

  • Posts: 1124

  • Since: 2007/10/5


That's true. AFAIK Xoops sticks with its header and footer and there is nothing we can do about it. I faced this when I tried to put an avatar edit page in a modal window so that users won't need to open a new page to edit their avatar. But having a full page in a modal window is a pretty weird idea.

47
alain91
Re: Roadmap 2.6.0 Discussion
  • 2012/11/17 18:31

  • alain91

  • Just popping in

  • Posts: 8

  • Since: 2012/11/11


@mamba

Could you tell me the best way to contribute to the next 2.6.0 version ?

I'm developper with an more than 5 years of experience in PHP (including work with some frameworks and cms).

48
Mamba
Re: Roadmap 2.6.0 Discussion
  • 2012/11/17 23:19

  • Mamba

  • Moderator

  • Posts: 11206

  • Since: 2004/4/23


Quote:
Could you tell me the best way to contribute to the next 2.6.0 version ?

Thank you so much for your interest in joining XOOPS!

I've sent you an email with more details, but contributing is very easy, and similar to other Open Source Projects, like the Apache Software Foundation

1) Become a member on SourceForge, and we'll add you to XOOPS there

2) Show us some code so we can see that you know what you're doing

3) start providing code improvements first in a separate branch, and once the Core Team feels comfortable with your code, you'll be able to contribute directly in the main tree.

Let me know if this makes sense to you.

Once again, welcome to XOOPS, and we're looking forward to your contributions!

Support XOOPS => DONATE
Use 2.5.10 | Docs | Modules | Bugs

49
bumciach
Re: Roadmap 2.6.0 Discussion
  • 2012/11/27 14:10

  • bumciach

  • Not too shy to talk

  • Posts: 153

  • Since: 2007/6/25


Quote:

irmtfan wrote:
In one sentence I repeat: That log/history module should be totally functional.


Did you think module like that can also store serialized state of XoopsObject? First, when $xoopsobject->get() and second after submit add/edit form when $xoopsobject->insert(). And make diff between old and new state of the object. It should be easy making history what data was changing on any individual record.
I thought of develop that module for a long time (something similar to XBS Logger). But have never started to do it.

50
trabis
Re: Roadmap 2.6.0 Discussion
  • 2012/11/28 1:11

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


Quote:

deka87 wrote:
That's true. AFAIK Xoops sticks with its header and footer and there is nothing we can do about it. I faced this when I tried to put an avatar edit page in a modal window so that users won't need to open a new page to edit their avatar. But having a full page in a modal window is a pretty weird idea.


Yes, we would like to be able to get the module output just as if it was a block.
We need to have a controller/action class with a given interface that modules would implement. The core would then be able to execute a module action without requiring the rendering of blocks or theme. Forwarding actions, ajax calls, rpc, ohhh... I believe it would be a small step for developers and a giant leap for Xoops.

Login

Username:
Password:

Lost Password? Register now!

Who's Online

72 user(s) are online (48 user(s) are browsing Support Forums)


Members: 0


Guests: 72


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