Open Sourcing the Journler code

[phildow]

http://developer.getsprouted.com/downloads/
email: developer-at-journler.com
(replace -at- with @ symbol)

I am going to begin open sourcing the Journler code. The code is not ready for it, but the project needs new momentum and I need extra eyes.

There are currently plans to open source five frameworks associated with the Journler project.

The first two are already available. They are the Sprouted Utilities and Sprouted Interface frameworks. I updated the Sprouted Utilities framework this evening and will post an updated version of the Interface code probably tomorrow.

The third framework is Sprouted AVI. It is responsible for the audio-video recording and picture taking in Journler, that nifty window that lets you do all three in one place. I posted the code for this framework this evening.

The last two frameworks are the Journler Core and the Journler Interface frameworks. These are the two that are not ready, but I am going to be releasing them in the coming days anyway.

Journler Core is the data layer. It is responsible for loading the journal and providing the Interface with access to folders, entries and resources. Journler Interface includes 95% of the rest of Journler's code: windows, tabs, custom controls and so on. It displays the information in the data layer.

I am aiming to release the Core code in just a few days. It would delight me if developers out there interested in the project were willing to take a look at it. The code is a mess, but that's why it -- and I -- need you.

The interface code will take a bit longer, as I haven't completely untangled it from the application layer.

I have established a new email address for folks interested in the code. You can reach me at developer-at-journler.com, replace the -at- with an @ symbol.

The code may be downloaded from http://developer.getsprouted.com/downloads/

Once I figure Subversion out I'll also establish an svn repository for the code. In the meantime I'll keep you updated as I make additions to that page and as the code changes.

[pmccarvalho]

Hi Phil,

I hope everything is Ok with you. This is a great news for Journler fans! Let's see if any talented developers come and help in the development on what still is the best journal application ever.

Just an idea, I moved my Journler folder to the documents folder and tried to synchronise it between different computer using MS Live Mesh. The files are moved from the main computer to the web interface and from that to the other computer, the entries title appear on the second computer but not the text inside. Do you happen to know if this has something to do with permissions? You might be asking why I am bothering you with this now but the reality is that cloud backup and sync are what all the journal applications are trying to do know and if you could make Journler work through Live Mesh the sync problem between computers would be completely automatised without the need of setting up servers...

Best and keep up with the good work

[justG]

[Curare]

[firedoctor]

+1 for Git and GitHub, or Mercurial and bitbucket (would prefer Mercurial, but can work with the community's choice). These DCVS systems are vastly superior to SVN, especially with a distributed community.

I'd like to contribute and help out here. It mightbe helpful if Phil kept an eye on the big picture, and suggested work areas and tasks, and we can start pitching in and help cleanup.

[firedoctor]

Phil,

You also need to think about what license you will be open sourcing under.

[firedoctor]

Now that Phil has made his end of development announcement, I'm interested in collaborating with anyone else who wants to get the open sourced code working.

Does anyone have a github/bitbucket/google code site set up yet for this code?

[macmike]

I would also be interested in collaborating on this as well