[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.technology.lepido] Re: What features do you want for Lepido?

Jens Maukisch wrote:

Hi,


It would be nice to have some wizards for CForms to create basic definitions/bindings/templates. E.g. you can select a bean, choose the required fields, click the finish button and then you have the 3 required files.


That should be rather easy to do, but the problem is how do we manage rountrips, i.e. what if the user changes the generated form, and then the bean and wants to regenerate the form?


I just thought about an initial creation as the first step :-)


Aha. That's the easy part, but also the one where most time can be saved.

A multipage-editor for CForms would be very helpful,
so that you can edit definition, binding and template in one
editor. Nice features would be autocompeltition of tags and
id's and refactoring support.


Yup. The problem I see coming with the semantic model that we'll have to build is that many files in Cocoon depend on other files, but this dependency isn't explicit. For example a subsitemap depends on its parent sitemap but doesn't link to it. Same applies to a form definition, template and binding which are all glued together by a flowscript.


Yes, but that's the general problem if you want to develop an IDE
for such a dynamic framework as cocoon :-)

Maybe this will require Lepido to store some additional information in the files (e.g. as a processing instruction) to be aware of these mutual dependencies between files.


Yup, you must store additional information. In the file itself or as a property on the resource.


Hmm... file properties, hadn't thought about that. Can a file property translate to some visual feedback? Because the dependency information must be quickly accessible and modifiable.

If we have some kind of project-type for Cocoon it should be
an extension of the WTP J2EE-Webproject so that we can use
the existing features for the servlet configuration and the server-stuff included in the WTP.


That's my idea also. I haven't studied this in much detail, but the Cocoon project nature should extend what's provided by WTP to be able to fully use its features.


I'm using the J2EE-Webproject for my current cocoon projects and I don't
miss a thing atm. So the question is what features should a cocoon project provide?


Don't know :-) But maybe we'll need some additional things to kick-in special features when a project has the Cocoon nature. We'll add this if the need arises.

Sylvain

--
Sylvain Wallez                        Anyware Technologies
http://apache.org/~sylvain            http://anyware-tech.com
Apache Software Foundation Member     Research & Technology Director