Recap of the first topic of my last message, for emphasis:
The obvious topic for the March newsletter is the DrupalCon, of course. There are over 800 people here, though and we need to recruit people to write up their favorite session/s. If you are at the conference, please write up at least one session, and/or find three other people who can write up a session. We only need a paragraph or two, but feel free to write up a whole big article if you're inspired.
Sneak preview of this discussion (if you decide not to click through to the rest of this discussion topic): http://drupal-newsletter.org/issue/2008/01
This DrupalCon has been phenomenal! We had an impromptu BoF session yesterday for the Drupal Newsletter. The three big things that came out of that were a plan for March's newsletter, the newsletter length, and building a stand-alone site for the newsletter.
The obvious topic for the March newsletter is the DrupalCon, of course. There are over 800 people here, though and we need to recruit people to write up their favorite session/s. If you are at the conference, please write up at least one session, and/or find three other people who can write up a session. We only need a paragraph or two, but feel free to write up a whole big article if you're inspired.
To the second item, we plan to use a system of teasers for the next issue. We'll put each section and/or article in the groups, and just link a manually created teaser in the digest that gets e-mailed and posted on d.o. We'll refine that process as we continue creating future newsletters.
Which is yet another strong case for a stand-alone newsletter site, bringing us to the third item of discussion. We created a working group, currently consisting of Alex UA, mlsamualson, and myself, to create a proof-of-concept stand-alone site. You can see it at http://drupal-newsletter.org/issue/2008/01 (which is just filler, as you'll see).
I think the feedapi integration patch is all that's really holding up a release, if you want to go over there and help test it...
when you say near term, is that near as in the next couple of weeks or near as in the next year? I have a job right now that could make use of this, I would like to stall for time until some sort of release, so an indication of any sort of release would be awsome. (I would be a willing tester)
cheers,,,, looks awsome.
Interface building is already possible: http://drupal.org/project/atck
besides the benefits this technology brings (ajax stuff), we have to remain on our toes not to overload the system, because for example the sproutcore system is painfuly slow.
Kinda interesting, it would be cool to see drupal apps going in this direction
http://www.sproutcore.com/ http://ajaxian.com/archives/an-interview-with-280-north-on-objective-j-a...
From a design standpoint It would pretty neat to build apps in visual interface builder. Sproutcore is heading this direction already. http://developer.apple.com/documentation/DeveloperTools/InterfaceBuilder...
for these kind of apps SEO really isn't necessary.
My battle plan was to offer API to other modules to display their content in 2 steps:
step 1) this is the first time content is being displayed. this will dump plain HTML from the server to the user
step 2) this will take the content in step 1 and attach actions to it so that when user interacts with that content it will isolate individual sections and communicate it back to the server via AJAX at which point content will be served through JSON + AJAX bypassing module's own theming layers.
the flaw with step 2 is that the module will be limited only to theme functions that are currently defined by js_theming module.
I will take care to come up with with some solution that will enable misc modules expand the javascript theming functionality. the project is still in very early stage of it's life and it already supports item lists, table theme, handles drupal status messages in a smart and admin configured way, allows table themes to offer table sorts just like drupal core does. offers themes for l() and url() functions. i think i forgot to mention other things but as you can see its growing rapidly and pretty soon will include more features to aid user end javascript theming.