Gah! How embarassing..
Around 6 yesterday I started writing a letter saying that, to my
chagrin, using the rleative context works so long as I've whacked my
repository and cleared all caches and so on.
Then I went on at length to say how pleased I am with this, as it
leaves me on schedule (where I thought I was otherwise going to go
over schedule), and that the tapestry team (Jesse) were to be
commended, thanked, praised even. I couldn't (and can't) say enough.
At that point, I should probably have hit send but instead I went
around the office putting with my golf ball.. so that draft -- which
read something like the gettysburg address -- is lost to us... I
almost made the shot from the other end of the office, however.
Urmm... anyway, lesson learned? The Tapestry team is always right.
Thanks again. Wonderful work, as usual. Everything's fine and I am
really, really thankful for it. I now have a customized dojo that is
tailored to my specified size. After I did that, the custom widgets in
my own domain started failing, so I just changed the relative path
from ../../../ to ../../ and those all started working... and voila.
it works.
However, I would still like to know how to build tapestry just
because... well, it's such a cool piece of code. Like the Linux
kernel... why _wouldn't_ I want to know!
:-)
Thanks again,
Josh
On 12/1/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
I'm not sure how I can help or what the exact problem is but I am very
concerned to see that you are manually building tapestry by hand.
I guess the context relative build just won't work for you? I did sit
down and specifically make sure that particular feature works. JETTY
wasn't correctly handling css relative image paths which I have filed
with them but other than that everything worked just fine.
On 11/30/06, Josh Long <[EMAIL PROTECTED]> wrote:
> OK spoke too soon on one bit --the revision youre using for dojo is hard
> coded into the dojo.js incuded so worst case i can just customize that build
> revision... However I still don't know what the tapestry revision and
> nonetheless, the resulting dojo.js breaks when i build it..
>
> Thanks in advance for any illumination,
>
> Josh
>
> On 11/30/06, Josh Long <[EMAIL PROTECTED]> wrote:
> >
> > Hello world!
> >
> > Jesse, with respect to building my own tapestry to get a dojo that's
> > customized (custom profile) and works, what's the recommended way to figure
> > out which version of dojo you used when you built it? How do you build it
> > and dojo?
> >
> > Assuming Im staring at svn head of both dojo and tapestry (or, better,
> > whatever version youve used, which seems to work but just doesnt have any of
> > the packages i really need inlined), what is my course of action?
> >
> > I tried going into [src]/tapestry-framework/src/js and then, having
> > delete the dojo directory, running
> >
> > ant package -Djava.classes.dir=. -Ddojo.dir=/home/me/Documents/Data/code/
> > dojo/buildscripts/
> >
> > Which in turn produces a tapestry-framework/src/js/dojo/dojo/dojo.js which
> > it tunrs out is 1 directory too nested for the maven build so i have to
> > manually move dojo/dojo to just dojo and then i run mvn clean install at the
> > root of the tapestry source and i get a dojo profile that works fine at
> > ${HOST}:8080/${CONTEXT_NAME}/app but not at just ${HOST}:8080/app! heh.....
> >
> > Anyway, thanks in advance, any help would be sincerely, genuinely, wholely
> > appreciated..
> >
> > Josh
> >
> >
> >
> >
> >
> >
> > my
> >
>
>
--
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
