Thanks Lance, I was able to get it to work.
I did notice you have all your js files on the main classpath and will need
to be moved to META-INF. I'm willing to do the work, but I still don't know
enough about RequireJS, modules, etc to know what the best practice is.
AssetsModule.AssetSource Pack
On Sat, 07 Dec 2013 14:13:10 -0200, Balázs Palcsó
wrote:
I have raised a bug in JIRA for this:
https://issues.apache.org/jira/browse/TAP5-2254
Thanks!
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
Help me spend a whole month wo
I think the same invoice that issue when you do freelancer work should do.
Not sure if there special rules if the company receiving the invoice is in
the EU.
Though I am not sure how does crowd funding changes the rules of invoicing.
Especially if the goal is not met.
Regards,
Balazs
On 7 Decem
On Sat, 07 Dec 2013 13:30:16 -0200, Balázs Palcsó
wrote:
Hi Thiago,
Hi!
I was wondering if my company could get an invoice of the amount
contributed if it contributes?
Good question. What are the requirements of this invoice?
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernat
I have raised a bug in JIRA for this:
https://issues.apache.org/jira/browse/TAP5-2254
On 5 December 2013 22:22, Balázs Palcsó wrote:
> I forgot to post the definition of @Validate("password") which makes the
> password field the first required field in the form (and making it to owner
> of the
Hi Thiago,
I was wondering if my company could get an invoice of the amount
contributed if it contributes?
Best regards,
Balazs
On Nov 27, 2013, at 12:02 PM, Howard Lewis Ship wrote:
> On Wed, Nov 27, 2013 at 8:07 AM, Thiago H de Paula Figueiredo <
> thiag...@gmail.com> wrote:
>
>> On Wed, 27 N
Thiago is correct. You can default the value of fwtype and then override it
by component. For example you could default your site to use small buttons
then set fwtype for the ones you want to large.
On Fri, Dec 6, 2013 at 1:18 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Fr
On Fri, 06 Dec 2013 22:57:14 -0200, John Prestel
wrote:
I'm building a service MasterFooProvider that takes contributions of type
FooProvider. I'd really love for one my FooProvider implementations,
ConfigurableFooProvider, to be able to take contributions of its own (of
type String), so its
I see what you mean Lance, yes that would be a neat solution so long as it is
performant.
John
- Original Message -
From: Lance Java
To: Tapestry users
Sent: Saturday, December 07, 2013 10:29 AM
Subject: Re: component paramter frustrations
Yep, I know. Which is why I sugg
Hmm... I thought it would pick it up from my github maven repo.
lazan-releases
https://github.com/uklance/releases/raw/master
I'll create a 5.4 fork when I get some time.
On 7 Dec 2013 11:15, "George Christman" wrote:
> That would be great if you could do that. I tried to do it, but I was
>
That would be great if you could do that. I tried to do it, but I was
missing your offline jar.
On Sat, Dec 7, 2013 at 3:10 AM, Lance Java wrote:
> Seems like the JSONObject(String...) constructor has disappeared.
>
> It might just require a recompile against 5.4. I don't have the source in
> fr
Yep, I know. Which is why I suggested a new strategy which still uses the
URL but uses the context instead of request parameters. Thus prettying up
your url without explicitly requiring you to add extra bits to the context.
On 7 Dec 2013 10:13, "John" wrote:
> Dmitry helped me identify the root
Dmitry helped me identify the root cause of my problem. The parameters were
bound to a FLASH persisted property hence they lost their initial values after
first use. I just made them CLIENT and (appart from the long client state
request payload) that issue is resolved satisfactorily.
John
---
Since you want two services which implement FooProvider you'll need to
disambiguate either by serviceId or by marker annotation. See here for info
http://tapestry.apache.org/defining-tapestry-ioc-services.html
Another solution is to instead use 2 service interfaces (FooProvider and
FooOverrides).
Seems like the JSONObject(String...) constructor has disappeared.
It might just require a recompile against 5.4. I don't have the source in
front of me but I'm guessing it's swapped to JSONObject(Object...) which is
why I guess a recompile will fix.
Perhaps you could write your own persistance strategy.
@Persist(MyPersistConstants.EVENT_CONTEXT)
Which implicitly appends to the actionlink / eventlink context clientside
and updates the fields serverside before delegating to the event.
16 matches
Mail list logo
