My Launcher/OS

[tizio]

Sounds Great Zakai!!! (By the way - this is reply # 500 in this thread!!!)

[ATOKserver]

Awesome work Hamilton =) I have followed this for a while now and I am still anxiously waiting for its arrival. I am betting your work will be superb ;)

[zhamilton1]

Good afternoon everybody :D

Well... ALOT has been active in the design thanks to jeff, J_F and many others (all of you in MSN ;) ).

First of all... I am reaching the 'platform independency' I wanted and it's looking great :D

So... what has changed:

Well... the OBS and ALDB are now merged into one. And the OBS has been improved in many ways. First of all... it's now a 'file based partition'... but don't worry... it can grow/shrink automaticly. The partition can be split into multiple streams which can even exist on multiple storage types. This is great since it makes the OBS a pluggable file system. This means that you can plug-in a 'card' and it can expand more memory for the registry/file system like OBS (Object Based Storage).

The 'layout' of the OBS has also been nearly finished. ScreensOS supports multiple users and multiple workspaces per user. ScreensOS allows applications to worry less about this by making applications only store settings per user without knowing what 'user' is active.

the OBS also has version control. ScreensOS can save multiple versions of the same document in the OBS file partition. When you tap 'Save', you can specify if to 'save' on the existing version or create a new version. ScreensOS also supports multiple undo levels because it stores the data of an object as a set of actions. So a document does not become a flat file but rather becomes actions such as 'Word a', 'Picture b', 'Letter c'. When the action becomes above the maximum undo level, the actions are automaticly merged to make the number of actions smaller. So if you type three words... they will be merged into a single sentence. This makes it easier for writing new data and faster for saving the data to the object. Objects basicly become a 'journel' of operations which is more user-friendly then a flat file chunk.

Multiple users can also edit the same objects with storing every users changes together. You can specify which users have more importance than others so that thier changes will 'win' if they conflict with another users changes. This is great for sharing documents between teachers and students since the teacher can design the document while the students changes can be viewed by the teacher. It makes swapping documents less of a hassle.

What? a file partiton... calm down... no hard reset or format required... to PalmOS it's just another database/memory chunk so you don't have to spare some space. ScreensOS will grow/shrink as neccessery :D

What does this mean to the demo? nothing. The demo uses a single 32K allocation stored in prefs. This design is forward compatible which means that even though the design is advanced, the implementation can play slow and safe.

Any questions will be welcome :D

[zhamilton1]

Alright everybody, Here is another technical post ;)

This whole week I have been working on the OBS design, improving it, tweaking it, making it's design more flexible and better designed on overall look.

The new OBS design is VERY flexible. All objects are at root and use meta-data to relate to each other. To the user it looks like a normal file system however underneath it's just a long list of interconnected objects.

However unlike a normal file system where one file can only belong to one folder, Objects can have multiple 'sources'.

If you remove an object, it sends all 'orphaned' objects to the 'Lost & Found' collection.

If you delete an object, it deletes all 'orphaned' objects from the action.

To a normal user this won't make a difference untill he starts realy using the flexibility of the system. This means that this flexible design is not forced on the user. To a normal user it acts like a normal file system while to an advanced user, he can connect between objects in ways never done before.

I have talked about this design to several MSN users and they loved it's design.

ScreensOS relies heavily on meta-data. There are two types of meta-data in OBS:
Relationships - Each object can relate to another 'linked list' of objects. A single object can have as many relationships as it wants.
Properties - These are the data streams connected to the object.

This might all sound complicated but it's been thought through alot and you will all see what I mean when the demo is released.

As you can guess... I will be late on shedule. I am very active on the project but ScreensOS is changing over time from a small core base to a full fledging multi-platform operating system. This is a hole in the industry which I will try to fill. However I (and many MSN users agree) that it's best to think the design through before jumping to the gun. I don't see anyone copying this size of project so I am not scared of someone doing it before me.

GUI Design Changes:

* Titles are tabs that stick out from the bottom middle of the 'window' when active. If the window becomes inactive, the title slides on top of the window covering the bottom bit of the window. This saves space for titles dynamicly. Maximized windows do not have a stick out tab when 'active' since the menu bar also shows the name of the 'active' object/window.

* Taping on the object name will show now the 'go' menu popup. Tap and hold on the object name to show the object menu. Tap, hold and drag to drag and drop the object itself. This saves the need of having to 'find' the object in the object storage to do direct manipulation to the object.

* When you tap and hold on any object it becomes 'actively selected' to show you that you tap and hold on the object.

That's the update at the moment... I'll keep you all posted as usual. :D

[zhamilton1]

Hello everybody,

I have taken most of this week as vacation (my first vaction of ScreensOS ;) ) and so far so good :D

Changes so far (before the vacation)

1. Dynamic Meta-Data
While static meta-data is any 'properties' which it's values are stored in the OBS partition, dynamic meta-data is 'properties' which point to values outside the object storage. To do so, I use applications as 'helpers' and ask applications to retrieve/set the information for the meta-data. This allows a very flexible design since any application can bring more 'data support' to the object storage.

2. Templates
If a template exists in a collection, a 'New' button will appear in the UI. If tapped, it will 'copy' the template and open it for 'using'. If there are multiple templates, you can tap on the arrow next to the 'New' button to show a menu of 'template' choices.

3. Actions
Many users want to do actions like turn bluetooth on/off, create a new appointment, lookup a number, browse the internet, take a picture, chat to a user and so on. However every users needs are different. Therefore the 'action' menu appears by tapping on the time. The menu can be changed and users can choose which 'actions' they want to appear in the menu. Another reason for this behaviour is so that the inconsistency of the menu bar is not broken. Before hand the summary window would appear. To avoid this behaviour a menu is displayed instead of a popup window. You can still show the summary by tapping the time and then the summary item (always available).

4. API's
Although the object API is very flexible, programmers won't use it directly but rather will use the API's for each component and using the object API only if neccessery for enhancing a component. Because functions can only have one state per message, messages could conflict with the state. Therefore tasks are used. When a task is created, all messages in that task share the state. All messages called from the task also share the state unless you spawn a message in a different task. Multi-tasking will allow multiple tasks to run at once. Remember that tasks has nothing to do with the windows you are using. Closing a task does not close the window you are viewing, neither does closing a window affect the task list. However since most tasks are used-event based, that won't be an issue.

Happy Chanukah and Happy Christmas to you all :D

[zhamilton1]

Well, I am back! :D

OK, I finished the design of the OBS component and I am now pre-coding it (this mostly catches 'last' issues of a component).

The SCode component will now work on top of the OBS component which basicly makes the OBS component... the first component. The reason for this is to give the SCode dynamic allocations a bit more umph and while the memory 'pointers' will be in dynamic memory, the object 'design' is in storage, so if a soft-reset happens, ScreensOS has a bigger picture of the failure. This also helps when running messages on external hosts (such as on another device) since it copies the 'memory chunks' which the message needs to work on and then copies them back. This allows both hosts to work on the same 'memory chunk'.

Tasks are called 'Jobs'. This is so that they are not confused with to-do lists 'Tasks'.

For those are new here:
OBS - Object Based Storage - The 'file system'
SCode - Simple Code - The 'allocation system'
Jobs - Like proccesses
Layers - Areas where applications draw to. Multiple layers 'make' a window/control.
Pre-Code - The proccess before actual coding. This normally founds out all problems with the component and makes the design more concrete before coding the component.

Relationships in objects are now just another type of property. Other types can be anything that an application wants to use. Each company+app has it's own 'workspace' of meta-data types.
The ScreensOS 'workspace' holds the basic types.
ScreensOS does not use actual string names so that ScreensOS can be 'transalated' to multiple languages without breaking the 'core' stability. Applications that use the meta-data can transalate the ID's into strings by checking them out in the ID object list.

I have finished the 'owner' design of the OBS component. This will work for any meta-data which is great for using multiple applications with the same meta-data since if any application 'destroys' the contents of a meta-data, it can always be 'restored' to the last application who wrote to it (before the 'corrupt' application did). This gives stability to the system especially when uninstalling applications. This makes sure that opening an object with an 'unknown' application can never ruin the contents of the object (unless the application hacks the database).

[jfer_rs]

Have anyone seen Zakai lastly?

Ive lost his tail last weeks... does anyone if something happend him, or just a lot of work?

Thanks

[Wintermute8]

I dunno. It's been a little bit since he posted. Could be sick or on vacation or something.

[Cwiiis]

He's been active and on msn, no need to worry :)

[Macka]

so how is it going on?

[Heep071]

I'll let Zakai tell the good news, but rest assured, things are moving! (something about SCode...) ;)

[Unregistered]

Anything New? Or is this project dead?

[J_F]

What is going to happen with it in relation to Palm 5.0 and now 6.0?

[cbulock]

Last I have heard from Zakai, he was still hard at work on the project, he has just made some major resdesigns that are really worth it, but is causing a slight delay in the release. I seem to remember him saying he was too busy on the project to post here even.
As for OS6, it will benefit from the built-in mulititasking, but will have the advantage of a windowing system not found in OS6. Plus, numerous other features not found in PalmOS6.

[icarus]

I followed the thread for a long time.....and that is really a long non-vacantion absence of Zakai in this forum.

That might be the ..........................unbelievable quietness :eek:    before the big DEMO Release. :D
Zakai, I wish you all the best in the final of the demo. I hardly can wait to get my hands on.

Best wishes from Switzerland :cool:

[mar_ning_2000]

It's must be the calm before the storm~~~
Scary~~:D

[Rabidrodents]

im xcitied!

[srcway]

Hi everyone, I have some important announcements to make concerning Zak's ScreensOS project. For starters, he has not been here for ages, as he has been working so hard on the pre-coding, so he has had no time to come. So, now all you conspiricists saying that he quit the project or died can leave. Secondly, pre-coding for all 4 modules is now complete, and he will start to code on Monday. Please remember that this is a ONE man project, so the new code cannot be ousted out super fast like at major companies. Big things take time, and this is just a classic example of that. Hopefully Zak will have time to post in the future, as the hardest part is done.

Thank you.

[Rabidrodents]

Ahhh bad news!
Search for screenos, its already a program! : (

[Wintermute8]

That's ok cause Zak's project is called ScreensOS not screenos. Woot!

[Rabidrodents]

W00T!

[Unregistered]

Cliepet is making his own sound API, could you incorperate support for this?
(Earlier you said there would be support for the Sony API when released)

-Palmer

[cbulock]

It doesn't sound like there is going to be much multimedia support in the first release, but is likely in the future.

[Wintermute8]

Zak's dead isn't he?:D

[Ambassador]

I'm beginning to think that this thread is just to see how long a thread can get. No betas, no screen shots, no nothin'. What's up with that?

[cbulock]

Zakai's not dead, but his personal life has recently become much more involved. He hasn't had a lot of time to put into this project. But he is trying to get this finished. It looks like not everything will be in the first release though due to time restraints.

[zhamilton1]

I know I have not replied for a long time...
it's just that I was sorry that I could not deliever the demo on time and was worried for flame wars.
I wanted to do more work than talk and that is exactly what I did.

Alot has changed in the design making it more structured, more powerful and just a better operating system.
The idea of ScreensOS is not to be just another OS... there are so many of them out there (maybe not for the mobile world) and it would be useless releasing another 'copy product'.

It's harder than you all think pushing all the features users want into a single product and so far I have done so in a very good fashion without any complexity problems.

A total revamp has happened internally as following:

The Storage component is the first component and deals with two things: Taking records and 'virtually' converting it into a single stream (for simplicity and limit removal) and then building the object storage on top of the stream.
Objects are a group of structures grouped together. Each object has attributes (a list of structures... however the structures are 'defined' to the object so that other objects can read the attributes and understand them) and relationships (that define the relationship of objects to objects like collections to objects or window to control, appointment to field and so on).

The next component is messages which is built entirely on top of the storage component and deals with the communication between different code and the cooperative multi-tasking (program must give up CPU time) model.

The layers component will follow which deals with all the graphics system from layers (areas of vectored draw commands) to windows to controls.

These 3 component sets are the core of ScreensOS and therefore are the most important components since they define the future of ScreensOS in it's flexibility to change.

Notice that the messages component has disappeared. This is because ScreensOS does not have two different models for allocating to dynamic and storage RAM. You create objects as normal but just specify the storage flag of the object as either:
1. Storage
These objects are stored on the stream in storage RAM and are stored even after soft-reset

2. Session
These objects are stored depending on the device and it's state in either dynamic RAM or storage RAM and are cleared when ScreensOS is closed (or soft-reset)

3. Message
These objects are stored mostly in dynamic ram unless the space is limited which it's stored in storage RAM (better slow than fail). These objects are removed when the message the objects were created from is expired.

Why is ScreensOS not ready? Why is there not even a letter of code? I am not giving it as a reason, but I am engaged to my girlfriend. This has made a tough time on both of us and I am freeking out from all the pressure of both ScreensOS and the wedding. They are BOTH important to me and I am working realy hard to acomplish both since they are both my dreams.

Coding requires focus which is not a luxary I have at the moment. The first moment I get to focus I will spend on coding but so far these last few months have been very rocky (thank you all MSN users for helping get through these tough times).

Many of you are spectical... I don't blame you... but I can't help you either... If I am full of hot-air... then why do I come up with these detail-specific designs? because I am bored?

Thankyou all for supporting me and hopefully something will come out of all this help... hopefully ScreensOS

P.S. I hope this proves that I am not dead ;)

[rkub]

LMAO!!! Zakai, please don't stress too much... I know the feeling of pressure, getting married in June... Don't let the stress from this carry over into stuff with your girl, not worth it. Trust me! Please enjoy this time with her and finish when you have time. Wedding only comes once, and unless you need to finish this to make money to support yourself, enjoy life!!!

[Wintermute8]

Second!

[zhamilton1]

About two years ago at the beggining of ScreensOS,
I made two demos (two different code sets... I have rewritten ScreensOS over 14 times)

Here they are:
http://www.geocities.com/zhamilton1/ScreensOS.zip
(remember to do save as...)

And here is my entire mockup collection:
http://www.geocities.com/zhamilton1/MyPictures.zip
(remember to do save as...)

The demo's allow you to move windows around using overlap (on the demo with two windows).

One of the demo's has a start button... tap it and Run/Help to show windows. You can move the windows around by the title and minimize/close them. Tap on a window to bring it to front and activate it or use the task manager button on the bottom right of the bar.

The other demo has a single window but the controls support 'actions' and therefore light up when tapped (just like PalmOS buttons). If you close the window then tap & hold on the desktop to bring the window back up.

Enjoy everybody :D

[cliekid]

OMG! This is awsome. Keep up the great work! I AM VERY HAPPY!!!

[Sharkk717]

If u need any beta testers, put me on the list! Great project, love the screenshots!

[abid786]

You sure don't seem dead to me;)

[spiderman951]

OMG that is SWEET :)

[rkub]

Dang, I can't see the pics... Can anyone post???

[zhamilton1]

The pictures (and all other files) are hosted on yahoo geocities and therefore to view them you must either 'copy' and 'paste' into the addressbar or right click and do 'save as'...

Enjoy ;)

[rkub]

Cool, didn't read the links at all.... lol thanks!!

[cliekid]

So are the pictures what it is going to look like or is it just ideas? They all look great... I can not wait to see a full version. Heck... you ever thought about going big? Actually perfecting this to make your own devices with ScreensOS or selling it to a company that will do so?

[zhamilton1]

At the time they were mockups of how it was going to look (throughout the verious stages) but I have not made mockups of the latest designs since it's exausting to make them all in MSPaint! ;)

I don't know about making my own devices at the moment... although if ScreensOS does succeed big, I do have plans to start hardware development but this is only if my company does very well with my software ideas (not just ScreensOS).

However I do plan to licence ScreensOS to companies like Sony/PalmOne if the inital 'boom' is successful.

The future for ScreensOS is very bright not only for it's side-kick products but for ScreensOS itself. While the first version is designed to be a full working operating system, future versions will have features that I chose not to include in the first version. I want the first version to know what it should do exellent.

So... what is left? the API syntax.
If I can get this done (which I am nearly there) I can start coding at 'amazing' speeds ;)

[Ezikial Anta]

This looks INSANE! I would love to help you test and i think there was a discussion on price a while back but, i would pay to buy this for sure, how much i dunno but i know i would at least pay something if thats how you choose to go about it!

[miskinis]

Name the band:

Everybody's got mixed feelings,
about the function, and the form.
Everybody's got to deviate, from the norm.

Anyway, I tried the screenos.zip, in the pose
emulator on my LINUX box. It seems to think
it is monochrome, and had a few memory leaks.

I have not looked at the pics yet...

John Miskinis

[zhamilton1]

Yes... it is monocrome because it was created in a b&w world... only the Palm IIIc was existing.

And it does have a few memory leaks... it just does not deallocate memory allocations when you close the app, nothing serious since PalmOS kills the allocations when you close the app anyway.

[cliekid]

Originally posted by zhamilton1
Yes... it is monocrome because it was created in a b&w world... only the Palm IIIc was existing.

Hold up.... you had this demo completed when the Palm3c was made? Im prob wrong but I gotta make sure...

[zhamilton1]

If I remember correctly... only the Palm IIIc existed at the time... I made it when I was still at NDS which means around 2000 ;)

[cliekid]

OMG... I can not believe this! Back then... I never thought this demo could be possible to make. If you made that back then... then when ScreensOS is completed... it is gonna be the bomb! Keep up the work!!!

[zhamilton1]

If you want the 'first' developer who did this: Andrew Downs

And I got inspired from him to take it further (he only did one version). You can find it in PalmGear under 'Extended Window Library'.

http://www.palmgear.com/index.cfm?fuseaction=software.showsoftware&SID=EA77FB38-7E95-2C3D-74E8E71FD31ABDDF&PartnerREF=&prodID=4466

Application Description:

This shared library for Palm OS provides a user interface element not present in the existing Palm API: moveable, resizeable windows for displaying text and graphics. The appearance and behavior of these windows is similar to that of Mac OS or Windows.

He did quite a good job (even if I found some 'bugs' ;) ) but I could not get it to work on OS5.

[cliekid]

That is cool. The point that I am getting at is I can not believe this is possible and it was made a long time ago. If you can do this... you can make ScreensOS the best ever IMO. I am so amazed... its freaky... keep it up! I cant wait to have a device that has ScreensOS as its own OS!

[zhamilton1]

Here we are with another update on what's happening ;)

Technical Info:

I am still working on the syntax rules and I finally found a 'valid' solution for my SQL like querying in C++ ( as a better C).

I call it function stacking. The idea is that some functions are stackable. This means that if multiple stackable functions of the same type are coded one after each other without any other functions inbetween, then there results are stacked with the existing results.

This allows things like SQL style querying to be easy to do without strings (since strings require more space). This is especially usefull when selecting objects since you specify multiple rules when 'filtering' the entire object list (i.e. Get all window objects which belong to a certain application).

The only downside I see with this method is that no other message based function (direct functions are allowed) can be called or else it will 'restart' the function stack. This means that stacks cannot be spread around multiple functions. This also means that you cannot use functions as parameters but rather must allocate local memory space and asign them to functions and use the local memory variables in the stackable functions. This is not recommended anyway since it causes confusion when reading code.

Hopefully I will not find any more syntax issues and can start finally coding the storage component collection API.

Note that the storage component is the hardest component in ScreensOS to code (since it's the core base) and therefore once it's completed I will able to finally post a 'demo' date :D

The messages component follows the storage component and since it encapsulates a certain object type, it's very simple to code and should be very quick.

The longest peice of code is the UI component which includes all components from windows, controls to action->key mapping and pen tracking components. But most of them are straightforward.

Once these components are coded, I can work on the menu bar component and basic 'launching' capabilities. The demo will be basicly a 'launcher' kind app so it will be usable (and not just a 'proof of concept' demo) however MSN users will get the alpha's before hand so join the ScreensOS group (by making me your buddy).

My MSN Messenger User name is: zhamilton1@yahoo.co.uk

Join now and help me get this OS out quicker & better ;)

[zhamilton1]

The syntax has been approved my multiple MSN members :D
I start coding on sunday :D

Once I finish coding the storage component, I will able to provide a dead-line.

There are 3 parts in the storage component:
1. Stream - deals with unifying the memory in the PalmOS design
2. Memory - allocation modal for the unified memory stream
3. Object - collection of allocations formed into a virtual file system

Thankyou all for helping me design in the last two years, be proud of yourselfs... ScreensOS is officially in-development coding :D

[The Mad Dog]

I know you probably posted it here, but I want toknow ifscreeners will support hires+

[cliekid]

YIPEEEEEEEEEEEEEE!

[zhamilton1]

ScreensOS supports HiRes+ ;)

[cliekid]

Originally posted by zhamilton1
ScreensOS supports HiRes+ ;)
YIPEEEEEEEEEEEEE! I was having a bad day until now... I can not wait to see your OS on my T3!!!

[ClieBen]

Just found this thread and read thru most of the 37 pages (time to take some aspirin), and I'm quite intrigued. I've added you to my buddy list (MSN), so hopefully we'll get a chance to chat sometime.

Keep up the great work, you have more patience than I could ever dream to have. :)

[CWolf]

I have added you too. I would love to be the first to review it, both for my site and for PalmOneCity. It looks great so far...

[zhamilton1]

I am online most of the mid-afternoon/night from about 5pm-12pm (GMT+2). Hopefully I will able to talk to both of you ;)
The more users in my MSN Messenger group the better because it allows me to get as many perspectives as possible.
I 'query' on online users to chat with (you can also start conversations with me ;) ) but if you are busy feel free to say so.

Sorry for the 37 pages... but it does provide a ScreensOS history :D

Patience is what is needed for a project this big. This is not your average project and if I did not have patience you might of got nothing or something which was not it.

I have a OS vision (everybody seems to have 'visions' these days ;) ) and I want to complete it. However this vision's implementation changes here and there (lately, it changes very mildly).

News:

Had an hour and a half talk with my father last night about the OBS system (Object Based Storage) and he helped me solve a 'module' related issue. The reason I still have not coded yet (read on... don't shoot yet) is because I think I got sick from my girlfriend (I have a doctors appointment next tuesday) so I sleep about 12 hours a day and still feel tired in between. This does not mean I am not working on ScreensOS, it means that I cannot focus while I am so tired. Please have patience with me like I have with this project.

I am focusing totally on the storage and messages component making them as stable and 'fixed' (as in details) as possible so that when I can code... I won't have any barriers such as syntax and function naming.

The storage is becoming more simple but flexible and I am very happy with it's results. What does this mean as in release date? Nothing... I will able to give a release date once the first component is coded. Yep, the first component basicly stores all the 'barriers' of ScreensOS. I decided that it would be best to tackle the hard parts first and let it go upstream from there instead of starting on the easy bits and hitting a wall later.

P.S. Hold that 'review' spot for me... ;)

[CWolf]

RIGHT!

After taking many hours last night I am proud to present the ScreenOS Development Log (http://www.cwolf.plus.com/palm/screenos.html).

Basically is is extracts from this thread, only the ones from Zakai (mostly) and editted slightly so that a person can read them without having to go through 38+ pages.

It runs latest post at top.

I am updating this every day and I will be reformatting it a little, maybe split it into years so that it is a little smaller on screen / download.

Hope this is helpful to anyone new to this thread!

[CliePet]

> After taking many hours last night I am proud to present the ScreenOS Development Log.
> Basically is is extracts from this thread

Friendly suggestion (open to anyone): instead of providing a website that contains extracts from this thread - why not provide a BBS for people to discuss this (pre-announced) product ?

Then this thread can be closed. It is over a year old with 500+ posts. IMHO this is an abuse of the free BBS service provided by ClieSource. ClieSource is a public BBS, not a personal BBS.

As far as I understand it ScreensOS should be a PalmOS product (ie. not CLIE specific) and since there no discussion of APIs and other developer related things -- this doesn't have much to do with the other CLIE developer topics in this forum.
If and when it becomes a real product, then discussion on this or other forums will be appropriate.

Please help out and provide 'zhamilton1' an appropriate forum to discuss his 'vision'. This is not the place to do so.
There are plenty of free web forum software choices, some that support chat.

[Shion Uzuki]

OMG. This is an AMAZING project!!!!

[CWolf]

I appreciate the suggestion, however this would mean that valuable input from Clie' owners would be missed. After all, how many people have seen this (as above) and then began to contribute constructively as opposed to it being a small and unknown/discovered forum...

[paulmdx]

Just curious if this project has got into the coding stages yet?

[I Think Im Dumb]

Well I have read this whole fourm and I think this will be big!;)
Just some questions though

-Will this program work with 0s 4.1?
-Will it work with a sj22?

[I Think Im Dumb]

Sorry for all the posts but my comp got screwed when I posted the original

[CWolf]

I Think Im Dumb - Yeah, please delete them.

In answer to your question:

It should work fine on any Clie or PalmOne device.

As for compatability - it should work on 4.1 but coding has only just started due to illness...

[I Think Im Dumb]

Thanks, oh and the posts are gone :D
Is there any kind of relese date set for ScreenOS?

[musk]

I Think Im Dumb, if you read zhamilton1's post from 4/26 (about 11 posts up), you'll find the answer to your release date question.

[cliekid]

Originally posted by musk
I Think Im Dumb, if you read zhamilton1's post from 4/26 (about 11 posts up), you'll find the answer to your release date question.
Tell me if I am wrong (and stupid)... but there is no exact date.

[musk]

True, but that was not the question :)

[sj22Gam3r]

Hello i have been reading this but almost fell asleep on page 8 not that this is boring its just that its going on vorever i know the longer it takes the better but i would like to see a screenshot please? And i heard something earlier mentioned about audio player os 4.1 ? am i right please explain. so far sounds great if you would like to know (when your done that is) if it works on an sj-22 send it to me!!!!!!!!!

[trayip]

As The Mad Dog said before, Edit -> Delete Text

Tray

[vw_bugg]

COUGH^bump^COUGH

Anything new?

[zhamilton1]

Well... now that this is 1src... maybe I can continue to post ;)

Nearly finished CODING the second component...

The object component is also nearly near design stamping and will be coded directly after the second component.

[Wintermute8]

Making progress. Awesome.

[gfunkmagic]

Well... now that this is 1src... maybe I can continue to post ;)

Nearly finished CODING the second component...

The object component is also nearly near design stamping and will be coded directly after the second component.

Cool...tx for the update!

[zhamilton1]

http://www.geocities.com/zhamilton1/MemoryComponent.txt

Here is a small description I wrote of the memory components design and API.
If there is anything you dont understand or if you have any questions ask away.

[vw_bugg]

make sure you change the link on you page to point to 1src.com instead of cliesource.com

[boogers]

can't wait!

[iebnn]

Note to everyone: I talk with him often and he's still working on this :) It WILL be out. It's an enormous project though.

[icarus]

Good to hear, that it has not yet put into a grave.
Looking forward to it.

Will Windows XP be able to compete? ;)

Are there by the way any more screen shots?

[cbulock]

None of the GUI has been coded yet, so there are no screenshots available. The only ones that have been released so far were mock screenshots and the final version will quite likely look different.

[iebnn]

ScreensOS will definitely give Windows XP a run for its money in some aspects ;)

He's done some very clever things with its design. Seriously, you will be amazed

[CliePet]

zhamilton1's blog is here:
http://www.screensenvironment.blogspot.com/

If you want to give praise (or derision), may I politely suggest posting there.

[SirKillalot]

ok, how's that thing working? are you still developing it? current state?

[mikeux50]

all I have to say is wow, and keep up the good work. I have have read through all of the posts and this looks really cool.

Do you have an approximate release date? I cant wait till this is finished.

[Mad]

<BUMP><COUGH><BUMP>

What the hell is going on? Isn't this meant to be out years ago or this just another case of vaporware?

[starbuckk]

<BUMP><COUGH><BUMP>

What the hell is going on? Isn't this meant to be out years ago or this just another case of vaporware?

This is an on going project completly done by one person. This is something very large that he is doing in his spare time.
Check out his blog for an update. It sounds like its coming along very well.
http://www.screensenvironment.blogspot.com/

[suppaman]

Bump again, after six months.

[zhamilton1]

Why bump? Still interested?

[ntw1103]

I am. What's happening with it?

[zhamilton1]

OK, Here is what is happening:

1. I am on schedule (so far) for the febuary alpha. Subscribe to my MSN user list to get the version when its released (I will be sending an email to all the users on the list).

2. The alpha will include the generic shell of the widget bar and the widget dialog and some sample widgets. Depending on the schedule, I might get more functionalty into the alpha.

3. I am coding like crazy and you can download the source code at my blog. My blog gets updated alot and you can find alot of interesting stuff about the project. I am always open to ideas or changes.

4. Screens Environment is public domain. Yes... That means the code is free and will be updated as time goes by.

5. Its amazing to see how long this is taking... My ideas have got more concrete but it did have the problem of becoming vaporware as time goes by. But I am still dragging the dead king around... long live the king :D

I will however open a new thread here when the alpha is ready to invite users to sign up to my MSN user list to get the version.

Beta versions will be publicly available to all... I thank 1src for allowing mass recognition of this project.

Its funny... you can see more and more articles here at 1src about the need for change... Screens Environment will provide that change! Wait and see!

[suppaman]

Why bump? Still interested?

Of course, as long as my SJ20 continues to work. But you should hurry, I won't bet it will last a long ;-)