Log in

No account? Create an account

Previous Entry | Next Entry

iJournal 2.0 development started

Now that my move is complete, and I'm recovering from my physical demonstration of Newton's Second Law, I've begun the design and feature layout of iJ2. All development on the 1.x branch has stalled, and I think there's a moral issue with the split that occurred within the project. Quite a few of the goals that were set for the 1.x branch were reached, and coding around the initial design flaws made things more complicated than they had to be. While the CVS repository is available on sourceforge.net allowing anyone to make changes and have them committed by those who have source tree access, development has been at a virtual standstill for months. My own view is that the code is complicated enough that newbies don't really have a way to jump in and just start coding. Abstracting the code out to APIs didn't really happen the way it should have, and there's lots of duplicated code that should be eliminated. I've thought long and hard about this, and looked at what time people have had to commit to the project, as well as my own personal time. Life gets in the way, and even great projects get moldy and stagnant. I've decided that I will commit my resources to the new branch and continue to do release engineering on the old branch should code get committed.

Bugs and feature requests can be dropped at http://bugs.warped.com (it's not as complicated as it looks).

For you loyal iJournal users and fans, thank you. I listen to your requests, complaints, and request for changes, and do my best to implement them within the realm they need to be in.

Those who are curious of what this radical change will look like, as well as all of the features it will have in it, will have to wait until the code is at a functioning state. I don't like to announce vaporware, or get hopes up high and then make people wait.

However, what I will say is that as dramatic as iJournal was in the beginning (and even now) compared to other blogging clients, iJ2 will prove to be worth the wait.


( 14 comments — Leave a comment )
Aug. 26th, 2004 06:03 am (UTC)
iJournal is already my preferred OS X client, and I've tried several of the others - so I'm eager to see the improvements in iJ2.

Thanks for all your hard work - you're doing a very good job.
Aug. 26th, 2004 06:32 am (UTC)
Part of my problem with the initial code base was that there was too little abstraction between the different components. That is, anyone wanting to add a button to the UI usually had to know the networking protocol (which didn't make sense).

Will you be basing the 2.0 code on the original code, the DEVEL_1 code, or something new, altogether? Should I continue work on patching up the DEVEL_1 and pruning the now redundant code? I have been really busy for the last 4 months but the term is almost over so I will have some time in about a week.

As for 2.0 ideas, I would like to say that the 1.x GUI is quite effective but more of the underlying operations need to be easier to hook into (maybe an event-based network abstraction, or something). The network abstraction code in DEVEL_1 may be a way to keep the network API a black box.
Aug. 26th, 2004 09:22 am (UTC)
[i]Will you be basing the 2.0 code on the original code?[/i]

God, I hope not. That was some of the craziest spaghetti code I've seen in a long while. There was UI depending on data, data depending on UI, etc.

It's not a *huge* app -- I'd like to see development start from a clean slate so that some of the major design issues with the app can be worked out.

My two cents,
Aug. 26th, 2004 09:24 am (UTC)
Whoops, I confused my HTML and UBB forum code again -- that [i] means italic :-)
Aug. 30th, 2004 06:29 am (UTC)
I never figured out why UBB had to have its own code, instead of just using HTML. How different is [i] from <i>?

And I'm looking forward to the new iJournal. I use Xjournal but detest its UI.
Sep. 6th, 2004 08:44 am (UTC)
It's a security issue, from preventing people from using HTML commands that aren't authorized and therefore PHP commands(since you can embed PHP code in an HTML script) or other nasty things in a comments site.
Aug. 26th, 2004 02:51 pm (UTC)
Sep. 6th, 2004 08:46 am (UTC)
New Development
So, I guess my question is, I'm a new developer, should I just download the iJournal source and start picking at it? or wait until 2.0 comes out?
Sep. 8th, 2004 03:49 pm (UTC)
the planetcryo link was down, but I found it here: http://www.os10.org/osx/iJournal.dmg.gz . I noticed that the sourceforge downloadable is only version 1.52.
Sep. 11th, 2004 06:07 am (UTC)
That didn't work for me either.

Sep. 11th, 2004 10:18 am (UTC)
Sep. 10th, 2004 06:41 am (UTC)
I use iJournal for my Blurty account, and I recently switched computers. What I really want to do is reinstall iJournal, not copy it onto my new HD. However, the link for iJournal goes to a server that doesn't exist/isn't up right now, and I was wondering how I could go about getting that.

In the meantime, I eagerly await v2.

Oct. 16th, 2004 02:26 pm (UTC)
i just downloaded ijournal, but i cant seem to log in.
everytime i click okay after getting in the user details and password, it says "last communication successful" but yet it returns me to the same screen again, asking me for my login details.
i thought my password was wrong, so i went back to www.livejournal.com and there wasnt anything thats different.

so help anyone?
Nov. 23rd, 2004 08:06 pm (UTC)
Thanks for a good client. If you need beta testers I'm happy to be involved (I beta'd SPSS for Mac and Atlas/ti for Windows). I give good beta. . .
( 14 comments — Leave a comment )


iJournal: Official LiveJournal Client for Mac OS X
iJournal Home

Latest Month

June 2011
Powered by LiveJournal.com
Designed by Lilia Ahner