Jonas know about WebOutliner?

Grok Headline matches for Jonas know about WebOutliner?

WebOutliner finished?

WebOutliner finished? 04/20/2004 07:24 PM

Marc Barrot is at it again - this time adding Technorati to radio.

Now he's just gotta go and finish the WebOutliner.

Now don't get me wrong - I LOVE Marc Barrot - but it's been a while and......

Technorat i Cosmos Links in Radio Templates.

I've recently added a small cosmos link to each footer section of this weblog's posts. It seems to be the latest fashion trend, at least among Movable Type publishers who are ready to customize their publishing templates. What about Radio Userland? Well, it doesn't seem to be possible to do it with the current (8.0.8) Radio version, unless you are ready and able to modify a small piece your Radio source code.

The trick is to modify the item template (#itemTemplate.txt file) to include an HTML link tag making a call to the Technorati Cosmos service. The Cosmos Service http GET request expects a 'url' argument specifying the permalink of the post:

http://www.tec hnorati.com/cosmos/search.html?url=permalink

wh ere permalink is the URI of the published item, suitably encoded to fit into the arguments component of a GET request.

This is where Radio cannot currently deliver: the <%permalink%> macro referenced for use in the item template does not provide a straight or encoded URL, but an image HTML tag encapsulating the URL instead.

However, if you're confident enough to modify Radio's source scripts, there's nothing preventing you from adding a new <%permalinkUrl%> macro. Template level macros are defined in the system.verbs.builtins.radio.weblog.render script.

To add a new 'permalinkUrl' pseudo-macro, locate the //set permalink bundle in the code, and add a single line at the end of that bundle's content:

t.permalinkUrl = string.urlEncode ( url )

Compile and save the modified script. Keep in mind of course that your modification will be wiped out the next time Userland publishes an update to the radio.weblog.render script.

The full HTML tag to add to the item template then looks like this:

<a href="http:\//www.technorati.com/cosmos/search.html?url=<%permalink Url%>" title="technorati cosmos link" target="_blank">cosmos</a>

Since this a very simple modification, let's hope the <%permalinkUrl%> macro will become part of the next Radio release.

[s l a m]

Hey Roland - Check out WebOutliner

Hey Roland - Check out WebOutliner 12/17/2004 06:28 PM

I'd send this to Roland via email - but my domains are still on hsi shit-list - so I keep getting bounceback from everyting I try and email him.

So here's Roland's post - which my answer is - The WebOutliner.

I want MarsLiner! I think in outlines so all I want for Christmas is an outliner like MORE or Radio that outputs the MetaWeblog API (including the Mov able Type MetaWeblog API extensions) so I can post to my blog text with simple markup (links, bold, italics, paragraphs and break, other tags would be nice but I don't need them!) and simple media (pictures, and audio and video for podcasts). That's it, that's all. Brent, please change your mind because I think you could sell a ton of these things. If not maybe the open source outliner based on Frontier that Dave is spearheading or maybe Omni Outliner 3 with a suitable export to Meta Weblog API script (doesn't seem like it since OO 2 which I love doesn't even do links!) will give me what I want. Otherwise, some day, I am going to have to dust off my dusty programming mitts and do it myself!

From inessential.com : Weblog: MarsEdit report.:

QUOTE

But MarsLiner was to be a huge improvement, it was supposed to be the outliner of my dreams.

But then I discovered something important: most people don't care about outliners. And the people who do care about outliners, many of them would want the embedded media features that I didn't care about. So I realized that the market would be small, just a subset of the outliner market, which is small enough already - and there are already some great outliners already.

UNQUOTE

[Roland Tanglao's Weblog]

JOnAS 3.0

JOnAS 3.0 03/13/2003 03:21 PM
An Open Source implementation of the J2EE specification.

JOnAS 4.1

JOnAS 4.1 06/07/2004 07:36 AM
An Open Source implementation of the J2EE specification.

Jonas on Clay on all of Us

Jonas on Clay on all of Us 05/05/2004 04:12 AM

Here's Jonas' reaction to Clay's latest piece - on 'Situated Software'.  I had a completely different reaction.  I see situated software - as teh same as what I call "activity based computing."

Inspired by Don Norman's work - I really think activity based computing happens when digital lifestyle aggregation is a norm.

Here's Jonas' post.....

Communicate.

Clay Shirky just published an essay on “Situated Software”, software tailored towards a specific situation.

Part of the future I believe I’m seeing is a change in the software ecosystem which, for the moment, I’m calling situated software. This is software designed in and for a particular social situation or context. This way of making software is in contrast with what I’ll call the Web School (the paradigm I learned to program in), where scalability, generality, and completeness were the key virtues.

Shirky touches on the very foundation the whole “Social Software” craze is all about – communication. He acknowledges, correctly, the basic foundation of it – communication.

Communication is cool. Everyone communicates, and sends verbal and non-verbal factoids at almost every waking second. The amazing part about mankind, and one of those things that not only set us apart from “lower” mammals and other life-forms, is our need and will to communicate, no matter what. Deprived of our primary means of communication, that is the verbal way, we invent and use secondary and tertiary means. Hearing and speech impaired use sign language, we use body language and simple pictorials to communicate, and if that all is taken away from us, we still seek and find a way.

Which by the way, also explains the withdrawal symptoms and “addictions” to email, Everquest, or IRC. We communicate. If taken away, we lose a form of communication, which is – as everyone who lost hearing or speech or vision will attest to – is something rather uncomfortable and painful. Losing this channel of communication equates to a loss of senses, sensory deprivation, and comes with all the psychological side-effects, such an event has to the affected.

In a way, communication is like lightning. It will always find the easiest way, no matter how. Deprived of simple ways to strike, the next easier path is taken, and so on. Successful “social software” is a lightning rod for such communication. It provides an easier way to convey factoids to other individuals. Take the whole “social network” misnomer, for an example. Friendships were expressed on online communities long before Friendster or Orkut. The WELL, heading into its 21st year of existence, is full of verbal and non-verbal displays or friendship and acquaintanceship. Or animosities, outright hate, curiosity. Name it, and it was there.

The problem is, telling it that way won’t get one quoted in eWeek. It’s one thing to call oneself an “expert” in Social Networking or a Visionary, or a Pioneer. Passersby stand in awe, the industry rejoices and jumps at the possibility of raking in VC money, and because it sounds academic, few questions are asked. Simply sounds better than “someone who knows, that people talk”, doesn’t it?

Take the “backchannel” discussion for a second. There are proponents and opponents of … communication. The basic understanding is simple – someone, somewhere, uses computerized means, such as IRC or AIM, or a WiKi, to comment in realtime on something. That something are mostly talks and presentations in conferences. Before IRC or IM was discovered, whispers were used, body language, such as yawning, applauding, rolling of eyes, or demonstrative snoring. With wireless networks starting to fill conference venues, the lightning strike of communication sought and found an easier, less prone to misscommunication, way in IRC and IM.

Skinned of the multiple layers of new words and stripped of the means, backchannel opponents and proponents are back to the basics – communication is good or bad, depending what’s it all about and who it is all about. Proponents point out the less disruptive and more constructive nature of IRC communications, opponents focus mostly on its exclusionary nature, both neglecting to acknowledge that before IRC and IM, other means were employed, which were equally exclusionary and similarly constructive – those things commonly called the “hallway track”.

Yes, speaking in new words, or calling ordinary things by academic sounding names has its advantages. Most importantly, it introduces a new lawyer of discussion. “I don’t really like it, when people talk about me behind my back” simply sounds less mature than “I think backchannels are useless”.

Communication is old. Providing better means to communicate and convey accurate factoids makes for a potential way to channel conversations into a system. It’s that simple, and I have no idea why we need to make it more complicated than that.

[a preponderance of evidence - What Willis Wuz' Talkin' 'Bout]

Congrats to Jonas on getting a job!

Congrats to Jonas on getting a job! 06/09/2004 05:54 AM
Does that mean I have to wear pants, again?.

Well, ladies and gentlemen, it's with not inconsiderable pleasure, that I announce my re-entry into the world of the bi-monthly paycheck. Starting today I will be getting paid to lend what little of expertise I have to offer and use it to play with and work on some cool Open Source collaboration things. Psyched.

[a preponderance of evidence blogs]

Collabnet is very lucky to get Jonas to work for them.

Bonita 1.3 (JOnAS)

Bonita 1.3 (JOnAS) 06/27/2004 11:19 AM
A cooperative workflow system based on the Workflow anticipation model.

Bonita 1.0 (JOnAS)

Bonita 1.0 (JOnAS) 10/31/2003 10:37 AM
A cooperative workflow system based on the Workflow anticipation model.

A New Butler For Jonas

A New Butler For Jonas 03/14/2005 05:06 PM
It has been two weeks since Jonas Luster fired his butler.  The primary reason cited was gross insubordination — an unwillingness on the part of the butler do as he was asked.  Perhaps the fact that the butler doesn’t help with of Jonas’s real needs — the ones behind the statement I am busy still trying to sift through all those advertisements — was also a factor. On the surface, it seems that Google’s AutoLink meets the letter of each of Yoz’s three rules for determining if such a tool is within the spirit of the Web.  However, upon closer examination, it turns out that there may be some wiggle room in the first rule.  Today the Google Toolbar for Internet Explorer is closed source.  The skills and techniques for creating such a thing are well beyond the abilities of most users.  Heck, they are black magic to most seasoned programmers. Simply put, if you can’t see the definition (and furthermore don’t trust the author to the point of being willing to write what amounts to a blank check), then how can a closed source toolbar ever pass the “completely understood” test? What if such a tool were open source?  Furthermore, suppose the tool were well commented, and structured in such a way that people who have even the most tenuous grasp on the concepts of HTML could reasonably modify it to remove the links and content that they don’t want, and add or reorder the links that they do want? Today Mark Pilgrim made available a new butler that is all this and more.  Made available under the GPL.  Share and enjoy. Now, Jonas, would you fire this butler too?
Grok Description matches for Jonas know about WebOutliner?
GrokA matches for Jonas know about WebOutliner?

Jonas know about WebOutliner?

The following phrases have been identified by the grok system as matching this entry: