should we bring hypeWall functionality into core

[jdalsem]

Could fix #3829

[beck24]

It's definitely a nicer UI, and it seems there tends to be a lot of demand for an integrated content creation UI. My experience working with it was that it's complex to customize, but that can probably be addressed better if it's integrated directly.

[hypeJunction]

I am rewriting it now to not require hypeApps. Should be much simpler then.

[jdalsem]

why not rewrite for core immediately... saves you a plugin to maintain

[hypeJunction]

I have a strong opinion about how the wall should work, so I am not sure I can come up with something versatile enough. I suppose if I were to do it for core, I would just hack my way through the wire plugin - migrate replies to comments, add some settings. I guess the idea of the wall is a rich post type - an object that can have a linked URL, file/object attachments, mentions etc. In the long run, blog, bookmark, discussion could all extend this rich post type. Perhaps adding ElggPost class with some interfaces would be the way to go.

[jdalsem]

i think more devs think the same about how you think the wire/wall should work. I would be happy to work on it (to help you), as modern social networks really need a good wall/stream/activity feature

[Facyla]

While i do not use hypeWall, a common issue from users/clients is that people want to start (something) without determining at first the object subtype, and also find content without having to know its subtype first ("was it a file, or a discussion with an embedded file, or...").

The group search and the group activity are partial answers to the search issue, but there is not much on the new content side.

Use case would be something like: "I want to share some info, let's add a few words...

• ..and also a link to the related web resource
• and this file too (saves)
• Nice, can i give edit access to (some users) ?
• And notify (some users) too ?
• Can i link it to another entity ? ..."

I am not sure what would be the right direction for core, but i suspect the commenting process to be a good candidate for this kind of features: it basically means attaching an object to an existing "parent" object => any other object type could be attached in a discussion in the same way, without even creating new content types.

Since comments are entities, the new logic would fit easily, one would mostly need to add a hook that defines which object subtypes can be used to comment a given object subtype. Eg. discussion could also be commented with bookmarks and files.

Ideally this would better work if the deletion of the container does not always delete the contained entities as well: owners might want to get their contribution back if the containing entity is deleted (related https://github.com/Elgg/Elgg/issues/10770 )

[dranii]

Can the Elgg3x version of hypewall be now included in core in the next release (if possible) - this discussion was started in 2016 and we are nearing 2020 end. Moreover, php 8 has been already released (alpha) and probably some servers like laragon allow testing stuffs into it. Thus, if hypewall (as it is now, it seems to work more or less okay with Elgg 3x and php 7x) is now included, next versions of Elgg can be tested for performance ( any major problem or not ) with respect to both hypewall and php 8

With many plugins being in deadpool ( with exception of coldtrick, iionly and few others) its high time, if it is kindly possible to bring Elgg usability, functions and interface w.r.t. "status box" at par with existing scenario as well as get ready for php8, in the sense, that whatever we do now should be working with php8 too. Although its php 8 alpha, if stuffs work in it, its is most likely that it will work in php 8 beta s and rc s.

[jdalsem]

i see nobody working on this right now, so i am expecting nothing at this moment

[daniyaree]

Is there any problem in adding hypewall 3x as a bundled plugin (like other bundled plugins) in the next downloadable Elgg zip/tar? This way, it can be tested by a wide user-base and maybe someone can submit patches, if needed at all.

[jdalsem]

Is there any problem in adding hypewall 3x as a bundled plugin (like other bundled plugins) in the next downloadable Elgg zip/tar

maybe not, but as i said, nobody is making an effort at this moment to investigate it

[jdalsem]

Closing due to lack of activity. All developed code will also be very outdated at the moment.