On 5/4/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I see no reason NOT to integrate everything within tacos.
Regarding AjaxForm, you normally don't have to do anything special.
However, a tacos component should be tested and be functional when:
- it is added to a page after the initial render (=through an ajax response)
- it exists in the page multiple times (=using @For).
- it exists in another component that exists in the page multiple times
But anyway, I believe we can help on those...
So, what should the next step be?
From Sam Gendler <[EMAIL PROTECTED]>:
> OK, I've been promising them for a while, but I am about to deliver a
> bunch of tapestry components that wrap various dojo widgets.
>
> I've implemented a slider that is similar to TurboSlider (but not
> dependant on turbo, just dojo).
>
> I've got somethign called ReportGrid which is based on a grid
> component that was submitted to dojo bug tracking. It has a header,
> footer, sortable columns (client side), client side
> internationalization, client side number and currency formatting,
> client side paging, and the ability to filter the visible rows in the
> client based on a specified filter value and _expression_ (greater then,
> equal to, etc). It is based on dojo plus mochikit for the
> internationalization and number formatting. The ReportGrid is
> intended as a read only grid with simple drill down (via hyperlinks).
> It does not yet support arbitrary html in a column, including other
> widgets. I figure the mythical dojo grid can handle that when it is
> complete. I've got a wrapper for TurboGrid, too, but sorting is just
> too darn slow in TurboGrid when result sets are large. The ReportGrid
> component takes a standard contrib:TableModel as the model, and
> otherwise emulates the contrib:table interface where possible.
>
> I've got components wrapping dojo Button2, dojo Tabs, dojo
> SplitContainer, dojo context menu, and dojo accordion.
>
> ReportGrid is very functional, the rest only have the dojo features
> that we are using exposed as Tapestry component attributes, so they
> will require extra work in order to be as functional as raw dojo. I
> haven't yet attempted to integrate any of them in a tacos AjaxForm,
> and I have no idea if special consideration is required in order to do
> so.
>
> The ReportGrid and Slider are implemented as dojo widgets outside the
> source tree, so they can be included in your application without
> modifying your dojo installation itself.
>
> Are folks interesting in integration with tacos, or should I release
> them as a separate library?
>
> I am hopeful I can wrap up our internal development within 2 days and
> make it public, but I'm willing to give a sneak preview to a tacos
> committer or two, if anyone wants it, although it will be rough around
> the edges.
>
> --sam
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd_______________________________________________
> Tacos-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/tacos-devel
>
>
--
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel
--
Jesse Kuhnert
Tacos/Tapestry, team member/developer
Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
