Hi,
When a new chat room view is opened it is usually populated with a list of existing/old messages loaded from the server. A preferred behavior might be to scroll the view to the last message or better yet to the first unread message on the list.
What would be the best way to scroll the chat room view to the last message or a specific message after the view is created?

Hello :)

On initializing the project various dependencies and plugins could not be resolved by maven.
Has someone fixed this ?

`
Cannot resolve com.codenameone:codenameone-core:7.0.16-SNAPSHOT
Cannot resolve com.codenameone:chat-ui-kit-lib:1.0.1-SNAPSHOT
Cannot resolve com.codenameone:codenameone-javase:7.0.16-SNAPSHOT
Cannot resolve plugin org.apache.maven.plugins:maven-source-plugin:
Cannot resolve plugin org.apache.maven.plugins:maven-source-plugin:
Cannot resolve plugin com.codenameone:codenameone-maven-plugin:7.0.16-SNAPSHOT
Cannot resolve plugin org.codehaus.mojo:build-helper-maven-plugin:
Cannot resolve plugin org.apache.maven.plugins:maven-source-plugin:
Cannot resolve plugin com.codenameone:codenameone-maven-plugin:7.0.16-SNAPSHOT
Cannot resolve plugin org.apache.maven.plugins:maven-source-plugin:
Cannot resolve plugin com.codenameone:codenameone-maven-plugin:7.0.16-SNAPSHOT
Cannot resolve plugin org.apache.maven.plugins:maven-source-plugin:
Cannot resolve plugin org.apache.maven.plugins:maven-source-plugin:
Cannot resolve plugin org.apache.maven.plugins:maven-source-plugin:
Cannot resolve plugin org.apache.maven.plugins:maven-source-plugin:
Cannot resolve plugin org.apache.maven.plugins:maven-source-plugin:
Cannot resolve plugin org.apache.maven.plugins:maven-source-plugin:
Cannot resolve plugin org.apache.maven.plugins:maven-source-plugin:

`

Best regards

Joost

I would like to have a ChatMessage entity to have property sender. Sender is a 'Contact' entity with own definition:

class Contact(n: String, a: String) : Entity() {
    var name: StringProperty?
    var avatar: StringProperty?
    private val TYPE: EntityType = object : EntityType() {
        init {
            name = string(tags(Thing.name))
            avatar = string(tags(Thing.thumbnailUrl))
        }
    }
    init {
        entityType = TYPE
        set(name, n)
        set(avatar, a)
    }
}

Now, I would like to have a ChatMessage entity defined like this:

class ChatMessage(m: String, s: Contact) : Entity() {
    var sender: EntityProperty<Contact>
    var content: StringProperty?

    private val TYPE: EntityType = object : EntityType() {
        init {
            content = string(tags(ChatMessage.text))
            sender = entity(tags(ChatMessage.creator)) // <--- This is the place I do not understand 
         // how to specify the entity type
        }
    }

    init {
        entityType = TYPE
        set(content, m)
        set(sender, s)
    }
}

How to specify entity type of complex entities?

Trying your demo Android apk on my Android 7 device, the app is completely frozen for some seconds to load a photo.

My hypothesis is that your code resizes the photo and it needs some seconds, blocking the EDT.

Executing your RADChatRoom code downloaded from Github, I get an exception trying to enter the text "Hello World"...

Please note in the screenshot below the text "MultiButton", appeared after entering "Hello World".

Full log:

ant -f /home/francesco/Teamify/ChatRAD -Dnb.internal.action.name=run run
Generating GUI sources
No GUI Entries available
init:
Deleting: /home/francesco/Teamify/ChatRAD/build/built-jar.properties
deps-jar:
Updating property file: /home/francesco/Teamify/ChatRAD/build/built-jar.properties
JavaFX is loaded
Retina Scale: 1.0
Updating merge file /home/francesco/Teamify/ChatRAD/css/theme.css.merged
Input: /home/francesco/Teamify/ChatRAD/css/theme.css
Output: /home/francesco/Teamify/ChatRAD/src/theme.res
Acquiring lock on CSS checksums file /home/francesco/Teamify/ChatRAD/.cn1_css_checksums...
Lock obtained
File has not changed since last compile.
Releasing lock
CSS file successfully compiled.  /home/francesco/Teamify/ChatRAD/src/theme.res
Compile is forcing compliance to the supported API's/features for maximum device compatibility. This allows smaller
        code size and wider device support
compile:
run:
JavaFX is loaded
Found theme.css file.  Watching for changes...
CSS> JavaFX is loaded
CSS> Retina Scale: 1.0
CSS> Updating merge file /home/francesco/Teamify/ChatRAD/css/theme.css.merged
CSS> Input: /home/francesco/Teamify/ChatRAD/css/theme.css
CSS> Output: /home/francesco/Teamify/ChatRAD/src/theme.res
CSS> Acquiring lock on CSS checksums file /home/francesco/Teamify/ChatRAD/.cn1_css_checksums...
CSS> Lock obtained
CSS> File has not changed since last compile.
CSS> Releasing lock
CSS> CSS file successfully compiled.  /home/francesco/Teamify/ChatRAD/src/theme.res
Retina Scale: 1.0
[EDT] 0:0:9,507 - Codename One revisions: 7dd4e7d08b3442d90959477ee52a5ae8c4361b29

java.lang.IllegalArgumentException: Entity type net.informaticalibera.test.chatrad.ChatMessageModel$1@6e07c9d1 does not contain property com.codename1.rad.models.DateProperty@54a32e09
[EDT] 0:0:9,508 - Exception: java.lang.IllegalArgumentException - Entity type net.informaticalibera.test.chatrad.ChatMessageModel$1@6e07c9d1 does not contain property com.codename1.rad.models.DateProperty@54a32e09
	at com.codename1.rad.models.Entity.get(Entity.java:440)
	at com.codename1.rad.ui.chatroom.ChatBubbleView$ChatBubbleListCellRenderer.getListCellRendererComponent(ChatBubbleView.java:591)
	at com.codename1.rad.ui.entityviews.EntityListView.lambda$new$1(EntityListView.java:78)
	at com.codename1.ui.util.EventDispatcher.fireActionEvent(EventDispatcher.java:349)
	at com.codename1.rad.models.EntityList.fireEntityAdded(EntityList.java:151)
	at com.codename1.rad.models.EntityList.add(EntityList.java:106)
	at com.codename1.rad.ui.chatroom.ChatRoomView$ViewModel.addMessages(ChatRoomView.java:462)
	at net.informaticalibera.test.chatrad.ChatFormController.lambda$new$4(ChatFormController.java:114)
	at com.codename1.rad.controllers.Controller.lambda$addActionListener$0(Controller.java:131)
	at com.codename1.ui.util.EventDispatcher.fireActionSync(EventDispatcher.java:459)
	at com.codename1.ui.util.EventDispatcher.fireActionEvent(EventDispatcher.java:362)
	at com.codename1.rad.controllers.Controller.dispatchEvent(Controller.java:154)
	at com.codename1.rad.controllers.ActionSupport.dispatchEvent(ActionSupport.java:79)
	at com.codename1.rad.nodes.ActionNode.fireEvent(ActionNode.java:438)
	at com.codename1.rad.nodes.ActionNode.fireEvent(ActionNode.java:411)
	at com.codename1.rad.ui.DefaultActionViewFactory.lambda$initUI$0(DefaultActionViewFactory.java:216)
	at com.codename1.ui.util.EventDispatcher.fireActionEvent(EventDispatcher.java:349)
	at com.codename1.ui.Button.fireActionEvent(Button.java:679)
	at com.codename1.ui.Button.released(Button.java:720)
	at com.codename1.ui.Button.pointerReleased(Button.java:827)
	at com.codename1.ui.LeadUtil.pointerReleased(LeadUtil.java:153)
	at com.codename1.ui.Form.pointerReleased(Form.java:3677)
	at com.codename1.ui.Component.pointerReleased(Component.java:4729)
	at com.codename1.ui.Display.handleEvent(Display.java:2324)
	at com.codename1.ui.Display.edtLoopImpl(Display.java:1216)
	at com.codename1.ui.Display.mainEDTLoop(Display.java:1134)
	at com.codename1.ui.RunnableWrapper.run(RunnableWrapper.java:120)
	at com.codename1.impl.CodenameOneThread.run(CodenameOneThread.java:176)
Found theme.css file.  Watching for changes...
BUILD SUCCESSFUL (total time: 50 seconds)

Screenshot:

I'm completely new to your CodeRAD library and RADChatRoom. I just discovered them by accident, noticing your last commit.

Have you wrote something the Codename One blog? Maybe I missed the news.

Hi,
I am going through the tutorial and I am at step 6. So, very simple code, just the beginning. The app compiles but I am getting the error at runtime:

java.lang.IllegalArgumentException: Component is already contained in Container: Container[x=0 y=0 width=0 height=0 name=null, layout = BoxLayout, scrollableX = false, scrollableY = false, components = [TextAreaPropertyView]]
	at com.codename1.ui.Container.insertComponentAtImpl(Container.java:927)
	at com.codename1.ui.Container.insertComponentAt(Container.java:918)
	at com.codename1.ui.Container.addComponent(Container.java:840)
	at com.codename1.ui.Container.encloseIn(Container.java:250)
	at com.codename1.ui.layouts.BoxLayout.encloseYCenter(BoxLayout.java:447)
	at com.codename1.rad.ui.chatroom.ChatRoomView.<init>(ChatRoomView.java:281)
	at com.codename1.rad.ui.chatroom.ChatRoomView.<init>(ChatRoomView.java:112)
	at com.example.controller.ChatFormController.<init>(ChatFormController.kt:16)

Do you have any suggestions on what can be wrong? My code is the exact copy of the code from examples in the tutorial.

Currently the swipe on the right to see time details can be nice, but in some circumstances it's better disabled. For example, I have to develop an app in which the swipe will be used to change the Form: in this case, the swipe of the RADChatRoom and the swipe that I'll add to change the Form will conflict.

I am following the tutorial and I am at the "Adding Phone and Video Conferencing" part. I used the code:

ViewNode viewNode = new ViewNode(
    actions(ChatRoomView.SEND_ACTION, send),
    actions(ProfileAvatarView.PROFILE_AVATAR_CLICKED_MENU, phone, videoConference) 
);

To add context menu for phone calls and videoconferencing. According to tutorial this should enable menu when clicked on title or on buble avatar. However, for me the menu only shows when I click on bubble avatar. Nothing happens when I click on title.

There seems to be mistake in the code. Both variables used for calculation have always the same value as they are assigned from prevDate.

https://github.com/shannah/RADChatRoom/blob/d4eaad7b1f1b47698abeafda616d6679263ee6b0/src/com/codename1/rad/ui/chatroom/ChatBubbleView.java#L594

I wonder if it would be possible to change the implementation to have the bubble entire look defined in CSS?
I worked on a similar app in JavaFX and it was possible to define shape of the background label with round corners, all the colors, gradients, etc.... I am not sure if it is possible with Codename One, but it could be really useful.

Hi,
I tried to reimplement the update method to put a custom content in the chat message, customize the chat bubble view and other things.
I am mostly interested in reimplementing the part within "if(changed) {...}" part, hoping to leave the rest of the code unchanged/copied.
However, the update() method uses lots of private fields and methods and most of the code in the class is private. This makes it nearly impossible to extended and customize some parts only.

I would suggest to change the access modifier to protected for most of the class members and/or split the update() method into smaller piece of code located in separate methods. This would allow for easier extensibility and flexibility in the future.

I am still pretty early in the tutorial at adding send button.

The input line seems te not updated when I type text in there. I mean, I type a few letters 'abc' and nothing shows in the input line. Then I mouse-click on the any place inside the app and the input line shows the text I typed in. The same when I remove the text, etc...
So, the input seems like not being updated in letters typed.

Is there something I need to do in order to have the input show text typed right away?

I had some suggestions in issues: #4 #5 However, the more I dig into the code the more different ideas I have. It seems the best solution would be to provide an API to create some sort of a factory to draw a buble and include all the information in the chat message that is needed.

Of course, I can write my own version of ChatBubbleView but it would be a waste of a very good piece of code which for the most part is perfectly fine. I suppose you plan to further work on it so more stuff would be coming in the future.

So, ways to inject customizations would be the best approach.

Right now, the user avatar and nickname is displayed only for "other" users. It would be useful to allow to display avatar and user nickname for own messages well. This would provide more consistent UI plus it does look nice.

I agree that it may not make much practical sense. People mostly know their own name and how they look, unless their mirror is broken for a long time. Still an app looks and feels better of the UI is consistent in all places.

Therefore, some kind of an option to allow to display these elements would be nice.

It works on desktop but on mobile you have to press the send button. As now physical keyboard is pretty common for tablets, it would be useful to have an option to enable send on ENTER for mobile devices as well.

Hi,
Is there any way to customize the look of the app, bubble colors and other elements through CSS?

I am wondering why there is no message content tag added to ChatMessage schema. The schema for Message on https://schema.org/Message has 'text' property which is supposed to keep the content of the message.
Is this something missing from the ChatMessage?

I am following tutorial and I am now at "Adding phone and video conferencing". In the code example from the tutorial we have:

addActionListener(phone, evt->{
    evt.consume();
    if (!CN.canDial()) {
        Dialog.show("Not supported", "Phone calls not supported on this device", "OK", null);
        return;
    }
    if (evt.getEntity().isEmpty(Person.telephone)) {
        Dialog.show("No Phone", "This user has no phone number", "OK", null);
        return;
    }

    String phoneNumber = evt.getEntity().getText(Person.telephone);
    CN.dial(phoneNumber);

});

However, the "evt.getEntity().getText(Person.telephone)" is always null. In fact all other properties like "evt.getEntity().getText(Thing.name)" is null as well.
It seems like the "evt" event does not have the property field filled at all.

Hi,
When on desktop and message is sent with ENTER it all works as expected. However, on mobile when a message is sent using "SEND" button, the input field does not regains focus after message is sent.
This leads to bad user experience as a user has to press "send" and then, again press on the input line to continue typing a message.

Correct behavior seems to make the focus return to the input field after message is sent.