Re: Eclipse WTP based Tapestry visual editor project update site
Hi, TapestryTools is built base on Eclipse WTP, so, if you install TapestryTools on Eclipse Classic, it has all the features of Eclipse for JavaEE, do not worry that you can not use Eclipse for JavaEE. The only problem is that you should install TapestryTools in Eclipse Classic, or there are already WTP's plugins in Eclipse JavaEE, then you can not install TapestryTools successful. 在 2011年8月24日 上午1:44，Dmitry Gusev 写道： > Gavin, > > having TapestryTools not working in Eclipse Indigo of JavaEE developer is a > sad limitation. > Are there any plans to support it in the future? > > 2011/8/23 Gavin Lei > >> Hi Igor, >> >> Please notice that you should *not* use Eclipse Indigo for JavaEE >> developer,please just use Eclipse Indigo Classic[1]. And then install >> the basic tools in my guide, after that, install TapestryTools. You >> can find the step-by-step install document here[2]. >> >> I will explain the reason, why you should not use Eclipse Indigo for >> JavaEE developer, as you know, TapestryTools is developed based on >> Eclipes WTP, there are two parts of job: >> >> 1. Add some new Eclipse plugin projects, such as >> "org.eclipse.jst.tapestry.ui" >> 2. Modify WTP's source code directory (very little, usually just add >> some entry points), for example, modify project >> "org.eclipse.jst.jsf.core" source code >> >> So TapestryTools is just a more powerful Eclipse WTP, if you use >> Eclipse for JavaEE developers which includes Eclipse WTP, then you try >> to install TapestryTools, Eclipse will find out that there are already >> many projects(for example org.eclipse.jst.jsf.core) in it, it will not >> updated this plugin with same name includes in TapestryTools, so you >> will miss some features of TapestryTools. >> >> So keep in mind that please just use Eclipse Classic :-) >> >> [1] http://www.eclipse.org/downloads/packages/eclipse-classic-37/indigor >> [2] >> http://code.google.com/p/tapestrytools/wiki/TapestryTools_Install_Guide >> >> 在 2011年8月23日 下午9:42，Igor Drobiazko 写道： >> > Hi Gavin, >> > I installed TapestryTools into "Eclipse IDE for Java EE Developers" [1]. >> I >> > think this is "all-in-one" package and should contain all the required >> > plugins. Unfortunately I'm experiencing problems which I reported to you >> in >> > a Skype chat. After installing the mentioned plugins manually, the >> problem >> > with missing components in the palette still exists. >> > Can you please install [1] om your machine and reproduce the problem? >> > [1] >> http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/indigor >> > Thank you >> > >> > 2011/8/22 Gavin Lei >> >> >> >> Hi guys, >> >> >> >> Important Notice: >> >> >> >> Before you install TapestryTools in Eclipse Indigo to have a trial of >> >> it, you should install these three basic tools first: >> >> >> >> 1. EMF and XSD SDK Combined EMF and EMF-XSD SDK >> >> 2.GEF SDK 3.7 (GEF Code and Source) >> >> 3. DTP sdk v1.9 (Code and Source) >> >> >> >> You guys can find the install guide documents here[1], and the >> >> download urls for these plugins is here[2], this step is very >> >> important, or your TapestryTools can not work properly, please keep >> >> it in mind, thank you :-) >> >> >> >> [1] >> >> http://code.google.com/p/tapestrytools/wiki/TapestryTools_Install_Guide >> >> [2] >> >> >> http://download.eclipse.org/webtools/downloads/drops/R3.3.0/R-3.3.0-20110607160810/ >> >> >> >> 在 2011年8月21日 下午7:54，Gavin Lei 写道： >> >> > Hi Igor, >> >> > >> >> > I have almost finished Issue 10[1] develoment job, users can >> >> > configuration custom. After user choose custom components packages, >> >> > and collect all the custom components, they will be available in Web >> >> > Page Editor's palette, and also in *.tml's auto-complete list. >> >> > >> >> > I have submited the source code to SVN workspace,updated the update >> >> > center[2], and i wrote a simple guide document[3] about this feature, >> >> > you guys can have a trial of it. >> >> > >> >> > [1] http://code.google.com/p/tapestrytools/issues/detail?id=10 >> >> > [2] http://tapestrytools.googlecode.com/svn/TapestryTools_UpdateSite/ >> >> > [3] >> >> > >> http://code.google.com/p/tapestrytools/wiki/Custom_Components_support_in_TapestryTools >> >> > >> >> > 在 2011年8月15日 下午2:52，Igor Drobiazko 写道： >> >> >> Hi Gavin, >> >> >> if you are stuck with supporting Live Class Reloading, please go >> ahead >> >> >> with >> >> >> other features, such as issue 10. Maybe we could concentrate on Live >> >> >> Class >> >> >> Reloading after GSOC deadline. >> >> >> Thank you. >> >> >> >> >> >> 2011/8/13 Gavin Lei >> >> >>> >> >> >>> Hi Igor, >> >> >>> >> >> >>> In the schedule, we should focus on Live Class Reloading support for >> >> >>> TapestryTools, but according to the survey job to Eclipse's WTP, we >> do >> >> >>> not have a good solution to resolve this problem, May be we should >> not >> >> >>> change WTP's running time module, it is just my personal idea. If >> you >> >> >>> have any
Re: [jira] [Commented] (TAP5-1508) Reduce memory utilization of Tapestry page instances
> TAP5-1508: Contributions to CCTW2 must be qualified with @Primary when > using @Contribute, to avoid collision with MetaWorker service Ack... I just spent an hour trying to figure out why my CCTW2 contributions started failing between alpha-2 and alpha-13. Howard, can you (or anyone who understands) elaborate on what this means? I think this is going to need some special documentation if it's going to be the case going forward. Josh On Thu, Jul 21, 2011 at 6:37 PM, Hudson (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/TAP5-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069342#comment-13069342 > ] > > Hudson commented on TAP5-1508: > -- > > Integrated in tapestry-trunk-freestyle #428 (See > [https://builds.apache.org/job/tapestry-trunk-freestyle/428/]) > TAP5-1508: Contributions to CCTW2 must be qualified with @Primary when > using @Contribute, to avoid collision with MetaWorker service > > hlship : > http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1149416 > Files : > * > /tapestry/tapestry5/trunk/tapestry-hibernate/src/main/java/org/apache/tapestry5/hibernate/HibernateModule.java > > >> Reduce memory utilization of Tapestry page instances >> >> >> Key: TAP5-1508 >> URL: https://issues.apache.org/jira/browse/TAP5-1508 >> Project: Tapestry 5 >> Issue Type: Improvement >> Components: tapestry-core >> Affects Versions: 5.3 >> Reporter: Howard M. Lewis Ship >> >> This is an umbrella bug for a number of changes aimed at reducing the >> overall memory footprint of a Tapestry page. Tapestry pages have been seen >> to be quite large in some production sites, and the shared-instance strategy >> introduced in 5.2 is still insufficient. A significant amount of space is >> consumed using Maps and Lists (for bindings, of sub-components, etc.) in a >> way that is optimized for a smaller code base and efficient read access, >> even though most of the information is only read when a page is first >> loaded, and is rarely needed or accessed after that. > > -- > This message is automatically generated by JIRA. > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Quartz-like CRON expressions for PereodicExecutor
It would probably be better to do this sooner, to ensure that the API I created is sufficient. I kind of winged it. On Tue, Aug 23, 2011 at 4:04 PM, Taha Hafeez wrote: > +1 > > I was also thinking about it but in a separate module e.g. > tapestry-schedule or something > > On Wed, Aug 24, 2011 at 3:23 AM, Igor Drobiazko > wrote: >> Now that we have PeriodicExecutor service, I'm thinking about the >> improvements. It would be awesome to support CRON expressions for job >> scheduling. >> >> It's obvious that implementing CRON parser is a waste of time, but making >> Tapestry depend on Quartz is a no-go. I'd like to copy >> Quartz's CronExpression [1] class into tapestry-core. We did it already for >> JSON and some Apache Commons utilities. CronExpression would be definitely >> worth to do it again. >> >> >> [1] >> http://svn.terracotta.org/fisheye/browse/Quartz/tags/quartz-2.0.2/quartz/src/main/java/org/quartz/CronExpression.java?r=HEAD >> >> -- >> Best regards, >> >> Igor Drobiazko >> http://tapestry5.de >> > > > > -- > Regards > > Taha Hafeez Siddiqi (tawus) > http://tawus.wordpress.com > > - > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Quartz-like CRON expressions for PereodicExecutor
+1 I was also thinking about it but in a separate module e.g. tapestry-schedule or something On Wed, Aug 24, 2011 at 3:23 AM, Igor Drobiazko wrote: > Now that we have PeriodicExecutor service, I'm thinking about the > improvements. It would be awesome to support CRON expressions for job > scheduling. > > It's obvious that implementing CRON parser is a waste of time, but making > Tapestry depend on Quartz is a no-go. I'd like to copy > Quartz's CronExpression [1] class into tapestry-core. We did it already for > JSON and some Apache Commons utilities. CronExpression would be definitely > worth to do it again. > > > [1] > http://svn.terracotta.org/fisheye/browse/Quartz/tags/quartz-2.0.2/quartz/src/main/java/org/quartz/CronExpression.java?r=HEAD > > -- > Best regards, > > Igor Drobiazko > http://tapestry5.de > -- Regards Taha Hafeez Siddiqi (tawus) http://tawus.wordpress.com - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Quartz-like CRON expressions for PereodicExecutor
Now that we have PeriodicExecutor service, I'm thinking about the improvements. It would be awesome to support CRON expressions for job scheduling. It's obvious that implementing CRON parser is a waste of time, but making Tapestry depend on Quartz is a no-go. I'd like to copy Quartz's CronExpression [1] class into tapestry-core. We did it already for JSON and some Apache Commons utilities. CronExpression would be definitely worth to do it again. [1] http://svn.terracotta.org/fisheye/browse/Quartz/tags/quartz-2.0.2/quartz/src/main/java/org/quartz/CronExpression.java?r=HEAD -- Best regards, Igor Drobiazko http://tapestry5.de
Re: Tapestry PeriodicExecutor
On Mon, Aug 22, 2011 at 2:22 PM, Taha Hafeez wrote: > Actually I was preparing a blog post for the new Tapestry 5.3 features > (Igor already beat me to it!) > Sorry for that :) > > > ObjectLocator.autobind() will internally do the rest > > This would definitely make my live easier. -- Best regards, Igor Drobiazko http://tapestry5.de
Re: Eclipse WTP based Tapestry visual editor project update site
Gavin, having TapestryTools not working in Eclipse Indigo of JavaEE developer is a sad limitation. Are there any plans to support it in the future? 2011/8/23 Gavin Lei > Hi Igor, > > Please notice that you should *not* use Eclipse Indigo for JavaEE > developer,please just use Eclipse Indigo Classic[1]. And then install > the basic tools in my guide, after that, install TapestryTools. You > can find the step-by-step install document here[2]. > > I will explain the reason, why you should not use Eclipse Indigo for > JavaEE developer, as you know, TapestryTools is developed based on > Eclipes WTP, there are two parts of job: > > 1. Add some new Eclipse plugin projects, such as > "org.eclipse.jst.tapestry.ui" > 2. Modify WTP's source code directory (very little, usually just add > some entry points), for example, modify project > "org.eclipse.jst.jsf.core" source code > > So TapestryTools is just a more powerful Eclipse WTP, if you use > Eclipse for JavaEE developers which includes Eclipse WTP, then you try > to install TapestryTools, Eclipse will find out that there are already > many projects(for example org.eclipse.jst.jsf.core) in it, it will not > updated this plugin with same name includes in TapestryTools, so you > will miss some features of TapestryTools. > > So keep in mind that please just use Eclipse Classic :-) > > [1] http://www.eclipse.org/downloads/packages/eclipse-classic-37/indigor > [2] > http://code.google.com/p/tapestrytools/wiki/TapestryTools_Install_Guide > > 在 2011年8月23日 下午9:42，Igor Drobiazko 写道： > > Hi Gavin, > > I installed TapestryTools into "Eclipse IDE for Java EE Developers" [1]. > I > > think this is "all-in-one" package and should contain all the required > > plugins. Unfortunately I'm experiencing problems which I reported to you > in > > a Skype chat. After installing the mentioned plugins manually, the > problem > > with missing components in the palette still exists. > > Can you please install [1] om your machine and reproduce the problem? > > [1] > http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/indigor > > Thank you > > > > 2011/8/22 Gavin Lei > >> > >> Hi guys, > >> > >> Important Notice: > >> > >> Before you install TapestryTools in Eclipse Indigo to have a trial of > >> it, you should install these three basic tools first: > >> > >> 1. EMF and XSD SDK Combined EMF and EMF-XSD SDK > >> 2.GEF SDK 3.7 (GEF Code and Source) > >> 3. DTP sdk v1.9 (Code and Source) > >> > >> You guys can find the install guide documents here[1], and the > >> download urls for these plugins is here[2], this step is very > >> important, or your TapestryTools can not work properly, please keep > >> it in mind, thank you :-) > >> > >> [1] > >> http://code.google.com/p/tapestrytools/wiki/TapestryTools_Install_Guide > >> [2] > >> > http://download.eclipse.org/webtools/downloads/drops/R3.3.0/R-3.3.0-20110607160810/ > >> > >> 在 2011年8月21日 下午7:54，Gavin Lei 写道： > >> > Hi Igor, > >> > > >> > I have almost finished Issue 10[1] develoment job, users can > >> > configuration custom. After user choose custom components packages, > >> > and collect all the custom components, they will be available in Web > >> > Page Editor's palette, and also in *.tml's auto-complete list. > >> > > >> > I have submited the source code to SVN workspace,updated the update > >> > center[2], and i wrote a simple guide document[3] about this feature, > >> > you guys can have a trial of it. > >> > > >> > [1] http://code.google.com/p/tapestrytools/issues/detail?id=10 > >> > [2] http://tapestrytools.googlecode.com/svn/TapestryTools_UpdateSite/ > >> > [3] > >> > > http://code.google.com/p/tapestrytools/wiki/Custom_Components_support_in_TapestryTools > >> > > >> > 在 2011年8月15日 下午2:52，Igor Drobiazko 写道： > >> >> Hi Gavin, > >> >> if you are stuck with supporting Live Class Reloading, please go > ahead > >> >> with > >> >> other features, such as issue 10. Maybe we could concentrate on Live > >> >> Class > >> >> Reloading after GSOC deadline. > >> >> Thank you. > >> >> > >> >> 2011/8/13 Gavin Lei > >> >>> > >> >>> Hi Igor, > >> >>> > >> >>> In the schedule, we should focus on Live Class Reloading support for > >> >>> TapestryTools, but according to the survey job to Eclipse's WTP, we > do > >> >>> not have a good solution to resolve this problem, May be we should > not > >> >>> change WTP's running time module, it is just my personal idea. If > you > >> >>> have any good advises, we can discuss it together. > >> >>> > >> >>> Now, As GSoC's deadline is coming, i think may be we should do some > >> >>> thing useful before the deadline, i will start the next feature in > the > >> >>> schedule: > >> >>> > >> >>> All the available component should appear in the palette view [1] > >> >>> > >> >>> You added this issue, it is hard to finish this feature because it > ask > >> >>> us to change Web Page Editor's palette's items loading module, we > need > >> >>> at least 10 days to do it. So, i would like to start
Re: Eclipse WTP based Tapestry visual editor project update site
Hi Igor, Please notice that you should *not* use Eclipse Indigo for JavaEE developer,please just use Eclipse Indigo Classic[1]. And then install the basic tools in my guide, after that, install TapestryTools. You can find the step-by-step install document here[2]. I will explain the reason, why you should not use Eclipse Indigo for JavaEE developer, as you know, TapestryTools is developed based on Eclipes WTP, there are two parts of job: 1. Add some new Eclipse plugin projects, such as "org.eclipse.jst.tapestry.ui" 2. Modify WTP's source code directory (very little, usually just add some entry points), for example, modify project "org.eclipse.jst.jsf.core" source code So TapestryTools is just a more powerful Eclipse WTP, if you use Eclipse for JavaEE developers which includes Eclipse WTP, then you try to install TapestryTools, Eclipse will find out that there are already many projects(for example org.eclipse.jst.jsf.core) in it, it will not updated this plugin with same name includes in TapestryTools, so you will miss some features of TapestryTools. So keep in mind that please just use Eclipse Classic :-) [1] http://www.eclipse.org/downloads/packages/eclipse-classic-37/indigor [2] http://code.google.com/p/tapestrytools/wiki/TapestryTools_Install_Guide 在 2011年8月23日 下午9:42，Igor Drobiazko 写道： > Hi Gavin, > I installed TapestryTools into "Eclipse IDE for Java EE Developers" [1]. I > think this is "all-in-one" package and should contain all the required > plugins. Unfortunately I'm experiencing problems which I reported to you in > a Skype chat. After installing the mentioned plugins manually, the problem > with missing components in the palette still exists. > Can you please install [1] om your machine and reproduce the problem? > [1] > http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/indigor > Thank you > > 2011/8/22 Gavin Lei >> >> Hi guys, >> >> Important Notice: >> >> Before you install TapestryTools in Eclipse Indigo to have a trial of >> it, you should install these three basic tools first: >> >> 1. EMF and XSD SDK Combined EMF and EMF-XSD SDK >> 2.GEF SDK 3.7 (GEF Code and Source) >> 3. DTP sdk v1.9 (Code and Source) >> >> You guys can find the install guide documents here[1], and the >> download urls for these plugins is here[2], this step is very >> important, or your TapestryTools can not work properly, please keep >> it in mind, thank you :-) >> >> [1] >> http://code.google.com/p/tapestrytools/wiki/TapestryTools_Install_Guide >> [2] >> http://download.eclipse.org/webtools/downloads/drops/R3.3.0/R-3.3.0-20110607160810/ >> >> 在 2011年8月21日 下午7:54，Gavin Lei 写道： >> > Hi Igor, >> > >> > I have almost finished Issue 10[1] develoment job, users can >> > configuration custom. After user choose custom components packages, >> > and collect all the custom components, they will be available in Web >> > Page Editor's palette, and also in *.tml's auto-complete list. >> > >> > I have submited the source code to SVN workspace,updated the update >> > center[2], and i wrote a simple guide document[3] about this feature, >> > you guys can have a trial of it. >> > >> > [1] http://code.google.com/p/tapestrytools/issues/detail?id=10 >> > [2] http://tapestrytools.googlecode.com/svn/TapestryTools_UpdateSite/ >> > [3] >> > http://code.google.com/p/tapestrytools/wiki/Custom_Components_support_in_TapestryTools >> > >> > 在 2011年8月15日 下午2:52，Igor Drobiazko 写道： >> >> Hi Gavin, >> >> if you are stuck with supporting Live Class Reloading, please go ahead >> >> with >> >> other features, such as issue 10. Maybe we could concentrate on Live >> >> Class >> >> Reloading after GSOC deadline. >> >> Thank you. >> >> >> >> 2011/8/13 Gavin Lei >> >>> >> >>> Hi Igor, >> >>> >> >>> In the schedule, we should focus on Live Class Reloading support for >> >>> TapestryTools, but according to the survey job to Eclipse's WTP, we do >> >>> not have a good solution to resolve this problem, May be we should not >> >>> change WTP's running time module, it is just my personal idea. If you >> >>> have any good advises, we can discuss it together. >> >>> >> >>> Now, As GSoC's deadline is coming, i think may be we should do some >> >>> thing useful before the deadline, i will start the next feature in the >> >>> schedule: >> >>> >> >>> All the available component should appear in the palette view [1] >> >>> >> >>> You added this issue, it is hard to finish this feature because it ask >> >>> us to change Web Page Editor's palette's items loading module, we need >> >>> at least 10 days to do it. So, i would like to start this part of job >> >>> and finished it in GSoC's period. Is it OK ? >> >>> >> >>> Meanwhile, if you have any advises about Live Class Reloading things, >> >>> please talk with me, we can make a plan or something, and then discuss >> >>> when to start the Live Class Reloading job. >> >>> >> >>> [1] http://code.google.com/p/tapestrytools/issues/detail?id=10 >> >>> >> >>> 在 2011年7月19日 下午3:50，Gavin Lei 写
Re: Eclipse WTP based Tapestry visual editor project update site
Hi Gavin, I installed TapestryTools into "Eclipse IDE for Java EE Developers" [1]. I think this is "all-in-one" package and should contain all the required plugins. Unfortunately I'm experiencing problems which I reported to you in a Skype chat. After installing the mentioned plugins manually, the problem with missing components in the palette still exists. Can you please install [1] om your machine and reproduce the problem? [1] http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/indigor Thank you 2011/8/22 Gavin Lei > Hi guys, > > Important Notice: > > Before you install TapestryTools in Eclipse Indigo to have a trial of > it, you should install these three basic tools first: > > 1. EMF and XSD SDK Combined EMF and EMF-XSD SDK > 2.GEF SDK 3.7 (GEF Code and Source) > 3. DTP sdk v1.9 (Code and Source) > > You guys can find the install guide documents here[1], and the > download urls for these plugins is here[2], this step is very > important, or your TapestryTools can not work properly, please keep > it in mind, thank you :-) > > [1] > http://code.google.com/p/tapestrytools/wiki/TapestryTools_Install_Guide > [2] > http://download.eclipse.org/webtools/downloads/drops/R3.3.0/R-3.3.0-20110607160810/ > > 在 2011年8月21日 下午7:54，Gavin Lei 写道： > > Hi Igor, > > > > I have almost finished Issue 10[1] develoment job, users can > > configuration custom. After user choose custom components packages, > > and collect all the custom components, they will be available in Web > > Page Editor's palette, and also in *.tml's auto-complete list. > > > > I have submited the source code to SVN workspace,updated the update > > center[2], and i wrote a simple guide document[3] about this feature, > > you guys can have a trial of it. > > > > [1] http://code.google.com/p/tapestrytools/issues/detail?id=10 > > [2] http://tapestrytools.googlecode.com/svn/TapestryTools_UpdateSite/ > > [3] > http://code.google.com/p/tapestrytools/wiki/Custom_Components_support_in_TapestryTools > > > > 在 2011年8月15日 下午2:52，Igor Drobiazko 写道： > >> Hi Gavin, > >> if you are stuck with supporting Live Class Reloading, please go ahead > with > >> other features, such as issue 10. Maybe we could concentrate on Live > Class > >> Reloading after GSOC deadline. > >> Thank you. > >> > >> 2011/8/13 Gavin Lei > >>> > >>> Hi Igor, > >>> > >>> In the schedule, we should focus on Live Class Reloading support for > >>> TapestryTools, but according to the survey job to Eclipse's WTP, we do > >>> not have a good solution to resolve this problem, May be we should not > >>> change WTP's running time module, it is just my personal idea. If you > >>> have any good advises, we can discuss it together. > >>> > >>> Now, As GSoC's deadline is coming, i think may be we should do some > >>> thing useful before the deadline, i will start the next feature in the > >>> schedule: > >>> > >>> All the available component should appear in the palette view [1] > >>> > >>> You added this issue, it is hard to finish this feature because it ask > >>> us to change Web Page Editor's palette's items loading module, we need > >>> at least 10 days to do it. So, i would like to start this part of job > >>> and finished it in GSoC's period. Is it OK ? > >>> > >>> Meanwhile, if you have any advises about Live Class Reloading things, > >>> please talk with me, we can make a plan or something, and then discuss > >>> when to start the Live Class Reloading job. > >>> > >>> [1] http://code.google.com/p/tapestrytools/issues/detail?id=10 > >>> > >>> 在 2011年7月19日 下午3:50，Gavin Lei 写道： > >>> > Hi there, > >>> > > >>> > As i missed the Live class reload feature in the last mail, so the > new > >>> > plan for the next period about the TapestryTools development job is: > >>> > > >>> > * 7.19 - 7.31: > >>> > > >>> > 3. Add MetaData? for Tapestry components in Web Page Editor's > palette > >>> > > >>> > Add proper icons and text label for tapestry components to improve > >>> > their looking. These tapestry components are current ugly just use > >>> > default icons and default text. > >>> > > >>> > AND > >>> > > >>> > 1.Validation function in Tapestry .tml file source view > >>> > > >>> > Beyond the basic JSP validation already provided with the JSP > editor, > >>> > this editor supplies semantic validation of the Tapestry standard > tag > >>> > libraries for both EL and non-EL attribute values. > >>> > > >>> > Details about these two features can be found here[1] > >>> > > >>> > *8.1 - 8.7 > >>> > Tapestry's built in Live Class Reloading support > >>> > > >>> > > >>> > * 8.8 - 8.15 > >>> > Add Eclipse Indigo support for TapestryTools, check details here[2] > >>> > > >>> > * 8.16 - 8.23 > >>> > Fix Issue 10.Add application's custom components support for > >>> > TapestryTools palette, check details here[3] > >>> > > >>> > * After GSoC's deadline > >>> > > >>> > Fix Issue 8, this part is difficult, i have no idea how much time it > >>> > will cost, i will
Re: Null check property expression syntax
> I think a more useful extension would be the Groovy :? operator > > expression ?: default-value > > This could even be combined with the safe de-reference: > > foo?.bar?.baz ?: computeFooBarBaz() Elvis operator is a nice feature to have too, but it's something different, I just would like to have a property null check equivalent to: foo?.bar?.baz != null or foo?.bar?.baz? Some logic is related to a condition when property is null or not. > BTW, existing syntax would do fine for you > > > > IMHO "baz" is converted to a boolean by converting it to a string first, I don't like an idea of toString called here. Denis - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Null check property expression syntax
I think a more useful extension would be the Groovy :? operator expression ?: default-value This could even be combined with the safe de-reference: foo?.bar?.baz ?: computeFooBarBaz() BTW, existing syntax would do fine for you On Tue, Aug 23, 2011 at 4:41 AM, Denis Stepanov wrote: > >> How does it differ from existing syntax? See the examples here: > >> propertyChain : term '.' propertyChain >> | term '?.' propertyChain >> | term; > > > Right now you can only check if property is a null when chaining to another > property to prevent a NPE. > > Maybe even better syntax would be: > >> value="prop?" >> value="prop.a.b.c?" >> value="prop?.a?.b?.c?" > > > Denis > > Aug 23, 2011 v 1:26 PM, Igor Drobiazko: > >> How does it differ from existing syntax? See the examples here: >> >> http://tapestry.apache.org/property-expressions.html >> >> On Tue, Aug 23, 2011 at 1:14 PM, Denis Stepanov >> wrote: >> >>> Hello, >>> >>> I would like to suggest a new syntax for checking if the property >>> expression value is a null: >>> value="?prop" >>> >>> >>> will return false if property "prop" is null or true if not >>> value="?prop.a.b.c" >>> >>> >>> will return false if property "c" is null or true if not >>> value="?prop?.a?.b?.c" >>> >>> will return false if one of the properties is null. >>> value="prop" >>> >>> >>> will call toString to convert it to a boolean, is not the best way how to >>> implement a null check. >>> >>> We have isNotNull component, which I would like to eliminate. >>> >>> Denis >>> >>> >>> >>> >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org >>> For additional commands, e-mail: dev-h...@tapestry.apache.org >>> >>> >> >> >> -- >> Best regards, >> >> Igor Drobiazko >> http://tapestry5.de > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Palette and Checklist don't use contributed value encoder?
I'm with you on this and I agree that this might be confusing for newcomers. But how would you solve this? I'm against removing the required flag and only have the user notice when he runs into an exception. It should be clear from the documentation that the parameter is indeed required but a default will be used if found and the parameter is not set. As Howard said, in those cases it is documented in the paramter description. An improvement could be an additional flag, maybe 'defaultprovided', to indicate that a default will be provided if not bound which the user can see directly without going through the description. Uli On 23.08.2011 04:08, Bob Harner wrote: > I know what everybody says it means. I'm just saying that it > *shouldn't* mean that, because it violates the principle of least > surprise. > > I'll stop now. I know I'm in the minority on this. > > > On Mon, Aug 22, 2011 at 9:59 PM, Howard Lewis Ship wrote: >> Required means that the value is required for the operation of the >> component. It does not mean that it must be explicitly bound when the >> component can provide a default. The parameter description will >> describe when a default can be provided automatically. >> >> On Sun, Aug 21, 2011 at 5:20 AM, Bob Harner wrote: >>> Wow, I am truly stunned. I'm not sure I've ever seen a piece of software so >>> completely disregard the common sense meaning of a commonly understood word. >>> So "required" sometimes means "optional if certain conditions are met >>> elsewhere". And users are just supposed to figure that out on their own??? >>> >>> Bob Harner >>> On Aug 21, 2011 7:03 AM, "Igor Drobiazko" wrote: The semantics are "the parameter is required. If no value is bound, the component will TRY to find a default. The lookup for a default value might be successful or not". For example, imagine you pass a list of Users to AjaxFormLoop and don't >>> bind a ValueEncoder. If no ValueEncoder for User is contributed, no default can be found and the component will complain about missing binding. That makes sense as the parameter is required. If you are using Hibernate or JPA integration, there is a ValueEncoder contributed automatically for every entity. In such a case, the default >>> can be found even though you didn't contribute any ValueEncoder manually. In summary: depending on the configuration of your app, a default ValueEncoder can be found or not. That's why marking the encoder parameter as required makes absolutely sense. On Sun, Aug 21, 2011 at 3:50 AM, Bob Harner wrote: > my other question would be why the "encoder" > parameter is marked as "required" for AjaxFormLoop, Hidden and > RadioGroup. After all, as Robert Z. says, those components seem to > have the ability to supply the default encoder based on the bound type > of value. My brain is a little sleep-deprived, so maybe I'm just not > understanding how this really makes sense. > -- Best regards, Igor Drobiazko http://tapestry5.de >> >> >> -- >> Howard M. Lewis Ship >> >> Creator of Apache Tapestry >> >> The source for Tapestry training, mentoring and support. Contact me to >> learn how I can get you up and productive in Tapestry fast! >> >> (971) 678-5210 >> http://howardlewisship.com >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: dev-h...@tapestry.apache.org >> >> > - > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Null check property expression syntax
> How does it differ from existing syntax? See the examples here: > propertyChain : term '.' propertyChain > | term '?.' propertyChain > | term; Right now you can only check if property is a null when chaining to another property to prevent a NPE. Maybe even better syntax would be: > value="prop?" > value="prop.a.b.c?" > value="prop?.a?.b?.c?" Denis Aug 23, 2011 v 1:26 PM, Igor Drobiazko: > How does it differ from existing syntax? See the examples here: > > http://tapestry.apache.org/property-expressions.html > > On Tue, Aug 23, 2011 at 1:14 PM, Denis Stepanov > wrote: > >> Hello, >> >> I would like to suggest a new syntax for checking if the property >> expression value is a null: >> >>> value="?prop" >> >> >> will return false if property "prop" is null or true if not >> >>> value="?prop.a.b.c" >> >> >> will return false if property "c" is null or true if not >> >>> value="?prop?.a?.b?.c" >> >> will return false if one of the properties is null. >> >>> value="prop" >> >> >> will call toString to convert it to a boolean, is not the best way how to >> implement a null check. >> >> We have isNotNull component, which I would like to eliminate. >> >> Denis >> >> >> >> >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: dev-h...@tapestry.apache.org >> >> > > > -- > Best regards, > > Igor Drobiazko > http://tapestry5.de
Re: Null check property expression syntax
How does it differ from existing syntax? See the examples here: http://tapestry.apache.org/property-expressions.html On Tue, Aug 23, 2011 at 1:14 PM, Denis Stepanov wrote: > Hello, > > I would like to suggest a new syntax for checking if the property > expression value is a null: > > > value="?prop" > > > will return false if property "prop" is null or true if not > > > value="?prop.a.b.c" > > > will return false if property "c" is null or true if not > > > value="?prop?.a?.b?.c" > > will return false if one of the properties is null. > > > value="prop" > > > will call toString to convert it to a boolean, is not the best way how to > implement a null check. > > We have isNotNull component, which I would like to eliminate. > > Denis > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > > -- Best regards, Igor Drobiazko http://tapestry5.de
Null check property expression syntax
Hello, I would like to suggest a new syntax for checking if the property expression value is a null: > value="?prop" will return false if property "prop" is null or true if not > value="?prop.a.b.c" will return false if property "c" is null or true if not > value="?prop?.a?.b?.c" will return false if one of the properties is null. > value="prop" will call toString to convert it to a boolean, is not the best way how to implement a null check. We have isNotNull component, which I would like to eliminate. Denis - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Radio and RadioGroup as AbstractField subclasses
I would like to have a zone param support for Chechbox and RadioGroup in 5.3. Will you manage to finish the refactoring into this version? Denis Aug 16, 2011 v 11:41 PM, Andreas Andreou: > :) Your patch is ok - it's basically a copy of the Select code that > did the same thing - but > what i'd like to do is investigate how to further improve on that. One > way is by generalizing > and reusing (instead of copy&pasting) and the other relates to reusing > AbstractField#processSubmission (that's what really allows impementing > this without > touching subclasses)
