Hi All,
Hi Werner & All,
Hi again,
BTW, have you given up or not found the time (to understand their
javascript magic) to adapt some of the TurboGears theme stuff,
especially keeping the table of content in view when scrolling would
be very nice:)
I know, but I am really crappy at this javascript stuff. I’ll try and
give it another go; if I can’t make it, someone else will have to look
into it.
Great. In case you can’t make it do you have a smallish test setup (I assume the full build takes quit a lot of time/stuff, no?) of the Phoenix doc which I could use to have a go at this.
I managed to get it working, I have a local copy of the docs with a movable/collapsible sidebar which always stays visible, plus the scrolling page header with its own search button (pretty much like the TurboGears docs). I’ll upload the new version tonight.
Now someone will have to find a way to provide code folding through JavaScript for the contributed examples…
OK, I managed to do both things in the end, and a bit more.
@Werner: the sidebar is now always visible, and it can be moved/collapsed. Also, the search field is now at the top scrolling header with the other top links, always visible.
It works in Chrome, IE7 and Firefox. I haven’t tested on other browsers.
@Chris: I have implemented an “accordion” behaviour for the contributed samples; they can be expanded/collapsed (default is collapsed) and they contain a link to download the samples (see http://xoomer.virgilio.it/infinity77/Phoenix/GridBagSizer.html)
It works in Chrome, IE7 and Firefox. I haven’t tested on other browsers. At some point we may want to start looking for sexier accordion images than the plain triangle ones, but I leave the graphics design part to someone else.
@Robin: there are a few issues I would like to ask for clarifications:
-
It seems like wx.AboutDialog lives into an entity called “wx.adv”. Are we going to have a wx.adv package in Phoenix? If this is the case, I have to re-generate the docs and make the appropriate changes to the sphinx_generator file;
-
There are 2 methods in the whole library for which the signature does not match the parameter list, namely:
class: wx.DropFilesEvent
method signature: init(id=0, files=None)
missing/misspelled parameter: noFiles
class: wx.Frame
method signature: SetStatusWidths(widths_field)
missing/misspelled parameter: n
I guess it is a simple tweaking of the extractors/etg files, but I am a bit afraid to touch them…
- I have made the following substitutions for parameter types and return types (in the docs only):
a) [‘Coord’, ‘Byte’, ‘FileOffset’, ‘short’, 'size_t, ‘time_t’, ‘IntPtr’, ‘UIntPtr’, ‘WindowID’] ==> Python integers (int
);
b) [‘longlong’] ==> Python long integers (long
)
c) [‘ArrayString’, ‘ArrayInt’, ‘ArrayDouble’] ==> [‘list of strings’, ‘list of integers’, ‘list of floats’]
Please let me know if I have to revert some of these changes.
Enjoy the new docs 
Andrea.
“Imagination Is The Only Weapon In The War Against Reality.”
http://xoomer.alice.it/infinity77/
···
On 3 April 2012 10:48, Andrea Gavana wrote:
On 2 April 2012 13:06, Werner wrote:
On 02/04/2012 11:00, Andrea Gavana wrote: