Log in

No account? Create an account

Previous Entry | Next Entry

My ideas

I am too lazy to see if this has been posted before.

Here's my suggestions for changes:

1.Clear mood to blank after each post (or have the option to)
2.Go back to default journal after each post (love those personal posts to unrelated communities, heh)

So yeah.


( 14 comments — Leave a comment )
Jul. 2nd, 2004 09:21 am (UTC)
2.Go back to default journal after each post (love those personal posts to unrelated communities, heh)

I give that a serious seconding.
Jul. 2nd, 2004 09:47 am (UTC)
Make that a third... I've been paranoid about that for too long... :-D

And a second for the mood change.

Great program, though, makes my life much easier.
Jul. 2nd, 2004 10:42 am (UTC)
I can only verify the first, at the moment, but I am almost positive that both of those features exist in DEVEL_1 (the 1.60 testing release).

The only real issues with the 1.60 testing release are with friend group modification. That still needs work. Normal posting should work, though, so you may be able to use that.
Jul. 2nd, 2004 10:50 am (UTC)
Jul. 2nd, 2004 11:54 am (UTC)
I post links to the milestone builds whenever I have had time to work on it. The last one I posted in this community is:

Check it out if you are interested and tell me if there are any glaring bugs. (The friend group modification stuff is quite broken and I know about that but there may be some other rough edges which I am unaware of).
Jul. 2nd, 2004 04:51 pm (UTC)
login bugs?
what happened to the login bugs? did those get fixed? last devel build i tried, iJournal could never log in at all. i posted messages from the console as well here
Jul. 2nd, 2004 06:06 pm (UTC)
Re: login bugs?
Unfortunately I couldn't reproduce that so it isn't fixed in that build but I know that it isn't a problem unique to you since a few users were able to reproduce the problem.

It seems to be an issue with some old settings, I think, which part of the program is picking up and using as if it were still the old design (that is, assuming that it could use a string where an array is currently expected).

I am not totally sure how to proceed with this issue. I did have an idea to make a special build which would give me specific crash lines which I could send to you. I may have time to do that later on today, actually. It just requires me writing a little app to pollute the code with tons of debugging data. I was going to try to do it conservatively but it will be easier to be liberal about and it may even work better. I will see what I can do.
Jul. 2nd, 2004 06:43 pm (UTC)
Re: login bugs?
As a corollary to my last post, I will probably be offline until saturday night since I will be on my way home from WWDC (they are kicking me out, in fact).
Jul. 4th, 2004 12:25 am (UTC)
Re: login bugs?
Ok, I am now back home so I had a chance to write a program which would riddle the iJournal source with thousands of tracing statements. Here is a build which you can use to help me debug the iJournal:

NOTE: using this build of iJournal will dump TONS of output into the console log files! This isn't a problem if it isn't used often but using the build regularly could start to use a lot of drive space to store the traces in the logs so don't use it regularly. In fact, if you are comfortable with running Cocoa apps from the command line, that is preferred since you will be able to redirect the trace data so that it never stays in the console. (what this build does is write a line of output to the console every time a function is called - so this is a large amount of output).

That said, try running this and then quitting as soon as you realize that the problem has been duplicated. If you run it from the command line, send me the file containing the full trace (if you need more contact data, get in touch) or, if you are running it normally, post the last 100 (more or less) lines of the Console.app dump in response to this.

Thank you very much for helping me out with this problem.
Jul. 4th, 2004 07:32 am (UTC)
i have no issues with the terminal; however, i am too lazy to look up what i need to do to redirect output. something like a pipe character, right (||)? lol....i don't remember too well...

and thanks, i'm glad to help.
Jul. 4th, 2004 10:25 am (UTC)
Re: terminal
Normally, you use ">" to redirect to a file but this us logging to standard error so you need to use "2>":

So, if you are in the same directory as the iJournal application, you could type something like:
./iJournal.app/Contents/MacOS/iJournal 2> output.log
Jul. 4th, 2004 06:21 pm (UTC)
here goes...
well, i did it all, and copied the output, which you can find here

first error occurs at 2004-07-04 20:50:22.356; it can't make the connection for the newVersion action. technically, this shouldn't really matter.
next problem at 20:50:22.739, following which is that "selector not recognized" error (note: it's under -[iJournalController _extractArchive:], which isn't the thing that normally shows up in the console)
at 20:50:30.955 is our predecessor to the real problem. i'm no programmer, but i have a feeling that because the extract failed (see previous line), now it's failing to insert the values it was supposed to extract.

later, I tried doing Login As... and the result was 20:52:17.637 iJournal[13995] *** +[NSArray arrayWithObject:]: attempt to insert nil . i clicked on the little arrow to view the drop-down menu for usernames, and there was nothing there! absolutely nothing. not only do I have 2 usernames, even if i had just one it should show up.

at the end, I think that this build is having problems with the Keychain. it seems that it can't retrieve the usernames and passwords, and thus is unable to log in, because it has no data to send.

hehe....now how close am I to being right (w/no programming experience)??
Jul. 4th, 2004 06:43 pm (UTC)
Re: here goes...
Well, the only problems which can occur are with the preference file and the key chain. Since this is a problem during login, it has to be the key chain.

There are some issues with the 1.60 use of the key chain since I am trying to come up with some solid rules about exactly what needs to be put there whereas the earlier implementations would just stick the data there. There is likely some problem there.

Thanks for the log, I will take a look at it.
Jul. 2nd, 2004 08:40 pm (UTC)
Is this not done for Reset After Post in the Preferences?
( 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