Hi folks,
There is a new page in my little Wine WWW -- the UI status page:
http://www.dssd.ca/wine/Wine-UI.html
This is a page that I've been meaning to create for many months now. Please check it out, and let me know if you notice any inaccuracies.
This is a page that I've been meaning to create for many months now. Please check it out, and let me know if you notice any inaccuracies.
I'd add the MDI "control" to the list too, and maybe the def procs (window, dlg...)
A+
On Thu, 30 Jan 2003, Eric Pouech wrote:
I'd add the MDI "control" to the list too, and maybe the def procs (window, dlg...)
I will add two more sections:
Fundamentals: -- Visible Region Handling -- Window Management -- MDI
(I think MDI falls more intuitively into the Window Management section than in the control section)
Common Dialog -- File Open/Save -- Font Selection -- etc.
Dan, currently it does not include the MDI issues you reported. First I will like to get a full inventory of items that make up the User Interface (UI). Once that's in, we can add notes to keep track of all this problems (and maybe link them to bugs in bugzilla).
So guys, if you can think of stuff that should go on this page, *please* speak up.
(I think MDI falls more intuitively into the Window Management section than in the control section)
agreed (that's why I put "control" in quoted)
Common Dialog -- File Open/Save -- Font Selection -- etc.
maybe, if you want full UI coverage, you could add a windowing driver section (X11, TTY, SDL...)
IMO, this type of information should be integrated in current status page.
A+
On Thu, 30 Jan 2003, Eric Pouech wrote:
maybe, if you want full UI coverage, you could add a windowing driver section (X11, TTY, SDL...)
That's a good idea, it will be another section.
IMO, this type of information should be integrated in current status page.
Sure, it's just so much easier to work with it on my site. I am a bit concerned that merging this page with the big status page will result in a huge page that is not that useful. I think that UI elements deserve a special place (I have not explained yet why I think so, that's another matter). Nevertheless, once this thing stabilizes, it can be integrated in the big status page if people feel it's a good idea. Or we can put it on the official site as a separate page, and link to it from the main status page. Details, let's get the content down first. :)
IMO, this type of information should be integrated in current status page.
Sure, it's just so much easier to work with it on my site. I am a bit concerned that merging this page with the big status page will result in a huge page that is not that useful. I think that UI elements deserve a special place (I have not explained yet why I think so, that's another matter). Nevertheless, once this thing stabilizes, it can be integrated in the big status page if people feel it's a good idea. Or we can put it on the official site as a separate page, and link to it from the main status page. Details, let's get the content down first. :)
what worries me is that status, from a DLL point of view, could be seen from different angles: - current status page gives an overall status, without focusing on any particular detail - you start creating another status page about the UI status of Wine - some good other fellow might want to start with, say, Unicode status in various DLLs or level of comments or attached bugs or...
this matrix about status(es): on one side the various DLLs we're working on, on the other side some metrics/characteristics we want to highlight... and working only by rows or columns is not very efficient I also agree that working on the ful matrix would be also difficult (at least to put it in place)
another piece, I forgot about some other control(s) (and here it's more than a simple control): - MCIWndClass in msvideo/msvfw32
A+
On January 30, 2003 03:59 pm, Eric Pouech wrote:
this matrix about status(es): on one side the various DLLs we're working on, on the other side some metrics/characteristics we want to highlight... and working only by rows or columns is not very efficient I also agree that working on the ful matrix would be also difficult (at least to put it in place)
Whether such a matrix is usable (may be too big) is not clear to me. But it's an interesting idea. However, the hard part is the content, and that's difficult to get. Once I finish this page, maybe we can create a unifing matrix, see how it looks.
another piece, I forgot about some other control(s) (and here it's more than a simple control):
- MCIWndClass in msvideo/msvfw32
Can you please help me complete the entry: -- URL to MS docs -- status (% completion, what it's missing) -- maybe to an audit against the latest MS docs, see _exactly_ what we're missing.
I've put something there, but I'm afraid it's not right. Check it out.
Whether such a matrix is usable (may be too big) is not clear to me. But it's an interesting idea. However, the hard part is the content, and that's difficult to get. Once I finish this page, maybe we can create a unifing matrix, see how it looks.
my idea was not necessary to use the matrix for display, but more for info gathering. afterwards, it would be easier to extract by rows and or columns. in any case, filling in the cells is the hardest task and the UI row is still empty... so, keep on filling it ;-) (or is it a column ? ;-)
another piece, I forgot about some other control(s) (and here it's more than a simple control):
- MCIWndClass in msvideo/msvfw32
the real official name seems to be MciWnd according to MS docs
Can you please help me complete the entry: -- URL to MS docs
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/multimed/mc...
-- status (% completion, what it's missing)
I'd say 20 to 30% completion. Very limited core implementation. All bells & whistles are missing including extended styles, notification, MCIWNDM_ messages
-- maybe to an audit against the latest MS docs, see _exactly_ what we're missing.
A+
So guys, if you can think of stuff that should go on this page, *please* speak up.
WebBrowser control?
Argh! *ducks*
Dimitrie O. Paun wrote:
There is a new page in my little Wine WWW -- the UI status page:
http://www.dssd.ca/wine/Wine-UI.html
Very cool. Does that include the UI issues mentioned in http://www.winehq.com/hypermail/wine-devel/2003/01/1053.html ? Duane's looking at the missing messages; I'd like to look into the misplaced scrollbars, but probably need a hint about where to start looking.
- Dan
-
Dan Kegel -
Dimitrie O. Paun -
Dimitrie O. Paun -
Eric Pouech -
Mike Hearn