JDS3 for Solaris 10 (Early Access)

For anyone who's wondering how JDS3 is shaping up on Solaris, it's included in the new Beta 7 release of the freely-downloadable Solaris Express.

Update: Brief review (in Hungarian) and screenshots of S10/JDS3 on x86. Warning: this page has 100+ large images on it, don't say I didn't warn you...

Comments:

So, care to give a summary on the blog for those of us without a solaris box handy? :)

Posted by Luis Villa on November 01, 2004 at 05:54 AM GMT+00:00 #

Well, I haven't seen the SE version so I don't want to say too much in case it doesn't include some of the things we've still got up our sleeve :)

Most components have had major upgrades... JDS3 is based on GNOME 2.6, Java 5.0 and Mozilla 1.7. X.org is now an option as well (dunno if that's in the SE version yet), Glow is included as a technology preview for the first time, and everyone's been working pretty hard on GOK and Gnopernicus recently to get them more stable and performant, particularly on Solaris where we haven't always had as many testers available. Oh, and we've got a lot more fancy icons now :)

Posted by Calum Benson on November 01, 2004 at 07:26 AM GMT+00:00 #

Here's a brief review (in Hungarian) and screenshots of S10/JDS3 on x86.

Posted by Calum Benson on November 02, 2004 at 03:32 AM GMT+00:00 #

Hi,
Is there any way for outsiders (not sun people) to help ?
  • I'd like to submit some JDS3 bugs (on sparc)
  • I'd like to update translations
thanks

Posted by Jan Matis on November 02, 2004 at 11:52 PM GMT+00:00 #

Hi Jan,

There are lots of different answers to this :)

For GNOME-related bugs and translations, probably the easiest thing to do is file them in GNOME bugzilla, noting that they apply to the version shipped with JDS3. For translations into languages that Sun doesn't support, the best idea would be to work with the GNOME Translation Project to get your changes into the community, and Sun will pick them up in the next version of JDS, or in a patch if the change is urgent enough.

Same for mozilla, evolution or staroffice-- if you file bugs at bugzilla.mozilla.org, bugzilla.ximian.com or issuezilla.openoffice.org respectively, a Sun engineer should spot them fairly quickly. Translations for unsupported (by Sun) languages should again go through the respective community translation teams; I don't have details of those to hand, I'm afraid.

For components that don't have a public bug database, like Flash or Acrobat Reader, it's a bit more difficult-- for those, you should probably go through Sun customer support and ask them to raise a change request on your behalf.

HTH, Calum.

Posted by Calum Benson on November 03, 2004 at 03:33 AM GMT+00:00 #

Post a Comment:
Comments are closed for this entry.
About


I am an Interaction Designer in the Systems Experience Design team, arriving at Oracle via Sun where I've worked since 2000. I currently work on sysadmin user experience projects for Solaris. Formerly I worked on open source Solaris desktop projects such as GNOME, NWAM and IPS.

Search

Archives
« April 2014
MonTueWedThuFriSatSun
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
    
       
Today