date:20120307

I'm pleased to announce the creation of a new Open Source project called
stillcollab-surface : http://code.google.com/p/stillcollab-surface/

Surface is a wysiwyg editing surface that doesn't rely on browser's
execCommand and queryCommandState commands.

Because of using these commands leads to output differences, this is not a
good behavior for products that need to compute produced HTML elsewhere
than in a browser.

Furthermore, table, list, paragraph, etc. manipulation can differ from a
browser to another one, so this wysiwyg try to handle these differences to
provide the same look and feel for every browser.

To finish, this editor is, as possible as it could be, developed in
Java/GWT, so it can be easily embedded in every GWT application, debugged
and improved.

This project is very young (about 1 month), and I hope to have a lot of
feedback in order to handle every bugs for every browsers. Furthermore, a
lot of basics functionalities are not implemented (subscript, superscript,
etc.) but this project is designed to allow everyone to easily add customs
inserters etc. So I hope there will be some contributions around these
functionnalities ;).
To finish, there is, at this time, absolutely no design for buttons,
controls etc. If someone can provide a good look and feel, I will gladly
use it.

Thank you.

-- 
Damien Picard
Axeiya Services : http://axeiya.com/
stillcollab-surface : http://code.google.com/p/stillcollab-surface/
Mon livre sur GWT : http://axeiya.com/index.php/ouvrage-gwt.html

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Embedding custom components with custom components


On Wednesday, March 7, 2012 2:50:54 AM UTC+1, bryn ryans wrote:


 Tried that but what I felt that if I am to do that it should do the same 
 as complex panel. Unfortunately it can't as ComplexPanel calls method 
 orphan which calls package protected methods on Widget. As my classes do 
 not reside in the same package Widget I cannot call that method (I would 
 rather not hack the package name or do some magic with JSNI to achieve 
 this). 

 I have my own mechanism which allows me to sink events in my embedded 
 components and its working well. What I am trying to find out is if GWT 
 2.5. (or future release) will support embedding of uibinder components 
 within other uibinder components? Be great if there is a plan as I can get 
 rid of my own mechanism.


There's no such thing as a UiBinder component, there are widgets (or 
UiObjects, or whatever actually) that internally make use of UiBinder, and 
there are widgets that can contain other widgets (either by implementing 
HasWidgets or using @UiChild methods).

I don't know what you're trying to do but there must be a simpler way of 
doing it.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/BXbWJvNdhpcJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: IsRenderable

2012-03-07 Thread Jens

Take a look at the new commits in the SVN. Nothing about IsRenderable ;-)

Its more likely that GWT 2.5 will contain all or some of:
- further JavaScript optimizations by using the closure compiler during GWT
compilation
- new code splitter algorithm to minimize the size of the initial and left
over fragment
- SourceMap support
- Faster Dev mode
- Java7 support (Java6 EOL is November 2012)

-- J.

Am Mittwoch, 7. März 2012 09:15:30 UTC+1 schrieb Chris Price:

Eric Clayberg recently mentioned that there was an arc of work
on-going by the GWT team that wasn't being released to the external
repo. I was wondering if this arc of work has anything to do with
IsRenderable? It looks like it was actively developed for about 3
months 6 months ago but there hasn't been any activity since [1].

If I have the right idea about it, i.e. that It is a stepping stone
towards a Closure-Library style decorate pattern (i.e. server-render,
client-attach), it would seem on the surface to be a big performance
win. However, the comments about it being highly experimental put me
off trying it for client work. If there isn't any on-going development
with it, I'd be interested in knowing why it was abandoned, did it
turn out not to be a performance win, is it simply a lack of resources
or was there another reason?

Cheers,

Chris

[1]
http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/user/client/ui/IsRenderable.java

Am Mittwoch, 7. März 2012 09:15:30 UTC+1 schrieb Chris Price:

Cheers,

Chris

[1]
http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/user/client/ui/IsRenderable.java

--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/z-SOCh3PN4EJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: IsRenderable



On Wednesday, March 7, 2012 9:15:30 AM UTC+1, Chris Price wrote:

 Eric Clayberg recently mentioned that there was an arc of work
 on-going by the GWT team that wasn't being released to the external
 repo. I was wondering if this arc of work has anything to do with
 IsRenderable? It looks like it was actively developed for about 3
 months 6 months ago but there hasn't been any activity since [1].

 If I have the right idea about it, i.e. that It is a stepping stone
 towards a Closure-Library style decorate pattern (i.e. server-render,
 client-attach), it would seem on the surface to be a big performance
 win. However, the comments about it being highly experimental put me
 off trying it for client work. If there isn't any on-going development
 with it, I'd be interested in knowing why it was abandoned, did it
 turn out not to be a performance win, is it simply a lack of resources
 or was there another reason?

I don't think IsRenderable is abandoned. I'm not sure it's really about a 
Closure-Library-style decorate either, but from what I recall it could be 
used that way I guess.

AFAIK (and IIRC), IsRenderable is used in UiBinder to build a single huge 
HTML string from many widgets, to parse things in one go: i.e. ask 
IsRenderable widgets to render themselves and inline that string into the 
parent's HTMLPanel content, and then attach the IsRenderable widgets back 
to what they generated. This bypasses the placeholder elements that need 
to be generated and then replaced by the widgets (using HTMLPanel's 
addAndReplaceElement).
 

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/RmSwxxnn9xsJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: IsRenderable

2012-03-07 Thread Chris Price

Thanks, yea I had a look over them this morning when Alan said he'd
kicked the sync script. My reading of that thread was that the sync
scripts have started replicating the stuff that's meant for the
external repo but there might be more that's being worked on, i.e. -

The GWT team is currently focused on an arc of work that has not been
released to the external repo yet.

I can understand if that wasn't the implication, still interested in
why development on IsRenderable stopped though?

Cheers,

Chris

On Wed, Mar 7, 2012 at 11:18 AM, Jens jens.nehlme...@gmail.com wrote:
Take a look at the new commits in the SVN. Nothing about IsRenderable ;-)

-- J.

Am Mittwoch, 7. März 2012 09:15:30 UTC+1 schrieb Chris Price:

Cheers,

Chris

[1]
http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/user/client/ui/IsRenderable.java

Am Mittwoch, 7. März 2012 09:15:30 UTC+1 schrieb Chris Price:

Cheers,

Chris

[1]
http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/user/client/ui/IsRenderable.java

--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.

Using validation api

2012-03-07 Thread Adolfo Panizo Touzon

Hi all,

In my last projects I've used without any problems the validation api,
because I've been using the 2.4 gwt sdk version.

Now, I am working in a project that uses the 2.1 version. I've tried to
extract the validation classes (from the 2.4 version) and compile
them myself, but the project doesn't work.

Is it possible use the validation api in the 2.1 version of gwt?... how?

Any ideas?

Pd: I know there are other libraries of validation, but I need to use the
gwt validation api.

Regards,

Adolfo.
-- 
El precio es lo que pagas. El valor es lo que recibes.
Warren Buffet

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Stillcollab-surface : an Open Source wysiwyg editor written for and with GWT


On Wednesday, March 7, 2012 11:45:45 AM UTC+1, Damien Picard wrote:

 I'm pleased to announce the creation of a new Open Source project called 
 stillcollab-surface : http://code.google.com/p/stillcollab-surface/

 Surface is a wysiwyg editing surface that doesn't rely on browser's 
 execCommand and queryCommandState commands. 

 Because of using these commands leads to output differences, this is not a 
 good behavior for products that need to compute produced HTML elsewhere 
 than in a browser. 

 Furthermore, table, list, paragraph, etc. manipulation can differ from a 
 browser to another one, so this wysiwyg try to handle these differences to 
 provide the same look and feel for every browser.


Looks great but:

   - is there a live demo somewhere?
   - it looks like you're kind-of reinventing the wheel, as Apache Wave 
   already has that kind of editor. Wave's one is based on an XML-like 
   document whose schema is not (X)HTML; the added flexible obviously 
   translates into a more complex design but it works quite well (I've used it 
   in a project where we had to constrain the input –e.g. no image in a 
   title–, and handle semantic links, among other things; and FWIW, the Wave 
   editor powers the new Blogger comment form), and has already been heavily 
   tested on many browsers (at Google, before being donated to Apache; though 
   given its use in Blogger, it's highly probably that it's still heavily 
   tested at Google, and I guess they'd contribute back to Apache if/when they 
   fix things)

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/mZlUn62KEwgJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Stillcollab-surface : an Open Source wysiwyg editor written for and with GWT

Hi,

You can find a demo here : http://surface-sample.elasticbeanstalk.com/
Indeed, I'm reinventing the wheel. I did not known the Wave editor, I will
take a look at it, but I'm not sure that handling something else than HTML
is the right thing to do in my use case. There is some existing wysiwyg
editors that uses the same idea of creating inserters instead of using
execCommand (Aloha, as an example).
But there is always something missing to me :

- I need a GWT based wysiwyg (Wave editor, XWiki editor are candidates)
- I need to create specific inserters
- I need to control strictly the HTML output (because the HTML is
exported with XSLT processors in my use case)
- I need to process the HTML in-place, by DOM manipulation
- and some other things...

Firstly, I did not want to reinvent the wheel, but every existing wysiwyg
solution always lead me to embarrassing limitations in my use cases. But I
repeat, I've not tried Wave editor, and I will do it quickly ; I wish it
could be a solution for me.

Thank you for your feedback.

Le 7 mars 2012 12:53, Thomas Broyer t.bro...@gmail.com a écrit :

On Wednesday, March 7, 2012 11:45:45 AM UTC+1, Damien Picard wrote:

I'm pleased to announce the creation of a new Open Source project called
stillcollab-surface :
http://code.google.com/p/**stillcollab-surface/http://code.google.com/p/stillcollab-surface/

Surface is a wysiwyg editing surface that doesn't rely on browser's
execCommand and queryCommandState commands.

Because of using these commands leads to output differences, this is not
a good behavior for products that need to compute produced HTML elsewhere
than in a browser.

Furthermore, table, list, paragraph, etc. manipulation can differ from a
browser to another one, so this wysiwyg try to handle these differences to
provide the same look and feel for every browser.

Looks great but:

- is there a live demo somewhere?
- it looks like you're kind-of reinventing the wheel, as Apache Wave
already has that kind of editor. Wave's one is based on an XML-like
document whose schema is not (X)HTML; the added flexible obviously
translates into a more complex design but it works quite well (I've used it
in a project where we had to constrain the input –e.g. no image in a
title–, and handle semantic links, among other things; and FWIW, the Wave
editor powers the new Blogger comment form), and has already been heavily
tested on many browsers (at Google, before being donated to Apache; though
given its use in Blogger, it's highly probably that it's still heavily
tested at Google, and I guess they'd contribute back to Apache if/when they
fix things)

--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/mZlUn62KEwgJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.

--
Damien Picard
Axeiya Services : http://axeiya.com/
stillcollab-surface : http://code.google.com/p/stillcollab-surface/
Mon livre sur GWT : http://axeiya.com/index.php/ouvrage-gwt.html

Re: Stillcollab-surface : an Open Source wysiwyg editor written for and with GWT


On Wednesday, March 7, 2012 2:07:38 PM UTC+1, Damien Picard wrote:

 Hi,

 You can find a demo here : http://surface-sample.elasticbeanstalk.com/


Thanks.

It's indeed a very young project: you cannot apply style across paragraphs 
or other styles' boundaries (typical example: fobo bia/br b/iaz → 
fo*o b**ar b*az)
That's one of the hardest things to handle in an editor, and the very first 
thing I try out ;-)
 

 Indeed, I'm reinventing the wheel. I did not known the Wave editor, I will 
 take a look at it, but I'm not sure that handling something else than HTML 
 is the right thing to do in my use case. There is some existing wysiwyg 
 editors that uses the same idea of creating inserters instead of using 
 execCommand (Aloha, as an example).
 But there is always something missing to me :

- I need a GWT based wysiwyg (Wave editor, XWiki editor are candidates)
- I need to create specific inserters
- I need to control strictly the HTML output (because the HTML is 
exported with XSLT processors in my use case)

 Wave is based on documents that can easily be serialized as XML (that's 
what we use for persistence).
Because it has to to handle operational 
transformationhttp://www.waveprotocol.org/whitepapers/operational-transform, 
inline styling (bold, italic, links, etc.) and paragraphs are represented 
by markers. Styling is represented by annotations, so the markers are 
annotation boundaries, serialized in XML as processing instructions. 
Paragraph boundaries are representing by line/ elements (similar to br 
in HTML except a line/ marks the beginning of a paragraph, and can have a 
type and level: title, ordered list, unordered list). These are just 
the built-in representations though, you're free to implement whatever you 
want (it'd just require a bit more work).
The persistent document is first processed to build a local document 
(line/xxx is transformed to l:pxxx/l:p, annotations are transformed 
to l:s spans, etc.), then each element of this document is rendered into 
HTML. Each modification made on the document (either persistent or local) 
is passed to the renderer to update the view.
Have a look at http://www.waveprotocol.org/code/tutorials/writing-a-doodad
 and http://www.waveprotocol.org/wave-protocol-summit/wave-summit-talks 
(particularly 
“Wave model deep dive” by Alex North, and “Wave panel and rendering” and 
“Real-time editor  Doodads” by Dave Hearnden), and search for my mails on 
the Wave mailing lists, where people answered with many valuable 
information and links. Re. the code, start with the EditorHarness GWT app.

In our case, we chose to keep the paragraphs-via-line/ and 
styling-via-annotations (because it was easier), and added table rendering, 
links (handled as elements so we can easily make sure we don't nest them), 
semantic annotations (same as links), and illustrations (similar to an 
image, but links to an entity that carries both the image and legend, among 
many other things).
In some rich text areas, we're able to limit available features: some 
areas a single paragraph with only styling a semantic markup, others 
allow several paragraphs but no titles, etc.
Finally, by listening to document changes, we keep a document outline, 
index of semantic markup (as CellTree widgets), and lists of tables and 
illustrations (as CellList widgets) in real-time.

The only thing needing real work is the copy/paste handling, which in Wave 
is tightly bound to Wave's wavelet document schema. In our case, we 
simply shadowed the class to strip every formatting and paste as plain text.

Overall, the code is complex but very well thought out, so once you grasped 
the concepts, it reads fairly easily.


- I need to process the HTML in-place, by DOM manipulation


Not sure what you mean by that, but Wave uses DOM manipulations exclusively 
(see above).

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/NIFKhsOGvlUJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Uploading a file 1MB

2012-03-07 Thread learning coding

Hi all ,

I have to make webapplication using java,
I have to upload a file which is bigger then 1MB .
Actually i need the contentStream of the file and the value of the
textBox which is on the FormPanel ,on the myProject.server side .

The file can be of .txt and .doc type.

Somebody suggested me to use BolbStore.


My Code :

Code
  client
  // Get The URL
  public void onClick(ClickEvent event) {
  System.out.println(blob +blobServices);
blobServices
.getBlobStoreUploadUrl(callback) ;
  }
});

//
..Some more code

public void onSubmitComplete(SubmitCompleteEvent event) {

  Window.alert(event.getResults());
  }

});

The above RPC call is working fine i am able get the URL.
Now i have to use this URL with servlet which is used to upload a
file.

   AsyncCallback callback = new AsyncCallback() {

public void onFailure(Throwable caught) {
// TODO Auto-generated method stub
caught.printStackTrace();
}

public void onSuccess(Object result) {
String tmp = result.toString();
uploadForm.setAction(tmp);

// Submit the form to complete the upload
uploadForm.submit();
uploadForm.reset();
}
};

On server Side

 public class UploadServiceImpl extends HttpServlet {

   BlobstoreService blobstoreService =
BlobstoreServiceFactory.getBlobstoreService();

 public void doPost(HttpServletRequest req, HttpServletResponse
res)
  throws ServletException, IOException {

MapString, BlobKey blobs =
blobstoreService.getUploadedBlobs(req);
BlobKey blobKey = blobs.get(upload);

if(blobKey == null){
res.sendRedirect(/);
}else{
res.sendRedirect(/serve?blob-key= 
+blobKey.getKeyString());
}
  }

 }

With this Code I am able to view only the .txt file on
Window.alert(event.getResults());
and also the size of .txt file is greater then 2 MB.

But when i submit the xyz.doc file it gives option to save file and
also the name of the file xyz.doc is changed to serve.doc
the size of the file is 130 KB.

Plz tell me what to do. file can be of type .txt or .doc with size
greater then 1 MB.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Stillcollab-surface : an Open Source wysiwyg editor written for and with GWT

Le 7 mars 2012 15:54, Thomas Broyer t.bro...@gmail.com a écrit :


 On Wednesday, March 7, 2012 2:07:38 PM UTC+1, Damien Picard wrote:

 Hi,

 You can find a demo here : 
 http://surface-sample.**elasticbeanstalk.com/http://surface-sample.elasticbeanstalk.com/


 Thanks.

 It's indeed a very young project: you cannot apply style across paragraphs
 or other styles' boundaries (typical example: fobo bia/br b/iaz →
 fo*o b**ar b*az)
 That's one of the hardest things to handle in an editor, and the very
 first thing I try out ;-)


Thank you to notice this problem ; in fact this is a selection range bug
(sometimes the range is not set correctly, but only in prod mode :(  I
think I will spent a long time on this...) But the behavior you notice
works fine, when the Range works... This is also the first thing I've
implemented



 Indeed, I'm reinventing the wheel. I did not known the Wave editor, I
 will take a look at it, but I'm not sure that handling something else than
 HTML is the right thing to do in my use case. There is some existing
 wysiwyg editors that uses the same idea of creating inserters instead of
 using execCommand (Aloha, as an example).
 But there is always something missing to me :

- I need a GWT based wysiwyg (Wave editor, XWiki editor are
candidates)
- I need to create specific inserters
- I need to control strictly the HTML output (because the HTML is
exported with XSLT processors in my use case)

 Wave is based on documents that can easily be serialized as XML (that's
 what we use for persistence).
 Because it has to to handle operational 
 transformationhttp://www.waveprotocol.org/whitepapers/operational-transform,
 inline styling (bold, italic, links, etc.) and paragraphs are represented
 by markers. Styling is represented by annotations, so the markers are
 annotation boundaries, serialized in XML as processing instructions.
 Paragraph boundaries are representing by line/ elements (similar to br
 in HTML except a line/ marks the beginning of a paragraph, and can have a
 type and level: title, ordered list, unordered list). These are just
 the built-in representations though, you're free to implement whatever you
 want (it'd just require a bit more work).
 The persistent document is first processed to build a local document
 (line/xxx is transformed to l:pxxx/l:p, annotations are transformed
 to l:s spans, etc.), then each element of this document is rendered into
 HTML. Each modification made on the document (either persistent or local)
 is passed to the renderer to update the view.
 Have a look at http://www.waveprotocol.org/code/tutorials/writing-a-doodad
  and http://www.waveprotocol.org/wave-protocol-summit/wave-summit-talks 
 (particularly
 “Wave model deep dive” by Alex North, and “Wave panel and rendering” and
 “Real-time editor  Doodads” by Dave Hearnden), and search for my mails on
 the Wave mailing lists, where people answered with many valuable
 information and links. Re. the code, start with the EditorHarness GWT app.

 In our case, we chose to keep the paragraphs-via-line/ and
 styling-via-annotations (because it was easier), and added table rendering,
 links (handled as elements so we can easily make sure we don't nest them),
 semantic annotations (same as links), and illustrations (similar to an
 image, but links to an entity that carries both the image and legend, among
 many other things).
 In some rich text areas, we're able to limit available features: some
 areas a single paragraph with only styling a semantic markup, others
 allow several paragraphs but no titles, etc.
 Finally, by listening to document changes, we keep a document outline,
 index of semantic markup (as CellTree widgets), and lists of tables and
 illustrations (as CellList widgets) in real-time.

 The only thing needing real work is the copy/paste handling, which in Wave
 is tightly bound to Wave's wavelet document schema. In our case, we
 simply shadowed the class to strip every formatting and paste as plain text.


I've checked out the code ; I will try to extract and use only the editor
in a sample project. Maybe you've already done this work ?


 Overall, the code is complex but very well thought out, so once you
 grasped the concepts, it reads fairly easily.


- I need to process the HTML in-place, by DOM manipulation


 Not sure what you mean by that, but Wave uses DOM manipulations
 exclusively (see above).

In fact, I want to launch a command that make some changes on the currently
editing content. If this is the only thing missing in Wave editor, I think
I can do it. This is not really difficult.

Thank you very much.

  --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To view this discussion on the web visit
 https://groups.google.com/d/msg/google-web-toolkit/-/NIFKhsOGvlUJ.

 To post to this group, send email to google-web-toolkit@googlegroups.com.
 To unsubscribe from this group, send email to

Re: Stillcollab-surface : an Open Source wysiwyg editor written for and with GWT



On Wednesday, March 7, 2012 4:41:20 PM UTC+1, Damien Picard wrote:



 Le 7 mars 2012 15:54, Thomas Broyer a écrit :


 On Wednesday, March 7, 2012 2:07:38 PM UTC+1, Damien Picard wrote:

 Hi,

 You can find a demo here : 
 http://surface-sample.**elasticbeanstalk.com/http://surface-sample.elasticbeanstalk.com/


 Thanks.

 It's indeed a very young project: you cannot apply style across 
 paragraphs or other styles' boundaries (typical example: fobo bia/br 
 b/iaz → fo*o b**ar b*az)
 That's one of the hardest things to handle in an editor, and the very 
 first thing I try out ;-)


 Thank you to notice this problem ; in fact this is a selection range bug 
 (sometimes the range is not set correctly, but only in prod mode :(  I 
 think I will spent a long time on this...) But the behavior you notice 
 works fine, when the Range works... This is also the first thing I've 
 implemented

  

 Indeed, I'm reinventing the wheel. I did not known the Wave editor, I 
 will take a look at it, but I'm not sure that handling something else than 
 HTML is the right thing to do in my use case. There is some existing 
 wysiwyg editors that uses the same idea of creating inserters instead of 
 using execCommand (Aloha, as an example).
 But there is always something missing to me :

- I need a GWT based wysiwyg (Wave editor, XWiki editor are 
candidates)
- I need to create specific inserters
- I need to control strictly the HTML output (because the HTML is 
exported with XSLT processors in my use case) 

 Wave is based on documents that can easily be serialized as XML (that's 
 what we use for persistence).
 Because it has to to handle operational 
 transformationhttp://www.waveprotocol.org/whitepapers/operational-transform,
  
 inline styling (bold, italic, links, etc.) and paragraphs are represented 
 by markers. Styling is represented by annotations, so the markers are 
 annotation boundaries, serialized in XML as processing instructions. 
 Paragraph boundaries are representing by line/ elements (similar to br 
 in HTML except a line/ marks the beginning of a paragraph, and can have a 
 type and level: title, ordered list, unordered list). These are just 
 the built-in representations though, you're free to implement whatever you 
 want (it'd just require a bit more work).
 The persistent document is first processed to build a local document 
 (line/xxx is transformed to l:pxxx/l:p, annotations are transformed 
 to l:s spans, etc.), then each element of this document is rendered into 
 HTML. Each modification made on the document (either persistent or local) 
 is passed to the renderer to update the view.
 Have a look at 
 http://www.waveprotocol.org/code/tutorials/writing-a-doodad and 
 http://www.waveprotocol.org/wave-protocol-summit/wave-summit-talks 
 (particularly 
 “Wave model deep dive” by Alex North, and “Wave panel and rendering” and 
 “Real-time editor  Doodads” by Dave Hearnden), and search for my mails on 
 the Wave mailing lists, where people answered with many valuable 
 information and links. Re. the code, start with the EditorHarness GWT app.

 In our case, we chose to keep the paragraphs-via-line/ and 
 styling-via-annotations (because it was easier), and added table rendering, 
 links (handled as elements so we can easily make sure we don't nest them), 
 semantic annotations (same as links), and illustrations (similar to an 
 image, but links to an entity that carries both the image and legend, among 
 many other things).
 In some rich text areas, we're able to limit available features: some 
 areas a single paragraph with only styling a semantic markup, others 
 allow several paragraphs but no titles, etc.
 Finally, by listening to document changes, we keep a document outline, 
 index of semantic markup (as CellTree widgets), and lists of tables and 
 illustrations (as CellList widgets) in real-time.

 The only thing needing real work is the copy/paste handling, which in 
 Wave is tightly bound to Wave's wavelet document schema. In our case, we 
 simply shadowed the class to strip every formatting and paste as plain text.


 I've checked out the code ; I will try to extract and use only the editor 
 in a sample project. Maybe you've already done this work ? 


I'm building Wave out-of-the-box (ant dist-libraries IIRC) and then 
picking the client, client-common, client-scheduler, common, media, model, 
and util JARs.
Maybe some of them are only needed for the EditorToolbar which we're also 
using, but I doubt so.
 

  

 Overall, the code is complex but very well thought out, so once you 
 grasped the concepts, it reads fairly easily.


- I need to process the HTML in-place, by DOM manipulation


 Not sure what you mean by that, but Wave uses DOM manipulations 
 exclusively (see above).

 In fact, I want to launch a command that make some changes on the 
 currently editing content. If this is the only thing missing in Wave 
 editor, I think I can do it. This is not really

Re: Stillcollab-surface : an Open Source wysiwyg editor written for and with GWT

Le 7 mars 2012 18:53, Thomas Broyer t.bro...@gmail.com a écrit :



 On Wednesday, March 7, 2012 4:41:20 PM UTC+1, Damien Picard wrote:



 Le 7 mars 2012 15:54, Thomas Broyer a écrit :


 On Wednesday, March 7, 2012 2:07:38 PM UTC+1, Damien Picard wrote:

 Hi,

 You can find a demo here : http://surface-sample.**elasticb**
 eanstalk.com/ http://surface-sample.elasticbeanstalk.com/


 Thanks.

 It's indeed a very young project: you cannot apply style across
 paragraphs or other styles' boundaries (typical example: fobo bia/br
 b/iaz → fo*o b**ar b*az)
 That's one of the hardest things to handle in an editor, and the very
 first thing I try out ;-)


 Thank you to notice this problem ; in fact this is a selection range bug
 (sometimes the range is not set correctly, but only in prod mode :(  I
 think I will spent a long time on this...) But the behavior you notice
 works fine, when the Range works... This is also the first thing I've
 implemented

  I've fixed the problem, you can play with it ;) (there is some other
bugs, but there are all dues to Ranges)




 Indeed, I'm reinventing the wheel. I did not known the Wave editor, I
 will take a look at it, but I'm not sure that handling something else than
 HTML is the right thing to do in my use case. There is some existing
 wysiwyg editors that uses the same idea of creating inserters instead of
 using execCommand (Aloha, as an example).
 But there is always something missing to me :

- I need a GWT based wysiwyg (Wave editor, XWiki editor are
candidates)
- I need to create specific inserters
- I need to control strictly the HTML output (because the HTML is
exported with XSLT processors in my use case)

 Wave is based on documents that can easily be serialized as XML (that's
 what we use for persistence).
 Because it has to to handle operational 
 transformationhttp://www.waveprotocol.org/whitepapers/operational-transform,
 inline styling (bold, italic, links, etc.) and paragraphs are represented
 by markers. Styling is represented by annotations, so the markers are
 annotation boundaries, serialized in XML as processing instructions.
 Paragraph boundaries are representing by line/ elements (similar to br
 in HTML except a line/ marks the beginning of a paragraph, and can have a
 type and level: title, ordered list, unordered list). These are just
 the built-in representations though, you're free to implement whatever you
 want (it'd just require a bit more work).
 The persistent document is first processed to build a local document
 (line/xxx is transformed to l:pxxx/l:p, annotations are transformed
 to l:s spans, etc.), then each element of this document is rendered into
 HTML. Each modification made on the document (either persistent or local)
 is passed to the renderer to update the view.
 Have a look at http://www.waveprotocol.**org/code/tutorials/writing-a-**
 doodad http://www.waveprotocol.org/code/tutorials/writing-a-doodad
  and http://www.**waveprotocol.org/wave-**protocol-summit/wave-summit-**
 talkshttp://www.waveprotocol.org/wave-protocol-summit/wave-summit-talks 
 (particularly
 “Wave model deep dive” by Alex North, and “Wave panel and rendering” and
 “Real-time editor  Doodads” by Dave Hearnden), and search for my mails on
 the Wave mailing lists, where people answered with many valuable
 information and links. Re. the code, start with the EditorHarness GWT app.

 In our case, we chose to keep the paragraphs-via-line/ and
 styling-via-annotations (because it was easier), and added table rendering,
 links (handled as elements so we can easily make sure we don't nest them),
 semantic annotations (same as links), and illustrations (similar to an
 image, but links to an entity that carries both the image and legend, among
 many other things).
 In some rich text areas, we're able to limit available features: some
 areas a single paragraph with only styling a semantic markup, others
 allow several paragraphs but no titles, etc.
 Finally, by listening to document changes, we keep a document outline,
 index of semantic markup (as CellTree widgets), and lists of tables and
 illustrations (as CellList widgets) in real-time.

 The only thing needing real work is the copy/paste handling, which in
 Wave is tightly bound to Wave's wavelet document schema. In our case, we
 simply shadowed the class to strip every formatting and paste as plain text.


 I've checked out the code ; I will try to extract and use only the editor
 in a sample project. Maybe you've already done this work ?


 I'm building Wave out-of-the-box (ant dist-libraries IIRC) and then
 picking the client, client-common, client-scheduler, common, media, model,
 and util JARs.
 Maybe some of them are only needed for the EditorToolbar which we're also
 using, but I doubt so.




 Overall, the code is complex but very well thought out, so once you
 grasped the concepts, it reads fairly easily.


- I need to process the HTML in-place, by DOM manipulation


 Not sure

Re: GWT DataGrid Widget unpredictable row height issue...

2012-03-07 Thread Bill M

Hi Vinayak,

I think I found the problem.  I have a column whose contents I want to
hide from the user.  However, I need the data available.  So, from
another post I came across, someone said the way to hide a column is
to set it's column width to 0.  However, it really seems I'm getting
some wrapping occuring with this hidden field, causing the height of
the entire row it's on to grow.

So, is there another way to hide the contents of a column?  Or, will I
need to come up with a paralled data structure to hold column's I
don't want displayed in the DataGrid?

Appreciate any assistance.
Thanks,
Bill M.

On Mar 2, 5:27 pm, Bill M blinte...@aol.com wrote:
 Hi Vinayak,

 I tried setting using the same data for eachrow, yet I still got some
 rows appearing with larger heights.
 And eachrowwas loaded with the same exact data.

 I'm try loading with field/column of therowwith  and see what that
 does.

 Thanks,
 Bill M.

 On Mar 2, 5:14 am, vinayak kulkarni bkvina...@gmail.com wrote:



  Hello,
  I am using thedatagridbut didnt face any issue related to largerrow
  size.
  It only occurs during data wrapping if text size is more.

  In your case, some data might have been overflown with space character
  to the next line which may be showing larger size

  On Feb 27, 11:55 pm, Bill M blinte...@aol.com wrote:

   Hi all,

   I'm loading the newDataGridWidget with the results of a SQL query.
   I have noticed that some rows (just a few) are appearing with a larger
  rowheightthan others, on a load of about 1000 rows.  I tried setting
   each column of therowto a fixed value (not using the results of the
   query), to see if maybe some potential overflow of field widths was
   occuring, maybe causing a wrap, which would explain the largerrow
  height.  But, I found this was not the case.  And for info purposes, I
   am using the default font from the FireFox Browser.

   Are there issues with getting a consistentrowheightout of GWT 2.4/
  DataGridwidget?  Are there workarounds?  I saw some others noting
   issues of rowHeight from the CellTable widget.  Are there issue's with
   this widget?  Or would an issue like this have to be originating from
   my application?

   Appreciate any insight!

   Thanks,
   Bill M.- Hide quoted text -

  - Show quoted text -- Hide quoted text -

 - Show quoted text -

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

How to hide a column in the GWT DataGrid Widget

2012-03-07 Thread Bill M

Hi,

Is there a way to hide a column in the GWT DataGrid widget?  I was
using someone's suggestion of setting the columnWidth of the column I
want to hide to 0.  However, with that approach the String data seems
to be wrapping in the hidden column, causing some rows to have a
larger height.

Is there another way to hide a column?  Or, do I need to implement my
own data structure to handle this?

Thanks,
Bill M

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Tree HTML item loses focus

2012-03-07 Thread Ben Klein

I have a Tree serving as a navigation pane, in which almost all of the
items are HTML links. Often, when tabbing through the tree, the Tree
itself will take back the focus from whichever link was selected. Is
there any way that I can prevent this from happening?

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Supported Browser Versions

2012-03-07 Thread David Self

The only place I've seen supported browsers listed is in the FAQ 
(http://code.google.com/webtoolkit/doc/latest/FAQ_GettingStarted.html#What_browsers_does_GWT_support),
 
but this list seems to be out of date (e.g., Firefox support for GWT 2.4 is 
listed as 1.0, 1.5, 2.0, 3.0, and 3.5).  Are the currently supported 
browser versions for each version of GWT specified anywhere?

My company needs to understand which browser versions each version of GWT 
supports in order to make decisions as to our officially supported browser 
list.  What is Google's strategy for this?  Is a list of supported browsers 
maintained anywhere?  If so, is this list revised for all GWT versions when 
new browser versions are released or is it a static list of browser 
versions that were available at the time that specific GWT version was 
released?

Thanks,
David

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/jnLEPGV5NE4J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

ImageResources cannot show image as expected

2012-03-07 Thread JoseM

Maybe the ehealthlogo.png is missing from the proper folder or it is 
misspelled. Look at the logs in the GWT Jetty window it might  say something 
(make sure to set the Level to Debug). Or you can also run a gwt compile that 
usually gives warning and errors when there is something wrong. 

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/ZP9QnVvf0LYJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: ImageResources cannot show image as expected

2012-03-07 Thread Kei Kei

I try to run a gwt compile but still have no any clue.
anyway, for the worst case, I can still use
Image ha_logo_files = new Image(imagepath);
without using ImageResources

On Thu, Mar 8, 2012 at 12:12 PM, JoseM jose.a.marti...@gmail.com wrote:

 Maybe the ehealthlogo.png is missing from the proper folder or it is
 misspelled. Look at the logs in the GWT Jetty window it might  say
 something (make sure to set the Level to Debug). Or you can also run a gwt
 compile that usually gives warning and errors when there is something wrong.

 --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To view this discussion on the web visit
 https://groups.google.com/d/msg/google-web-toolkit/-/ZP9QnVvf0LYJ.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 To unsubscribe from this group, send email to
 google-web-toolkit+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/google-web-toolkit?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Compilation Error with jar dependency

2012-03-07 Thread Vicky

Solved it. Need to include java src files in the jar along with the
class files.

FYI, for folks who might not know, GWT needs the java source (and not
the byte code) to compile to javascript.

On Mar 6, 9:38 pm, Vicky vicky...@gmail.com wrote:
 Hi

 I am using GWT 2.4. I have a use case where i need to use classes from
 a certain jar file. As part of the GWT project in eclipse i added that
 jar file as a classpath dependency. With this my java compilation went
 through successfully. However when i tried to do a GWT compile it
 failed with the followingerror,

 [java]    [ERROR] An internal compiler exception occurred
 [java] com.google.gwt.dev.jjs.InternalCompilerException: Failed to get
 JNode
 [java]     at com.google.gwt.dev.jjs.impl.TypeMap.get(TypeMap.java:
 140)
 [java]     at com.google.gwt.dev.jjs.impl.TypeMap.get(TypeMap.java:71)
 [java]     at
 com.google.gwt.dev.jjs.impl.BuildTypeMap.getType(BuildTypeMap.java:
 730)
 [java]     at com.google.gwt.dev.jjs.impl.BuildTypeMap.access
 $000(BuildTypeMap.java:99)
 [java]     at com.google.gwt.dev.jjs.impl.BuildTypeMap
 $BuildDeclMapVisitor.visit(BuildTypeMap.java:195)
 [java]     at
 org.eclipse.jdt.internal.compiler.ast.LocalDeclaration.traverse(LocalDeclaration.java:
 237)
 [java]     at
 org.eclipse.jdt.internal.compiler.ast.ForeachStatement.traverse(ForeachStatement.java:
 527)
 [java]     at
 org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.traverse(MethodDeclaration.java:
 239)
 [java]     at
 org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:
 1239)
 [java]     at
 org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.traverse(CompilationUnitDeclaration.java:
 687)
 [java]     at
 com.google.gwt.dev.jjs.impl.BuildTypeMap.createPeersForNonTypeDecls(BuildTypeMap.java:
 637)
 [java]     at
 com.google.gwt.dev.jjs.impl.BuildTypeMap.exec(BuildTypeMap.java:514)
 [java]     at
 com.google.gwt.dev.jjs.impl.BuildTypeMap.exec(BuildTypeMap.java:523)
 [java]     at
 com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.precompile(JavaToJavaScriptCompiler.java:
 599)
 [java]     at
 com.google.gwt.dev.jjs.JavaScriptCompiler.precompile(JavaScriptCompiler.java:
 33)
 [java]     at com.google.gwt.dev.Precompile.precompile(Precompile.java:
 284)
 [java]     at com.google.gwt.dev.Precompile.precompile(Precompile.java:
 233)
 [java]     at com.google.gwt.dev.Precompile.precompile(Precompile.java:
 145)
 [java]     at com.google.gwt.dev.Compiler.run(Compiler.java:232)
 [java]     at com.google.gwt.dev.Compiler.run(Compiler.java:198)
 [java]     at com.google.gwt.dev.Compiler$1.run(Compiler.java:170)
 [java]     at
 com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:88)
 [java]     at
 com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:
 82)
 [java]     at com.google.gwt.dev.Compiler.main(Compiler.java:177)
 [java]       [ERROR] nosourceinfo:publicinterface
 com.temp.operator.IBuilderOperator
 [java]     extends java.lang.Object
 [java] /*   methods   */
 [java]publicabstract java.lang.String getValue()
 [java]

 Firstly why is GWT not able to resolve this dependency. Secondly how
 do i solve this issue.

 Thanks,
 Vicky

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

[gwt-contrib] Re: Add cursor: pointer for Hyperlink (issue1615808)


committed as r10894

http://gwt-code-reviews.appspot.com/1615808/

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: Add layout.onAttach/onDetach calls (issue1615804)


Fixed as r10895

http://gwt-code-reviews.appspot.com/1615804/

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: Fixed issue 1394 : Need a new getSplitter() method in SplitPanel (issue1398801)


committed as r10896

http://gwt-code-reviews.appspot.com/1398801/

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: Fixing a bug in CellWidget where the cell isn't rendered if the initial value is null. We were ... (issue1655803)


committed as r10897


http://gwt-code-reviews.appspot.com/1655803/diff/1/user/src/com/google/gwt/user/cellview/client/CellWidget.java
File user/src/com/google/gwt/user/cellview/client/CellWidget.java
(right):

http://gwt-code-reviews.appspot.com/1655803/diff/1/user/src/com/google/gwt/user/cellview/client/CellWidget.java#newcode153
user/src/com/google/gwt/user/cellview/client/CellWidget.java:153:
setValueWithoutEqualityCheck(initialValue, false, true);
On 2012/03/06 18:58:32, skybrian wrote:

Nit: I think it would be more straightforward to inline this, since

it's just

two if statements.


Done.

http://gwt-code-reviews.appspot.com/1655803/

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: Improving the JavaDoc of ListDataProvider to explain that the wrapped list should not be modifie... (issue1656803)


committed as r10898


http://gwt-code-reviews.appspot.com/1656803/diff/1/user/src/com/google/gwt/view/client/ListDataProvider.java
File user/src/com/google/gwt/view/client/ListDataProvider.java (right):

http://gwt-code-reviews.appspot.com/1656803/diff/1/user/src/com/google/gwt/view/client/ListDataProvider.java#newcode574
user/src/com/google/gwt/view/client/ListDataProvider.java:574: * more
optimal because the data provider knows which rows were modified and
On 2012/03/06 19:43:08, skybrian wrote:

nit: s/is more optimal/performs better/
(and elsewhere)


Done.

http://gwt-code-reviews.appspot.com/1656803/

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: Added a method to allow 'snap closed' behavior in SplitLayoutPanel. (issue1657803)