P.S. I was still in the middle of doing the tacos-ish ajax xml layer, but
was hoping to hit you up for help on figuring out exception handling + your
very cool debug console.
I am not happy at all with the current exception window that tacos pops up
(could be the shadowed border thing that the floating pane is doing), but
either way think that we could definitely benefit from a full featured
exception presenting sort of widget. There are a lot more things we could
help to show the state of and present better than just dumb html output.
(your console is already doing some of these cool things)
My hope was that PropertySelection would help get the initial render layer
built, while the debug console and exception handling would help to flesh
out the majority of remaining functionality(ie effects / widget building /
js package building system / etc...). I'd really like to spend a large
portion of time on the debug console + exception widgets so that they are as
functional and useful as possible.
Other than linking / form behaviour I don't care at all if the initial
4.1alpha release has only this functionality at a minimum. (The rest
of the
components / widgets should be very fast and easy to throw in if we have
properly setup the API to do so.)
What do you think?
On 5/14/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
If I'm correct in my thinking, disabling cookies is effectively equal to
disabling sessions. Since assets and other similar items require a valid
session to be included (ie protected or private assets, which dojo
definitely is ) it makes sense to me that this broke things.
On 5/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Yea, i know, saw your commits yesterday and tried it at once.
> It's cool, I'll start adding widgets this week.
> Anyway, then i somehow disabled cookies and this breaks dojo's
> inclusion by Tapestry. I looked into it a bit and then sent the
> 'Stateless Services are url encoded.Why?' email to this list.
> Any comments on it?
>
> From Jesse Kuhnert <[EMAIL PROTECTED]>:
>
> > Hey Andreas,
> >
> > This is fixed now. The original problem was with me having
> debugAtAllCosts
> > turned on. (something I must've enabled in some sort of desperate
> action to
> > get something else working ;) )
> >
> >
> >
> > On 5/11/06, Jesse Kuhnert < [EMAIL PROTECTED]> wrote:
> > >
> > > Hmm... I haven't actually run the app in a couple days (been writing
> unit
> > > tests only) . When svn comes back online I'll take a look. (The
> > > autocompleter is pretty sexy btw :) )
> > >
> > >
> > > On 5/11/06, Andreas Andreou <[EMAIL PROTECTED]> wrote:
> > > >
> > > > The version that comes closest to working is ... the one we have
> in
> > > > tapestry trunk!
> > > > Both dojo 0.3 and dojo trunk complain with
> > > > DEBUG: no tag handler registed for type: dojo:combobox
> > > > (i'm just trying to see the autocompleter in action)
> > > >
> > > > Anyway, i'll go finish tacos issues these days
> > > >
> > > >
> > > > Jesse Kuhnert wrote:
> > > > > Definitely dojo trunk. The 0.3 release won't be enough either
> because
> > > > > of a
> > > > > ~bug~ with dojo.uri.Uri() and how it handles munging together
> urls to
> > > > > resolve widget resources. (ie templateCssPath, templateHtmlPath
> ) .
> > > > That,
> > > > > and your baseTag bug.
> > > > >
> > > > > When 0.3 comes out (tomorrow), I'll start pestering them for
> fixes to
> > > > > these
> > > > > core items for tapestry. (bugs have been logged of course)
> > > > >
> > > > > On 5/9/06, Andreas Andreou <[EMAIL PROTECTED]> wrote:
> > > > >>
> > > > >> Jesse Kuhnert wrote:
> > > > >> > It's been a huge headache for me. I'm still not sure of the
> best
> > > > >> overall
> > > > >> > solution.
> > > > >> >
> > > > >> > For me, I've been manually running the ant target "copy-libs"
> from
> > > > >> > framework/src/js when I want to run the demo application to
> test
> > > > them.
> > > > >> > (TimeTracker) I haven't even actually been using the dojo
> build
> > > > >> that's
> > > > >> > checked in.
> > > > >> Aha, that's why the autocompleter currently breaks on the
> client :)
> > > > >> But I love the ajax responses= {"0":"English","1":"French"}
> > > > >> So, for dojo, you'd advice tacos trunk or dojo trunk?
> > > > >>
> > > > >> > (mostly because it's such a verbose effort to update them and
> > > > >> > commit the changes to svn)
> > > > >> >
> > > > >> > Any ideas on how to improve this process would be
> appreciated.
> > > > >> That's a tough one... i can't think of any better alternatives.
> > > > >> I guess with the 0.3 release it'll sort of stabilize.
> > > > >>
> > > > >> >
> > > > >> > On 5/9/06, Andreas Andreou < [EMAIL PROTECTED]> wrote:
> > > > >> >>
> > > > >> >> With the svn files as is,
> > org.apache.tapestry.html.dojo(javascript)
> > > > >> >> files
> > > > >> >> are getting compiled directly in /bin. This is happening
> because
> > > > >> >> org/apache/tapestry/html/dojo is defined as src folder.
> > > > >> >>
> > > > >> >> However, they should really end up in
> > > > >> >> /bin/org/apache/tapestry/html/dojo.
> > > > >> >>
> > > > >> >> So, I simply removed org/apache/tapestry/html/dojo from
> being src
> > > > >> >> folder, but i'm just wondering, how are you guys using this?
> > > > >> >>
> > > > >> >>
> > > > >> >>
> > > > >> >>
> > > >
> ---------------------------------------------------------------------
> > > > >> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > >> >> For additional commands, e-mail:
> [EMAIL PROTECTED]
> > > > >> >>
> > > > >> >>
> > > > >> >
> > > > >> >
> > > > >> > --
> > > > >> > Jesse Kuhnert
> > > > >> > Tacos/Tapestry, team member/developer
> > > > >> >
> > > > >> > Open source based consulting work centered around
> > > > >> > dojo/tapestry/tacos/hivemind.
> > > > >> >
> > > > >>
> > > > >>
> ---------------------------------------------------------------------
> > > >
> > > > >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > >> For additional commands, e-mail: [EMAIL PROTECTED]
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > > Jesse Kuhnert
> > > > > Tacos/Tapestry, team member/developer
> > > > >
> > > > > Open source based consulting work centered around
> > > > > dojo/tapestry/tacos/hivemind.
> > > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Jesse Kuhnert
> > > Tacos/Tapestry, team member/developer
> > >
> > > Open source based consulting work centered around
> > > dojo/tapestry/tacos/hivemind.
> > >
> >
> >
> >
> > --
> > Jesse Kuhnert
> > Tacos/Tapestry, team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind.
> >
>
>
> --
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Jesse Kuhnert
Tacos/Tapestry, team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.
--
Jesse Kuhnert
Tacos/Tapestry, team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.
