Right now I have the following progress made with printing: - WxPrinterDC - 100% - WxPrinter, 90% - WxPrintData - 10% - WxPrintDialog - 80% - WxPrintDialogData - 10% - WxHtmlPrintout - 10% - WxPrintout - 0% (this is abstract class I need to work on so wxRuby users can subclass) - WxPrintPreview - 0% By the end of this weekend I hope to have all of the above classes completed. I do have partial Windows printing capabilities working at this point. I thought''d I''d give the community a heads up. Nick/Curt/Kevin, how should I submit my code when I am done, email it to one of you or can i commit into cvs? Zach
Zach Dennis wrote:> Right now I have the following progress made with printing:Cool!> Nick/Curt/Kevin, how should I submit my code when I am done, email it to > one of you or can i commit into cvs?Hopefully Nick is in a position to accept your submission via email and check it in. Our project policy so far has been to request patches to be submitted via email (off-list, if they are large). After we have confidence in the skills and intent of a contributor, we would grant that person cvs rights to make it easier for everyone. As an aside, that''s my biggest frustration with cvs (and subversion), and the reason I experimented with darcs for version control a few months ago. I still expect to switch to a distributed version control system like arch/arx or monotone at some point. So far, none of the distributed version control systems are stable, robust, and usable on all three major platforms (win/mac/linux). But all are close, and are making good progress. Such a tool could greatly improve the productivity of small projects like wxruby. Thanks, Kevin
I have the following classes complete except for a few methods... - WxPrinter - WxPrinterDC - WxPrintDialog - WxPrintDialogData - WxPrintData - WxHtmlPrintout - WxPrintPreview For the most part printing is working on Windows. I have my Linux and my OS X box up, and I''m going to test it on there tomorrow. I still need to convert my .cpp and .h file into a .t file. Does anyone have a script that converts the .cpp and .h file into a .t file (just to save me a little time)? I still have to write a wrapper for the wxPrintout abstract class, and that should be done tomorrow. My question is....as I am testing this I would like to start writing on the Wiki at the same time so I make sure I document it as I go. There are a few quirks I found, but I haven''t used wxWindows outside of wxRuby so I don''t know if it''s my work or just how wxWindows works. Should I just write on the wiki (even though the printing isn''t in a release yet) or should I hold off until someone (Nick?) gets a chance to check it out? Also, the API documentation needs to be updated on the wiki. Is there a script that auto does this, or...does it need to be written? I don''t mind writing one if it needs to be there. If there is one, could I look at it''s source, I am thinking of writing a semi-intelligent ruby script which links to the approriate wxWindows documentation page for a class and/or method. Thanks, Zach
Zach Dennis wrote:> I still need to convert my .cpp and .h file into a .t file. Does anyone > have a script that converts the .cpp and .h file into a .t file (just to > save me a little time)?I wouldn''t bother converting them. The .t files are intended to serve two purposes: 1) make it easier to implement a class, and 2) Eliminate duplicate code between classes. The former is not an issue here, since you have already done the work. The main benefits of the latter don''t kick in until *all* the classes are .t files, at which point things like memory management become easier to implement system-wide. So my advice would be to just go ahead and submit your .cpp and .h files. Later, someone can sweep through the entire system converting existing .cpp/.h files to be .t files, if there is enough benefit. However, my guess/hope is that wxruby-swig will be working before then.> My question is....as I am testing this I would like to start writing on > the Wiki at the same time so I make sure I document it as I go. There > are a few quirks I found, but I haven''t used wxWindows outside of wxRuby > so I don''t know if it''s my work or just how wxWindows works. Should I > just write on the wiki (even though the printing isn''t in a release yet) > or should I hold off until someone (Nick?) gets a chance to check it out?If I understand your question correctly, I think it would be best for you to write your documentation on the wiki, but put a note at the top saying that as of this date/version, these classes are not yet part of the official project. Later, you (or someone) can update or remove the note. Thanks, Kevin
I haven''t been able to my Printing additions to wxRuby because I can''t get my OSX (10.2.8) box to connect to my Windows shared printer. I also dont'' have this working on my *Nix box either, but I think I can get this one going. Anyone out there w/a Mac and a printer willing to test my additions before I send them to Nick for review? Thanks, Zach
I''ve got a Mac with a network printer you can try. Nick Zach Dennis wrote:> I haven''t been able to my Printing additions to wxRuby because I can''t > get my OSX (10.2.8) box to connect to my Windows shared printer. > > I also dont'' have this working on my *Nix box either, but I think I can > get this one going. > > Anyone out there w/a Mac and a printer willing to test my additions > before I send them to Nick for review? > > Thanks, > > Zach > _______________________________________________ > wxruby-users mailing list > wxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-users > > >