RE: Improvements on SmartFrog
"Guijarro, Julio" <[email protected]>
| Newsgroups | gmane.comp.java.smartfrog.devel |
|---|---|
| Message-ID | <8D5B24B83C6A2E4B9E7EE5FA82627DC9855712@sdcexcea01.emea.cpqcorp.net> |
Hi Gustava and Flavio, > -----Original Message----- > From: smartfrog-developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org > [mailto:smartfrog- developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of > Gustavo Mendes > Sent: 02 March 2005 14:59 > To: smartfrog-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org > Subject: [Smartfrog-developer] Improvements on SmartFrog > > Hi people! > > We have developed some SmartFrog components last year such as > JBoss and MySQL. Related the process of developing in SmartFrog, we > have some doubts and suggestions: Would you like to contribute those components to Open Source? I could be that other people would like to use them in their deployments. If you are interested we could host them in SourceForge. > > - Are you planning to improve the Eclipse plugin to allow to > click in the component names and its declaration appear as the Eclipse > does with Java files? We think that it is an important feature to the > developers/administrators to navigate in the hierarchy of their > components. For example, when the developer click on the attribute > that is defined as "comp ATTRIB ext" the eclipse plugin has to show > the attributte that comp is related to. Yes, we plan to continue the development of the Eclipse plugin. We are currently deciding with features to include next and this suggestion helps. It could be that I send a survey asking what extensions would be more useful for people. In any case, the plugin is also opensource and any contribution for is further development is very welcomed. > > - Are you planning to improve the error messages that are showed > in the process of compilation? We think that the error messages and > the way that they are showed are not intuitive. Clearly yes. Plese, feel free to send any suggestions for corrections. For us is sometimes difficult to know which messages are not clear enough or misleading because we are used to them. We need the users to guide us in improving this. > > - Build.xml file: We think that the build.xml that is > distributed with SmartFrog is extremely dependent on the SmartFrog > directories hierarchy. For example, if a developer want to develop a > new component in SmartFrog, the easiest way is creating a subdirectory > in $SMARTFROG/examples/ to use the build.xml to build his project. We > think that via the Eclipse plugin or via a new build.xml for > developers/administrators is a good idea. > > Thanks a lot, > > Gustavo and Flávio > The Eclipse Plugin helps a lot with this. What it does not do yet is to create a build.xml for the new component so that it could be compiles without Eclipse. We will take a note about your suggestion. We will document the process of adding a new component into our build environment and I have quickly put together and attached a "template" for a build.xml and directories to create new components. > > _______________________________________________ > Smartfrog-developer mailing list > Smartfrog-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org > https://lists.sourceforge.net/lists/listinfo/smartfrog-developer
sfNewComponentBuildTemplate.zip.rename
(application/octet-stream, 5.4 KB) - not displayed