|
|
Home » Developing U++ » Releasing U++ » Release 11.10
|
|
Re: Release 11.10 [message #33960 is a reply to message #33956] |
Sat, 01 October 2011 04:01   |
Sender Ghost
Messages: 301 Registered: November 2008
|
Senior Member |
|
|
Hello, Mirek.
mirek wrote on Fri, 30 September 2011 15:10 |
Now the question is what is missing. I guess we should fix to bugfixing mode and resolve some release policy issues.
|
I hope, you will review latest redmine (#62) patch for OWC builder about correct support for .rc files, before new release.
mirek wrote on Fri, 30 September 2011 15:10 |
One question is what to do with rainbow. It is a great addition to U++ (I hope), but it has little practical uses for release users.
|
There are options:
1) Creation of rainbow assembly, along with bazaar, examples, reference, tutorial, uppsrc, etc.
2.1) Creation of Rainbow package inside rainbow assembly, which consist of various rainbow platforms:
description "Rainbow GUI platforms\377";
uses(SKELETON) Skeleton;
uses(WINALT) WinAlt;
uses(WINFB) WinFb;
uses(LINUXFB) LinuxFb;
uses(SDLFB) SDLFb;
uses(WINGL) WinGl;
file
Rainbow.cpp;
2.2) Creation of RainbowApps assembly (new or mirror of MyApps assembly with rainbow directory), where developer could add Rainbow package for his|her applications and appropriate build flags.
3) Automatic recognition for "RAINBOW <RAINBOW_PLATFORM>" (or just "RAINBOW_<PLATFORM>") build flags inside TheIDE to add appropriate packages for GUI application. But this could be ambiguous.
I vote for 1 and 2 option.
Edit 2011-10-03:
Added rainbow changed files and diff for current 3947 revision, to clarify what I meant.
[Updated on: Mon, 03 October 2011 15:54] Report message to a moderator
|
|
|
|
|
|
Re: Release 11.10 [message #33981 is a reply to message #33979] |
Thu, 06 October 2011 07:08   |
Sender Ghost
Messages: 301 Registered: November 2008
|
Senior Member |
|
|
mirek wrote on Wed, 05 October 2011 16:59 | w.r.t. Rainbow, well, maybe the correct solution is to move WinFB to reference, as it is a reference example about how to use rainbow after all.
It would add just two or three packages to reference, which is OK IMO (Framebuffer, WinFB and some example, perhaps UWord)
|
Ok, now I understand what you mean - size matters (for release).
Sure, complete reference examples will show how to use selected Rainbow backends for applications.
But I don't think that reference assembly is right place for Framebuffer package on long term. It could be placed into uppsrc directory, in this case.
|
|
|
Re: Release 11.10 [message #33982 is a reply to message #33979] |
Thu, 06 October 2011 07:42   |
|
mirek wrote on Wed, 05 October 2011 10:59 | w.r.t. Rainbow, well, maybe the correct solution is to move WinFB to reference, as it is a reference example about how to use rainbow after all.
It would add just two or three packages to reference, which is OK IMO (Framebuffer, WinFB and some example, perhaps UWord)
|
I think this is wrong. Framebuffer (and winfb + linuxfb) is a software renderer backend for upp's painting engine and it's place is in the Rainbow package. I think that win32 and x11 renderers should be detached from ctrlcore and moved to Rainbow package as well. My point is that all available renderers should be in one place. In examples should be only classic UWord and in theide one chooses a proper flag (maybe in a separate drop list to make it easier) for rendering engine (default is GUI).
|
|
|
Re: Release 11.10 [message #33984 is a reply to message #33982] |
Thu, 06 October 2011 10:44   |
 |
mirek
Messages: 14255 Registered: November 2005
|
Ultimate Member |
|
|
unodgs wrote on Thu, 06 October 2011 01:42 |
mirek wrote on Wed, 05 October 2011 10:59 | w.r.t. Rainbow, well, maybe the correct solution is to move WinFB to reference, as it is a reference example about how to use rainbow after all.
It would add just two or three packages to reference, which is OK IMO (Framebuffer, WinFB and some example, perhaps UWord)
|
I think this is wrong. Framebuffer (and winfb + linuxfb) is a software renderer backend for upp's painting engine and it's place is in the Rainbow package. I think that win32 and x11 renderers should be detached from ctrlcore and moved to Rainbow package as well. My point is that all available renderers should be in one place. In examples should be only classic UWord and in theide one chooses a proper flag (maybe in a separate drop list to make it easier) for rendering engine (default is GUI).
|
I agree that Framebuffer should, in long term, be moved to uppsrc. Putting it to reference is just the solution for the next release.
I also agree that in theory, there should be some rainbow subdirectory of uppsrc. But I vote against putting win32/x11 outside CtrlCore - simply for practical reasons...
Mirek
|
|
|
Re: Release 11.10 [message #34008 is a reply to message #33984] |
Sat, 08 October 2011 21:32   |
 |
kohait00
Messages: 939 Registered: July 2009 Location: Germany
|
Experienced Contributor |
|
|
what about leaving x11/win32 backend in uppsrc, but placing it in a seperate package there, which gets selected by default...
this would still isolate the backend stuff for itself (in the same manner as in rainbow), but leave it in the place where it as used per default belongs to (according to mirek)..
moving Framebuffer in uppsrc wouldnt make much sense for a simple reason..as standalone it doesnt serve much..it always needs at least one final FB backend to compile..
putting it together i'd say:
* rainbow is the destination for all backend packages..no examples of how to use it..
* default arch drawing backends can be 'moved' to uppsrc and selected as per default, for simplicity reasons
* WinFb is an important development backend for Fb emulation during design phase.. just as SDLFb, leave it in rainbow, together with Framebuffer
* use examples on rainbow should go to examples or reference..we should mayba append a suffix to those examples or make a special subassembly under reference/examples.
[Updated on: Sat, 08 October 2011 21:33] Report message to a moderator
|
|
|
|
Goto Forum:
Current Time: Tue Apr 29 08:30:34 CEST 2025
Total time taken to generate the page: 0.01059 seconds
|
|
|