- kune-commits - lists.ourproject.org

[Kune - Feature #302] chat history
by Redmine Communes 15 Jun '12

15 Jun '12

Issue #302 has been updated by Stanislav German-Evtushenko. test ---------------------------------------- Feature #302: chat history http://redmine.ourproject.org/issues/302#change-315 * Author: Stanislav German-Evtushenko * Status: New * Priority: Normal * Assignee: * Category: Chat * Target version: * Resolution: ---------------------------------------- With chat history kune.cc would be great xmpp-replacement for gtalk. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://redmine.ourproject.org/my/account

1 0

[kune issues] #284: Add time in errors
by kune issues 04 Jun '12

04 Jun '12

#284: Add time in errors --------------------+------------------- Reporter: samer | Owner: vjrj Type: defect | Status: new Priority: major | Milestone: Component: Others | Version: Keywords: | Blocked By: Blocking: | --------------------+------------------- When we go to More=>"Errors info" we see a sequence of actions and sometimes errors. When we are trying to locate errors, this sequence is very confusing, as there is no indicator to check if that error appeared an hour ago or it just happened now, when I was trying X... Possible quick fix: add the time of the error message. Even if it's without the date, it'd help a lot. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/284> kune issues <http://kune.ourproject.org/issues/>

1 0

[kune issues] #283: Create custom "More" menu in Kune
by kune issues 04 Jun '12

04 Jun '12

#283: Create custom "More" menu in Kune --------------------+------------------- Reporter: samer | Owner: vjrj Type: defect | Status: new Priority: major | Milestone: Component: Others | Version: Keywords: | Blocked By: Blocking: | --------------------+------------------- Each deployment of Kune should have a customized "More" menu in Kune. For example, in http://kune.cc there should be a link to the Donate page. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/283> kune issues <http://kune.ourproject.org/issues/>

1 0

[kune issues] #282: The unread notification in the header does not get updated automatically sometimes
by kune issues 03 Jun '12

03 Jun '12

#282: The unread notification in the header does not get updated automatically sometimes -------------------------+------------------ Reporter: vjrj | Owner: vjrj Type: defect | Status: new Priority: minor | Milestone: Component: User space | Version: Resolution: | Keywords: Blocked By: | Blocking: -------------------------+------------------ #Gtannous says: The unread notification in the header does not get updated automatically, u need to reload the whole page to have it updated. I don't know if there's already a ticket open in that concern so i thought i could mention it here. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/282> kune issues <http://kune.ourproject.org/issues/>

1 0

Re: [kune-commits] [kune issues] #36: Better logging system in the client side
by kune issues 02 Jun '12

02 Jun '12

#36: Better logging system in the client side ---------------------+-------------------- Reporter: vjrj | Owner: vjrj Type: defect | Status: closed Priority: major | Milestone: Component: Common | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: ---------------------+-------------------- Changes (by vjrj): * status: new => closed * resolution: => fixed -- Ticket URL: <http://kune.ourproject.org/issues/ticket/36#comment:2> kune issues <http://kune.ourproject.org/issues/>

1 0

[kune issues] #281: Cannot load waves too frequently
by kune issues 02 Jun '12

02 Jun '12

#281: Cannot load waves too frequently -------------------------+------------------- Reporter: samer | Owner: vjrj Type: defect | Status: new Priority: major | Milestone: Component: WIAB Server | Version: Keywords: | Blocked By: Blocking: | -------------------------+------------------- Ticket from Stas, video attached. FF 12 in Linux. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/281> kune issues <http://kune.ourproject.org/issues/>

1 1

[kune issues] #274: Make different size versions of avatars
by kune issues 01 Jun '12

01 Jun '12

#274: Make different size versions of avatars --------------------------+------------------ Reporter: vjrj | Owner: vjrj Type: enhancement | Status: new Priority: minor | Milestone: Component: Common | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Relevant info (in Spanish): http://kune.cc/?locale=es#kune.cc/w+1fb57lfqj015wS A example of the problem: http://cl.ly/0m3b0Z161L2E0l3v3b37 -- Ticket URL: <http://kune.ourproject.org/issues/ticket/274> kune issues <http://kune.ourproject.org/issues/>

1 1

[kune issues] #265: Avatar Digests flickering in Kune
by kune issues 01 Jun '12

01 Jun '12

#265: Avatar Digests flickering in Kune -------------------------+------------------ Reporter: vjrj | Owner: vjrj Type: defect | Status: new Priority: minor | Milestone: Component: User space | Version: Resolution: | Keywords: Blocked By: | Blocking: -------------------------+------------------ Coment by Yuri: Hello. I tried the Kune service and really enjoyed it. Especially I like the ability to switch to "Wave" mode by clicking on the "user space" icon. However, it seems like every time I press a key it causes the digests flickering. The issue also happens in WIAB but IMO to a lot less extent. From looking at the network it seems like every key press causes a new request to http://kune.cc/ws/servlets/EntityLogoDownloadManager?token=senrof21&onlyuse… So I guess you are using your own ProfilesManager implementation on the client. And maybe your own servlet. You might check that the servlet doesn't disable cache and that the client PoriflesManager implementation caches the image URL. If this doesn't help, you can try to change the code in DigestProxy so it will not use WaveBasedDigest author |Edit|Reply|Delete|Link 21 abr 19:16 Vega113 // Switch to a live digest if the wave is open. WaveContext wave = waveStore.getOpenWaves().get(waveId); if (wave != null) { proxy.activate(wave); } which probably tries to update the snippet whenever the document content changes and causes total rerendering of the digests. A better solution would be to update just the snippet in the active digest and only in case it is required. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/265> kune issues <http://kune.ourproject.org/issues/>

1 2

[kune issues] #280: Group long name change, seems update the project with the short name
by kune issues 01 Jun '12

01 Jun '12

#280: Group long name change, seems update the project with the short name --------------------------+------------------ Reporter: vjrj | Owner: vjrj Type: defect | Status: new Priority: minor | Milestone: Component: Group space | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Also the logo is not updated -- Ticket URL: <http://kune.ourproject.org/issues/ticket/280> kune issues <http://kune.ourproject.org/issues/>

1 1

[kune issues] #276: Long text in "copy-paste" is lost
by kune issues 01 Jun '12

01 Jun '12

#276: Long text in "copy-paste" is lost -------------------------+------------------- Reporter: samer | Owner: vjrj Type: defect | Status: new Priority: major | Milestone: Component: WIAB Server | Version: Keywords: | Blocked By: Blocking: | -------------------------+------------------- Scenario: * I create a new wave * Copy a large amount of text that I want to comment in a wave (lets say, a Wikipedia article) * Paste it in a wave * Wave shows "Connecting..." for a few seconds. * I can see the text pasted and work with it. However, when I leave the wave, the wave appears empty, without any change or text. It seems as if when pasting "too much", everything is lost. It's pretty dramatic, as copy-pasting is a common action. Also, it seems this happens with "medium size" pieces of text, not only with very large ones. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/276> kune issues <http://kune.ourproject.org/issues/>

1 3