Difference between revisions of "WxSmith Timeline"
From Code::Blocks
(4 intermediate revisions by the same user not shown) | |||
Line 3: | Line 3: | ||
{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%; table-layout: fixed;" | {| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%; table-layout: fixed;" | ||
|- style="background: #ececec;" | |- style="background: #ececec;" | ||
− | ! style="width: | + | ! style="width: 15em" | Task |
! Description | ! Description | ||
! style="width: 7em" | Estimated time | ! style="width: 7em" | Estimated time | ||
Line 48: | Line 48: | ||
*[[Image:Chk.png]] wxFileDialog | *[[Image:Chk.png]] wxFileDialog | ||
*[[Image:Nop.png]] wxFindReplaceDialog | *[[Image:Nop.png]] wxFindReplaceDialog | ||
− | *[[Image: | + | *[[Image:Chk.png]] wxMultiChoiceDialog |
*[[Image:Nop.png]] wxSingleChoiceDialog | *[[Image:Nop.png]] wxSingleChoiceDialog | ||
*[[Image:Nop.png]] wxTextEntryDialog | *[[Image:Nop.png]] wxTextEntryDialog | ||
Line 77: | Line 77: | ||
|- | |- | ||
! Virtual-function events | ! Virtual-function events | ||
− | | style="text-align: left;" | Some items provide functinalities in derived classes only by calling virtual functions. Such functions could be | + | | style="text-align: left;" | Some items provide functinalities in derived classes only by calling virtual functions. Such functions could be threated as some kind of events and could be generated automatically by wxSmith (by automatically generating some derived class) |
| 1 week | | 1 week | ||
+ | | {{no}} | ||
+ | |- | ||
+ | ! Include one resource in another | ||
+ | | style="text-align: left;" | There could be some special item which would allow adding other resources (like wxPanels) into another ones. Curently it msut be done by making some tricks like changing "Class name" or by using custom item. wxSmith could really easily integrate with such resources. The only problem I see here is that there's changing list of constructor arguments which can be passed into other resources and wxSmith won't be able to guess values for custom arguments - but this can be implemented similarily to generation of custom resources - by providing some kond of script-code where all arguments would be provided by the user | ||
+ | | 3 days | ||
+ | | {{no}} | ||
+ | |- | ||
+ | ! Using //{ and //} comments to allow folding of wxSmith code | ||
+ | | style="text-align: left;" | In resouce wizard there could be an option to automatically add //{ and //} comments which notify wxScintilla that the block should be foldable. One of following solutions could be used here: | ||
+ | |||
+ | Firts solution: | ||
+ | |||
+ | //{//(*CodeName | ||
+ | ... | ||
+ | //*)//} | ||
+ | |||
+ | It will require changing detection of block folding | ||
+ | |||
+ | Second solution: | ||
+ | |||
+ | //{ wxSmith-generated code | ||
+ | //(*CodeName | ||
+ | .. | ||
+ | //*) | ||
+ | //} | ||
+ | |||
+ | Third solution: | ||
+ | |||
+ | //{ wxSmith-generated code | ||
+ | //(*CodeName | ||
+ | .. | ||
+ | //*)//} | ||
+ | |||
+ | | 1 hour | ||
| {{no}} | | {{no}} | ||
|- | |- | ||
|} | |} |
Latest revision as of 11:49, 21 January 2008
Timeline for wxSmith: