View mode: basic / threaded / horizontal-split · Log in · Help
December 03, 2006
Re: minwin unicode
Bill Baxter wrote:

> Tomas Lindquist Olsen wrote:
> > Walter Bright wrote:
> > 
> > 
> > > Chris Miller wrote:
> > > 
> > > > > Do you care about Win95?  If so then I recall there are some
> > > > > limitations to using unicode there, and you need something
> > > > > called unicows.dll to make it work at all.  I think unicows
> > > > > only supports a  subset of the win32 api.
> > > > > 
> > > > > Personally I don't care about Win95, but apparently a lot of
> > > > > people  still do.
> > > > > 
> > > > > If you don't care about Win95, then I believe you're right
> > > > > that the -W  functions are the way to go.
> > > > 
> > > > It also applies to Windows 95 and ME, which I believe still
> > > > have a chunk  of users. MSLU is an option but is a dependency.
> > > 
> > > Don't use MSLU to support 95 and ME. Look into how std.file does
> > > it, that's the right way for D.
> > 
> > 
> > I have committed the Unicode update for Windows to SVN :)
> > Thanx again for pointing out how it should be done!
> > 
> 
> And I can confirm that Japanese works now!  Yea!
>  (though without in-place IME support, but that's a separate kettle o
> fish)
> 
> --bb

I have never heard of that IME.
Danish works fine.
If you know something that I can do to fix this please let me know!

And thanx for testing :)

--
December 03, 2006
Re: minwin unicode
Tomas Lindquist Olsen wrote:
> Bill Baxter wrote:
> 
> 
>>Tomas Lindquist Olsen wrote:
>>
>>>Walter Bright wrote:
>>>
>>>
>>>
>>>>Chris Miller wrote:
>>>>
>>>>
>>>>>>Do you care about Win95?  If so then I recall there are some
>>>>>>limitations to using unicode there, and you need something
>>>>>>called unicows.dll to make it work at all.  I think unicows
>>>>>>only supports a  subset of the win32 api.
>>>>>>
>>>>>>Personally I don't care about Win95, but apparently a lot of
>>>>>>people  still do.
>>>>>>
>>>>>>If you don't care about Win95, then I believe you're right
>>>>>>that the -W  functions are the way to go.
>>>>>
>>>>>It also applies to Windows 95 and ME, which I believe still
>>>>>have a chunk  of users. MSLU is an option but is a dependency.
>>>>
>>>>Don't use MSLU to support 95 and ME. Look into how std.file does
>>>>it, that's the right way for D.
>>>
>>>
>>>I have committed the Unicode update for Windows to SVN :)
>>>Thanx again for pointing out how it should be done!
>>>
>>
>>And I can confirm that Japanese works now!  Yea!
>> (though without in-place IME support, but that's a separate kettle o
>>fish)
>>
>>--bb
> 
> 
> I have never heard of that IME.
> Danish works fine.
> If you know something that I can do to fix this please let me know!
> 
> And thanx for testing :)

After some experimentation, it looks like you need to use the RichEdit 
text control (2.0 or greater) to be able to do inline IME conversion.

The annoying thing about that is apparently you have to load the 
RichEdit dll yourself.  See what wxWidgets does here:

http://cvs.wxwidgets.org/viewcvs.cgi/wxWidgets/src/msw/textctrl.cpp?rev=1.279&content-type=text/vnd.viewcvs-markup

General info about MSW rich edit controls:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platform/commctls/richedit/richeditcontrols/aboutricheditcontrols.asp

My feeling is that if MinWin is only going to offer one flavor of text 
control, it would be best for it to use the RichText control since it 
has all-around more functionality.

On the other hand I notice that even on Japanese Windows things like the 
Win+R run dialog use the plain "Edit" control and do not have in-place 
IME support.  Perhaps the best idea would be to use the simple "Edit" 
control for one-line text and the RichEdit control for multi-line text.

--bb
December 03, 2006
Re: minwin
Bill Baxter wrote:
> Tomas Lindquist Olsen wrote:
>> Ultimate++ is a window less GUI toolkit. Everything is written from
>> "scratch" and only the TopWindow has a native handle. They are working
>> on skinning in the latest dev releases (which btw have some nice
>> features and are pretty stable).
> 
> Thanks.  I think both approaches have merit.  Sometimes you really just
> want to make a custom widget that draws itself and will work immediately
> on every platform (then emulation==good).  But other times you really
> want to have the native look-and-feel (then wrapping==good).  Other
> times you just want to have a consistent look or theme across all
> platforms (then emulation==good).  But some particular things like file
> dialogs tend to easier on users if they are native (then wrapping==good).

Some platforms don't have one native look-and-feel. On one of my Linux
desktops I have quite equal amount of programs written in 7 different
toolkits: fltk, gtk+ 1 and 2, qt, motif, swing and custom toolkits (e.g.
blender). Then, of course there are also those ugly plain X apps, but
does anyone really use them. Luckily the fltk & gtk+ 1 -programs are
some day "upgrading" their toolkits to some more common one. For example
XMMS is being replaced by BMP and Audacious.

Then there are those less common desktop environments that have pretty
minimalistic native toolkits.

I just hope that one day someone makes a general purpose toolkit for all
the environments and for all kinds of users. And with the help of
metaprogramming it just might be possible to create that without too
much bloat. A great potential killer app for D. :)
December 03, 2006
Re: minwin
Jari-Matti Mäkelä wrote:
> Bill Baxter wrote:
>> Tomas Lindquist Olsen wrote:

> Some platforms don't have one native look-and-feel. On one of my Linux
> desktops I have quite equal amount of programs written in 7 different
> toolkits: fltk, gtk+ 1 and 2, qt, motif, swing and custom toolkits (e.g.
> blender). Then, of course there are also those ugly plain X apps, but
> does anyone really use them. 

xfig!!

> Luckily the fltk & gtk+ 1 -programs are
> some day "upgrading" their toolkits to some more common one. For example
> XMMS is being replaced by BMP and Audacious.
> 
> Then there are those less common desktop environments that have pretty
> minimalistic native toolkits.
> 
> I just hope that one day someone makes a general purpose toolkit for all
> the environments and for all kinds of users. And with the help of
> metaprogramming it just might be possible to create that without too
> much bloat. A great potential killer app for D. :)

Software that sets out with the goal of being the right tool for 
everybody is usually delivered late (if at all), and ends up satisfying 
nobody.

--bb
Next ›   Last »
3 4 5 6 7
Top | Discussion index | About this forum | D home