components

I have a set of jsf components that are statically generated from a set of excel files (they are updated by business people). Each generated file represents a business object that has slightly different data, and all of them belong to a same class. In order to render this dynamically, the only solution I found was to set up a bunch of ui:fragment and dispatch to the right component at runtime: <!-- IMPLEMENTATION --> <composite:implementation> <ui:fragment rendered="#{cc.attrs.type eq 'cartcred'}"> <limites:limites-cartcred limite="#{cc.attrs.limite}"/> </ui:fragment> <ui:fragment rendered="#

I have a batch file (setting changer) that uses xcopy to list specific files formats in a specific folder, then allows me to type in one of the names and the script uses that name to copy that file to another location. First xcopy creates a copy of the original as a backup ( rolling backup only 1 copy ) then does the file copy (extension is fixed in batch only body of filename needed This works great BUT I would love to try and do this in Inno Setup for a nice clean GUI. I would like to populate the list of components/types from this list of files found in a specific fixed folder. Or even

I have a requirement to create a javascript function that when invoked will save all of the valid components on a JSF 2.0 form. Since the complete form will never be valid as a whole I need to figure out a way to run the lifecycle per component so that if the validation phase is successful the model will be updated and eventually saved. Ideally, this needs to be a single ajax request as iterating over each component with a separate ajax request would be painfully inefficient. Has anyone solved the problem before? If not could you give me some pointers on possible implementations? Edit: Here's

I've been using COM and .NET assemblies in the past to develop component-based-systems. Now I'm going to work on a cross-plattform-C++-project and want to structure the code in components aswell… Obviously COM and .NET are not an option, as COM is not available anywhere but Windows and Assemblies would add dependencies to the .NET framwork which may be not available at the target system. I'm aware that due to ABI-differences I won't be able to move components between different operating systems without recompilation, but I would like to write the code in a manner, that it's compatible at

So I have a need to create an ExtJS component (version 2.3.0). The component is simply plain HTML (styled) - it is a heading. My current approach is to create a custom component as follows: /** * A ExtJS component for a header for the application */ Ext.ux.AppHeader = Ext.extend(Ext.Component, { height: 32, tpl: new Ext.Template ('<div class="title-bar"><h1>My App</h1></div>'), onRender: function(ct) { this.el = this.tpl.append (ct); Ext.ux.AppHeader.superclass.onRender.apply(this, arguments); } }); Ext.reg('AppHeader', Ext.ux.AppHeader); This works fine, but I'm not convinced it is the "right