On 31 May 2007, at 10:16 AM, Dries Buytaert wrote:
http://radar.oreilly.com/archives/2007/05/google_releases.html http://gears.google.com/
I'm having trouble thinking of a use case for Drupal though. Anyone have any contrib module ideas for this stuff ?
adrian rossouw wrote:
On 31 May 2007, at 10:16 AM, Dries Buytaert wrote:
http://radar.oreilly.com/archives/2007/05/google_releases.html
I'm having trouble thinking of a use case for Drupal though.
Anyone have any contrib module ideas for this stuff ?
How about the most simple one: write your posts offline, and have them uploaded to your site once you're online? Isn't it is what it's all about?
use case is manage content, prepare a new edition of a site all ready to synchronize with on line edition... another: have a drupal site on your desktop, synchronized with online, then, when you travel or can't get to a connection, you can still browse the data. another: recently for the Argentine elections, the list of registered voters was distributed in a CD with an apache stack... here we could have something like a Drupal stack, although, as a Rich App instead of an apache stack. so, instead of distributing CD's with apache, etc., you can just have a rich app allow users to browse material offline, and even then sync with new content online. saludos, Victor Kane http://awebfactory.com.ar On 5/31/07, adrian rossouw <adrian@bryght.com> wrote:
On 31 May 2007, at 10:16 AM, Dries Buytaert wrote:
http://radar.oreilly.com/archives/2007/05/google_releases.html
I'm having trouble thinking of a use case for Drupal though.
Anyone have any contrib module ideas for this stuff ?
On 31 May 2007, at 11:05 AM, Victor Kane wrote:
use case is manage content, prepare a new edition of a site all ready to synchronize with on line edition... except that all the pages used to manage content are generated and validated via php.
we'd have to move that all to the javascript layer.
Perhaps it could be used to integrate with desktop apps, since both the desktop app and the web app would have direct access to local storage. Often times importing/exporting data from these things is a multi-step process, and this could be a "digestion" layer where the user prepares data (possibly offline) and then synchronizes with the web app. adrian rossouw wrote:
On 31 May 2007, at 11:05 AM, Victor Kane wrote:
use case is manage content, prepare a new edition of a site all ready to synchronize with on line edition... except that all the pages used to manage content are generated and validated via php.
we'd have to move that all to the javascript layer.
well, one possibility is php gtk, see http://gtk.php.net/ (there is a data persistence layer in gears) But I wasn't speaking only of using Gears itself, but rather of the paradigm shift to rich clients, with offline support. On the one hand stuff like Apollo, on the other ... if we have Drupal on a stick, we can have Drupal on a rich client. The paradigm shift of web apps recycled as rich client apps can be seen on many fronts, for example in the world of light, agile J2EE, the Spring Framework has the Rich Client sub-project (see http://www.springframework.org/spring-rcp). Victor Kane http://awebfactory.com.ar On 5/31/07, adrian rossouw <adrian@bryght.com> wrote:
On 31 May 2007, at 11:05 AM, Victor Kane wrote:
use case is manage content, prepare a new edition of a site all ready to synchronize with on line edition...
except that all the pages used to manage content are generated and validated via php.
we'd have to move that all to the javascript layer.
The weird thing is, with the dawn of cheap broadband, and wifi-covered cities, planes, trains and buses, noone is actually offline to enjoy this now. Robin On 5/31/07, Victor Kane <victorkane@gmail.com> wrote:
well, one possibility is php gtk, see http://gtk.php.net/ (there is a data persistence layer in gears) But I wasn't speaking only of using Gears itself, but rather of the paradigm shift to rich clients, with offline support. On the one hand stuff like Apollo, on the other ... if we have Drupal on a stick, we can have Drupal on a rich client. The paradigm shift of web apps recycled as rich client apps can be seen on many fronts, for example in the world of light, agile J2EE, the Spring Framework has the Rich Client sub-project (see http://www.springframework.org/spring-rcp).
Victor Kane http://awebfactory.com.ar
On 5/31/07, adrian rossouw <adrian@bryght.com> wrote:
On 31 May 2007, at 11:05 AM, Victor Kane wrote:
use case is manage content, prepare a new edition of a site all ready to synchronize with on line edition...
except that all the pages used to manage content are generated and validated via php.
we'd have to move that all to the javascript layer.
-- Robin Monks @ www.civicspacelabs.org @ www.gmking.org Fax: (419) 791-8076 "Some people, when confronted with a problem, think "I know, I'll use regular expressions." Now they have two problems." ~IRC
That's a nice vision, but unfortunately we're not quite there yet... (besides, soon, fully functional Drupal sites will be sold on the market, next to the oranges stand, where wi-fi doesn't reach :-) ). Robin Monks wrote:
The weird thing is, with the dawn of cheap broadband, and wifi-covered cities, planes, trains and buses, noone is actually offline to enjoy this now.
Robin
On 5/31/07, * Victor Kane* <victorkane@gmail.com <mailto:victorkane@gmail.com>> wrote:
well, one possibility is php gtk, see http://gtk.php.net/ (there is a data persistence layer in gears) But I wasn't speaking only of using Gears itself, but rather of the paradigm shift to rich clients, with offline support. On the one hand stuff like Apollo, on the other ... if we have Drupal on a stick, we can have Drupal on a rich client. The paradigm shift of web apps recycled as rich client apps can be seen on many fronts, for example in the world of light, agile J2EE, the Spring Framework has the Rich Client sub-project (see http://www.springframework.org/spring-rcp).
Victor Kane http://awebfactory.com.ar
On 5/31/07, *adrian rossouw* <adrian@bryght.com <mailto:adrian@bryght.com>> wrote:
On 31 May 2007, at 11:05 AM, Victor Kane wrote:
use case is manage content, prepare a new edition of a site all ready to synchronize with on line edition...
except that all the pages used to manage content are generated and validated via php.
we'd have to move that all to the javascript layer.
-- Robin Monks @ www.civicspacelabs.org <http://www.civicspacelabs.org> @ www.gmking.org <http://www.gmking.org>
Fax: (419) 791-8076
"Some people, when confronted with a problem, think "I know, I'll use regular expressions." Now they have two problems." ~IRC
On Thursday 31 May 2007 08:16, Robin Monks wrote:
The weird thing is, with the dawn of cheap broadband, and wifi-covered cities, planes, trains and buses, noone is actually offline to enjoy this now.
As one who travels a lot on business, I have to disagree. Specifically, * A fair number of airports that offer wifi only do so at an exorbitant fee. Instead of spending a few thousand dollars on hubs for a multi- billion-dollar airport, they leave it to private contractors who by definition have a profit requirement. * I know of at least one international airport where the wifi contractor is a local company rather than a large multinational like Verizon or T-Mobile, meaning anyone who lives outside that community has to pay for an account just to use their wifi once. (My guess is that someone's brother-in-law is a city alderman...) * Wifi in hotels can be spotty, because (1) they don't always have enough hubs in place to cover the building and (2) the local staff usually don't know how to fix problems. * Wifi on aircraft is not yet widely available, and where available is almost never free. * I've heard about commuter trains with wifi, but I've yet to be on one even though I've recently been in both NYC and San Francisco. Perhaps this is yet another area where the enlightened Europeans and Asians are leaving the US in the dust. (And that is intended as a snark at my own country, not Europe or Asia. We in the USA just don't "get it" about the economic benefits of public wifi.) * Rural areas are still not well-served for broadband Internet of any kind. Try getting broadband in the Rocky Mountains, away from large cities. Robin, I really wish the world you envision were here, or that I could believe it's coming soon, but I'm afraid it's a long, long way off. To bring the discussion back to Drupal, I think offline capabilities would be a very strong feature to add to Drupal. On my largest Drupal sites, registered users are allowed to submit comments and stories, but nothing is published without editorial review. That being the case, the ability to suck down the editorial queue, review and edit offline, then upload the changes including scheduling items (using scheduler.module) for publication would be doubleplusgood. Scott -- ------------------------------------------------------------------------------- Syscrusher (Scott Courtney) Drupal page: http://drupal.org/user/9184 syscrusher at 4th dot com Home page: http://4th.com/
On 31 May 2007, at 2:51 PM, Syscrusher wrote:
To bring the discussion back to Drupal, I think offline capabilities would be a very strong feature to add to Drupal. On my largest Drupal sites, registered users are allowed to submit comments and stories, but nothing is published without editorial review. That being the case, the ability to suck down the editorial queue, review and edit offline, then upload the changes including
If it were just the list, i could see it happening. But it would require the node / comment views to be available. Perhaps change it so you can view the content in a jquery popup (like craqbox). That might also help for speeding up the moderation workflow. Or even just the first x characters of a post in a tooltip tied to a hover event.
scheduling items (using scheduler.module) for publication would be doubleplusgood. Hah. I was just berating for someone trying to have a conversation with doublespeak / newspeak.
On Thursday 31 May 2007 10:13, adrian rossouw wrote:
If it were just the list, i could see it happening. But it would require the node / comment views to be available.
Perhaps change it so you can view the content in a jquery popup (like craqbox). That might also help for speeding up the moderation workflow.
Or even just the first x characters of a post in a tooltip tied to a hover event.
In my situation, it's not a "community" site where the posts are simply moderated and approved, but rather a publication where the posts are actually edited for content and HTML formatting. What I envision is that one could download all the unpublished nodes to local storage, edit them there, mark the desired publication date/time for each, and upload the changed versions. I'm not saying it's trivial to build this, just that it would be very useful if available. :-) Scott -- ------------------------------------------------------------------------------- Syscrusher (Scott Courtney) Drupal page: http://drupal.org/user/9184 syscrusher at 4th dot com Home page: http://4th.com/
On 5/31/07, Syscrusher <syscrusher@4th.com> wrote:
In my situation, it's not a "community" site where the posts are simply moderated and approved, but rather a publication where the posts are actually edited for content and HTML formatting. What I envision is that one could download all the unpublished nodes to local storage, edit them there, mark the desired publication date/time for each, and upload the changed versions.
I'm not saying it's trivial to build this, just that it would be very useful if available. :-)
Which is possible already with the Blog API (been editing Drupal posts offline for years). Except for the desired publication date/time, which would mean extending the MetaWeblog API. Although I'd rather see people work on the Atom Publishing Protocol. -- Boris Mann Office 604-682-2889 Skype borismann http://www.bryght.com
On Thursday 31 May 2007 11:21, Boris Mann wrote:
Which is possible already with the Blog API (been editing Drupal posts offline for years).
Now why didn't I think of that? {thwacks self in head} -- ------------------------------------------------------------------------------- Syscrusher (Scott Courtney) Drupal page: http://drupal.org/user/9184 syscrusher at 4th dot com Home page: http://4th.com/
On 5/31/07 11:21 AM, Boris Mann wrote:
On 5/31/07, Syscrusher <syscrusher@4th.com> wrote:
In my situation, it's not a "community" site where the posts are simply moderated and approved, but rather a publication where the posts are actually edited for content and HTML formatting. What I envision is that one could download all the unpublished nodes to local storage, edit them there, mark the desired publication date/time for each, and upload the changed versions.
I'm not saying it's trivial to build this, just that it would be very useful if available. :-)
Which is possible already with the Blog API (been editing Drupal posts offline for years).
*and* presuming you're using a "simple" content type - i.e. title & body only.
Except for the desired publication date/time, which would mean extending the MetaWeblog API.
MetaWeblogAPI already supports sending pubDate (supported by most major clients) ... the issue is more that Drupal by default doesn't have any concept of "don't show anything published in the future".
Although I'd rather see people work on the Atom Publishing Protocol.
/me *winks* at eaton. -- James Walker :: http://walkah.net/ :: xmpp:walkah@walkah.net
With the advent of Google Maps I was very hesitant to use them or recommend that others use them. Essentially because I was really afraid about where Google was going with this. Of course my fears have been meaningless and ignored by Google and practically everyone else in the computing world and Google maps are becoming ubiquitous. My point is at that I'm starting to think "if you can't beat them, join them". In my view we are headed into a brave new world. Led, for better or worse, by Google. The rate of change they are pushing is mind boggling. I have wondered for a long time whether they could keep it up - but it seems clear that they are accelerating and deepening. In my view core Drupal needs to "play nice" with google stuff (as well as others). The world is changing. 2-3 years from now the way people use the Web will look different from what it does now. Very different. People will use Drupal if it is relevant to them. Dan
http://radar.oreilly.com/archives/2007/05/google_releases.html http://gears.google.com/
-- Dries Buytaert :: http://www.buytaert.net/
I disagree. Honestly, Google isn't really pushing anything all that advanced. They aren't innovating, they are just beating people on quality. They didn't "invent" searching they just made it 1000 times better than the next guy. They didn't "invent" gmail, they just had to not be hotmail. They didn't "invent" google maps, they just had to make it prettier. They didn't "invent" writely, they bought it. The only thing they really lead in is quality and flawless execution. While taking them into consideration for future development is a wise idea, putting handcuffs on because of their direction would be a huge mistake for anyone period. On 5/31/07 11:36 AM, "Dan Robinson" <dan@civicactions.com> wrote:
In my view core Drupal needs to "play nice" with google stuff (as well as others). The world is changing. 2-3 years from now the way people use the Web will look different from what it does now. Very different. People will use Drupal if it is relevant to them.
sounds like a lot of market leaders. sounds like Japan in the 80s. Dan
I disagree. Honestly, Google isn't really pushing anything all that advanced.
They aren't innovating, they are just beating people on quality.
They didn't "invent" searching they just made it 1000 times better than the next guy.
They didn't "invent" gmail, they just had to not be hotmail. They didn't "invent" google maps, they just had to make it prettier. They didn't "invent" writely, they bought it.
The only thing they really lead in is quality and flawless execution.
While taking them into consideration for future development is a wise idea, putting handcuffs on because of their direction would be a huge mistake for anyone period.
On 5/31/07 11:36 AM, "Dan Robinson" <dan@civicactions.com> wrote:
In my view core Drupal needs to "play nice" with google stuff (as well as others). The world is changing. 2-3 years from now the way people use the Web will look different from what it does now. Very different. People will use Drupal if it is relevant to them.
erm, 2 + 2 = 5 On 5/31/07, Mike Bishop <mbishop@adamsonadvertising.com> wrote:
I disagree. Honestly, Google isn't really pushing anything all that advanced.
They aren't innovating, they are just beating people on quality.
They didn't "invent" searching they just made it 1000 times better than the next guy.
They didn't "invent" gmail, they just had to not be hotmail. They didn't "invent" google maps, they just had to make it prettier. They didn't "invent" writely, they bought it.
The only thing they really lead in is quality and flawless execution.
While taking them into consideration for future development is a wise idea, putting handcuffs on because of their direction would be a huge mistake for anyone period.
On 5/31/07 11:36 AM, "Dan Robinson" <dan@civicactions.com> wrote:
In my view core Drupal needs to "play nice" with google stuff (as well as others). The world is changing. 2-3 years from now the way people use the Web will look different from what it does now. Very different. People will use Drupal if it is relevant to them.
Funny, I seem to recall this same sentiment being proffered many times about a company run by an aggressive dropout from harvard who managed to take out an awful lot of the OS space.... a lot... but not all :) imho, no one need fear interoperability. The only question is if Googles rich client api is the right thing. I have a use case in the non-profit sector. The VISTA program likes to promote Drupal for it's projects and many of them have existing data sources, under developed client side solutions and a lot of new web-enabled out- reach initives. Google Gears may be the right ticket to integrate their systems and bridge the "digital divide" that much of their clientele is oppressed by. Climbing off soapbox, Steve "CTC-VISTA wannabe" Wills On May 31, 2007, at 12:36 PM, Dan Robinson wrote:
With the advent of Google Maps I was very hesitant to use them or recommend that others use them. Essentially because I was really afraid about where Google was going with this. Of course my fears have been meaningless and ignored by Google and practically everyone else in the computing world and Google maps are becoming ubiquitous. My point is at that I'm starting to think "if you can't beat them, join them". In my view we are headed into a brave new world. Led, for better or worse, by Google. The rate of change they are pushing is mind boggling. I have wondered for a long time whether they could keep it up - but it seems clear that they are accelerating and deepening.
In my view core Drupal needs to "play nice" with google stuff (as well as others). The world is changing. 2-3 years from now the way people use the Web will look different from what it does now. Very different. People will use Drupal if it is relevant to them.
Dan
http://radar.oreilly.com/archives/2007/05/google_releases.html http://gears.google.com/
-- Dries Buytaert :: http://www.buytaert.net/
A module to detect the presence of Gears that can create a local cache of "anonymous" content wouldn't hurt Drupal's performance. Gears has both SQLite and a "LocalServer" which could serve files. Think preloading - but run in the back ground after DocumentReady. This cache could be greedy or intelligent - but that's easy enough to make a configurable. More thoughts: It's under a "new BSD" license - but may become as ubiquitous as flash. I don't know how Drupal community feels about Gears licensing. SQLite is really quite useful BTW: http://video.google.com/videoplay?docid=-5160435487953918649 OffTopic: some may also be interested in scrapbook for firefox, for offline viewing... http://amb.vis.ne.jp/mozilla/scrapbook/ Stephen Wills wrote:
Funny, I seem to recall this same sentiment being proffered many times about a company run by an aggressive dropout from harvard who managed to take out an awful lot of the OS space.... a lot... but not all :)
imho, no one need fear interoperability. The only question is if Googles rich client api is the right thing. I have a use case in the non-profit sector. The VISTA program likes to promote Drupal for it's projects and many of them have existing data sources, under developed client side solutions and a lot of new web-enabled out-reach initives. Google Gears may be the right ticket to integrate their systems and bridge the "digital divide" that much of their clientele is oppressed by.
Climbing off soapbox, Steve "CTC-VISTA wannabe" Wills
On May 31, 2007, at 12:36 PM, Dan Robinson wrote:
With the advent of Google Maps I was very hesitant to use them or recommend that others use them. Essentially because I was really afraid about where Google was going with this. Of course my fears have been meaningless and ignored by Google and practically everyone else in the computing world and Google maps are becoming ubiquitous. My point is at that I'm starting to think "if you can't beat them, join them". In my view we are headed into a brave new world. Led, for better or worse, by Google. The rate of change they are pushing is mind boggling. I have wondered for a long time whether they could keep it up - but it seems clear that they are accelerating and deepening.
In my view core Drupal needs to "play nice" with google stuff (as well as others). The world is changing. 2-3 years from now the way people use the Web will look different from what it does now. Very different. People will use Drupal if it is relevant to them.
Dan
http://radar.oreilly.com/archives/2007/05/google_releases.html http://gears.google.com/
--Dries Buytaert :: http://www.buytaert.net/
-- Jonathan Hendler Fort Lauderdale, Florida, USA cell: 617-216-1475 AIM/MSN: snooplegoop pgp key @: pgp.mit.edu
On 5/31/07, Dries Buytaert <dries@buytaert.net> wrote:
http://radar.oreilly.com/archives/2007/05/google_releases.html http://gears.google.com/
You can watch the videos from Google Developer Day here: http://youtube.com/googledeveloperday They took a lot of flak for not supporting OpenID as their authentication mechanism. Presumably they are concerned about phishing which maybe easier with OpenID. Cheers, Kieran --
Dries Buytaert :: http://www.buytaert.net/
-- To strive, to seek, to find, and not to yield.
participants (14)
-
adrian rossouw -
Boris Mann -
Dan Robinson -
Dries Buytaert -
James Walker -
Jonathan Hendler -
Kieran Lal -
Mike Bishop -
Robert Douglass -
Robin Monks -
Stephen Wills -
Syscrusher -
Victor Kane -
Zohar Stolar