hi,
I need a functionality, that new users, when logged in, would see highlighted categories (in a sideblock), which have new items.

Does XOOPS have a articles/news/blog module with such functionality?

ps.: in addition it would be nice to have cats/topics with new comments marked as well.

The new item marking would be more significant than new comment.

If there's no such module, would it be hard to implement this?

I think most forums (at least phpBB) have similar feature, but there new topics are equivalent to simple replies/comments..

Quote:

Its more fundamental thing - better ask this not in "beginners corner" but some devs..

I know there are such technique as "remote procedure calls" or so - this way You can link scripts even on different servers.

but anywhay, why not learn PHP? :) (PHP5 has many of pythons features, OO and similar)

hi, I found it on mamboforge, but nevertheless it shares lots of things with any CMS -- a good tutorial for young admins :)
http://mamboforge.net/frs/download.php/408/Securing_Mambo_OS-v0.4.pdf

* well I had primitive idea with shared logins for several portal systems to be used symultaneusly (would be intresting to hear some feedback, as mambers are not very geeky ;)

* well, looks like portal system with (nearly) all kinds of features ishttp://tikiwiki.org . Google doesnt show something very bad about it. You can compare problems of tiki and xoops (well number of pages found might mean not only that XOOPS has more problems, but also, that forums are more actively used ;).

* some more short and quite "to the point" overviews of PS's


ps.: well, I don't intend to misvaluate XOOPS -- I try to compare things, in order to make a better choice..
pps: somewhy I wasn't allowed to edit my last post? (probably I am loosing my XOOPS karma (or maybe after edits are allowed only in current session..))

Quote:

well, for recent projects I prefer mambo to xoops, but Ilived with XOOPS for two years and I like the community :). And of course I'd like XOOPS to be better :), so I point out what are shortcomings for users like me.
well from time to time I think, it's a pitty, that there are so many portal systems, with quite similar purposes, but with quite different feature-packs. My dream is to see XOOPS and mambo (and moodle and e-groupware) merged someday some (positive) way
of course moodle and e-groupware have their specific, but it would be nice to have some standart way to integrate/join such systems easily. well, You see, I'm a dreamer

short overview of 10 CMS's: mxx included :)
http://biz-whiz.com/print225.html

Hi, I am more of programmer than designer. and thats my experience of my two sites of XOOPS for communities of about 300 peoples (10% really active - submitters):
XOOPS is my first CMS to live with.
* Fluent instalation
* quite intuitive admin panel (backend) - thoug sometimes was time consuming to deal with access rights..
* smarty wasn't of big (or maybe even any) use for me..
* was time-consuming to find and make up the design we wanted
* I managed to hack some modules, but didn't manage to make up my own (even a blank one..).
** because there were not enough docs
** for me XOOPS OO seemed compicated to code according to it
* was hard time (well, more of "took a while") making up horizontal dynamic menus
* my XOOPS theme loads slower than mambo sites I know (well may be I overloaded it with js.. - for dynamic menu and and ability for modules to collapsehttp://somsa.ktusa.lt/xoops)


MAMBO is what I used now for several projects.
* installation no worse than XOOPS (even has sample data - to see the basic design of site at once)
* theming/designing is more simple (HTML with some php)- so time-saving (we all like it, don't we :) - bigger variety than XOOPS
* can have unlimited areas for blocks (xoops has just 5: R, CC, CR, CL, L).
* Has good content management in the core (xoops has probably 5 content management modules, and its confusing..)
* a bunch of adopted dynamic menus and WYSIWYG editors
* navbar/pathway in the core
* more flexible, because
** mambo is more modular (imho) - it lets develop and manage blocks separately from modules (in mambo terms blocks are called "modules" and modules are called "components" - strange ;).
** mambots - things for linking between modules(components in mamb) - didn't try, but they have potential
* user management - groups can inherit rights according to hierarchy - so easier to setup installed features (especially, when there are many features)
* seems to have bigger community
=> generally - more admin-friendly and user-atractive, and users are the reason, why we need Portal systems, isn't it?
* and multilanguage (still a hack, but promises to be in the core of v4.6 (now is v4.5.1)) (also multiple categories for articles promised in 4.6)
several minuses:
- at first it seems weird, that components and modules are stored separately
- doesn't have comments feature in core, but there is mambot whitch can help ;) (generaly it is orentiered more towards content than community).
- well, they have tey own cache system, don't know about it more
- updates are more often than xoops, but the reason in my mind is that mambo is evolving more dynamically
- v4.5.1 still doesn't have fully integrated gallery. but media manager or paralelly installed RC Gallery with random photo block can help

may be I wrote not very clearly, so I'll check out if some questions will arise

http://mambots.com/
mambo has it in its core as sth very interesting, but it is used simply:
You can include some tags into your text: for example {mosimage}, {mos_sb_discuss:26} or so,
and mambots are small pieces of code, which use regexp to replace those tags with appropriate things..

If now we use xoops-code interpreter, so it also could be xoops-bot. (I mean thees things sould be handled quite similary).

Could some core guys explain, is it difficult to add similar functionality?

We know from html history, that tagging has a great power to connect things, so why not bring it to xoops?

if You find a good way , please leave aline about it here
http://wiki.xoops.org/wakka.php?wakka=DynamicMenu

hey I found than wf-section is goint the way, I am expecting :)