Showing messages 1 through 17 of 17.

• For what?
  2007-03-21 11:33:23 alski [Reply | View]
  
  I'd say it greatly depends on what functionality you plan to offer.
  
  If it is just straight rendering of HTML content with perhaps some ability to capture certain events, then a gecko wrapper is fine.
  
  If you are looking to extend and control the layout and do something more dynamic, then I'm not sure how gecko would fit in. In that case it depends on if you own the generation of the content. If you can guarantee XHTML + CSS (flying saucer) is easy and extendable. If you don't own the content and can't vouch for it, all bets are off and you better start looking for a paddle.
  
  There have been many times where I've wanted to render uncontrolled HTML but then I think of the user experience. I generally now just popup a browser and point it at the content. The user has already chosen the weapon for viewing HTML, use it.

• Evaluate free HTML renderers
  2007-03-21 08:56:13 dtrehas [Reply | View]
  
  I saw that XAMJ warrior (http://html.xamjwg.org/) comes also with XAML support.

• Dont waste too much manpower
  2007-03-21 03:54:04 aehrenr [Reply | View]
  
  I think an all java version would be fine, but maybe not worth the huge work to reproduce gecko in pure java and keep it up to date. A way to display pdf files from java would also be very fine
• Dont waste too much manpower
  2008-03-26 14:03:53 will69 [Reply | View]
  
  Adobe is offering a pure Java PDF viewer. Just search for "PDF viewer" in this forum, or look here:
  
  http://today.java.net/pub/a/today/2005/10/20/accessing-pdf-with-acrobat-viewer-javabean.html

• ALL JAVA would be way cool
  2007-03-20 16:06:45 aberrant [Reply | View]
  
  ..but, then what about plugins? Can the goal of handling "real world pages" realy be accomplished without say, flash, or quicktime ? What if you visit a page with an applet? Does an applet spawn another JVM? Does it use the current JVM? If we are only taking about rendering the crazy mess of non-standard compliant HTML that is out there then I'd say it may not be worth the effort.

• Buy an existing solution
  2007-03-19 05:06:41 rabbe [Reply | View]
  
  Rather than waste a lot of man hours on this, why not buy the rights to webwindow or one of the commercial Java browsers?
  
  I would prefer a pure Java solution, but I'm not overly confident that it will be properly maintained as new standards emerge.

• Java browser
  2007-03-18 14:43:06 haraldk [Reply | View]
  
  The most flexible thing would be a an all-Java browser. But if that means another half-hearted job at creating something that doesn't cut it, I'd rather spend more time polishing the JDIC browser. In that case I agree to the one browser (and Gecko is probably the one) for all platforms argument.
  
  But I'm thinking, how hard would it be to actually port Gecko (or something of equal quality and maybe a more compatible license) to Java? It's hardly rocket science, is it? ;-)

• Generating Thumbnails?
  2007-03-17 16:01:09 kennardconsulting [Reply | View]
  
  Presumably, a Java-based browser would make it a snap to render a page to a Java2D image, then resize it to a thumbnail and save it as a JPEG.

  Is this something that is possible with any of the other approaches?

• _One_ Browser For _All_ Platforms
  2007-03-16 18:53:13 tompalmer [Reply | View]
  
  Ideally in Java, but __Gecko__ would be fine, too. Java should behave the same everywhere. That means the only current browser that would fit the bill is Gecko. And deep integration would be great.
• _One_ Browser For _All_ Platforms
  2007-03-16 18:53:27 tompalmer [Reply | View]
  
  And to be clear, if Gecko shipped in Java, then there'd be no need to know whether it was coded in Java directly.
• _One_ Browser For _All_ Platforms
  2007-03-16 18:54:17 tompalmer [Reply | View]
  
  Sorry that was if shipped in Java (the runtime), no need to be coded in Java (the language).
• _One_ Browser For _All_ Platforms
  2007-03-17 07:01:01 tompalmer [Reply | View]
  
  And I still wasn't clear. (Sorry for all the comments.) What I mean is that dll and so files are just fine if they behave the same on all platforms and are prebundled. Sad thing would be not to see their memory in the Java heap or participate in GC, but that might be livable.

• JDIC is the most feasable solution
  2007-03-16 15:24:42 augusto [Reply | View]
  
  I would like to see more work on the JDIC browser, which still needs more work and support in order to be stabilized.
  
  Now, and all Java browser would be great, the only problem is the feasibility of such a project. I wish I could both for both options actually, I think JDIC integration with the native browsers is important and doing a Swing based browser would be great (ideal if it can scale down to smaller devices).
  
  

• JDIC is the most feasable solution
  2007-03-16 15:22:36 augusto [Reply | View]
  
  I would like to see more work on the JDIC browser, which still needs more work and support in order to be stabilized.
  
  Now, and all Java browser would be great, the only problem is the feasibility of such a project. I wish I could both for both options actually, I think JDIC integration with the native browsers is important and doing a Swing based browser would be great (ideal if it can scale down to smaller devices).
  
  

• Pure Java Browser
  2007-03-16 10:18:25 fcmmok [Reply | View]
  
  JDIC has to solve the problem of integrating different browser on different OS. Why not write our browser in Java so it can run perfectlt on any OS.
  
  If MEPG decoder can be written in Java, why not HTML browser !
  

• Realistically
  2007-03-16 10:12:11 carcassi [Reply | View]
  
  Like most people, I'd like a all-Java browser, but... is it feasable?
  
  I think one would have to start from an existing (open source?) codebase, or the project would take too long... I don't actually know that space: are there any suitable candidate?
  
  Assuming there was one, browser compatibility is still a major problem. So, what should it align itself to? IE? Mozilla? Opera? The spec? I can see that for different apps, you might need it to be aligned to different things...
  
  I'd really like the first option... but I don't see it happening... :-( Maybe someone can show me how can it be possible?

• It depends...
  2007-03-16 09:54:22 fabriziogiudici [Reply | View]
  
  A Java component would be preferred since for sure it would deliver the maximum of flexibility (e.g. the capability of using LayeredPanes etc...).
  
  But if the JDIC integration would deliver the same flexibility, this latter solution would be preferred since it would give the maximum compatibility with HTML.