oh lord, that rock must be very large, yes it will be a program

Kerm, if you can, you can count me in as a beta tester.

@Kerm: I'm glad to hear it, and am quite looking forward to this iteration of Doors.

Yay! More DCS! (DCE is a good name, but make it similar to DCS. DCS is great about the "your calc crashed or reset" stuff.)

What does the programs handling of RAM clears (or, in this case, the deleting of certain AppVars) have to do with its name?

Heya! i'm new to this, so don't expect any advanced feedback from me. but i'd like to know how much CE 9 is developping I'm a newbie to this, so please don't come at me with all kinds of "compressen hex for ExecHex"(random example) stuff, i won't understand that ^-^ if possible i will help with whatever i can, beta testing, trying to find issues with it, that kind of things. Also, as i understand, this program is designed for the CE. will it have any major issues on a CE-T? since i have that one

As far as I know, Kerm is working on adding some useful routines to it, finish the BASIC editor, and get proper poweroff working (?), while tr1p1ea is working on xLIBCE, almost the same as xLIBC

Current issues.

• Resolve problems with implementing poweroff to ensure that OS will not crash after quitting DCE after poweroff/APD.
  
• Ensure that memory leak when DCE ran itself via HomeRun is resolved.
  
• Test C/ASM library loading from Mateo within DCE
  
• Make hook chainer work properly, at least with GetKeyHook and AppChangeHook.
  
• Make shell functions called via ExecArcHook put their cleanup routines in safeRAM instead of assuming the layout of Archive hasn't changed. Done for AppChangeHook, not yet for ParserHook.
  
• Make editing both archived and Unarchived programs from the home screen work. Sorted and tested, other than implementing the previous item.
  
• Debug crash when loading new DCE version over old on emulator. -> Probably caused by HomeRun pointing to the wrong place because the stub is not loaded. Yep, caused by stub not holding proper contents. Need to detect this and let the OS handle running the program instead. [color=orange]Possibly (untested) fixed. Relies on following item.
  
• HomeRun ParserHook uses absolute calls to ParserHookChkPrgm, getHomescreenToken, and getHomescreenByte. This makes it crash it many circumstances.
  
• Consider label/home/end menu
  
• Create small core ASM library for DCE programs?
  
• xLIBCE!

Since tr1p1ea now has a family and was already extremely busy to begin with before, in the event where he would be forced to permanently quit calculator development, does it mean that you would take over xLIBCE, scrap it or postpone DCSE indefinitely?

Don't worry, Doors CE will come out either way; it just might take a little longer.

I hope it will come out before the end of the year. I love Doors CE and I can't wait to use it. Without it, I have to wait to play all the DCSE basic games out there.

Wow, this is quite an undertaking. I wish you the best of luck!


Anywho, as long as you have assembly program execution done, this will work.

Has xLIBCE already been split outside of the main DCE binary, for modularity ?

Mr. Kerm,
I'd like to find out how much more time it will take to complete this project.

Hey, do you guys have any guess on when it'll be ready?

For now, it's soon™

Ok so good news, I have commenced seriously porting over xLIBC to the CE.

I have had some minor challenges but have been making good progress this week, all things considered .

Yay! Progress! Glad you're able to find time to work on this!

Nice job tr1p1ea!

Does doors CE plan to have a plugin system? What would be cool is that when someone develops a utility program (ex: text editor), they could make the program, at runtime, install a plugin into doorsCE.
So continuing my text editor example, the plugin will, for example, allow doors to identify the file type of the text editor and use the text editor when opening that type of file
How does that sound?