http://tacoscomponents.jot.com/WikiHome/ReportGrid+Example
On 5/4/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
Well, I tried to attach an example showing the ReportGrid widget, but
the file was too large (courtesy of mochikit and dojo). So I created
a page in the wiki and uploaded a tgz. It is j
Well, I tried to attach an example showing the ReportGrid widget, but
the file was too large (courtesy of mochikit and dojo). So I created
a page in the wiki and uploaded a tgz. It is just a static page,
rather than a tap component, but I'll have that out shortly. I've
been in meetings for the
Sam, you're the man.Sleep is overrated anyway! :-DThanks on behalf of the comunity for your efforts...Good luck for the rest of the task... Andy's here... you have all the help you could wish! :-)Will be waiting for the results...
Cheers,On 5/4/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
On 5/4/06,
Just got back.
Last 3 hours where as if someone was playing towers of hanoi
with my car's tyres.
So, if there's anything not car related i can see, please, send along!
>From Sam Gendler <[EMAIL PROTECTED]>:
> OK, I have it working in a 'tacos-style' within my own codebase. I
> will now rename p
Thanks for taking the time...
I now get the point of 58...
>From Leonardo Quijano Vincenzi <[EMAIL PROTECTED]>:
> [EMAIL PROTECTED] wrote:
> > I'm in favor of closing
> > http://tacoscomponents.jot.com/BugReporter/Bug58 and
> > http://tacoscomponents.jot.com/BugReporter/Bug104
> > as won't fix.
>
OK, I have it working in a 'tacos-style' within my own codebase. I
will now rename packages and attempt to integrate with a tacos build
before zipping it up and mailing it to Jesse or anyone else that wants
it. This is just the ReportGrid so far, although I expect the others
to go much faster.
On 5/4/06, Pedro Viegas <[EMAIL PROTECTED]> wrote:
Sorry for the apparently obvious question earlier, but i'm guessing your so
sick of trial and error by now you may be in that "how didn't I see that"
fase... ;-)
Pretty much, but I figured it out. Just had to do everything in
dojo.addOnLoad()
OK, I've got it all figured out. It sure is hard to be a tapestry
neophyte, tacos neophyte, and javascript neophyte all at the same
time. I feel like I felt in my first programming class in college,
when I knew absolutely nothing and everything was a struggle. I'll
get there, though.
--sam
Sorry for the apparently obvious question earlier, but i'm guessing your so sick of trial and error by now you may be in that "how didn't I see that" fase... ;-)On 5/4/06,
Pedro Viegas <[EMAIL PROTECTED]> wrote:
Do you have a browser _javascript_ console?Have you checked for runtime errors?Maybe t
Do you have a browser _javascript_ console?Have you checked for runtime errors?Maybe the dojo debug is not picking it up...Don't know what else to say...Try posting your code here so more eyes can try to track down the problem.
On 5/4/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
I am completely stump
[EMAIL PROTECTED] wrote:
I'm in favor of closing
http://tacoscomponents.jot.com/BugReporter/Bug58 and
http://tacoscomponents.jot.com/BugReporter/Bug104
as won't fix.
For more details, see the above links.
I'll just wait 1-2 days, in case someone objects or has a better solution
Andy
-
Do you have dojo debug turned on ? Are you using firefox, are there any js errors? What happens if you add a "dojo.debug("my widget :" + dojo.widget.byId(myWidgetId)) " at the end of your page to see if it got created at all ?
I reccomend installing the "FireBug" extension if you haven't already.O
I am completely stumped now. The page loads without any errors. All
the relevant lines of code appear to execute, according to dojo.debug,
but nothing ever appears in my page any longer. Needless to say, the
version that didn't use dojo.widget.createWidget() had no such
problems. All code is i
Mail in your problems Sam... maybe one of us out here can help.By your initial mail your drilling into this for 14 hours straight... even for an all GMT-8 to GMT+3 kind of guy, take a break before you break! ;-)
Mail those errors if you think it'll help.I'm sure someone will be able to lend you a h
Can I just say, out of sheer frustration, that there has never been an
open source project more in need of documentation than dojo - and I
was an early Zope user, so I know of what I speak. It is intended to
be something like a libc for javaascript, but can anyone imagine
writing a c program with
On 5/4/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
OK, guys. Thanks. That helped. Although I still can't get it to
work, I am on to a new bug. I think I am just minutes away.
--sam
On 5/4/06, Pedro Viegas <[EMAIL PROTECTED]> wrote:
> Close call Jesse... nearly bumped our heads sending our e
OK, guys. Thanks. That helped. Although I still can't get it to
work, I am on to a new bug. I think I am just minutes away.
--sam
On 5/4/06, Pedro Viegas <[EMAIL PROTECTED]> wrote:
Close call Jesse... nearly bumped our heads sending our emails through the
mailing list channel there! :-D
Close call Jesse... nearly bumped our heads sending our emails through the mailing list channel there! :-DOn 5/4/06, Jesse Kuhnert <
[EMAIL PROTECTED]> wrote:The last argument to createWidget needs to be an actual node. (I think) Ie
dojo.byId("testdiv") )On 5/4/06, Sam Gendler <
[EMAIL PROTECTED]
Hi there Sam...been tracking this topic literally salivating with anticipation. :-)
Not a very experienced developer in Tapestry and dojo, just starting, so pardon my eventually basic and silly remark.
I think that you have to pass a dom node to the createWidget as in:
var node = dojo.byId("testD
The last argument to createWidget needs to be an actual node. (I think) Ie dojo.byId("testdiv") )On 5/4/06, Sam Gendler <
[EMAIL PROTECTED]> wrote:Home come this works:enableMultipleSelect="true" rowAlternateClass="alternateRow"headClass="fixedHeader" tfootClass="fixedFooter"containerClass="tableCo
Home come this works:
But this does not:
dojo.widget.createWidget("ReportGrid", {
headClass:"fixedHeader",
headerSortUpClass:"headerSortUp",
tfootClass:"fixedFooter",
maxRows:20,
headerSortDownClass:"headerSortDown",
containerClass:"tableContainer",
rowAlternateClass:"alternateRow",
id:"repGri
I've solved the informalParameter thing by just passing the
renderInformalParameter method an IMarkupWriter which populates a Map
when the attribute() method is called. Then I retrieve the Map and do
with it what I want.
--sam
On 5/4/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
I'm not using So
I'm not using SortableTable. I am using ReportGrid, which someone
attached to a bug in dojo. We then modified the heck out of it, but
it is much more functional (and faster) than SortableTable. It
formats numbers and dates using java standard format strings that can
be specified as a parameter
Oh cool you're using the SortableTable! For _javascript_ + using .script files you shouldn't need to worry about when / where to put it. Tacos captures the script output and makes sure it only gets invoked when it's "safe" from the documents perspective.
You'll notice that almost all of the tacos
On 5/4/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
The wiki is open to editing by guests, but I can give you a real account.
Yeah, I already figured that out. I added a couple of lines ot the
build instructions.
---
Using Tomcat but need
OK, I've simplified the problem a bit. I can leave the table data the
way it, for now. I just need to replace the following code:
writeScript(cycle, pageRenderSupport);
writer.begin("div");
writer.attribute("dojoType", "ReportGrid");
writer.attribute("widgetId", get
OK, I need some help. I am a little confused about too many things.
Could someone with some tacos component dev experience get in touch
with me offline and I'll share the ReportGrid component as it exists
in my current app, and then work with me to move it over to tacos.
Once I've done that one
HmmmI guess adding them to the dtacos package won't hurt right? I only named it dtacos so it wouldn't conflict with the existing tacos.js. My original intention was to replace tacos.js with a more friendly (readable) dojo packaged version of the same.
On 5/4/06, Sam Gendler <[EMAIL PROTECTED]>
Should I add my dojo widgets to the src/js/dtacos package or create a
different package?
--sam
On 5/4/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
On 5/4/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
> http://tacoscomponents.jot.com/BuildingTacos
>
> Don't forget to run "ant fetch-libs" first.
The wiki is open to editing by guests, but I can give you a real account.On 5/4/06, Sam Gendler <[EMAIL PROTECTED]
> wrote:On 5/4/06, Jesse Kuhnert <[EMAIL PROTECTED]
> wrote:> http://tacoscomponents.jot.com/BuildingTacos>> Don't forget to run "ant fetch-libs" first.I can't forget to do so, because
On 5/4/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
http://tacoscomponents.jot.com/BuildingTacos
Don't forget to run "ant fetch-libs" first.
I can't forget to do so, because there is no mention of it anywhere on
the tacos site ;-) Perhaps an error message suggesting that target
when it fails
http://tacoscomponents.jot.com/BuildingTacosDon't forget to run "ant fetch-libs" first.On 5/4/06,
Sam Gendler <[EMAIL PROTECTED]> wrote:
BUILD FAILED/Users/sgendler/src/euroclick/tacos/build.xml:61: The following erroroccurred while executing this line:/Users/sgendler/src/euroclick/tacos/build.xml
BUILD FAILED
/Users/sgendler/src/euroclick/tacos/build.xml:61: The following error
occurred while executing this line:
/Users/sgendler/src/euroclick/tacos/build.xml:70:
/Users/sgendler/src/euroclick/tacos/lib not found.
On 5/4/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
And are there build instr
And are there build instructions anywhere?
On 5/4/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
The Readme.txt file in the trunk of tacos has a most recent entry of
nearly a year ago. Is the trunk currently the latest code, or is that
in some other branch?
-sam
On 5/4/06, Sam Gendler <[EMAIL PR
The Readme.txt file in the trunk of tacos has a most recent entry of
nearly a year ago. Is the trunk currently the latest code, or is that
in some other branch?
-sam
On 5/4/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
easy enough
On 5/4/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
> If you vie
easy enough
On 5/4/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
If you view the source (subversion browser on sf ), any of the tacos
components do this.. IE
dojo.widget.createWidget(type, props {}, node);
On 5/4/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
>
Right now, the tapestry component j
The tacos demo does this and it works. Maybe start there ?On 5/4/06, Jonathan Bullkich <[EMAIL PROTECTED]
> wrote:
Has anyone tried this?
I can't get it to work. It seems that the widget
is not updated with the new html data.
Any help would be appreciated.
From:
[EMAI
If you view the source (subversion browser on sf ), any of the tacos components do this.. IE dojo.widget.createWidget(type, props {}, node);On 5/4/06,
Sam Gendler <[EMAIL PROTECTED]> wrote:
Right now, the tapestry component just writes the appropriate div withdojoType attribute plus whatever else
Has anyone tried this?
I can't get it to work. It seems that the widget
is not updated with the new html data.
Any help would be appreciated.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Bullkich
Sent: Monday, May 01, 2006 7:03 PM
To: tacos-devel@lis
Right now, the tapestry component just writes the appropriate div with
dojoType attribute plus whatever else is necessary. THey can be
modified easily enough, but I'm not entirely sure what you mean by
'create the widgets using javascript,' but if you can provide an
example, we can get them modif
It's speed. The widget parser is nice, but letting it parse ~all~ content on all of your pages while searching for widgets is a bit much for performance.On 5/4/06,
Andreas Andreou <[EMAIL PROTECTED]> wrote:
There's one last thing...How do you create the dojo widgets?By using _javascript_ or by usi
There's one last thing...
How do you create the dojo widgets?
By using javascript or by using html + dojo's attributes (dojo:type
e.t.c.) ?
I can't recall the initial reason (perhaps it was html validation)
but all tacos components are built with javascript and we even have
djConfig.parseWidgets=f
Documentation? What's that. Seriously, I am working on doing the
final polish and removal of proprietary code today, and I hope to have
them available later today or tomorrow, depending on my schedule. I
still have to change package names and such (and I am a vi guy, so I
get no help from my ed
Indeed. They sound like great additions that would be welcome. (assuming that they come with documentation/selenium or other sort of tests/ examples in demo app). If they look like good components and all I'm sure something could be done about commit access.
On 5/4/06, [EMAIL PROTECTED] <[EMAIL P
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 mul
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
compo
46 matches
Mail list logo
