Hey guys, ive been looking at the forums for some time now and decided it was time to jump in.
Im actually starting a group of stutend programmers to get youger people interested by new programming methods instead of writing plain old c++ win 32 apps.
I will be actually driving them toward multitouch in september.
This post inspired me to work with my student group to create a new mouse /touch broadcasting module from wich multitouch and standard apps could work nicely.
If you guys wanna work with us we could start something interesting
Yeah, I(and probably others) would be happy to collaborate! What language do you plan on doing it in, and what OS are you planning on targeting? I gotta make a quick run, but Ill be back shortly. We can talk about it on IRC then.
I am reflecting about os support, i really can’t choose an os or all os…
I i think our best shot is @ working on linux or osx since microsoft has already announced that windows 7 will be multitouch enabled and since its microsoft they will do it their own way :O
so what do you guys think ?
I however dont think a multi-platform module is the best idea since i think we should aim for native support intead of always patching an os with other shits.
thx
Gabriel Gb
PS : if you guys wanna be part of this work, i will be starting a new blog soon.
Just created a blog to work on : sx2workgroup.blogspot.com
if you guys wanna post on the blog send me a pm, i will give you the email adress to send to your messages
I am thinking Linux Support because that gives us the most freedom to modify anything we need. I am sure Apple will do their own thing, M$ Will too, and if we wanted to do it right and not write patches, well, Linux is our only choice(and BSD, but lets not go there). I agree we should not patch it, but with the new version of X11 with MPX support built in, I see no reason we can’t just write a driver. That would make our end so much easier, and I don’t think a driver is really considered a patch. Stop by IRC sometime on IRC.freenode.net, channel #nuigroup.
yeah i think so too, if you people wana be part of our project your all welcome, i have started tinking about it, me and nui people who wants to will write the driver, and the students from my workgroup will start writing applications for x11 multitouch.
I am creating a website with a dot com soon for the project and the workgroup.
but i do think that wimp is not the way to go and that with future application written with x11 and multitouch we can prove that there are alternatives that can be better for the end user.
A first would be to remove the mouse pointer in multitouch applications…
When I get back from my vacation (3 days) I gotta implement a few concepts , xela you’ll love these :D.
Also , ZUI is not really the way we should go , in some apps it will be good , but not in an OS form.
We should just sit down and think , bye.
The concept is nice , but switching between intense applications using ZUI would only resume to a windows-like freeze-to-death system :D. And also I’m back from my vacation a day early , so we can talk whenever you’re on IRC>
Not necessarily. If we wrote it right it could(and should) be done. Ill have to upgrade my GPU, all I have is a wimpy NVidia 7300GS. I ZUI is there the world is going, it makes a ton of sense.
Ill be on IRC pretty spotty tomorrow, but probably all day Monday.
ZUI = Zoomable User Interface. It’s esencialy what microsoft did with it’s “plex” demonstration , using deep-zoom/seadragon. I’ve seen a few plugins for KDE that do this , I need to research it a little bit more , but Xela , it’s gonna be a hell of a project and it will take alot of time, you know that right?
I went trough alot of material about ZUI’s today , and here’s a small list of conclusions I’ve gathered.
It’s a great way to explore content , powerfull , natural etc.
If it where to be vector-based it’d be really CPU-taxing , and the codeing part is gonna be hard to implement.
If we don’t implement sectioning or a transition between aplications only the UI is gonna hog alot of resources.
If we don’t make it fast enough transition between zoom-layers and apps is gonna be jerky and slow.
There’s research into implementing it into kde 4.1 , and a few hacked togheter plugins.I think if we where to implement this , that’s our starting place.
Larky: ZUI is nothing like Apple Spaces(which is BTW ripped off Compiz Fusion, and before that X Workspaces) completely. With a true ZUI there are no Zoom Layers, you can zoom in or out to any level you want. I know its gonna be a hell of a project, but its only one part. That would be one on the last things we implement, and by then hardware should have caught up a little better. I can’t do this alone, we will need a lot of other people to contribute.
ZUI will have to be vector based, so we get a good image at every level. Ill talk to you(and anyone else interested) on IRC,
OK cool, I’ll try and get on IRC at work, I have little time at home right now.
From the vids I saw (not too many) demoing a KDE ZUI, it was basically spaces and looked a bit poor. I know Apple stole it, I don’t care who’ idea anything was as long as we can steal it and improve it!
Really? I don’t think the KDE ZUI looks anything like spaces, its all on a level of its own. And IMO, it would be Spaces looking like KDE ZUI You were probably looking at the KDE workspace switcher.
You were probably looking at the KDE workspace switcher.
