User:ConradPino/Join Project JEDI
Contents
21 Jan 2010 00:55:35 -0800
From: "Conrad T. Pino" <>
To: "'Christian Wimmer'" <>
Subject: RE: Join jedi-apilib
Date: Thu, 21 Jan 2010 00:55:35 -0800
- Hello Conrad,
Hi Christian,
- I need to make clear that I am not the head of all JEDI projects but just JEDI API & WSCL. Thus I cannot make decisions for all projects. If you want to change something in all projects you need to ask - unfortunately - all project leader separately. The newsgroups are the place to ask all JEDI members at once.
Thank you.
- Okay, I need to say that I didn't work with the wiki at all. I know it would be great but currently I don't want to put too much effort into this area. I just don't have time for it.
Understood, who are players to contact to get changes for http://sourceforge.net/projects/projectjedi/ project?
- This is the code style guide for JEDI component library. The styleguide for JEDI API isn't really written down (not that I know of). I didn't have time yet to do so but I also think that it isn't urgent for two reasons:
- 1. 99% of the code is just declarations directly converted from C/C++ which does not leave so much room for changes.
- 2.There is a template file that proved to be really useful (_JwaTemplate.pas) because people use this file and put the conversions into it in the fashion of all the other files. (declarations, static and dynamic loading) People don't want to read big guides how to add features. They just want to get starting... and with some consulting and human examination this works great.
- Furthermore, applying a strict style guide to all existing files means a lot of work and the high probability of errors (I don't speak about compiler errors but about the ones you detect only when running the code). Don't get me wrong. I am a documentation fetishist (as JWSCL code proves) but we shouldn't put too much work into this area. It could be used in better places. But if you insist on doing it I won't be in the way! (The other way around: I support it.)
I agree we should set this aside. I disagree about labor cost. I've done before with sed script and Subversion can verify only whitespace changed.
- Which one exactly?
I'll setup a test compile and run it this weekend.
- I cannot do anything about the others. Sorry. That is the price of a missing commander-in-chief. There was a time before mine when there was a JEDI council but it disappeared. I am here to grant source access and to be a contact partner.
Understood; joining your subprojects (JWAPI JWSCL) is fine.
- I can grant source access to you. Just tell me your sourceforge username and user ID (for verification) and I will add you.
conradpino 1173801 http://sourceforge.net/users/conradpino
- The main platform for JEDI API&WSCL is http://blog.delphi-jedi.net I have full control of it.
Thank you.
- I think you should ask this in the newsgroups (e.g. j.general).
Thank you.
- I can grant access only to SVN of the JEDI API&WSCL project.
Thank you; I accept.
- Yes, I hope this is a good start. However, please contact me if you want to do big changes. Usually, this means that they need to be tested thoroughly in a separate branch. JWSCL and a lot of customers depend on the JWA. But it is good to hear that people still care about the project.
Please be assured I shall make NO commits without prior notice until another consensus emerges.
- Thanks
Your welcome and thank you,
- Christian
Conrad
20 Jan 2010 17:58:59 +0100
Date: Wed, 20 Jan 2010 17:58:59 +0100
From: Christian Wimmer <>
To: "Conrad T. Pino" <>
Subject: Re: Join jedi-apilib
- Hello Christian,
Hello Conrad,
I need to make clear that I am not the head of all JEDI projects but just JEDI API & WSCL. Thus I cannot make decisions for all projects. If you want to change something in all projects you need to ask - unfortunately - all project leader separately. The newsgroups are the place to ask all JEDI members at once.
- Background:
- I'm proficient in all Windows flavors, Debian Linux, Apache and Tomcat.
- I've adopted JEDI on Delphi 6 as an alternative to upgrading Delphi.
- I relax by doing MediaWiki editing (Wikipedia) and ProjectJEDIWiki:
- http://wiki.delphi-jedi.org/index.php?title=Special:Contributions/ConradPino
- I'm proficient with CVS and Subversion.
Okay, I need to say that I didn't work with the wiki at all. I know it would be great but currently I don't want to put too much effort into this area. I just don't have time for it.
- Source code discoveries:
- 1. While working with JWAPI I noted coding style inconsistencies see attached patch.
- 2. I use TextPad for editing Delphi source and when I first saved my edits to create the patch I noted TextPad made a LOT of whitespace changes. After researching the topic I found Project JEDI source code is whitespace NOT compliant with style guide:
- http://wiki.delphi-jedi.org/index.php?title=Project_JEDI_Delphi_Language_Style_Guide
- Project JEDI files contain Tabs and trailing whitespace on lines and end of file.
This is the code style guide for JEDI component library. The styleguide for JEDI API isn't really written down (not that I know of). I didn't have time yet to do so but I also think that it isn't urgent for two reasons:
- 99% of the code is just declarations directly converted from C/C++ which does not leave so much room for changes.
- There is a template file that proved to be really useful (_JwaTemplate.pas) because people use this file and put the conversions into it in the fashion of all the other files. (declarations, static and dynamic loading) People don't want to read big guides how to add features. They just want to get starting... and with some consulting and human examination this works great.
Furthermore, applying a strict style guide to all existing files means a lot of work and the high probability of errors (I don't speak about compiler errors but about the ones you detect only when running the code). Don't get me wrong. I am a documentation fetishist (as JWSCL code proves) but we shouldn't put too much work into this area. It could be used in better places. But if you insist on doing it I won't be in the way! (The other way around: I support it.)
- 3. The Style Guide says nothing regarding trailing whitespace and perhaps it should.
- 4. The head revision of JwaWindows.pas does NOT compile under Delphi 6, file deleted from tree but not from JwaWindows.pas file.
Which one exactly?
- Project discoveries:
- 5. This is my understanding of Project JEDI's scope:
- 6. Project JEDI lives in many places:
- 7. Some Project JEDI subprojects don't have public Source Code Repositories and IMO should if only for consistencies sake.
I cannot do anything about the others. Sorry. That is the price of a missing commander-in-chief. There was a time before mine when there was a JEDI council but it disappeared. I am here to grant source access and to be a contact partner.
I can grant source access to you. Just tell me your sourceforge username and user ID (for verification) and I will add you.
- ProjectJEDIWiki and WWW Site:
- I want to be clear; I like MediaWiki; it's very strange technology but the immediate gratification is hard to beat. On the other hand; a controlled edit access Project JEDI Portal doesn't have to be patrolled and policed.
The main plattform for JEDI API&WSCL is http://blog.delphi-jedi.net I have full control of it.
- 8. Each can serve a good purpose but for labor conservation sake it shouldn't be the same purpose. A discussion about how and when to use either might be worthwhile.
- 9. Right now ProjectJEDIWiki is feature poor; if ProjectJEDIWiki has a future I'd like to see specific MediaWiki features enabled and feature extensions installed.
I think you should ask this in the newsgroups (e.g. j.general).
- What's most important to me is establishing a path for bug fixes back into Project JEDI repository so I can avoid tracking Project JEDI in my source code repository.
I can grant access only to SVN of the JEDI API&WSCL project.
- I believe I've enumerated sufficient choices so I ask where would you like me to begin?
- Thank you,
- Conrad
Yes, I hope this is a good start. However, please contact me if you want to do big changes. Usually, this means that they need to be tested thoroughly in a separate branch. JWSCL and a lot of customers depend on the JWA. But it is good to hear that people still care about the project.
Thanks
Christian
19 Jan 2010 01:16:33 -0800
From: "Conrad T. Pino" <>
To: "'Christian Wimmer'" <>
Subject: RE: Join jedi-apilib
Date: Tue, 19 Jan 2010 01:16:33 -0800
Hello Christian,
Background:
I'm proficient in all Windows flavors, Debian Linux, Apache and Tomcat.
I've adopted JEDI on Delphi 6 as an alternative to upgrading Delphi.
I relax by doing MediaWiki editing (Wikipedia) and ProjectJEDIWiki:
http://wiki.delphi-jedi.org/index.php?title=Special:Contributions/ConradPino
I'm proficient with CVS and Subversion.
Source code discoveries:
- While working with JWAPI I noted coding style inconsistencies see attached patch.
- I use TextPad for editing Delphi source and when I first saved my edits to create the patch I noted TextPad made a LOT of whitespace changes. After researching the topic I found Project JEDI source code is whitespace NOT compliant with style guide:
- http://wiki.delphi-jedi.org/index.php?title=Project_JEDI_Delphi_Language_Style_Guide
- Project JEDI files contain Tabs and trailing whitespace on lines and end of file.
- The Style Guide says nothing regarding trailing whitespace and perhaps it should.
- The head revision of JwaWindows.pas does NOT compile under Delphi 6, file deleted from tree but not from JwaWindows.pas file.
Project discoveries:
- This is my understanding of Project JEDI's scope:
http://wiki.delphi-jedi.org/index.php?title=Project_JEDI_Subprojects
- Project JEDI lives in many places:
- Some Project JEDI subprojects don't have public Source Code Repositories and IMO should if only for consistencies sake.
ProjectJEDIWiki and WWW Site:
I want to be clear; I like MediaWiki; it's very strange technology but the immediate gratification is hard to beat. On the other hand; a controlled edit access Project JEDI Portal doesn't have to be patrolled and policed.
- Each can serve a good purpose but for labor conservation sake it shouldn't be the same purpose. A discussion about how and when to use either might be worthwhile.
- Right now ProjectJEDIWiki is feature poor; if ProjectJEDIWiki has a future I'd like to see specific MediaWiki features enabled and feature extensions installed.
What's most important to me is establishing a path for bug fixes back into Project JEDI repository so I can avoid tracking Project JEDI in my source code repository.
I believe I've enumerated sufficient choices so I ask where would you like me to begin?
Thank you,
Conrad
18 Jan 2010 17:28:02 +0100
Date: Mon, 18 Jan 2010 17:28:02 +0100
From: Christian Wimmer <>
To: "Conrad T. Pino" <>
Subject: Re: Join jedi-apilib
Hello Conrad,
thank you for your offering to participate in JEDI API project.
Do you have any specific idea what or how to contribute? Otherwise I can give you some ideas if you like (basic ideas can be found here:
http://blog.delphi-jedi.net/2008/05/02/wishlist/).
Furthermore there is the other part of JEDI API: the project JWSCL.
Would you have any intention to participate in this project, too?
I know that writing just API functions can be very dull. Therefore I suggest to everybody to also write an example application for demonstration. Of course it is also possible to contribute an article on our blog:
http://blog.delphi-jedi.net
Well, the last two parts are only optional, but they will make the API more comprehensible.
Best regards,
Christian Wimmer
PS:
My timezone:
GMT+1, Stuttgart, Germany
15 Jan 2010 22:54:54 +0000
To: dezipaitor <>
From: "Conrad T. Pino" <>
Subject: Join jedi-apilib
Date: Fri, 15 Jan 2010 22:54:54 +0000
Message body follows:
I'm developing using this project; in appreciation I'd like to contribute back to the project. I'm an experienced developer proficient with SVN. I've contributed to CVS project.
My WWW site is http://www.pino.com/
Please let me know how to contribute or commit patches.
Best regards,
Conrad T. Pino
--
This message has been sent to you, a registered SourceForge.net user, by another site user, through the SourceForge.net site. This message has been delivered to your SourceForge.net mail alias. You may reply to this message using the "Reply" feature of your email client, or using the messaging facility of SourceForge.net at:
https://sourceforge.net/sendmessage.php?touser=1173801
