 New Instant Outliner 
I have converted the IO code in iJot to adapt to the new instant outline framework, which now lives outside of Scripting2 in OPML Editor and has a brand new server of its own at instant.opml.org.
I have a new bunch of active buddies showing up in the buddies outline, but apparently dropped some of my previous ones from the Scripting2 implementation, most notable matt, amy and kellie.
I'm posting this from iJot, to make sure everything is back in order on the Scripting2 side.
 8/11/2010; 5:45:38 PM. .
Another Test today
This is subtext.
Posting from Scripting2.
Now posting from iJot.
8/11/2010; 12:28:26 PM. .
 Buddies Outline First Draft
Some details on iJot's dev weblog.
8/10/2010; 6:28:36 PM. .
An Instant Outline in iJot phase 1
I've learned enough of the inner working of the Instant Outliner in Scripting2 to start working on my first task: showing IO's buddies outline in iJot.
I need to create a 'buddies' tab in the right pane, which will only appear to logged on users, same as 'my site' as opposed to demo in the left sidebar.
To display the buddies outline in there, I need to add some backend code to call scripting2.getallinstantoutlines via XML-RPC, then render a combination of all returned OPML strings into a DHTML outline.
Cross posted to Scripting2 Reverse Engineering.
7/29/2010; 12:00:00 AM. .
I just polished the Scripting2 posting.
I removed a couple of quirks.
Everything seems to work really smoothly.
As a matter of fact, I find it easier to post to Scripting2 from iJot in Safari than using the Scripting2 tool in the OPML Editor. Of course, I'm biased :-)
Cross-posting this story to the iJot dev weblog.
7/26/2010; 12:00:00 AM. .
Checking save status
when saving to Scripting2.
After I save this post, when I hit 'new outline', I should not be asked for any confirmation.
Bingo ! It worked.
7/26/2010; 11:10:32 AM. .
Testing profile auto update.
This is a scripting2 post created from iJot.
My current user profile has no value yet for my s2 username and server.
Saving now.
My profile now holds the scripting2 user name I filled in the first save dialog, as well as the default scripting2 server url.
7/26/2010; 11:03:56 AM. .
This is another test post from iJot
This time, the username and server attributes should be present in the published OPML the first time around.
Saving now..
They were indeed present.
I reloaded the story in iJot's outliner using the Scripting2 stories list in iJot's left sidebar.
When I save next, the default dialog should be save to Scripting2 instead of save to iJot.
I think I can forget about the rawUrlEncoding.
It worked indeed. Wunderbar !
7/26/2010; 10:42:29 AM. .
A New Post From Scripting2
I am posting this from Scripting2.
I need to check the published OPML after the first save.
The username and server attributes are already there. I have fixed my code in iJot to deliver the same attributes.
The created and whenLastSave attributes are not rawUrlEncoded. I wonder why I took the trouble of rawUrlencoding them in iJot's outliner. There must be a reason.
I am saving these latest modifications from iJot.
7/26/2010; 10:35:32 AM. .
This is a test post.
I'm saving from iJot straight to Scripting2.
I want to check the first node's attributes each time I'm performing a save operation.
So here goes the first save in iJot.
This is my second save attempt. The sever and username attributes are part of the outliner now.
So the username and server attributes are now part of the published OPML document.
So that's 2 bugs I need to correct before the system is really seamless.
7/26/2010; 9:51:46 AM. .
Scripting2 / iJot Interop
Editing a post created with Scripting2 in iJot: check.
Creating a new Scripting2 post in iJot: check.
Listing your most recent Scripting2 posts in iJot: check.
I believe the interop of Scripting2 and iJot is now as complete as can be as far as posting goes.
The next step will be collaborating through Scripting2's Instant Outliner directly in iJot, and publishing the instant outline in a web page.
7/23/2010; 6:44:04 PM. .
I found the obvious.
Stubbornness works both ways...
And now the url of the published Scripting2 page appears at last!
Hoorah !!
But it didn't appear properly upon the second save.
This is sooo frustrating :-(
Ahh... It should appear correctly this time.
It did. All is well that ends well. My next edit will be from Scripting2.
Back in Scripting2, everything appears as it should. I'm saving this update before going back to iJot through iJotEdit.
And now in iJot, saving for the last time...
7/20/2010; 6:24:33 PM. .
I must be missing the obvious
I often am.
So let's try a work around.
7/20/2010; 6:16:49 PM. .
One more test is in order
Still looking at the export form parameters.
7/20/2010; 6:14:01 PM. .
The content of the cache is fine.
But the top.postExport function is not finding the expected export form fields.
Weird... Added more debugging alerts.
7/20/2010; 6:10:32 PM. .
Checking the content of the cache iframe
After saving this post, I should see some javascript with a call to top.postExport.
Or so I think...
7/20/2010; 6:03:22 PM. .
Posting to see the postExport javascript function at work
If it is called properly, I should get at least one alert after saving.
It is clearly not called properly.
7/20/2010; 5:50:44 PM. .
Once more, one last time, Murphy willing
This time the url of the page on the Scripting2 server should appear properly at the bottom of the outliner in Ijot.
Aargh ! It didn't.
7/20/2010; 5:42:45 PM. .
Once more unto the breach, dear friends
Last times my attributes where slightly off.
This time it should be perfect.
I think it was. Let's see if I can save another time directly from iJot.
SUCCESS: The second consecutive save went through.
Now all I need to do is figure out a way of storing the url attribute were it belongs in webOutliner.
7/20/2010; 5:28:12 PM. .
Still testing iJot new posts
I should get the html rendering updated with the attributes sent back by Scripting2.
7/20/2010; 5:23:28 PM. .
|
