Thanks Thiago, I didn't know that servlet 3.0 supports META-INF. That will
help a lot, actually.
As far as the IDE issues, I was just trying to be too smart for my own good:
I tried to do the following to separate the source from resources types in the
IDE:
META
I believe if you keep prototype, there is a compatibility module that keeps
that namespace. I am not 100% sure about that because I never tested that
scenario.
On Sep 11, 2013, at 11:34 AM, Norman Franke wrote:
> What about the missing Zone Manager? I have a number of scripts that need
> tha
On Wed, Sep 11, 2013 at 8:44 AM, Lenny Primak wrote:
> I believe if you keep prototype, there is a compatibility module that
> keeps that namespace. I am not 100% sure about that because I never tested
> that scenario.
>
> On Sep 11, 2013, at 11:34 AM, Norman Franke wrote:
>
> > What about the mi
What about the missing Zone Manager? I have a number of scripts that need that.
If it's missing, then he is partially correct in that a good deal of things
will need to be re-written.
Norman Franke
Answering Service for Directors, Inc.
www.myasd.com
On Sep 10, 2013, at 6:57 PM, Thiago H de Pa
Hi guys,
I've been recently trying to convert some of our client apps to tapestry 5.4
I am using alpha-17 as of this report.
All of these depend on the FlowLogix library so one of the first tasks is to
migrate the library.
Here are some first impressions so far:
Goals:
- Migrate to T5.4
- Mi
On Tue, 10 Sep 2013 20:12:37 -0300, Lenny Primak
wrote:
I just realized there is another issue that I came across with assets.
We use netbeans and it doesn't support having META-INF/assets very well
for maven projects.
Define "doesn't support very well". I don't use NetBeans, so I got
c
All good points, Thiago. I agree that the way my email was worded cold be
misconstrued.
On Sep 10, 2013, at 6:57 PM, "Thiago H de Paula Figueiredo"
wrote:
> On Tue, 10 Sep 2013 18:35:07 -0300, Lenny Primak
> wrote:
>
>> You are technically correct on these points but the goals as stated in
On Tue, 10 Sep 2013 18:35:07 -0300, Lenny Primak
wrote:
You are technically correct on these points but the goals as stated in
my post are to make a clean break with prototype.
Agreed, but the way you wrote your e-mail it seemed that everything in
JavaScript needed to be rewritten from s
I just realized there is another issue that I came across with assets.
We use netbeans and it doesn't support having META-INF/assets very well for
maven projects.
I have a simple proposal, why not /t5-assets and /t5-js-modules/ from root?
This way META-INF isn't involved, it's in the place where
On Tue, 10 Sep 2013 16:08:53 -0300, Lenny Primak
wrote:
Hi guys,
Hi!
All JavaScript basically had to be rewritten nearly from scratch (see
below)
Rewritten from scratch just because you wanted to convert you existing
JavaScript code from Prototype to jQuery. Otherwise, you wouldn't n
You are technically correct on these points but the goals as stated in my post
are to make a clean break with prototype.
On Sep 10, 2013, at 3:40 PM, "Thiago H de Paula Figueiredo"
wrote:
> On Tue, 10 Sep 2013 16:08:53 -0300, Lenny Primak
> wrote:
>
>> Hi guys,
>
> Hi!
>
>> All JavaScrip
On Tue, Sep 10, 2013 at 12:08 PM, Lenny Primak wrote:
> Hi guys,
>
> I've been recently trying to convert some of our client apps to tapestry
> 5.4
> I am using alpha-17 as of this report.
>
> All of these depend on the FlowLogix library so one of the first tasks is
> to migrate the library.
> Her
On Sun, Dec 2, 2012 at 10:00 AM, Lenny Primak wrote:
> I disagree with the statement that most people are going to be using
> Prototype or JQuery, but not both.
> We have a lot of legacy components that use Prototype, but our new
> components use JQuery.
> Those components need to function properl
On Sun, Dec 2, 2012 at 7:51 AM, Serge Eby wrote:
> Hi,
>
> Disclaimer: T5.4 is still work in progress, so this is just to provide an
> initial feedback of my experience upgrading a small pet project from T5.3.6
> to T5.4.
>
> Overall, the upgrade was smooth. I am building the Jars locally while
>
On Sun, 02 Dec 2012 13:51:04 -0200, Serge Eby wrote:
Hi,
Hi!
I ran into a few issues:
a. I still see Prototype & Scriptaculous (+t5.3-compatibility) being
loaded. How can I get rid of these completely without overriding the core
JavascriptStack?
I haven't used T5.4 yet, but I guess the
That's fair! My main point here was that I don't want to drag Prototype in if
I don't use it.
So an option to select the one(s) I need would be nice.
/Serge
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/T5-4-First-impressions-tp7583860p7583862.html
Sent from the Tape
I disagree with the statement that most people are going to be using Prototype
or JQuery, but not both.
We have a lot of legacy components that use Prototype, but our new components
use JQuery.
Those components need to function properly on the same page.
We use noConflict mode and Tapestry-JQuery
Hi,
Disclaimer: T5.4 is still work in progress, so this is just to provide an
initial feedback of my experience upgrading a small pet project from T5.3.6
to T5.4.
Overall, the upgrade was smooth. I am building the Jars locally while
skipping the tests as I know things are still in flux. I just wa
18 matches
Mail list logo
