From what Marcel is saying about his continuing to focus on QPC code
changes, and debate if he should port the changes to the Q40 (I hope that I
summarized that correctly), we may need to tailor our approach to how we do
this.
I would really, really, really, like to see SMSQ/E behave basicall
Joachim wrote:
> As I already mentioned, I am willing to volunteer for the following
> changes in SMSQ.
>
>- have all windows draw their contents in the save area
>- background update of windows (same mechanism)
Ye! :-)
>In general I propose the following changes.
>- Application should not
On 16 Mar 2002, at 12:01, Phoebus Dokos wrote:
> Below you can find the organizational structure for the ReactOS project as
> it was forwarded to me.
> This indeed is a VERY good starting point to get a feel for things and
> organize the OpenSMSQ project accordingly
>
> Any input?
Yes, somethi
OK, here one of the more important answers from me, the rest has to
wait until I have more time (this is also true for everybody waiting
for a private answer).
First of all some facts: SMSQ/E for QPC is not per default included in
the offer from Tony. Tony doesn't even have the source code for th
As I already mentioned, I am willing to volunteer for the following changes
in SMSQ.
- have all windows draw their contents in the save area
- background update of windows (same mechanism)
In general I propose the following changes.
- Application should not draw onscreen, but in the save area. W
> Like Wolfgang I think it's unreasonable to expect the "prime developer" to
> also be the manager of the project. I have frequently been in such a
> position as a software developer for my employer and it is in no way
ideal.
I agree as well. In fact, I think we should see this as a chance to ha
> And the idea of having accelerated ProWesS
> drivers etc. has been in my head for a long time, too.
Well Marcel, this could be done if you allow switching between native code
and back. Then recompile ProWesS with some glue code and...
If we first handle the screen update thingies I suggest, we c
> Arnould Nazarian wrote:
> > OK then, so after fixed size prop fonts, what about jobs with output to
> > screen not blocked if overlapped?
>
> I have already thought about that but I probably can't do it. Let's
> see.
As I mentioned before with the reverse approach I suggest, this should not
be
>As for the ability to be more user friendly, I think the whole thing proves
>itself... The fact that many QLers have moved from QPC1 to QPC 2 proves
>that if someone is given the choice, they go for the extra colours and the
>"useless" features of Windoze.
I do not agree. I don't know exactly ho
Oops,
Sounds familiar. I think it has something to do with the PC or current
quality of disk drives.
I get these kinds of problems very often when trying to transfer files (by
disk) between PC's. A real pain but...
Joachim
10 matches
Mail list logo
