- kune-devel - lists.ourproject.org

Re: [kune-devel] [kune issues] #114: Explain properly the tools
by kune issues 02 Nov '11

02 Nov '11

#114: Explain properly the tools --------------------------+------------------ Reporter: samer@… | Owner: vjrj Type: enhancement | Status: new Priority: major | Milestone: Component: Group space | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Comment (by vjrj): If anybody want to help with the description of the tools, you can edit this public wave: https://wave.google.com/wave/waveref/googlewave.com/w+266QsbkSA/~/conv+root… -- Ticket URL: <http://kune.ourproject.org/issues/ticket/114#comment:3> kune issues <http://kune.ourproject.org/issues/>

1 0

Re: [kune-devel] [kune issues] #120: Close new inbox wave
by kune issues 02 Nov '11

02 Nov '11

#120: Close new inbox wave -------------------------+-------------------- Reporter: anonymous | Owner: vjrj Type: defect | Status: closed Priority: major | Milestone: Component: User space | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: -------------------------+-------------------- Changes (by vjrj): * status: new => closed * resolution: => fixed Comment: Sorry, I'm closing this because the lack of info. To close your inbox, just sign-out (as in gmail). -- Ticket URL: <http://kune.ourproject.org/issues/ticket/120#comment:2> kune issues <http://kune.ourproject.org/issues/>

1 0

[kune issues] #146: General Home page should now be # instead of #home
by kune issues 02 Nov '11

02 Nov '11

#146: General Home page should now be # instead of #home --------------------------+------------------ Reporter: vjrj | Owner: vjrj Type: enhancement | Status: new Priority: minor | Milestone: Component: Home space | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Now that home of Kune have stats and more info, its better, IMHO, to be the home page when you don't have other url than, for instance, http://kune.beta.iepala.es/ -- Ticket URL: <http://kune.ourproject.org/issues/ticket/146> kune issues <http://kune.ourproject.org/issues/>

1 2

Fwd: Walkaround -- Wave on App Engine
by Vicente J. Ruiz Jurado 26 Oct '11

26 Oct '11

Interesting... (someone from Google make WIAB to work in AppEngine)... -------- Mensaje original -------- Asunto: Walkaround -- Wave on App Engine Fecha: Wed, 26 Oct 2011 12:55:52 -0700 De: Christian Ohler <ohler(a)google.com> Responder a: wave-dev(a)incubator.apache.org Para: wave-dev(a)incubator.apache.org Fellow wavers, rather than making waves accessible in Google Docs, which takes too long, we are releasing our code in a form that will hopefully be useful in the short term. You can find it at https://code.google.com/p/walkaround/ . >From the project description: Walkaround is a variant of Wave, based on the Apache Wave code base, that runs on App Engine. Walkaround can import waves from wave.google.com to allow users to keep working with their data regardless of the future of wave.google.com. (The import feature is still experimental.) Much of the walkaround code is not specific to Wave, but factored out as a separate, more general collaboration layer that manages shared live objects. These objects can be modified by multiple clients at the same time, with changes made by any client immediately broadcast to all others. The Wave application is built on top of this, but the live collaboration layer is flexible enough to support other applications. Walkaround supports live concurrent rich-text editing, in-line replies, user avatars, wave gadgets, attachments, and we are working on integrating App Engine's full text search service. For now, it does not support Wave robots, federation, or private replies, but these features could be added. --- Some of you have been asking about Wave on App Engine; perhaps this is what you are looking for. The Wave application in walkaround depends very heavily on the Apache Wave code base, but the general collaboration layer is useful independently, so we put it into a separate repository for now. Happy hacking, Christian. -- Vicente J. Ruiz Jurado http://comunes.org http://ourproject.org http://homes.ourproject.org/~vjrj/blog "Nadie está más esclavizado que esos que erróneamente creen ser libres" [Goethe]

1 0

Manuales GWT
by jp zafra 26 Oct '11

26 Oct '11

Buenas! Últimamente, por motivos de trabajo, he estado probando varios frameworks me he escontrado este Vaadin http://en.wikipedia.org/wiki/Vaadin , habéis trabajado con él? lo conocéis? Por otra parte me encontré este manual de GWT http://casidiablo.net/tutorial-de-introduccion-al-google-web-toolkit/ creo que está bastante bien como alternativa al oficial, os lo paso por si a alguien le resulta de utilidad. Un saludo. -- Juan Pablo Zafra Delgado http://jpzafra.wordpress.com (+34) 651 802464 skype: jp_zafra twitter/identi.ca: @jpzafra PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xFBEE4CC2FA0328C1

2 1

[kune issues] #141: Kune client is always "connecting" in chrome/chromium
by kune issues 26 Oct '11

26 Oct '11

#141: Kune client is always "connecting" in chrome/chromium --------------------------+------------------ Reporter: vjrj | Owner: vjrj Type: defect | Status: new Priority: major | Milestone: Component: WIAB Server | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Seems that it's a problem with chrome and socket.io: https://github.com/LearnBoost/socket.io-client/issues/282 https://github.com/LearnBoost/socket.io/issues/429 "Known issue, it's because Chrome started using a different WebSocket specification that Socket.IO is not yet supporting.. @guille is working on it" Then I think that socketio-java should be updated to use socketio 0.8. Workaround: To use old versions of chromium (for instance v12) meanwhile. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/141> kune issues <http://kune.ourproject.org/issues/>

1 1

Versión con UiBinder de Donate
by Esteban Carreras Genis 23 Oct '11

23 Oct '11

Buenas, he commiteado la primera versión de donate con UiBinder No tengo claro si es correcto todo, seguro que se puede reducir el código más, pero yo no he sido capaz. Lo seguiré intentando. Por cierto, alguien se ha fijado de que el widget del kune-intro no se ve bien en IE, creo que es un tema de estilos. Si queréis puedo echarle un ojo. Me quedo a la espera de los comentarios de Vicente. Un saludo, -- Esteban Carreras Genis

2 14

[kune issues] #142: UTF-8 enconding problems using firefox
by kune issues 20 Oct '11

20 Oct '11

#142: UTF-8 enconding problems using firefox -------------------------+------------------ Reporter: vjrj | Owner: vjrj Type: defect | Status: new Priority: major | Milestone: Component: User space | Version: Resolution: | Keywords: Blocked By: | Blocking: -------------------------+------------------ How to reproduce: Create a wave, write something like ññççç open another wave, reopen that wave and you will get something like �� Know issue: https://issues.apache.org/jira/browse/WAVE-187 -- Ticket URL: <http://kune.ourproject.org/issues/ticket/142> kune issues <http://kune.ourproject.org/issues/>

1 1

[kune issues] #128: Remove /ws/ prefix in kune URL
by kune issues 20 Oct '11

20 Oct '11

#128: Remove /ws/ prefix in kune URL --------------------------+------------------ Reporter: vjrj | Owner: vjrj Type: enhancement | Status: new Priority: minor | Milestone: Component: Common | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ -- Ticket URL: <http://kune.ourproject.org/issues/ticket/128> kune issues <http://kune.ourproject.org/issues/>

1 1

[kune issues] #145: Wave websocket still connected after user sign-out
by kune issues 20 Oct '11

20 Oct '11

#145: Wave websocket still connected after user sign-out -------------------------+------------------ Reporter: vjrj | Owner: vjrj Type: defect | Status: new Priority: minor | Milestone: Component: User space | Version: Resolution: | Keywords: Blocked By: | Blocking: -------------------------+------------------ -- Ticket URL: <http://kune.ourproject.org/issues/ticket/145> kune issues <http://kune.ourproject.org/issues/>

1 0