From: SourceForge.net <no...@so...> - 2003-09-26 14:19:15
|
Support Requests item #812917, was opened at 2003-09-26 00:06 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=211118&aid=812917&group_id=11118 Category: None Group: None Status: Open Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Sources for windows Initial Comment: i downloaded sources as i wanted to add some stuff that is bothering me in windows version (ex. proxomitron user), like some additional tracing of posted data in console window (that i want to change allso into RTF control, some coloring is nice to find info you are looking for). As usual in all open source projects i have encoutered by now (except Snort, tiny light of tidy sources in open source chaos), source is really *easy* compilable and it compiles without warnings, errors etc. Even *sigh* .rc file is opened without complaing some config.h (what config.h? that one with #include "..\config.h? :D) file is missing. Would you be so nice and create some source pack where people first time encountering your project would be repelled by 510 error(s), 142 warning(s) and some other annoyances. It is nice that you included project files for msvc++, but be so nice to configure them to work with BASE installation of msvc++ or at least include documentation how to build them (not with make!). Some will probably call me lazy ass (or i missed something; it is 9.00 here and i still didnt drink my coffee :), but i am really annoyed, if i want to do something that will take me 2 hours of development and spend 2 days to configure project so i can start developing. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-09-26 07:19 Message: Logged In: NO Oh, i forgot something; quote; "but what about something a little more cross- platform?" Nice and easy... make color.cfg file for coloring different infos with extremly cross platform format RGB (red, green, blue :) and call some gui callback (int nLogLevel, int nType /*=type in color.cfg*/, char *pInfo). GUI developer will filter this trough options set inside gui... (previous example can be optimised, as there is no need for allocating buffer for info if gui doesnt want it, so something like if (callback_heyguidoyouwantthis(&loglevel)) callback_hereyouhaveit(int nType, char *pInfo); :) have a nice friday... ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-09-26 07:07 Message: Logged In: NO Concerning: ...logging; logs are usefull for bunch of things (debugging html, getting links to files (like swf), etc...), so they have to be as descriptive as possible (as set (!)) and able to change their setting on-the-fly (not with flags in some cfg file :D). There are allso some issues about current logging... wtf *crunch!* means... breakfast? :D There are comments in cfg files, what is wrong if you show them (in short form (!!)) instead of *crunch!*. Furthermore, posted data are a NEED for anyone using http for anything beside surfing (like spying on windows update or reversing some web based protection scheme). Showing HEAD requests can be allso usefull. imho, with using html, sooner or later, log file will be full of banners :D, although it can be usefull as for instance link to data about *crunch!*ed code. ...cross platform; i somehow aggree with writting code cross platform although i still have some dark spots of memory reminding me on how world looked like when there were no M$ around (spectrum, commodore, atari, amiga,... and code has to be written for bunch of platforms, even if they doesnt have anthing in common) ... (and how nice it was when PC and m$ run them over, and how likely it will happen again if linux/windows fight will go on... btw. i am not starting old issue about ms vs *nix vs vms vs ... c64 RULEZ! :)), but gui is part of coding where nothing looks ok if same code runs on *all* systems. I think better way is to provide some library, with callbacks or something to provide and receive info from filtering system than to glue everything together in some *java* (i overlooked this proposal in your post, in second reading, i am adding; You must be joking :) like gui, that no one likes to use (hmm java gui *allways* looks to me like developer forgot something, like mouse support :). I believe entusiasts will build non cross platform guis sooner or later (i would :). p.s. i finished compiling damn code, but i still have some issues with linker, maybe tomorow will be a better day. As i predicted, 2 days spent just to get code ready for development, instead of finishing the idea... and yeah, i will provide doc (and some #ifdefs if needed) how to build it after/if i succed :D ---------------------------------------------------------------------- Comment By: David Schmidt (david__schmidt) Date: 2003-09-26 06:01 Message: Logged In: YES user_id=249980 The tools to build Privoxy are very GNU-oriented, and thus extremely cross-platform. MSVC++ is not particularly so. :-) That's why everything essentially requires autoheader, autoconf and make... and, by the way, that's how config.h gets generated. I think some work has gone on in years past to make building with stock Windows tools easier, but that inevitably falls behind the core development on every other platform. The Windows gurus stop by now and again, so hopefully someone who knows more about that platform will be able to help you more. Your comment about the RTF control is interesting... but what about something a little more cross-platform? Like HTML tagging the log lines so we could have a browser display them, or some other control in java or something? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=211118&aid=812917&group_id=11118 |