Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
SDK API changes
Michael:
--- Quote from: mandrav on December 14, 2005, 11:36:40 am ---Btw, if you haven't seen the wxIFM demo, do so. It's amazing :)
--- End quote ---
Thanks for the wxIFM demo link. Yes, it is really amazing :D.
Michael
killerbot:
I also prefer the second option. We are the early adaptors, for us it's no problem. We are svn users ;-)
It was the same with firefox, suddenly all plug-ins break, and the authors have orphaned their plug-ins. This gives a bad user experience. Better to break now, and have everthing nicely up and running at version 1.0, and preferably not break afterwards.
By the way, RC3, I am at RC1508 :P
And now when can still add some features, yipeeeeee.
Lieven
killerbot:
wxIFM : yes yes yes !!!!
Haha, M$ DevStud 2005 also has these kind of functionalities, but now CB will have it to.
I need a special smiley/emoticon here (I think in old icq it would say : killerbot is jumping anxiously up and down )
mandrav:
Regarding wxIFM, here's part of the mail I sent to its author. This contains the showstoppers for us now.
--- Quote ---1) Add child as a tab of a specific window.
When adding a child, I can specify if it will be created as a tab (data.m_tabify=true). But can I specify which child this tab will be created in? According to wxIFM's docs, it is created as a tab of the last added child. This is not good at all. As you may know, C::B is quite a dynamic environment using plugins. So the order in which windows are created is not predetermined. For example, a plugin might add a message log panel at any time. But I 'd like it to be added as a tab of the "messages" group of tabs, initially. I don't see how this is possible...
2) Loading/saving the layout.
Equally important for obvious reasons and I 'm really surprised you haven't already implemented it. I mean it's nice to give the end-users the kind of freedom they get using wxIFM in customizing their environment, but it's not worth a cent if next time they launch the app they 're back at square zero ;)
I could start writing such a serialization mechanism, but I 'd like a few pointers on where to start. I see I can get the visibility state for each managed window (btw, it 'd be nice if I could access that list of windows) but I don't see how I could get to the child size, orientation, etc.
Any pointers on that?
--- End quote ---
thomas:
Massive changes are best done early. The earlier, the less dependencies that break.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version