AltME groups: search
Help · search scripts · search articles · search mailing listresults summary
world | hits |
r4wp | 0 |
r3wp | 110 |
total: | 110 |
results window for this page: [start: 101 end: 110]
world-name: r3wp
Group: !REBOL3 Extensions ... REBOL 3 Extensions discussions [web-public] | ||
Maxim: 9-Dec-2009 | jocko, yes and no. ;-) Glass is going to be rebol code only, but its going to be based on rebogl, the OpenGL extension I am currently working on (as I write this). Rebogl its going to be an evolutionary process, starting with simple high-level pre-defined primitives and colors and then will get more and more customisable (deformers, animation, textures, programmable shaders, etc). I am still not sure how the Glass engine will evolve, but there is a good chance that it will be based on the scene graph technology I am working on for the Scream game engine. This has the benefit that Glass can be used to build the interfaces within the games themselves. But it most definitely won't require you to load a complete (and inherently complex) 3d world manager, just to build a window with a form. if possible, I'd like to have window masks, so that the 3D forms can actually live like 3d models direclty on the desktop... so some of the nice 3d feature isn't wrapped within an OS window border. | |
Group: !REBOL3 GUI ... [web-public] | ||
GrahamC: 20-Oct-2010 | to get the best result need async processes for each pipe in the graph | |
Pekr: 16-Dec-2010 | Cyphre: "Brian, yes, what would you want to see on the screen if something has zero size?" - really, I am not sure I care about if something is theoretically visible in 0x0 size, because face itself will not have a meaning even with 1x1 size, but I think that visibility (event flow) should be separate. OTOH, I can't find any practical reason how it could be internally usefull to have some inner state as shown, while being at 0x0. I thought about some graph models, event flows via the face hierarchies, etc., but with 0x0 size, you can't receive events anyway (apart from timer events maybe) Max - speak on :-) | |
Pekr: 17-Dec-2010 | hmm, I lack imagination for all possible usage cases. But we should have in mind the most complex scenarios, which might be some animations along with timers, simply a graph structure. | |
Henrik: 7-Jan-2011 | Regarding roadmap, I suppose a comprehensive graph style does not need much else than what is available now, as it would mostly rely on DRAW. | |
Pekr: 7-Jan-2011 | I think that talking a graph style, if we don't have tabs, tree, grid, is a bit preliminary. We need imo basic styleset, usefull to work with general DB apps, then we need more modern skin, and only then we need additional styles. We still can't see even concepts as accelerator keys being displayed, etc. :-) | |
Henrik: 7-Jan-2011 | Pekr, I can't be sure at this time, because currently the styles are worked on via immediate need for fixes for things like the SCRUM tool, which is partially why I couldn't complete the roadmap. It's probably fair to say that the styles currently present in the style browser will be completed by RM Asset, but that may change. What I imagine is that some of these styles that I mentioned will be comprehensive, long running separate, autonomous projects. A style like graph will need a ton of features, possibly separated into substyles and it would hopefully not depend on anything, but low-level features in the GUI system. Someone like Maxim could do this as he knows how to do high performance graphics. A windowing system can also be run as a separate project. Each project could be immediately stored on github. RM Asset can do everything ourselves, but in the end, this will just take much, much longer, perhaps an additional year, which affects everyone interested in the GUI. | |
Group: Core ... Discuss core issues [web-public] | ||
MikeL: 4-Apr-2011 | I am making a simple (I hope) worfkflow prototype and want to use REBOL objects which I can SAVE and LOAD. A workflow object! to have a node-map collection in it of simple nodes of the workflow graph. Source ->A -> B -> SINK where the workflow knows about the next node and status. Externally there is UI to support the work part ... which is URL data on a given node. Looks like it fits into Cheyenne RSP well - maybe zmq when I get a bit further along. Save a flow in process as a .txt file using SAVE/ALL filename.txt work-flow-instance. But no success with work-flow-instance: LOAD filename.txt Do I have to BIND on LOAD to re-instantiate the object? | |
Group: !REBOL3 Source Control ... How to manage build process [web-public] | ||
Fork: 29-Oct-2010 | When there are various tracks of development on forked repositories at GitHub, you can see the state of their convergence (or divergence) with the network graph visualizer: http://github.com/blog/39-say-hello-to-the-network-graph-visualizer | |
Group: !REBOL3 Proposals ... For discussion of feature proposals [web-public] | ||
Ladislav: 13-Jan-2011 | You can understand the whole referencing business as a kind of a graph - A refers to B, B refers to C, C refers to A, ... |
101 / 110 | 1 | [2] |