Thread: [Doxygen-develop] MacOS X doxywizard status
Brought to you by:
dimitri
From: George V. <gy...@ma...> - 2003-09-05 06:28:39
|
Dear All, I have made great progress on creating the Doxywizard application for MacOS X. I should say that at some stages I just said I will stop here, but after a calm down I went back and continued. I have built QT 3.2.1 for Mac and compiled doxywizard. I have also created the bundle and now doxywizard can start up and edit the Doxyfiles. It can also run the doxygen from itself. The compilation has been done on MacOS X 10.1.5 so the resulting executable is able to run 10.1, 10.2 and up. To Do: creating icons for doxywizard. For this I would need a rather large image (100x100 pixel) that will be used as the recurring element for the application and for doxyfile icons. Unfortunately the Doxygen logo (with the string in it) is not useful because when it is scaled back to 32x32 it would be just an orange rectangle. I would prefer use the gear used in doxywizard to run doxygen. I do not know however if this gear is a generic one or created for doxygen. modifying the make files (doxywizard.pro or doxywizard.pro.in or doxywizard.t) and adding new files for the application bundle. To create the wizard I had to change the makefile.doxywizard link settings. I had to remove the X11 libs and had to add some MacOS specific libs. I hand created the application bundle and moved its contents by hand into it. This could be also automated via the makefile. As I am not really good at the tmake automation I might need your help to adjust the root files (*.pro or *.t) depending on the supplied makefiles. creating installation package (disk image file). Testing on other systems. I will do this on the week-end on 10.2. Updating Building Doxygen pages. On my progress I want to add help for the next ones. Known problems: Because macOS X does not support scrolling the tabs as windows does the window is very wide. It might not fit on smaller screens. (I am running 1600x1200). I will measure this. The contents of the tab panels have sometimes shrunk to not fill the available space. It usually jumped between filled state and shrunken state. It caused controls on the right side being hidden. I think this is might be a Qt bug. The look of the application is just not mac like. It has the aqua widgets but it looks a bit weird. This is an inherent problem of Qt applications. Saving a new (not yet saved) document does not pops up the Save As dialog. Neither on Windows. George Varga |
From: Jens M. <ju...@ma...> - 2003-09-05 07:22:24
|
Am Freitag, 05.09.03 um 08:16 Uhr schrieb George Varga: > Dear All, > > I have made great progress on creating the Doxywizard application for > MacOS X. I should say that at some stages I just said I will stop > here, but after a calm down I went back and continued. > > I have built QT 3.2.1 for Mac and compiled doxywizard. I have also > created the bundle and now doxywizard can start up and edit the > Doxyfiles. It can also run the doxygen from itself. > > The compilation has been done on MacOS X 10.1.5 so the resulting > executable is able to run 10.1, 10.2 and up. Thanks, that sounds great! > To Do: > creating icons for doxywizard. For this I would need a rather large > image (100x100 pixel) that will be used as the recurring element for > the application and for doxyfile icons. Unfortunately the Doxygen logo > (with the string in it) is not useful because when it is scaled back > to 32x32 it would be just an orange rectangle. I would prefer use the > gear used in doxywizard to run doxygen. I do not know however if this > gear is a generic one or created for doxygen. > > modifying the make files (doxywizard.pro or doxywizard.pro.in or > doxywizard.t) and adding new files for the application bundle. To > create the wizard I had to change the makefile.doxywizard link > settings. I had to remove the X11 libs and had to add some MacOS > specific libs. I hand created the application bundle and moved its > contents by hand into it. This could be also automated via the > makefile. As I am not really good at the tmake automation I might need > your help to adjust the root files (*.pro or *.t) depending on the > supplied makefiles. > > creating installation package (disk image file). I could probably contribute to this - I've got some shell scripts that whip together the disk image on another project... > > Testing on other systems. I will do this on the week-end on 10.2. If you can send me the disk image or let us know where to get it, I could also do some testing on it... > > Updating Building Doxygen pages. On my progress I want to add help for > the next ones. > > Known problems: > Because macOS X does not support scrolling the tabs as windows does > the window is very wide. It might not fit on smaller screens. (I am > running 1600x1200). I will measure this. The contents of the tab > panels have sometimes shrunk to not fill the available space. It > usually jumped between filled state and shrunken state. It caused > controls on the right side being hidden. I think this is might be a Qt > bug. The OS X way would probably be to have a scrollable row of icons on top of the window, but I doubt that would be easy to squeeze in without having to conditionalize a lot of code :( > > The look of the application is just not mac like. It has the aqua > widgets but it looks a bit weird. This is an inherent problem of Qt > applications. I think it's either live with it or design e.g. a Cocoa app as the frontend. Maybe there's some common code that could be used to get the available options, etc? AFAIK, doxygen itself uses a subset of the Qt libraries for some generic classes (strings, localization, whatnot). I haven't had a look at the doxywizard code yet, but maybe there's some code that could be shared among a Qt implementation and a custom UI frontend? OTOH, it may not be worth the time if the Qt frontend is functional, but just not quite as aesthetic as a native Aqua frontend... :( </jum> |
From: George V. <gy...@ma...> - 2003-09-05 07:43:51
|
>> >>creating installation package (disk image file). > >I could probably contribute to this - I've got some shell scripts that >whip together the disk image on another project... Thank you. Naturally making it by hand is my first goal then we should automate it. >>Testing on other systems. I will do this on the week-end on 10.2. > >If you can send me the disk image or let us know where to get it, I could >also do some testing on it... My mac is currently off the internet. On the week-end I will put an "installer" onto my .Mac homepage. >>Because macOS X does not support scrolling the tabs as windows does the >>window is very wide. It might not fit on smaller screens. (I am running >>1600x1200). I will measure this. The contents of the tab panels have >>sometimes shrunk to not fill the available space. It usually jumped >>between filled state and shrunken state. It caused controls on the right >>side being hidden. I think this is might be a Qt bug. > >The OS X way would probably be to have a scrollable row of icons on top of >the window, but I doubt that would be easy to squeeze in without having to >conditionalize a lot of code :( > >> >>The look of the application is just not mac like. It has the aqua widgets >>but it looks a bit weird. This is an inherent problem of Qt applications. > >I think it's either live with it or design e.g. a Cocoa app as the >frontend. Maybe there's some common code that could be used to get the >available options, etc? AFAIK, doxygen itself uses a subset of the Qt >libraries for some generic classes (strings, localization, whatnot). I >haven't had a look at the doxywizard code yet, but maybe there's some code >that could be shared among a Qt implementation and a custom UI frontend? >OTOH, it may not be worth the time if the Qt frontend is functional, but >just not quite as aesthetic as a native Aqua frontend... :( I think we have to live with these limitations. Doxywizard uses lots of code from doxygen and Qt. George |