This is one the more ambitious ideas and is a repost from the discussion page. It effectively present the user with a modular view of AWB with its options presented in a matrix. @Dispenser 04:43, 26 February 2008 (UTC)
Description
Description
Event Timeline
Comment Actions
<div style="background:ThreedFace; padding:15px; width:350px">
'''AWB's Find and Replace goes up here'''
----
<div style="border:2px groove silver; padding:5px; ">
<div style="background:ThreedFace; position:relative; top:-1em; width:200px;">Pre-programmed options</div>
{| style="border:inset gray 2px; background:white; width:100%;"
| [[Image:Icone CheckBox VB.JPG]]
| General fixes
|
|
|
| [[Image:Fairytale redo.png|16px]]
|-
| [[Image:Icone CheckBox VB.JPG]]
| Automatic Tagging
|
|
|
| [[Image:Fairytale redo.png|16px]]
|-
| [[Image:Icone CheckBox VB.JPG]]
| Unicodify
|
|
|
| [[Image:Fairytale redo.png|16px]]
|-
| [[Image:Icone CheckBox VB.JPG]]
| RegexTypoFix
|
|
| [[Image:Arrow refresh.png]]
| [[Image:Fairytale redo.png|16px]]
|-
| [[Image:Icone CheckBox VB.JPG]]
| External processing
|
| [[Image:gtk-stop.svg|16px]]
| [[Image:Vista-kate.png|16px]]
| [[Image:Fairytale redo.png|16px]]
|-
| [[Image:Icone CheckBox VB.JPG]]
| PyWikipedia script
|
| [[Image:gtk-stop.svg|16px]]
| [[Image:Vista-kate.png|16px]]
| [[Image:Fairytale redo.png|16px]]
|-
| [[Image:Icone CheckBox VB.JPG]]
| Custom wiki-loaded regex fixes
| [[Image:gtk-stop.svg|16px]]
| [[Image:Arrow refresh.png|16px]]
| [[Image:Vista-kate.png|16px]]
| [[Image:Fairytale redo.png|16px]]
|-
| [[Image:Crystal Clear action edit add.png|16px]]
| width="100%"|<i>Add</i>
|-
| height="20"|
|}</div>
</div>@Kingboyk 12:17, 5 March 2008 (UTC) wrote:
Do you program in C#? Or are you capable at least of designing Windows Forms* in Visual Studio? If you are, perhaps you should join the team. Judging by our efforts up to now we don't have any UI artists aboard. *Or we could go with WPF, which would necessitate a move to .net 3.5, a jump I personally feel we will have to make at some stage.
@Dispenser 22:28, 5 March 2008 (UTC) wrote:
I don't know anything about C/C++/C#, yet. But I'd be willing to give the GUI thing as free time becomes available. I assume its part of the Visual Studio package I use to compile AWB.
@Kingboyk 19:17, 6 March 2008 (UTC) wrote:
Yes it is. Windows Forms in Visual Studio is ''fairly'' simple if you're sticking to design, don't really need to be able to code much to do the visual part.
The .Net Framework 3.5 introduced design/code seperation I believe, a replacement for https://en.wikipedia.org/wiki/Windows Forms called https://en.wikipedia.org/wiki/Windows Presentation Foundation and a new markup language (https://en.wikipedia.org/wiki/XAML?). I've not tried any of these features yet and we're currently using .Net 2.0 with AWB so we're stuck with Windows Forms unless there's a compelling reason to "upgrade". Visual Studio can do both types of design anyway.
@Reedy 19:33, 6 March 2008 (UTC) wrote:
If you can do the graphical side.. It wouldnt be too hard to tie the backend code into it all... I suspect, looking at that, we're gonna need to make a custom control, probably inheriting from listview/similar... As a list view can do the different types of view like you see in Windows Explorer - Large Icon, Small Icon, Details... I may have a play later on
@Reedy 20:56, 6 March 2008 (UTC) wrote:
Bit of googling/looking about. We are certainly going to need either a custom control, or to write our own. As list views by default do not accept images in the sub items (ie columns other than the first)