Let's imagine a user wants to create a scheme command and add it as a denemo default command. What process should be followed ? I am not sure I understand roles of tools : extract_all.sh, generate_sources and the sources it generates, commands.c, denemoui.xml, GENERATE_SOURCE_CODE define etc. and some other I probably miss. It should be understandable by reading and hacking, but as the process seems quite complicated, I think developers comments would be helpful.
2013/5/5 Éloi Rivard <[email protected]> > I mean data from filesystem. > > > > 2013/5/5 Richard Shann <[email protected]> > >> On Sat, 2013-05-04 at 19:54 +0200, Éloi Rivard wrote: >> > Hi, >> > >> > Could it be possible to get some explanations about command generation >> > mechanism ? >> Do you mean when a user creates a new command while using the program >> and (optionally) stores it for future use, or the generation of the >> commands from the data stored in the file system >> ( $PREFIX/share/denemo/actions/menus and ~/.denemo-xxx/actions/menus + >> complications that arose when making the strings translatable)? >> >> Richard >> >> >> >> > What are the steps and what generates what ? What about menus ? >> > >> > If you don't have time for this, it is not a big deal. Otherwise it >> > would be great since the code is not trivial. >> > >> > Thanks ! >> > >> > -- >> > Éloi Rivard - [email protected] >> > >> > « On perd plus à être indécis qu'à se tromper. » >> > >> > _______________________________________________ >> > Denemo-devel mailing list >> > [email protected] >> > https://lists.gnu.org/mailman/listinfo/denemo-devel >> >> >> > > > -- > Éloi Rivard - [email protected] > > « On perd plus à être indécis qu'à se tromper. » > -- Éloi Rivard - [email protected] « On perd plus à être indécis qu'à se tromper. »
_______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
