Code Monkey home page Code Monkey logo

fosmessage's People

Contributors

aitboudad avatar bjrothman avatar ionafan2 avatar soullivaneuh avatar tgalopin avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

fosmessage's Issues

What persistance systems do we have to support for first release?

Hello everyone,

One of the questions we have to ask ourselves is what persistance system do we have / want to support for first release?

I think Doctrine ORM and ODM are clearly needed. However, I don't know very well the popularity of the others.

FOSUserBundle supports Propel. Are there a lot of people using Propel?
Does anyone else use another persistance layer and would like a support for it in the library?

Collection of messages is not synchronized in conversation

New message is not added to messages collection in conversation. For example Conversation returned by Sender::startConversation() has empty messages collection. It's fine if we redirect user to another page immediately after conversation, but if we want make some additional stuff it's not convenient.

I know that it may be quite easy change by extending base models, but maybe it is good idea to change default behaviour.

Integrate FOSMessage with / use within Drupal CMS

Drupal CMS uses many Symfony components now within Drupal 8, however it's use of Doctrine is limited to Annotations as far as I believe. It does not look like full Doctrine integration will be anytime soon, if ever. See: https://www.drupal.org/node/1817778

This library was highlighted to me in the Drupal.org issue queues for the Message Private module which I maintain. https://www.drupal.org/node/2613152#comment-10697278

When I upgrade Message Private to Drupal 8, which is ongoing, I will look to improve upon it. There is currently no Threading / Conversation ability, so if appropriate, this library could be a great solution.

A few initial questions / discussion items:

  • Determine if this library is appropriate (which it looks to be so far)
  • Find out what is involved and how much work it would be to create a Drupal driver
  • Create pull request here for Drupal driver to integrate directly with Message Private or preferrably with new Drupal FOSMessage bridge / API module (to be made available on drupal.org)

Perhaps you could help with answering the above. Some of this work would be a while away on my side, but just to start conversation now will help later on. Thanks.

error when run composer install

i'm trying to use the FOSMessage with symfony , i've download it and configure it however when trying to run composer install i got this error
[InvalidArgumentException] Bundle "fos_message" does not exist or it is not enabled.
i know it is not a bundle yet so do i neet to enable in the symfony appkernel.php ? or what .

Can't extend sender object

I wanted to extend the sender object to overwrite existing methods to match with our business specs.But I can't do, because lots of methods and properties are private. can you please change it to protected so it is easier to overwrite.

I can re-write that to have same effect, but it was best that if it can be avoided.

not yet implemented error "search message"

Hello im a beginner in Symfony 2.8
i installed the FOSMessagebundle i followed the basics all goes great only when i go to search twig
i got a message "not yet implemented "
im i missing anything ?
image

thank you ! :)

Why isn't there a default order on messages ?

Hello @tgalopin !

image

As you can see above if I display the messages like this:

//Controller
$conversations = $this->get('fos_message.repository')->getPersonConversations($this->getUser());

// Template
{% for message in conversation.messages %}
    {{ message.id }} :
    {{ message.body|truncate }}
    <br>
{% endfor %}

So the conversation.messages.last returns a complete random message from the conversation. Did I miss something out ?

The entity src/Driver/Doctrine/ORM/Entity/Conversation.php should sort messages by date or at least by id.

How do you plan to use the library?

Hello everyone,

I know most of the use cases of this library will be quite classical: conversation between users. However, some of you may have ideas of what they need that we didn't think of.

Please don't hesitate to propose ideas about this library, about how you would like it to work.

Would love to help

Hey I would love to help with this project.

I actually rewrote the fos messagebundle once
https://github.com/Miliooo/MilioooMessageBundle
It actually works but I wrote that code two years ago and I hate most of the code.

Since messaging is a huge part of my project, I started to refactor the code
https://github.com/Miliooo/MilioMessage

It starts with a command:
https://github.com/Miliooo/MilioMessage/blob/master/src/Commands/CreateThread.php
This gets handled by a handler:
https://github.com/Miliooo/MilioMessage/blob/master/src/Handler/CreateThreadCommandHandler.php
Which then creates a thread model:
https://github.com/Miliooo/MilioMessage/blob/master/src/Model/Thread.php

Configuration option to disable "Conversation Subject"

From playing around with the demo I noticed "Conversation Subject". In the cases where someone might want to reproduce a system like the Facebook Messenger; i.e. - no conversation subject, is it possible to bundle messages by recipient rather than Conversation Subject?

i.e. - Is it possible to easily remove Conversation Subject and have Conversations based on receipients without changing so much code?

Email instead of ID and long-term tracking?

Hello,

I saw that the project had been resumed, but little improvement for the moment due to a lack of time no doubt.

So I wanted to know if the project would continue and be compatible with symfony3?

I noticed a small error logic, to write a message to another user, inspecting the input we see the email address of the user instead of his ID, which seems strange to me since we can aspire All the e-mail addresses of a site thanks to this system ...

Thanks for the job done!

library migration

hello ,
i've been use this library for testing but i think the documentation and the library still in development as mentioned , so can i easily migrate to this library "FOSMessageBundle" specially i'm using symfony actually i was confused about the difference between them .

How to override template?

Hello,
I have installed and using the fosusr_message bundle for my projet. The view looks like a raw white page content. I want to to a bootstrapping on those page.

Is there any possibilities to override the views?

capture

What is the mission of this library ?

While we probably all agree that this library aims to provide user-to-user messaging features, I'm not sure we all have the same idea of what we should really do.

I discussed quite a lot with @ChristianRiesen about this and we worked on an easy to use API for the library. I want to explain here what is our current idea so it can be discussed and adapted to your needs.

1. We don't base the work on the current bundle

We chose to not base our work on the bundle. We didn't want to be restricted in our ideas by the bundle concepts. So even if some ideas will be the same, please keep in mind we want to create a library from scratch.

2. The library and framework implementations

  • FOSMessage is conversation-based and supports multiple participants per conversation.
  • FOSMessage is divided in two parts: the library and its implementation in frameworks (bundle, module, etc.).
  • The library is very simple: it's nothing more than a coherent data structure. We don't provide validation, UI, forms, etc. The developer will use the library as a way to persist and fetch messages in an elegant way.
  • The framework implementation of the library (bundle, module, etc.) may implement more things to help the development.
  • The library won't implement any "inbox/sentbox" system as it's quite complex to define what a sent message is. The framework implementation may implement it in the context of the UI.
  • The library is independant from any framework, any persistance system and any user system.

3. Implementation details

  • The library provides two main components:
    • The Repository to fetch conversations / messages
    • The Sender to start conversations / send messages
  • The library provides other components (for the moment only one) that can be used but are optionnal (they will have a seperated documentation page):
    • The Tagger to tag conversations
  • The library provides a few models: Conversation, Message, PersonInterface (interface for User model), ConversationPerson linking conversations and persons and MessagePerson linking messages and persons ;
  • A TagInterface let the developer implement a tagging system ;
  • Drivers let the developpers choose what persistance system they want to use (we decided in #1 to limit the persistance systems to Doctrine ORM and Mongo ODM)
  • An event dispatcher is available (either a native one to use the library alone or various bridges with famous event dispatchers, for the moment, only Symfony: https://github.com/tgalopin/message/tree/master/src/EventDispatcher)

4. Usage ideas

Here is how we would like to interact with the library, as a developer: https://gist.github.com/tgalopin/33641d43f200e8010c2a

You can note that there is neither any concept of inbox/outbot nor validation or UI. The library as we plan it is a smart but simple data strcture, and nothing more.

I worked a bit on an implementation of what we had in mind with Christian (https://github.com/tgalopin/message) so the code can help you see how the library would work from our perspective.

I am very interested by your opinions about this plan: what do you think the library should be? What was your idea when you thought of a framework-agnostic messaging library? Does this plan fit your needs?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.