Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2009-08

Jedi Code Formatter - sync with upstream

3 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Graeme Geldenhuys

Hi,

How often is JCF changes merged/synced from upstream?

What is the correct development procedure for JCF in Lazarus? Because I make changes in my JCF code that is included with Lazarus. But last time I created a patch and added to Mantis, I was told to rather submit it in the upstream JCF project on sourceforge. I don't think this is ideal development path.

Couldn't it be committed in Lazarus repository and then pushed from Laz repo to JCF repo in SourceForge by whoever has write access to both?

Anyway, I have a few more fixes locally, but ain't sure where it must go. Lazarus Mantis bug report or JCF SourceForge project. The problem is, I do not track the JCF SourceForge project, so I don't know is such bugs have already been fixed or not.

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/

Reply by email

Paul Ishenin
to Graeme Geldenhuys
Graeme Geldenhuys wrote
How often is JCF changes merged/synced from upstream?

Depends on changes JCF project have. If it is only some version change or another non-functional changes then I see no reason to update lazarus copy.

Show quoted text 5 lines
What is the correct development procedure for JCF in Lazarus? Because I make changes in my JCF code that is included with Lazarus. But last time I created a patch and added to Mantis, I was told to rather submit it in the upstream JCF project on sourceforge. I don't think this is ideal development path.

Correct is to report your changes to the JCF project. But I see at moment Anthony (main JCF developer) does not do anything with his project. Therefore if it is something related to FPC you can send your patches to me or post them to our tracker to the packages subproject.

Show quoted text 7 lines
Couldn't it be committed in Lazarus repository and then pushed from Laz repo to JCF repo in SourceForge by whoever has write access to both? Anyway, I have a few more fixes locally, but ain't sure where it must go. Lazarus Mantis bug report or JCF SourceForge project. The problem is, I do not track the JCF SourceForge project, so I don't know is such bugs have already been fixed or not.

Best regards,
Paul Ishenin.

Reply by email

Graeme Geldenhuys
to Paul Ishenin
Paul Ishenin wrote
Correct is to report your changes to the JCF project. But I see at moment Anthony (main JCF developer) does not do anything with his

That was my problem... what if upstream takes forever to commit a supplied patch. That means Lazarus stays with a buggy JCF when it doesn't have to be.

project. Therefore if it is something related to FPC you can send your patches to me or post them to our tracker to the packages subproject.

All my patches will be related to FPC. ;-) That's the only compiler I use, and Lazarus is the only IDE I use. Currently the JCF (v2.44) in Lazarus produces many inconsistency compared to jcfNotepad.exe version 2.38.

So I run most of my code formatting externally via jcfNotepad, but would really like to start using JCF inside Lazarus IDE. And no, I can't setup jcfNotepad.exe via Lazarus Tools menu, because I run Lazarus under Linux and jcfNotepad.exe is a Windows app. <I tried though> ;-)

I'll start committing my patches to Mantis.

Regards,
- Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/

Reply by email