Which is pretty much the same as i get when i run that gadget (prefixing it with http:// is a good thing btw) in the java shindig gadget server

The patch is meant to be applied to the shindig source dir, so you could apply it by doing:

# svn checkout <shindig repo url>
# cd shindig/php
# patch -p1 < [patth to the patch]/php-shindig.patch

Keep in mind, as i wrote, its based on a checkout from feb 14th, so it should have the exact same functioning as it ... there's still some new features to catch up on, and some iGoogle features (like finance etc) will never work on a shindig gadget server, so if you could please for now focus the bug reports for now on what is different from the java branch, or patches for funcitonality it's still missing, i'd very much appreciate it :)

        -- Chris

On Mar 2, 2008, at 6:36 PM, Akash Xavier wrote:

Chris,
I tried this gadget. It displays nithing
http://shindig.chabotc.com/gadgets/ifr?url=delicious-bookmarks.googlecode.com/svn/trunk/delicious.xml
Its a del.icio.us gadget

On Sun, Mar 2, 2008 at 9:31 AM, Akash Xavier <[EMAIL PROTECTED]> wrote:

Yeah
Thanks for updating it Chris.
Before u msged back, I was excited to see a working version and hence
downloaded the patch file and was trying to open it. I opened the patch file
in mozilla firefox on my local server, but couldnt extract it.  :)
Thanks.... I am now directly downloading it  :)


On Sun, Mar 2, 2008 at 9:26 AM, Chris Chabot <[EMAIL PROTECTED]> wrote:

Ps if you want to run it locally, just download
http://chabotc.com/php-shindig.tar.gz
, untar, copy files to your web root, and point your browser to it ...
deploying it rly is quite simple ;)

On Mar 2, 2008, at 6:19 PM, Chris Chabot wrote:

That hosted demo version of it wasn't updated to the latest code
yet, and was also in the old location (without the /gadgets part,
which i've now added because there might be a social part soon too).
I've just updated this and made a opensocial-0.7 feature with an
opensocial-reference dependency, so the compliancetest should
function correctly now:


http://shindig.chabotc.com/gadgets/ifr?url=http://opensocial-resources.googlecode.com/svn/tests/trunk/compliancetests.xml

Keep in mind it doesn't really do 'social' yet, and it also doesn't
have the port from the social part of the java branch yet either
(since this was made after the feb 14th checkout which i based my
work on). So while it'll load ok, it wont really do very much yet,
just render the gadget, proxy the remote calls if any, and that's it
until the social part has been written too.

     -- Chris

On Mar 2, 2008, at 5:42 PM, Akash Xavier wrote:

Chris,

I tested the code on your site with the compliance gadget.

http://shindig.chabotc.com/ifr/?url=http://opensocial-resources.googlecode.com/svn/tests/trunk/compliancetests.xml

It shows an error "Error. Unsupported feature(s): opensocial-0.7"

Wondering whether u uploaded the latest version to the site too??

On Sun, Mar 2, 2008 at 8:38 AM, Akash Xavier
<[EMAIL PROTECTED]> wrote:

Chris,
Is it running on your site chabotc.com? (you posted a link
sometime ago)


On Sun, Mar 2, 2008 at 8:06 AM, Chris Chabot <[EMAIL PROTECTED]>
wrote:

Hey Guys,

As you can see the patch for the new php shindig gadget server has landed. I've tested this server with all the simple gadgets i could get my hands on, and with sample containers, and it seems to behave
identical to the java shindig server now (the one from feb 14th
that
is, what i based my porting efforts on).

It's still missing a few things, including a good bit of extra
documentation for all the classes etc, once this patch has been
accepted i'll file bug reports for all the todo's that i have open,
and desirable fixes/changes/etc, so that other people could
easily get
started on collaborating and expanding on this.

When the patch has gone thru some basic review and is included in
the
svn repo, i would like to also apply for commit access to it. What
would be the procedure for this?

Look forward to your feedback!

    -- Chris

On Mar 2, 2008, at 4:56 PM, Chris Chabot (JIRA) wrote:

New PHP Shindig gadget server code
----------------------------------

             Key: SHINDIG-103
             URL:
https://issues.apache.org/jira/browse/SHINDIG-103
         Project: Shindig
      Issue Type: Improvement
      Components: Gadgets Server - PHP
        Reporter: Chris Chabot
        Assignee: Brian McCallister


This patch completely replaces the old code in the php directory
of
the shindig project, and replaces it with a port of the java
shindig
code.

The java code used is from a checkout from February the 14th, this
because keeping track of the changes while porting and testing
would
have gotten in the way of completing the first release in a timely
fashion.

It implements the structure and workings from the java server and
includes:
- Gadget server
- Proxy service
- JS service

The maIn differences from the Java branch are:
- Different caching engine (abstracted base class, sample file
implementation included)
- Different gadget rendering work flow (no multithreading in PHP)
- No enum's or name spaced classes in php, so their top level
classes now
- Locale class to emulate the Java's Locale class
- Somewhat servlet like event handling to stay close to the Java's
structure


Missing is the RPC feature, some custom speedups to get it
closer to
the Java's speed (it's about 40% slower right now, but that gap
might be fixed later on), and a better logging / error reporting structure, it now only has a basic DEBUG flag in the config, which
if set, causes it to dump debug backtrace's on errors.

It's also missing Caja support, since that is Java only at the
moment. Maybe somewhere in the future we'll have a command line
version available that we can use.

It also contains a copy of the features directory structure (so
that
it doesn't break on updates from the Java side of things, changes
will have to be implemented before you can copy over the new
version) and a copy of the sample container (minus the Caja
options), so that people can test it directly.




--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.




--
Akash Xavier
[EMAIL PROTECTED]




--
Akash Xavier
[EMAIL PROTECTED]




--
Akash Xavier
[EMAIL PROTECTED]




--
Akash Xavier
[EMAIL PROTECTED]

Reply via email to