Hi, concerning AJAX< I think you guys should take a look at : http://www.technicalpursuit.com/ajax.htm
The code is still not released, but should be out within a week or two. (the guys are currently doing documentation for their product). Regards, Sami Dalouche Selon Adam Jenkins <[EMAIL PROTECTED]>: > Hi All, > > Will do JIRA issue etc this weekend (tomorrow). > > In terms of improvement, there are a couple of things that jumped out. > > 1) Pollinate: Pollinate development has fallen way behind beehive > development and has begun to stagnate. I tried to jump in and give a > hand but the learning curve was too steep. Productivity is great with > beehive, having pollinate available would kick its you know what. If > you want to see beehive absolutely take off, you may want to temporarily > spare some developers to help out over there (I think it currently has > only one active developer). Beehive has everything a techo wants, > pollinate makes it a no brainer to sell to management, not to mention > would really make app development heaps easier and faster. > > 2) Issues BEEHIVE-839 and BEEHIVE-843: This is something that I think > needs to be resolved. The ability to use XMLBeans in your web services > is something I think everyone is going to want. There is a patch > attached to BEEHIVE-839, it just hasn't been applied. > > 3) Ajax (hating that buzzword): you guys are already on top of that, I'm > really looking forward to the day when ajax is as easy as datagrids and > popups are :) > > 4) Integration of the following libraries: > http://openrico.org/rico/home.page > http://script.aculo.us/ > > You guys really need to go look at their demos. They're cross platform > libraries for things like javascript drag and drop, autocompletion and a > bunch of cool cinematic effects (fade out divs, expanding rows in > datagrids etc). They are dead easy to use and hence would be dead easy > to wrap in a custom tag. They're also under an apache style license i > believe. Integrating the functionality from these libraries would give > you some amazing eye candy and client side functionality for very little > development effort. Check out the demos on their sites, you'll be blown > away. > > 5) Maven plugin: The point eddie and rich made about ibiblio is quite > valid. After I upload the maven plugin source someone should endevour > to get the m1 libraries (and 1.0 when they're out) up to ibiblio so it > can work with mavens auto download features. > > That's about it. Hope it was helpful > > Cheers > Adam > > > > On Wed, 2005-09-07 at 09:01 -0600, Daryl Olander wrote: > > Adam, > > > > Thanks for the complements. For me and I'm sure for all of us, this means a > > lot to hear from people who are using it what they think (good and bad). > For > > me, your comments make me feel like we are accomplishing our overall goals > > for Beehive. > > > > My question is, now that you've used it, what features post 1.0 do you > think > > we need? Where can we improve and what is missing? > > > > On 9/6/05, Eddie O'Neil <[EMAIL PROTECTED]> wrote: > > > > > > Adam-- > > > > > > Hey; it's definitely of interest! Thanks for sending it along; Rich > > > is right, attaching this to a JIRA issue would be quite helpful. > > > > > > Probably won't make it in for Beehive 1.0 just because we really need > > > to kick that out the door, but we should definitely get a Maven plugin > > > in very soon. > > > > > > Can't wait to take a look at it. > > > > > > This reminds me -- as part of shipping Beehive 1.0, we need to > > > publish the Beehive JARs into the Maven repository so that they're > > > downloadable that way... :) > > > > > > Eddie > > > > > > > > > > > > Rich Feit wrote: > > > > Hi Adam, > > > > > > > > Really glad to hear you're enjoying it! :) > > > > > > > > We definitely do need a maven plugin -- this sounds great. > > > > Unfortunately, attachments can't make it onto the list. Would you open > > > > a JIRA enhancement issue with your attachment? > > > > > > > > Also... excuse my maven ignorance here. I've been using it recently > > > > (and liking it), but haven't written my own plugins for it. In order to > > > > make this usable by the masses (without people having to edit their > > > > project.properties to add a custom repository), would this need to get > > > > out onto ibiblio.org <http://ibiblio.org>? > > > > > > > > Thanks, > > > > Rich > > > > > > > > Adam Jenkins wrote: > > > > > > > >> Hi Guys, > > > >> > > > >> I've just finished my first beehive app, it's currently with the > client > > > >> for acceptance testing...it uses pageflows, controls, xmlbeans, > > > >> webservices and pretty much every netui tag and I have to give massive > > > >> kudos to you all. I've been commercially programming in java since > 1997 > > > >> and this is without a doubt the most fun I've ever had. Revolutionary > > > >> design. Beehive is going to do phenominal things to j2ee productivity. > > > >> > > > >> I use maven for my builds and, as I've discussed a couple of times, > > > I've > > > >> been working an a maven plugin for beehive. To be honest, there wasn't > > > >> anything to it, just had to get my head around beehive first. > > > >> > > > >> Attached is the maven 1.1 plugin and a suggested directory > > > >> structure/configuration. It has a 4 goals that you can position > > > >> anywhere you want in the build process using mavens preGoal/postGoal > > > >> tags. It works with all the other maven plugins, specifically > > > >> maven:war. > > > >> > > > >> The goals are: > > > >> > > > >> beehive:generate-xmlbeans > > > >> beehive:build-pageflows > > > >> beehive:build-controls > > > >> beehive:build-webservices > > > >> > > > >> An example of my maven.xml is > > > >> <preGoal name="java:compile"> > > > >> <attainGoal name="beehive:generate-xmlbeans"/> > > > >> </preGoal> > > > >> > > > >> <postGoal name="java:compile"> > > > >> <attainGoal name="beehive:build-controls"/> > > > >> <attainGoal name="beehive:build-pageflows"/> > > > >> <attainGoal name="beehive:build-webservices"/> > > > >> </postGoal> > > > >> > > > >> The default directories are: > > > >> > > > >> src/controls > > > >> src/java > > > >> src/resources/schemas > > > >> src/pageflows > > > >> src/ws > > > >> src/webapp (see maven war plugin for more info on this) > > > >> > > > >> and all generated classes default to target/classes > > > >> > > > >> All these can be changed by editing your project.properties with the > > > >> following properties > > > >> > > > >> beehive.xmlbeans.schemas.dir > > > >> beehive.xmlbeans.classgen.dir > > > >> beehive.controls.dest.dir > > > >> beehive.controls.src.dir > > > >> beehive.controls.gen.dir > > > >> beehive.pageflows.src.dir > > > >> beehive.pageflows.dest.dir > > > >> beehive.pageflows.gen.dir > > > >> beehive.pageflows.content.dir > > > >> beehive.webservices.src.dir > > > >> beehive.webservices.dest.dir > > > >> beehive.webservices.gen.dir > > > >> > > > >> > > > >> So any way, have a quick look over it and let me know if it's of > > > >> interest to you...if it is, I'll write some doco this weekend. > > > >> > > > >> Thanks again for all the great work guys. > > > >> > > > >> Cheers > > > >> Adam > > > >> > > > >> > > > > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
