Dave [2007-02-27 12:58]: > Tilman Sauerbeck ha scritto: > >Dave [2007-02-24 02:11]: > > > >>Carsten Haitzler (The Rasterman) ha scritto: > >> > >>>On Mon, 5 Feb 2007 20:53:16 +0100 Tilman Sauerbeck > >>><[EMAIL PROTECTED]> > >>>babbled: > >>> > >>> > >>> > >>>>dan sinclair [2007-02-05 12:17]: > >>>> > >>>> > >>>>>Tilman Sauerbeck wrote: > >>>>> > >>>>> > >>>>>>DaveMDS [2007-02-05 05:05]: > >>>>>> > >>>>>> > >>>>>>>here's a patch for edje_decc that create a file called default.edc > >>>>>>>in the decompiled source dir. > >>>>>>> > >>>>>>>The file contents is only a line that include the main edc file. > >>>>>>>If the default.edc file exist none is created > >>>>>>>With this patch I can open edj file from edje_editor (engrave run > >>>>>>>edje_decc and always open default.edc). > >>>>>>> > >>>>>>> > >>>>>>NAK. Breaks compatibility with redact for no good reason. > >>>>>> > >>>>>> > >>>>>> > >>>>>It used to be that edje would output the main .edc file as > >>>>>main_edje_source.edc (or something similar) this made life for engrave > >>>>>really easy as we'd just look for that file. Now, it uses whatever the > >>>>>coder sets as their default file. > >>>>> > >>>>>We have no-way to know what the main .edc file is called anymore. > >>>>>(Well, besides parsing the rebuild script I think). Having it either > >>>>>rename he main .edc file to something common, or spitting out a > >>>>>commonly named file means that an editor can open the .edc files > >>>>>decompiled from the .edj file. > >>>>> > >>>>> > >>>>The correct way would be of course to just read the EET. > >>>>But maybe you want to introduce another edje_decc switch that overrides > >>>>the name of the first SourceFile entry (= main file name). > >>>> > >>>>edje_decc --main_file BLAH.EDC > >>>> > >>>>It's a hack, but I still think that the concept of Engrave isn't quite > >>>>perfect :o > >>>> > >>>>Regards, > >>>>Tilman > >>>> > >>>> > >>>parsing build.sh is probably a clean way to do this - or making it a > >>>different > >>>name that hasnt been used before (eg edje.edc) which wouldnt break > >>>anything > >>>(and ALWAYS write it) :) > >>> > >>> > Like raster said, I have done a new patch that ALWAYS create a file named > main_edje_source.edc > This file simply include the user main source. > I think that this doesn't break anything. > If you prefer can also change the name of the created file.
And as I already said, this breaks redact. Want me to make my suggestion for an elegant and world-compatible implementation again? ;p Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
pgpSLAMB7ixV1.pgp
Description: PGP signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
