Wow, there are a lot of questions in here, I'll try to answer as many as I can in one breath.
> This Cognition framework is sounding better by the minute. > I'm in the middle of creating a base platform for app development exactly > with T4, Hivemind, Hibernate, so it's really a quick fit for me, it appears. > Model based code generation ou reverse engeneering is preciselly what I have > started with, using Hibernate Tools ant scripts with custom velocity > templates. Glad to hear it. Most things that people create are because the environment demands it - I think we are all on the same train. > Tell me Steve are there some catches to app development with Cognition... > things like, do you have to do things like this or other way, link pages to > one another for page navigation with a specificly provided feature, > instanciate classes based on these mandatory abstract classes, or > implementing a half a dozen interfaces and extend the method A or B, only > use these component librarys... you know what I mean kind of hard-coupled > features. There are catches with any 'way of doing things' that are sometimes necessary to create a standard, almost like creating an interface itself. We have really tried to keep these to a minimum and none that are as burdensome as what you describe. We back many of the data components with XML that is generated by default, or you have to name a Block a certain way for a datagrid column, for example. We hate tools that create bad code or don't let you dig under the hood. For the most part, it's just about being a Tapestry developer and having things set up the way you'd like them to be and maximizing your productivity. If you don't want to use any of the Cognition components, fine. You still can use the DAO methods and have a project that is ready to go. It's really about being lean, but at the same time providing ease of use for certain common practices and conventions (yes, we need to learn from ROR and Microsoft). I personally hate having to build a validated form from scratch. These and other data interaction / presentation patterns should just be as easy as possible, but allow the advanced user to customize at their will. > I saw your demo, and was very impressed. It all fits togheter. I also saw > the dozens of ANT tasks... that scared me a little I must say. All of this > funcionality with a few mouse clicks is what makes me ask what I did. Is it > all very strickly linked in a particular and restricted way or is it just a > quick start witch one can easilly extend and change to ones needs. It's really functionality that you'd have to do anyways, like putting properties into a Spring XML file or placing your pages into your .application file. We are going to try to do a better job of both documenting what is going on during this process and creating some GUI items for these too. At the same time, by having items as ANT tasks, they are very portable and can be used sans tool. (We removed a task that even translates all your language properties files into 12 different languages. We may reintroduce, but it sure does provide some laughs for native speakers.) Some of the ANT tasks are linked or distinctly ordered - for example, you'd like to be able to actually create your schema - and THEN create the Hibernate POJOs for it. ;) > You talk of the custom EditTypes we can provide. Are these components? They are classes that extend a base, pretty simple wrappers for existing form types. You can put whatever components within an EditType as you like. Admittedly we do need to decouple this some from the Edit component so that they can be added more easily without modifying the Component module. > What about Page Navigation. Does Cognition provide something for that? I > mean, a very usefull feature in many projects is the ability to produce Site > Maps, ou bread crumbs for navigation, or even dynamicly generated > hierarchical menus. > Other features like the Structs or JSF visual action based page navigation > modeler, is there anything planed for these kind of features? Of course there are plans... I was trying to get us to jump on this too early. Sometimes you have to just make sure the basics are solid. We are considering Spring Web Flow as an option, but no Spring folk are actively working on Tapestry integration currently (Raible just turned me onto a WebWork implementation...). This, along with some not too pretty Spring 2.0 intros give us pause. What are our other options other than something custom rolled? Who's working on HiveFlow? ;) > Another issue is AJAX. You say your planning on suporting it. Do you have it > under way? Is it a soon to apperar feature? I think it's a must have since > it reduces needed bandwith in a brutal way, and adds a rich client usability > to prior "submit oriented" pages. > A project comes to mind, Tacos! Are you planning to integrate it? It seems > to be a must have for any T4 project, even thought it's still Beta. What do > you plan to do here? Wait till T4.1 with AJAX allready bundled in? The Tacos libs will be intregrated by default in the future and we will allow for adding new libs and components within the Modeler. We have plans to 'AJAXify' some of the existing components but are short on bandwidth. I hit up Jesse but he is up to his ears. I have yet to contact Andreas. Otherwise, for anyone that wants to - have at! > Sorry for the pop quiz! :-) > I'm really curious with Cognition and I'm very motivated to try it on, but > time is short and I would like to get a better view of it before I drill in > to it! Don't sit on the sidelines - drill away! ........................................ Steve Motola [EMAIL PROTECTED] (310) 422-5521 The Lab, LLC http://www.thelabllc.com Content is for intended recipient only. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
