At Monday 09-01-06, you wrote: Hi Sid
Are you not happy with the range of possibilities offered by skins? I have been using VCLskin myself, a true "change the skin and that is it" solution (no special components other than a single skin component dropped onto the main form). You can load skins at runtime. There is a skin designer, but in my brief look at it I did not see the need to go outside the 30 or so supplied skins. If you want to edit the dfm, I don't know of an immediate solution. You know about the ObjectResourceToText function and its companions I guess. There is a dfm parser here http://www.felix-colibri.com/papers/colibri_utilities/dfm_parser/dfm_parser.html which might help. Having changed the DFM I guess you want to poke it back into the compiled exe .. easy enough to extract the dfm from an exe http://www.howtodothings.com/ViewArticle.aspx?article=104 and I guess that would give some clues as to how to write the modified version back. There might also be some clues in the RemakeForm function http://www.skch.net/columns/HOPE.html However, that might not be a very wysiwyg way of doing things. What about a small component on each form accessed by a hot key at run time which will allow the designers to modify the look and feel of the components on the form (you can iterate over the components array) and saves the modified dfm (ObjectResourceToText), which you then give back to the delphi programmers to use instead of the original dfm? It might work fwiw >Hi All, > >We're looking to do a major overhaul of the look and feel of our >product. At the same time, we're developing new features and don't >want to have our programmers spend time on this. Several other >people (non-programmers) at the office could be trained to use the >IDE's DFM editor and modify existing forms (they are facile with >other products that allow the visual creation and manipulation of >objects, such as Photoshop and even Word). > >However, we'd like to not use Delphi's IDE to do this, because: > >1) It would be really expensive to buy Delphi licenses for the >non-programmers for this one-time use > >2) We want to restrict the properties they can edit to look-and-feel >properties (e.g. color, font, left, top, height, width) and not >"programmer" properties (e.g. enabled, readonly, windowstate). Of >course we could tell them what not to modify, but then mistakes can happen. > >Does anyone know of a product that will let us do this? If not, any >code available to help us build something like this without too much >trouble? TIA. > > > >Regards, >Sid Gudes >PIA Systems Corporation >[EMAIL PROTECTED] > > >_______________________________________________ >Delphi mailing list -> [email protected] >http://www.elists.org/mailman/listinfo/delphi _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
