Again, frustration with things google, i.e. docs.google
posted Monday, December 03, 2007 at 2:35 pm MSTNB: HTML here-under copied/pasted from docs.google's edit page
This is being created in docs.google (here is the publically-viewable original ) and, perhaps, if I'm lucky, published to my main blospot.com blog.
(Since this is going to be in my blog,Take 3 ... the "publish to blog" test showed no faults,
Take 5? Nawww ... I've got better things to do.
But how typical of things google: the Publish function is about 80% done, so they cut their costs and move on to more flashy things. My point: entering the blog ID failed; it went to the first blog in my list. Entering the blog name failed; it seems it wasn't published at all. Entering both, using the same format as the prompt/hint failed in the same way.
And here's my point: why isn't this integrated with blogger.com?! If I select to publish there (apparently I have the option of sending to other platforms, LJ for example) then why can't I be provided with a list of blogs? Those are under the same login data / authorization / permissions as what I'm doing here.
Frustrating.
And if I want to publish this elsewhere by using IFrame I need to dig around to find my key.
Sorry, but no ... no thanks. Spent too much time on this already.
Screenshot of desktop using ExtJS at Keliglia.com ... see also my blogpost at LiveJournal.
<>
Have a look at this:
Check out the live demo.
This came up in forum thread on Dashboards and GUI builders ... it has its own thread.
For my money? break-through stuff.
<>
What's old is new again? Bedouin co-working
posted Sunday, December 02, 2007 at 2:15 pm MST*X-posted from ''Gnodal'' at LiveJournal*Thinking about OpenSource and crowd-sourcing and all of that I found myself coming back again and again to the idea of "going Bedouin". (Now I happen to really admire Bedouin culture and traditions, but that's another essay.) I'm talking about foundational co-working.
Just now I realized with some shock that the concepts that are central to Bedouin-style co-working are exactly the same as what I envisioned with my first startup. (Alas, it succumbed to infant mortality.)
Back-story: in the late 80s Texas Instrument's new generation of video chips gave rise to an awesome breakthrough in capabilities, the best example being the Amiga 2500 and the VideoToaster. Combined, video production costs were 1/10th what they had been previously. I saw that as a massive (if only transient) business opportunity.
My idea was this: provide people who were already working in video with turn-key video studios using those systems ... they would rapidbly find themselves independent. But key to the franchise concept was networking: small shops off-loading cumbersome tasks or repetitive chores to one another ... a sort of load-leveling. Bonus would be that projects would become networked, so contracts that might be far too large and complex for any one studio could be shared.
That was 1988.
In 2007? That, basically, is co-working ... and "going Bedouin" fits perfectly with that business model.
Feeling manic? Pumped for consecutive 14 hour days? Just fine.
Distracted by some aspect of personal life? NP ... 2 or 4 hours of maintenance (email and such) keeps things ticking over for a little while.
Addendum, from MozDawg comments:
Interesting that you brought up InnoCentive here ... it continues the thread I've been working today i.e. alternative business models.I really have come full circle, back to 1989!
Context: looking through material on Alfresco I find that, while it promotes itself as seriously OpenSource, it is far more closed than the dev communities in, say, SalesForce or FaceBook or NetVibes. I felt like I needed a battering ram to access documentation. (Registering as a developer will do the trick, but still ... odd to see their reticence.)
On the other hand, by way of contrast, I came across Automattic, who specializes in WordPress ... it seems that they're entirely distributed i.e. no bricks&mortar head office, but everybody draws against revenue.
Then reading about a new Drupal support startup, Acquia, I can't help thinking that a lot of hours are spent doing what others are doing, and wondering if there isn't a way of producing better results while reducing over-work.
So many people were so very busy, and pondered why collaboration wasn't lightening the load or leading to economies of scale.
