You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Jordan Zimmerman <jo...@shop.com> on 2009/03/18 10:19:04 UTC
Possible bug: NekoSerializer
The latest version of NekoSerializer.printStartElement() is outputting
empty attributes in a way that isn't XML compliant. i.e. given '<img
title=""/>' NekoSerializer will output '<img title/>'. This causes
Firefox's (I haven't tried others) DOM parser to throw an error. This is
coming up when using the OS templates framework.
Thoughts?
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
Shop Smart, Save Big(tm)
www.shop.com
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
RE: Views
Posted by Jordan Zimmerman <jo...@shop.com>.
>Socialsite is a good option for a Java FE.
I don't need to develop a front end. I just need to integrate Shindig
with my application (http://www.shop.com).
Kevin wrote:
"There aren't really any plans to do much of anything with the sample
container javascript (code in the top level javascript directory),
because it's just there for testing purposes."
How would I have known this? Where is the documentation on how to
replace these files? What I have to do now (as I've been doing for
months) is search the net at length, look at other people's code for
clues, debug inside of Shindig writing toy apps, etc. Using this
"method" I've figured out enough to write Mediated OpenSocial.
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
Shop Smart, Save Big(tm)
www.shop.com
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
Re: Views
Posted by Dan Peterson <dp...@google.com>.
Shindig itself is focused on implementing the OpenSocial spec, but, as Paul
says, it doesn't cover everything involved with shipping a full application
platform, but it is a (big?) tool towards the backend of such a system.
The post that introduced Partuza , which is primarily the frontend written
in PHP, on the OpenSocial blog is at:
http://blog.opensocial.org/2008/08/lets-get-this-partuza-started.html
Socialsite is a good option for a Java FE.
-Dan
On Wed, Mar 18, 2009 at 3:46 PM, Paul Lindner <pl...@hi5.com> wrote:
> I understand integrating a social site with shindig isn't easy. There's
> lots of integration to do.
>
> Developer Accounts
> Application Gallery
> Interface with profile/canvas
> Messaging
> Permissions
> etc.
>
> These are beyond the scope of Shindig.
>
> Ff you want java examples you can look at Sun's Social Site implementation,
> it's built on top of shindig (and a number of other components.)
>
> https://socialsite.dev.java.net/
>
>
>
> On Mar 18, 2009, at 3:41 PM, Jordan Zimmerman wrote:
>
> For a real container implementation, you'd probably want to start with
>>> something like Partuza.
>>>
>>
>> Lovely. This is the first time I've heard of Partuza. I am trying to
>> write a real container. I assumed I could use Shindig. Do I need to use
>> something else in addition? How is a developer supposed to get a handle
>> on all of this?
>>
>> Kevin, I really appreciate that you answered my question quickly and are
>> trying to help. But, putting yourself in my position, wouldn't you be
>> incredibly frustrated if you worked at a small company and were tasked
>> with implementing an OS container using Shindig?
>>
>
>
Re: Views
Posted by Dan Peterson <dp...@google.com>.
On Wed, Mar 18, 2009 at 7:29 PM, Jordan Zimmerman <jo...@shop.com> wrote:
> >I have to say that I agree with you, so you're not the only one - there
> >is documentation missing - that's always going to be tough for open
> >source projects though
>
> I've done a few open source projects and I've always been able to
> provide _some_ documentation. Shindig has zero. Also, Shindig's approach
> is a radical departure from most code libraries that a developer will be
> used to therefore the lack of documentation is particularly frustrating.
Hey Jordan,
I also think it might be useful to take a look at some of the docs that are
linked off of:
http://cwiki.apache.org/SHINDIG/
-Dan
RE: Views
Posted by Jordan Zimmerman <jo...@shop.com>.
>I have to say that I agree with you, so you're not the only one - there
>is documentation missing - that's always going to be tough for open
>source projects though
I've done a few open source projects and I've always been able to
provide _some_ documentation. Shindig has zero. Also, Shindig's approach
is a radical departure from most code libraries that a developer will be
used to therefore the lack of documentation is particularly frustrating.
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
Shop Smart, Save Big(tm)
www.shop.com
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
RE: Views
Posted by Tim Wintle <ti...@teamrubber.com>.
On Wed, 2009-03-18 at 15:51 -0700, Jordan Zimmerman wrote:
>
> I keep feeling like I'm missing something as I'm the only one
> complaining.
I have to say that I agree with you, so you're not the only one - there
is documentation missing - that's always going to be tough for open
source projects though, and I don't hold it against any of the
developers. Have to admit I haven't written any documentation myself, so
I can't really complain.
Tim Wintle
RE: Views
Posted by Jordan Zimmerman <jo...@shop.com>.
>I understand integrating a social site with shindig isn't easy.
>There's lots of integration to do.
The integration has been very easy. I know how my app works and where it
stores accounts, etc. What has been maddeningly difficult is figuring
out how to interface with Shindig. Shindig is not a code library with
well-defined integration points. It is a self-contained application.
Also, there is literally no supported documentation whatsoever. The only
docs are written by people like me or Chris Chabot etc. who have gone
down the integration path or some design docs from the code
contributors.
I keep feeling like I'm missing something as I'm the only one
complaining.
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
Shop Smart, Save Big(tm)
www.shop.com
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
Re: Views
Posted by Paul Lindner <pl...@hi5.com>.
I understand integrating a social site with shindig isn't easy.
There's lots of integration to do.
Developer Accounts
Application Gallery
Interface with profile/canvas
Messaging
Permissions
etc.
These are beyond the scope of Shindig.
Ff you want java examples you can look at Sun's Social Site
implementation, it's built on top of shindig (and a number of other
components.)
https://socialsite.dev.java.net/
On Mar 18, 2009, at 3:41 PM, Jordan Zimmerman wrote:
>> For a real container implementation, you'd probably want to start
>> with
>> something like Partuza.
>
> Lovely. This is the first time I've heard of Partuza. I am trying to
> write a real container. I assumed I could use Shindig. Do I need to
> use
> something else in addition? How is a developer supposed to get a
> handle
> on all of this?
>
> Kevin, I really appreciate that you answered my question quickly and
> are
> trying to help. But, putting yourself in my position, wouldn't you be
> incredibly frustrated if you worked at a small company and were tasked
> with implementing an OS container using Shindig?
RE: Views
Posted by Jordan Zimmerman <jo...@shop.com>.
>For a real container implementation, you'd probably want to start with
>something like Partuza.
Lovely. This is the first time I've heard of Partuza. I am trying to
write a real container. I assumed I could use Shindig. Do I need to use
something else in addition? How is a developer supposed to get a handle
on all of this?
Kevin, I really appreciate that you answered my question quickly and are
trying to help. But, putting yourself in my position, wouldn't you be
incredibly frustrated if you worked at a small company and were tasked
with implementing an OS container using Shindig?
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
Shop Smart, Save Big(tm)
www.shop.com
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
Re: Views
Posted by Kevin Brown <et...@google.com>.
There aren't really any plans to do much of anything with the sample
container javascript (code in the top level javascript directory), because
it's just there for testing purposes.
For a real container implementation, you'd probably want to start with
something like Partuza.
On Wed, Mar 18, 2009 at 3:24 PM, Jordan Zimmerman <jo...@shop.com> wrote:
> Are there plans for enhancing Shindig's view support? Currently, it
> looks like view changes are implemented via
> gadgets.IfrGadgetService.prototype.getUrlForView which is hard-coded to
> append to the URL path. For now, I could just override this, I guess.
>
> Jordan Zimmerman
> Principal Software Architect
> 831.647.4712
> 831.214.2990 (cell)
> jordanz@shop.com
>
> SHOP*COMTM
> Shop Smart, Save Big(tm)
> www.shop.com
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this
> message
> immediately if this is an electronic communication.
>
> Thank you.
>
Views
Posted by Jordan Zimmerman <jo...@shop.com>.
Are there plans for enhancing Shindig's view support? Currently, it
looks like view changes are implemented via
gadgets.IfrGadgetService.prototype.getUrlForView which is hard-coded to
append to the URL path. For now, I could just override this, I guess.
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
Shop Smart, Save Big(tm)
www.shop.com
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
RE: Possible bug: NekoSerializer
Posted by Jordan Zimmerman <jo...@shop.com>.
I'll write it up. I have a fix.
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
jordanz@shop.com
SHOP*COMTM
Shop Smart, Save Big(tm)
www.shop.com
-----Original Message-----
From: Adam Winer [mailto:awiner@google.com]
Sent: Wednesday, March 18, 2009 8:38 AM
To: shindig-dev@incubator.apache.org
Subject: Re: Possible bug: NekoSerializer
That's clearly a bug. I'm looking at it now - the trick is getting
Neko to identify the difference between:
<input disabled ...>
and
<input title="">
... where the former should be rendered XML-wise as
disabled="disabled", the latter as title="".
On Wed, Mar 18, 2009 at 2:19 AM, Jordan Zimmerman <jo...@shop.com>
wrote:
> The latest version of NekoSerializer.printStartElement() is outputting
> empty attributes in a way that isn't XML compliant. i.e. given '<img
> title=""/>' NekoSerializer will output '<img title/>'. This causes
> Firefox's (I haven't tried others) DOM parser to throw an error. This
is
> coming up when using the OS templates framework.
>
> Thoughts?
>
> Jordan Zimmerman
> Principal Software Architect
> 831.647.4712
> 831.214.2990 (cell)
> jordanz@shop.com
>
> SHOP*COMTM
> Shop Smart, Save Big(tm)
> www.shop.com
>
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this
> message
> immediately if this is an electronic communication.
>
> Thank you.
>
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
Re: Possible bug: NekoSerializer
Posted by Adam Winer <aw...@google.com>.
That's clearly a bug. I'm looking at it now - the trick is getting
Neko to identify the difference between:
<input disabled ...>
and
<input title="">
... where the former should be rendered XML-wise as
disabled="disabled", the latter as title="".
On Wed, Mar 18, 2009 at 2:19 AM, Jordan Zimmerman <jo...@shop.com> wrote:
> The latest version of NekoSerializer.printStartElement() is outputting
> empty attributes in a way that isn't XML compliant. i.e. given '<img
> title=""/>' NekoSerializer will output '<img title/>'. This causes
> Firefox's (I haven't tried others) DOM parser to throw an error. This is
> coming up when using the OS templates framework.
>
> Thoughts?
>
> Jordan Zimmerman
> Principal Software Architect
> 831.647.4712
> 831.214.2990 (cell)
> jordanz@shop.com
>
> SHOP*COMTM
> Shop Smart, Save Big(tm)
> www.shop.com
>
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this
> message
> immediately if this is an electronic communication.
>
> Thank you.
>