java-gnome-hackers Mailing List for The java-gnome language bindings project (Page 111)
Brought to you by:
afcowie
Menu
▾
▴
java-gnome-hackers — Hacking on the bindings themselves: design issues and co-ordination
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(102) |
Sep
(43) |
Oct
(32) |
Nov
(43) |
Dec
(51) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(6) |
Feb
(19) |
Mar
(39) |
Apr
(22) |
May
|
Jun
(11) |
Jul
(2) |
Aug
(4) |
Sep
|
Oct
(3) |
Nov
(9) |
Dec
(73) |
| 2004 |
Jan
(88) |
Feb
(141) |
Mar
(116) |
Apr
(69) |
May
(199) |
Jun
(53) |
Jul
(90) |
Aug
(23) |
Sep
(11) |
Oct
(212) |
Nov
(57) |
Dec
(61) |
| 2005 |
Jan
(88) |
Feb
(17) |
Mar
(21) |
Apr
(50) |
May
(44) |
Jun
(33) |
Jul
(21) |
Aug
(37) |
Sep
(39) |
Oct
(43) |
Nov
(40) |
Dec
(15) |
| 2006 |
Jan
(21) |
Feb
(69) |
Mar
(23) |
Apr
(6) |
May
(29) |
Jun
(19) |
Jul
(17) |
Aug
(15) |
Sep
(13) |
Oct
(16) |
Nov
(9) |
Dec
(7) |
| 2007 |
Jan
(30) |
Feb
(39) |
Mar
(1) |
Apr
(12) |
May
(53) |
Jun
(30) |
Jul
(39) |
Aug
(75) |
Sep
(16) |
Oct
(13) |
Nov
(20) |
Dec
(5) |
| 2008 |
Jan
(8) |
Feb
(14) |
Mar
(33) |
Apr
(7) |
May
(22) |
Jun
(23) |
Jul
(17) |
Aug
(9) |
Sep
(9) |
Oct
(25) |
Nov
(9) |
Dec
(1) |
| 2009 |
Jan
(20) |
Feb
(38) |
Mar
(9) |
Apr
(15) |
May
(30) |
Jun
(35) |
Jul
(22) |
Aug
(10) |
Sep
(7) |
Oct
(23) |
Nov
(6) |
Dec
(8) |
| 2010 |
Jan
(5) |
Feb
(10) |
Mar
(17) |
Apr
(10) |
May
(16) |
Jun
(8) |
Jul
(3) |
Aug
(15) |
Sep
(14) |
Oct
(26) |
Nov
(11) |
Dec
(14) |
| 2011 |
Jan
(10) |
Feb
(8) |
Mar
(6) |
Apr
(7) |
May
(18) |
Jun
(17) |
Jul
(6) |
Aug
(1) |
Sep
(2) |
Oct
(6) |
Nov
(2) |
Dec
(10) |
| 2012 |
Jan
(6) |
Feb
(9) |
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
(5) |
Aug
(14) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
(8) |
Mar
(6) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2014 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jeffrey M. <ku...@zo...> - 2004-01-21 02:26:54
|
Please let me know when you need help. I am more than happy to spend all of the time necessary to help you learn the JNI code. -Jeff On Tue, 2004-01-20 at 21:19, Luca De Rugeriis wrote: > Thanks Jeff! > Your explanation was great and really of use ;) > I'm sorry I couldn't reply earlier, but real life has taken me away. > Generating the headers then converting from decls to impls sounds smart! > I'm going to try the thing, you made the concept clear, it just a matter > of taking care about C syntax and rules, something I'm not used to ;) |
|
From: Luca De R. <pie...@li...> - 2004-01-21 02:21:39
|
Il mar, 2004-01-20 alle 16:26, Jeffrey Morgan ha scritto:
> > > Luca, if you are still interested in learning some of the JNI
> > > code I could work with you on the FileChooser.
> > >
> > That would be great! I was just thinking to take a look at FileChooser
> > (at least to know how it looks;)
> > Remember, however, that I'm with that old pc, and pratically it's
> > impossible for me to compile. I could always do with a simple text
> > editor, but without the possibility to test further changes...
>
> You can do some of the editing and I'll do the testing 8-)
> I just added a class FileFilter that needs some native code.
> You can start by compiling this file and then running jdk
> utility to create the initial JNI header file like:
>
> javah org.gnu.gtk.FileFilter
>
> This will create a file called org_gnu_gtk_FileFilter.h in
> the directory where you run it. Copy this file to
> gtk/src/jni/org_gnu_gtk_FileFilter.c (notice I changed the
> extension from .h to .c). Now the real fun begins!!
>
> The first thing we need to do is update the header and then
> convert all of the method decls to method impls.
>
> For the header you can just copy/paste it from another .c file
> in the package. This will make sure the file "includes" the
> correct headers.
>
> For the methods you can follow the following examples:
>
> Example 1:
> .h
> JNIEXPORT jint JNICALL Java_org_gnu_gtk_FileFilter_gtk_1file_1filter_1new
> (JNIEnv *, jclass);
>
> .c
> JNIEXPORT jint JNICALL Java_org_gnu_gtk_FileFilter_gtk_1file_1filter_1new
> (JNIEnv *env, jclass cls)
> {
> return (jint)gtk_file_filter_new();
> }
>
>
> Example 2:
> .h
> JNIEXPORT void JNICALL
> Java_org_gnu_gtk_FileFilter_gtk_1file_1filter_1set_1name
> (JNIEnv *, jclass, jint, jstring);
>
> .c
> JNIEXPORT void JNICALL
> Java_org_gnu_gtk_FileFilter_gtk_1file_1filter_1set_1name
> (JNIEnv *env, jclass cls, jint filter, jstring name)
> {
> gchar* n = (gchar*)(*env)->GetStringUTFChars(env, name, NULL);
> gtk_file_filter_set_name((GtkFileFilter*)filter, n);
> (*env)->ReleaseStringUTFChars(env, name, n);
> }
>
>
> In the first example we just make a call to a native gtk method
> and cast the results to a jint during the return.
>
> In the second example you see that I am calling a JNI method to
> read the string from the jstring, calling the native method, and
> then freeing the memory used by the gchar*. The filter parameter
> is nothing more than a jint that holds the address of the underlying
> native struct.
>
> Most methods should be this easy but occasionally you will find a
> method that will require more code to convert data types, etc.
>
> Please give this a try and let me know if you get stuck on anything.
Thanks Jeff!
Your explanation was great and really of use ;)
I'm sorry I couldn't reply earlier, but real life has taken me away.
Generating the headers then converting from decls to impls sounds smart!
I'm going to try the thing, you made the concept clear, it just a matter
of taking care about C syntax and rules, something I'm not used to ;)
--
Luca De Rugeriis <pie...@li...>
|
|
From: Jeffrey M. <Jef...@Br...> - 2004-01-20 15:26:54
|
> > Luca, if you are still interested in learning some of the JNI
> > code I could work with you on the FileChooser.
> >
> That would be great! I was just thinking to take a look at FileChooser
> (at least to know how it looks;)
> Remember, however, that I'm with that old pc, and pratically it's
> impossible for me to compile. I could always do with a simple text
> editor, but without the possibility to test further changes...
You can do some of the editing and I'll do the testing 8-)
I just added a class FileFilter that needs some native code.
You can start by compiling this file and then running jdk
utility to create the initial JNI header file like:
javah org.gnu.gtk.FileFilter
This will create a file called org_gnu_gtk_FileFilter.h in
the directory where you run it. Copy this file to
gtk/src/jni/org_gnu_gtk_FileFilter.c (notice I changed the
extension from .h to .c). Now the real fun begins!!
The first thing we need to do is update the header and then
convert all of the method decls to method impls.
For the header you can just copy/paste it from another .c file
in the package. This will make sure the file "includes" the
correct headers.
For the methods you can follow the following examples:
Example 1:
.h
JNIEXPORT jint JNICALL Java_org_gnu_gtk_FileFilter_gtk_1file_1filter_1new
(JNIEnv *, jclass);
.c
JNIEXPORT jint JNICALL Java_org_gnu_gtk_FileFilter_gtk_1file_1filter_1new
(JNIEnv *env, jclass cls)
{
return (jint)gtk_file_filter_new();
}
Example 2:
.h
JNIEXPORT void JNICALL
Java_org_gnu_gtk_FileFilter_gtk_1file_1filter_1set_1name
(JNIEnv *, jclass, jint, jstring);
.c
JNIEXPORT void JNICALL
Java_org_gnu_gtk_FileFilter_gtk_1file_1filter_1set_1name
(JNIEnv *env, jclass cls, jint filter, jstring name)
{
gchar* n = (gchar*)(*env)->GetStringUTFChars(env, name, NULL);
gtk_file_filter_set_name((GtkFileFilter*)filter, n);
(*env)->ReleaseStringUTFChars(env, name, n);
}
In the first example we just make a call to a native gtk method
and cast the results to a jint during the return.
In the second example you see that I am calling a JNI method to
read the string from the jstring, calling the native method, and
then freeing the memory used by the gchar*. The filter parameter
is nothing more than a jint that holds the address of the underlying
native struct.
Most methods should be this easy but occasionally you will find a
method that will require more code to convert data types, etc.
Please give this a try and let me know if you get stuck on anything.
-Jeff
|
|
From: Luca De R. <pie...@li...> - 2004-01-20 14:32:30
|
Il mar, 2004-01-20 alle 13:24, Jeffrey Morgan ha scritto: > > > This would be a big help. I could also spend some time with > > > you and help you learn the C code if you are interested. It > > > really is quite easy. > > Of course that I'm interested... How could it be so easy? > > I wish I had some good pointers to start with ;) > > > > -- > > Luca De Rugeriis <pie...@li...> > > Now that 2.5.3 is behind us I will be working on the following > for 2.5.4: > > 1) Fix the last remaining bug with ActionGroup > 2) Implement the FileChooser classes > 3) Update the Menu* classes > 4) Fix any remaining gconf problems > > Luca, if you are still interested in learning some of the JNI > code I could work with you on the FileChooser. > That would be great! I was just thinking to take a look at FileChooser (at least to know how it looks;) Remember, however, that I'm with that old pc, and pratically it's impossible for me to compile. I could always do with a simple text editor, but without the possibility to test further changes... I will be happy to work with you and to learn something. Thanks Jeff ;) -- Luca De Rugeriis <pie...@li...> |
|
From: Jeffrey M. <Jef...@Br...> - 2004-01-20 14:31:49
|
There have been numerous changes that also apply to the 0.8 branch. At what point should we consider a new 0.8.3 release? -Jeff |
|
From: Jeffrey M. <Jef...@Br...> - 2004-01-20 12:24:52
|
> > This would be a big help. I could also spend some time with > > you and help you learn the C code if you are interested. It > > really is quite easy. > Of course that I'm interested... How could it be so easy? > I wish I had some good pointers to start with ;) > > -- > Luca De Rugeriis <pie...@li...> Now that 2.5.3 is behind us I will be working on the following for 2.5.4: 1) Fix the last remaining bug with ActionGroup 2) Implement the FileChooser classes 3) Update the Menu* classes 4) Fix any remaining gconf problems Luca, if you are still interested in learning some of the JNI code I could work with you on the FileChooser. -Jeff |
|
From: Luca De R. <pie...@li...> - 2004-01-17 23:06:00
|
Il sab, 2004-01-17 alle 22:53, Jeffrey Morgan ha scritto: > On Sat, 2004-01-17 at 14:37, Luca De Rugeriis wrote: > > Il ven, 2004-01-16 alle 12:56, Jeffrey Morgan ha scritto: > > I'm sorry Jeff couldn't reply faster, and thanks for the credit in the > > authors file. > > At the moment I'm stuck with an old pentium 200mhz that is a pain to use > > :( but I'm about to upgrade my hardware. I hope I'll get the new stuff > > in about 2 weeks. > > It means that it takes me like a couple of hours to j-g. (apart from > > compiling gnome libs). So I think I have to wait.... > > I hope you get a nice one!! I'm aiming at some quite fast hardware :) > > > > Here are my proposals for the items to be completed. I am sure > > > > that I am missing numerous items so please respond and help > > > > me build a complete list. > > > > > > > > complete/debug *Action* and UIManager classes (2.5.3) > > > > implement the new FileChooser class (2.5.4) > > > > update the Menu* classes to reflect the latest gtk (2.5.4) > > > > update of gnome and gnomeui classes to current (beta1) > > > > update all remaining gtk classes to current (2.5.4 through beta1) > > > > fix remaining gconf issues (2.5.4) > > > > update all examples to latest api (release candidate) > > I'll help with each one of these items, but since, for now, can't > > write C code, I think it's better to decide case by case. > > Be sure that I could write the most of the public interfaces.(I haven't > > tried with listeners yet...) > > I could also provide some examples. > > This would be a big help. I could also spend some time with > you and help you learn the C code if you are interested. It > really is quite easy. Of course that I'm interested... How could it be so easy? I wish I had some good pointers to start with ;) -- Luca De Rugeriis <pie...@li...> |
|
From: Jeffrey M. <ku...@zo...> - 2004-01-17 22:03:59
|
On Sat, 2004-01-17 at 14:37, Luca De Rugeriis wrote: > Il ven, 2004-01-16 alle 12:56, Jeffrey Morgan ha scritto: > I'm sorry Jeff couldn't reply faster, and thanks for the credit in the > authors file. > At the moment I'm stuck with an old pentium 200mhz that is a pain to use > :( but I'm about to upgrade my hardware. I hope I'll get the new stuff > in about 2 weeks. > It means that it takes me like a couple of hours to j-g. (apart from > compiling gnome libs). So I think I have to wait.... I hope you get a nice one!! > > > Here are my proposals for the items to be completed. I am sure > > > that I am missing numerous items so please respond and help > > > me build a complete list. > > > > > > complete/debug *Action* and UIManager classes (2.5.3) > > > implement the new FileChooser class (2.5.4) > > > update the Menu* classes to reflect the latest gtk (2.5.4) > > > update of gnome and gnomeui classes to current (beta1) > > > update all remaining gtk classes to current (2.5.4 through beta1) > > > fix remaining gconf issues (2.5.4) > > > update all examples to latest api (release candidate) > I'll help with each one of these items, but since, for now, can't > write C code, I think it's better to decide case by case. > Be sure that I could write the most of the public interfaces.(I haven't > tried with listeners yet...) > I could also provide some examples. This would be a big help. I could also spend some time with you and help you learn the C code if you are interested. It really is quite easy. > > update all documentation to latest api (release candidate) > I could do it with javadocs, but for the tutorial, a native speaker is > better. I should be able to update the tutorial after the code freeze. > > > > > Please help me complete the list and then we can determine who will > > > be working on each of the remaining items. > > > > I think it's quite complete, we also have the TODO.gtk file. I added a new section at the end of the TODO.gtk file listing all items that need to be updated as I start a code comparison between java-gnome and the latest gtk/gnome libs. These are what I mean when I stated: > > update all remaining gtk classes to current (2.5.4 through beta1) -Jeff |
|
From: Luca De R. <pie...@li...> - 2004-01-17 19:36:52
|
Il ven, 2004-01-16 alle 12:56, Jeffrey Morgan ha scritto: > Does anybody have any input on this posting? > > -Jeff I'm sorry Jeff couldn't reply faster, and thanks for the credit in the authors file. At the moment I'm stuck with an old pentium 200mhz that is a pain to use :( but I'm about to upgrade my hardware. I hope I'll get the new stuff in about 2 weeks. It means that it takes me like a couple of hours to j-g. (apart from compiling gnome libs). So I think I have to wait.... > > Release 2.5.3 is due Monday and our beta 1 with code freeze is due > > one month from Friday.. I would like to start a discussion > > on where we > > are with current work, what we should try to complete by each of the > > milestone dates, and who will be working on each of those tasks. OK. > > Here are my proposals for the items to be completed. I am sure > > that I am missing numerous items so please respond and help > > me build a complete list. > > > > complete/debug *Action* and UIManager classes (2.5.3) > > implement the new FileChooser class (2.5.4) > > update the Menu* classes to reflect the latest gtk (2.5.4) > > update of gnome and gnomeui classes to current (beta1) > > update all remaining gtk classes to current (2.5.4 through beta1) > > fix remaining gconf issues (2.5.4) > > update all examples to latest api (release candidate) I'll help with each one of these items, but since, for now, can't write C code, I think it's better to decide case by case. Be sure that I could write the most of the public interfaces.(I haven't tried with listeners yet...) I could also provide some examples. > > update all documentation to latest api (release candidate) I could do it with javadocs, but for the tutorial, a native speaker is better. > > > Please help me complete the list and then we can determine who will > > be working on each of the remaining items. > > I think it's quite complete, we also have the TODO.gtk file. |
|
From: Jeffrey M. <Jef...@Br...> - 2004-01-16 14:55:41
|
Great. As far as I know the project cvs has the latest snapshot of the site. I will need to add you to the project team so you will have write access to cvs. Please send me your sourceforge id and I will do this as soon as possible. You might take the time to review the list and send an email to all who are providing translations of the site and introduce yourself. Once you are setup as a project member I would recommend joining the java-gnome-hacker list. This list is where the project developers discuss the details of the project. Also, as stated in the request-for-help, the site needs to be updated. -Jeff > On Fri, 16 Jan 2004 08:57:54 -0500 > Jeffrey Morgan <Jef...@Br...> wrote: > > Im intersted because another guy is working with the spanish > translation of the manual. > > > Our site is currently quite out of date. The java-gnome team > > is interested in finding somebody that will take responsibility > > to stay informed on the status of the project, coordinate with > > all of the translators, and ensure that the site is kept > > up-to-date. If you are interested in this task please respond > > to this list. > > > > -Jeff > > > > > Hi, > > > Sorry for not responding to the website for a long time - > > > we have been > > > very busy preparing the code for the gnome bindings release. > > > It is clear > > > that we need to keep the website more updated. Your work on > > > the website > > > has been absolutely fantastic - it looks really great and > > > professional. > > > I was hoping that perhaps you would consider staying on > as webmaster. > > > Since you might not follow java-gnome development as > closely as us, I > > > will send you detailed information about what updates > need to be made > > > each time. In addition to updating the site, could you possibly > > > coordinate the translations too? we have quite a few > people writing > > > translations at the moment. One suggestion was to have a > > > "team" page on > > > the website which gives details of everyone in the java-gnome > > > team. This > > > could also be used to keep track of the status of the > translations. > > > > > > Please do edit my changes to make them sound better - english > > > never was > > > one of my strongest abilities. > > > > > > Current updates: > > > > > > Front page - add a new paragraph > > > Java-Gnome is committed to providing a reliable API for GNOME > > > to be used > > > in real applications. As such, we are part of the official <a > > > href="http://www.gnome.org/start/2.5/bindings">Gnome Bindings > > > Release</a>. This commits us to high quality releases and > a release > > > schedule closely following the main gnome release schedule. > > > > > > > > > News: > > > It might be best to replace this page with a link to > cvsweb. Then it > > > wouldn't require as much work to keep updated. > > > CVSweb is down at the moment, so I can't give a url. The file > > > needed is > > > java-gnome/common/NEWS > > > > > > Roadmap - please change to: > > > > > > We will follow the <a > > > href="http://www.gnome.org/start/2.5/bindings">Gnome > bindings release > > > schedule</a>. This includes making stable releases which > change API > > > every 6 months followed by a number of bug fix releases. > When gnome > > > start work on their next version, we will also start work > modifying > > > java-gnome for it. During this developmental period, we will make > > > developmental releases of our latest code roughly every two weeks. > > > > > > Version numbers will always follow GNOME/GTK version > numbers - i.e. > > > a.b.c where b being odd indicates a developmental release and even > > > indicating a stable release. > > > > > > Throughout all releases, we ... + last paragraph from > current roadmap > > > > > > Supporting New Libraries > > > As we get time, we also hope to provide support for new > > > libraries. These > > > will be released when ready and will not follow the schedule > > > until they > > > become reasonably complete and stable. Current plans for > new additions > > > include: > > > gnome-panel-applet > > > gtkhtml > > > libvte > > > Work has already started on some of these, but they are not > > > yet of good > > > enough quality to enter the gnome bindings release. > > > > > > > > > Download: > > > Stable Releases > > > The current stable release series is 0.8.x. This provides > support for > > > gtk 2.0 / gnome 2.2. The current release includes > tarballs for each > > > individual module, plus an all-in-one java-gnome tarball. Most > > > developers recommend using this tarball. > > > > > > Sources are available from <link>sourceforge</link> > > > > > > Precompiled Debian packages are available in the main > distribution. > > > <code>apt-get install libjava-gnome-doc libgtk0-java > libgnome0-java > > > libglade0-java</code> > > > > > > RPMs -- is anyone creating these? > > > > > > If anybody creates precompiled binary packages for other > platforms, > > > please send us a link. > > > > > > Developmental Releases > > > Current developmental releases are available in the gnome bindings > > > release at ftp.gnome.org/pub/GNOME/bindings/Java/. The all-in-one > > > tarball is available from link:sourceforge. > > > > > > The very latest code is available from <link>cvs > > > > > > Support (new section in download) > > > We are more than pleased to help new developers get started with > > > java-gnome. Please send your queries to > > > jav...@li.... > > > > > > Applications: > > > please replace the top two paragraphs with: > > > The following is a taste of some of the applications written with > > > Java-Gnome. If you would have written an application in > Java-Gnome, > > > please send a link to your website (with screenshots) and > we'll add it > > > to the list. > > > > > > Related links: > > > Please add the gnome bindings release. > > > > > > -- > > > .''`. Mark Howard > > > : :' : > > > `. `' http://www.tildemh.com > > > `- mh...@de... | mh...@ti... | mh...@ca... > > > > > > > > > ------------------------------------------------------- > > > This SF.net email is sponsored by: IBM Linux Tutorials. > > > Become an expert in LINUX or just sharpen your skills. Sign > > > up for IBM's > > > Free Linux Tutorials. Learn everything from the bash shell > > > to sys admin. > > > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > > > _______________________________________________ > > > java-gnome-developer mailing list > > > jav...@li... > > > https://lists.sourceforge.net/lists/listinfo/java-gnome-developer > > > > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by EclipseCon 2004 > > Premiere Conference on Open Tools Development and Integration > > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > > http://www.eclipsecon.org/osdn > > _______________________________________________ > > java-gnome-developer mailing list > > jav...@li... > > https://lists.sourceforge.net/lists/listinfo/java-gnome-developer > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > java-gnome-developer mailing list > jav...@li... > https://lists.sourceforge.net/lists/listinfo/java-gnome-developer > |
|
From: Jeffrey M. <Jef...@Br...> - 2004-01-16 11:56:51
|
Does anybody have any input on this posting? -Jeff > Release 2.5.3 is due Monday and our beta 1 with code freeze is due > one month from Friday.. I would like to start a discussion > on where we > are with current work, what we should try to complete by each of the > milestone dates, and who will be working on each of those tasks. > > Here are my proposals for the items to be completed. I am sure > that I am missing numerous items so please respond and help > me build a complete list. > > complete/debug *Action* and UIManager classes (2.5.3) > implement the new FileChooser class (2.5.4) > update the Menu* classes to reflect the latest gtk (2.5.4) > update of gnome and gnomeui classes to current (beta1) > update all remaining gtk classes to current (2.5.4 through beta1) > fix remaining gconf issues (2.5.4) > update all examples to latest api (release candidate) > update all documentation to latest api (release candidate) > > Please help me complete the list and then we can determine who will > be working on each of the remaining items. > > -Jeff > > > ------------------------------------------------------- > This SF.net email is sponsored by: Perforce Software. > Perforce is the Fast Software Configuration Management System offering > advanced branching capabilities and atomic changes on 50+ platforms. > Free Eval! http://www.perforce.com/perforce/loadprog.html > _______________________________________________ > java-gnome-hackers mailing list > jav...@li... > https://lists.sourceforge.net/lists/listinfo/java-gnome-hackers > |
|
From: Jeffrey M. <Jef...@Br...> - 2004-01-14 13:00:50
|
Release 2.5.3 is due Monday and our beta 1 with code freeze is due one month from Friday.. I would like to start a discussion on where we are with current work, what we should try to complete by each of the milestone dates, and who will be working on each of those tasks. Here are my proposals for the items to be completed. I am sure that I am missing numerous items so please respond and help me build a complete list. complete/debug *Action* and UIManager classes (2.5.3) implement the new FileChooser class (2.5.4) update the Menu* classes to reflect the latest gtk (2.5.4) update of gnome and gnomeui classes to current (beta1) update all remaining gtk classes to current (2.5.4 through beta1) fix remaining gconf issues (2.5.4) update all examples to latest api (release candidate) update all documentation to latest api (release candidate) Please help me complete the list and then we can determine who will be working on each of the remaining items. -Jeff |
|
From: Jeffrey M. <Jef...@Br...> - 2004-01-13 15:15:32
|
> OK, I will first get a final effort to the french translation. I will > save these javadoc minor enhancements for later (as they are less > important). > > I started with the GNOME-tutorial translation , so that it > helps me to > get into this project at the same time ;) > > I hope to send you the first french doc very soon. Please be aware that the tutorial will undergo some changes due to changes in the gtk/gnome libraries. -Jeff |
|
From: Eric Le G. <eri...@gi...> - 2004-01-13 15:12:53
|
Luca De Rugeriis wrote:
> Il lun, 2004-01-12 alle 11:12, Eric Le Goff ha scritto:
>
>>Luca De Rugeriis wrote:
>>
>>> [...]
>>>I hope this is clear. I'm just talkin about the javadocs ;)
>>>This is an example of what I was thinking:
>>>
>>> /**
>>> * Sets the {@link ToolTips} object to be used for ToolItem, the text to be
>>> * displayed as tooltip on the item and the private text to be used.
>>> *
>>> * @see ToolTips#setTip(Widget, String, String)
>>> * @param tooltips the {@link ToolTips} object to be used
>>> * @param tipText text to be used as tooltip text for ToolItem
>>> * @param tipPrivate text to be used as private tooltip text
>>> */
>>>
>>>As you see the description has caps and periods, while the parameters has none of them.
>>>Also a link which points to the class you are in should be avoided.
>>>(for example I would not write {@link ToolItem} but simply ToolItem}.
>>>
>>>What do you think? Old classes' javadocs could be fixed, for example, if
>>>you open the class to take a view of the source, then you can quickly
>>>fix the punctuation.
>>
>>Agreed. I had a quick look at java code with checkstyle and it seems
>>that many javadoc are also out of date (missing @return , etc..).
>>If you like I could do some javadoc review and submit you a patch.
>
> Great! but be aware that many liks are broken because of yet
> unimplemented classes/methods, so you have to guess what to do case by
> case.
>
>
>>Would you suggest a globl patch for this, or one per package ? class ?
>
> If you have a chance, it's better to have separated ones.
>
> Note also that your work on translation is far more important ;)
>
OK, I will first get a final effort to the french translation. I will
save these javadoc minor enhancements for later (as they are less
important).
I started with the GNOME-tutorial translation , so that it helps me to
get into this project at the same time ;)
I hope to send you the first french doc very soon.
Cheers
--Eric
|
|
From: Luca De R. <pie...@li...> - 2004-01-12 15:28:33
|
Il lun, 2004-01-12 alle 11:12, Eric Le Goff ha scritto:
> Luca De Rugeriis wrote:
> > [...]
> > I hope this is clear. I'm just talkin about the javadocs ;)
> > This is an example of what I was thinking:
> >
> > /**
> > * Sets the {@link ToolTips} object to be used for ToolItem, the text to be
> > * displayed as tooltip on the item and the private text to be used.
> > *
> > * @see ToolTips#setTip(Widget, String, String)
> > * @param tooltips the {@link ToolTips} object to be used
> > * @param tipText text to be used as tooltip text for ToolItem
> > * @param tipPrivate text to be used as private tooltip text
> > */
> >
> > As you see the description has caps and periods, while the parameters has none of them.
> > Also a link which points to the class you are in should be avoided.
> > (for example I would not write {@link ToolItem} but simply ToolItem}.
> >
> > What do you think? Old classes' javadocs could be fixed, for example, if
> > you open the class to take a view of the source, then you can quickly
> > fix the punctuation.
> Agreed. I had a quick look at java code with checkstyle and it seems
> that many javadoc are also out of date (missing @return , etc..).
> If you like I could do some javadoc review and submit you a patch.
>
> Would you suggest a globl patch for this, or one per package ? class ?
Sorry, I hadn't read the mail from Jeff: it's ok for the all in one
patch ;)
--
Luca De Rugeriis <pie...@li...>
|
|
From: Luca De R. <pie...@li...> - 2004-01-12 15:26:38
|
Il lun, 2004-01-12 alle 11:12, Eric Le Goff ha scritto:
> Luca De Rugeriis wrote:
> > [...]
> > I hope this is clear. I'm just talkin about the javadocs ;)
> > This is an example of what I was thinking:
> >
> > /**
> > * Sets the {@link ToolTips} object to be used for ToolItem, the text to be
> > * displayed as tooltip on the item and the private text to be used.
> > *
> > * @see ToolTips#setTip(Widget, String, String)
> > * @param tooltips the {@link ToolTips} object to be used
> > * @param tipText text to be used as tooltip text for ToolItem
> > * @param tipPrivate text to be used as private tooltip text
> > */
> >
> > As you see the description has caps and periods, while the parameters has none of them.
> > Also a link which points to the class you are in should be avoided.
> > (for example I would not write {@link ToolItem} but simply ToolItem}.
> >
> > What do you think? Old classes' javadocs could be fixed, for example, if
> > you open the class to take a view of the source, then you can quickly
> > fix the punctuation.
> Agreed. I had a quick look at java code with checkstyle and it seems
> that many javadoc are also out of date (missing @return , etc..).
> If you like I could do some javadoc review and submit you a patch.
Great! but be aware that many liks are broken because of yet
unimplemented classes/methods, so you have to guess what to do case by
case.
> Would you suggest a globl patch for this, or one per package ? class ?
If you have a chance, it's better to have separated ones.
Note also that your work on translation is far more important ;)
--
Luca De Rugeriis <pie...@li...>
|
|
From: Jeffrey M. <Jef...@Br...> - 2004-01-12 11:35:56
|
> Agreed. I had a quick look at java code with checkstyle and it seems > that many javadoc are also out of date (missing @return , etc..). > If you like I could do some javadoc review and submit you a patch. > > Would you suggest a globl patch for this, or one per package ? class ? Thanks Eric. This would be great. One patch would seem easier to apply on our side if that is ok. -Jeff |
|
From: Eric Le G. <eri...@gi...> - 2004-01-12 10:07:48
|
Luca De Rugeriis wrote:
> [...]
> I hope this is clear. I'm just talkin about the javadocs ;)
> This is an example of what I was thinking:
>
> /**
> * Sets the {@link ToolTips} object to be used for ToolItem, the text to be
> * displayed as tooltip on the item and the private text to be used.
> *
> * @see ToolTips#setTip(Widget, String, String)
> * @param tooltips the {@link ToolTips} object to be used
> * @param tipText text to be used as tooltip text for ToolItem
> * @param tipPrivate text to be used as private tooltip text
> */
>
> As you see the description has caps and periods, while the parameters has none of them.
> Also a link which points to the class you are in should be avoided.
> (for example I would not write {@link ToolItem} but simply ToolItem}.
>
> What do you think? Old classes' javadocs could be fixed, for example, if
> you open the class to take a view of the source, then you can quickly
> fix the punctuation.
Agreed. I had a quick look at java code with checkstyle and it seems
that many javadoc are also out of date (missing @return , etc..).
If you like I could do some javadoc review and submit you a patch.
Would you suggest a globl patch for this, or one per package ? class ?
--Eric
|
|
From: Jeffrey M. <ku...@zo...> - 2004-01-11 16:01:17
|
Not me. On Sun, 2004-01-11 at 09:24, Luca De Rugeriis wrote: > I'm about to write the public interface for it. I hope no-one is already > doing this. |
|
From: Luca De R. <pie...@li...> - 2004-01-11 14:24:40
|
I'm about to write the public interface for it. I hope no-one is already doing this. -- Luca De Rugeriis <pie...@li...> |
|
From: Luca De R. <pie...@li...> - 2004-01-10 19:23:38
|
I saw, in gtk-docs too, that there are little inconsistencies in the
description fields and in the @param fileds, like cap letter at the
beginning of a phrase or the period at the end.
I would suggest to follow a common line for this, so our javadocs will
look more professional:
The main descriptions of methods and classes should always use caps at
the beginning of periods and obviously periods at the end. They should
also contain links to every thing that can be linked.
Description of parameters and returned values are like minimal
statements, so the shouldn't begin with a cap and the should have no
period at the end.
I hope this is clear. I'm just talkin about the javadocs ;)
This is an example of what I was thinking:
/**
* Sets the {@link ToolTips} object to be used for ToolItem, the text to be
* displayed as tooltip on the item and the private text to be used.
*
* @see ToolTips#setTip(Widget, String, String)
* @param tooltips the {@link ToolTips} object to be used
* @param tipText text to be used as tooltip text for ToolItem
* @param tipPrivate text to be used as private tooltip text
*/
As you see the description has caps and periods, while the parameters has none of them.
Also a link which points to the class you are in should be avoided.
(for example I would not write {@link ToolItem} but simply ToolItem}.
What do you think? Old classes' javadocs could be fixed, for example, if
you open the class to take a view of the source, then you can quickly
fix the punctuation.
Also, what about the @since and @author tags?
Are we going to use them? If so, I'll commit new classes with these tags
included, (and maybe fix some older one).
Sorry for the long mail, I know this is not vital, but it will make our
docs more consistent.
--
Luca De Rugeriis <pie...@li...>
|
|
From: Jeffrey M. <ku...@zo...> - 2004-01-10 14:16:04
|
On Fri, 2004-01-09 at 14:26, Luca De Rugeriis wrote: > Il ven, 2004-01-09 alle 13:00, Jeffrey Morgan ha scritto: > > What do you think? Should we place names beside the items > > in the NEWS file? > Yes, it's nice! (but also removing the gtk folks' ones) Then please go through the common/NEWS file and take credit for your work. Just place your name (example: [Mickey Mouse]) beside the item you worked on. -Jeff |
|
From: Jeffrey M. <ku...@zo...> - 2004-01-10 00:22:46
|
When I try to build now I am getting an error. The build is trying to create a synlink to /usr/local/lib/libgtkjava2.3.so when I just compile the proejct. -Jeff |
|
From: Luca De R. <pie...@li...> - 2004-01-09 19:27:32
|
Il ven, 2004-01-09 alle 13:00, Jeffrey Morgan ha scritto: > What do you think? Should we place names beside the items > in the NEWS file? Yes, it's nice! (but also removing the gtk folks' ones) -- Luca De Rugeriis <pie...@li...> |
|
From: Mark H. <mh...@ca...> - 2004-01-09 08:34:04
|
Thanks Jeff. You are doing an amazing job. Hopefully I'll get a new garnome at the weekend - I'm sure java-gnome will be at the top of my list of distractions from real work :) -- .''`. Mark Howard : :' : `. `' http://www.tildemh.com `- mh...@de... | mh...@ti... | mh...@ca... |
34 messages has been excluded from this view by a project administrator.
