This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - AHelper
31
« on: January 04, 2012, 05:24:30 pm »
This could go in another topic, but...  glassKILL is finally done for now. An extended demo showing glassKILL, gFiler, suspending and resuming of those processes, and the highscore storage for glassKILL Here is a screenie:  Just added the score tracking and the backgrounding support
32
« on: January 04, 2012, 01:42:31 pm »
Ah, didn't know that the other pocket had the TA1 also.
33
« on: January 04, 2012, 01:38:36 pm »
I wonder if it will have a TA3 or a TA1 chip inside...
34
« on: January 02, 2012, 04:56:20 am »
To get at the problem posted above, I will use port 27 to remap global data from RAM 0. Actually, has anyone ever had to depend on this feature before (port 27 not 28)? Also, the USB communication testing has gone well, so here is a look at the GUI running and browsing files and folders from the calc:  Not done, obviously, and more extensive notes on how the above was done was posted on the Cemetech GlassOS thread. (No need to copy/paste) <edit> Oh I should make a note about this Do you mean on extra RAM pages calcs there is multitasking and on other models there isn't? 1) Task switching is allowed on all calcs as there is always the Launcher running. You can jump to the Launcher at any time and run other programs or kill running ones. 2) Not quite multitasking, but more task switching. Once a program is backgrounded, it only gets to run again if a USB event or custom callback is triggered for that process. 
35
« on: December 29, 2011, 03:35:12 am »
Note that there is always one program running. 3 RAM pages lets the Launcher and a user program run. But yes, I could make the global RAM the Launcher's RAM page and have the other 2 pages open for user programs.
36
« on: December 29, 2011, 03:04:22 am »
Currently, yes. I am going to get around this by hopefully removing the global ram, or at least mapping it elsewhere. Note that with games, you probably can't task switch anyways, as well as non-full page programs. Again, I will work on it later on.
37
« on: December 27, 2011, 11:06:52 am »
Yeah... the lack of RAM pages kinda sucks as GlassOS uses them for task switching, but when there's only three, it will only allow one user program and the launcher...
I could redo it to have the launcher and two user apps with 3 pages, but the page layout needs to be slapped about
38
« on: December 27, 2011, 01:48:18 am »
The OS has quite a bit of code put towards the USB and clock. Removing those would not let any PC connections as I don't have IO code (no IO cable to test with). I don't have the actual hardware so I simply can't code and test it.
Older models as-in the ti84___ calcs with 8 RAM pages?
39
« on: December 27, 2011, 01:30:16 am »
That is true DJ_O. The OS depends on the added hardware of the 84 line. Currently, only the ti84pse is supported due to the flash size harded coded still. I still need to fix that -_-
40
« on: December 18, 2011, 12:48:28 am »
(I need more input from the above query)
On a side note: Should the Launcher theme the background for seasons/special occasions? I was thinking about a monochrome image placed onto the background using light grey for things such as x-mas/december-stuffs, holidays, birthdays, special events, or w/e. Probably configurable - specify a date and a filename and it will display the image when the day comes around. Maybe even changing the banner text.
On the other side of the note: The OS is winding down as the PC-software will need to be moved along. The OS is in good shape right now, still with a few bugs, like turning the calc off when the USB or timers trigger, contrast cannot be changed, LCD doesn't change power levels, etc.. Almost there!
41
« on: December 14, 2011, 12:10:57 am »
Nope. The file is read unbuffered. Writing is done per fputc/fputs (fputs will become fwrite later) call. The fs page is locked until either a fragment is made or fclose is done. crashing programs leave open-ended files which must be recovered or removed.
42
« on: December 13, 2011, 10:14:21 pm »
hmm... for 1&2, I could add in a magic number in global ram, and changing it will signal to all open file handles, when used, to update their page/addresses...
I do agree that it should be transparent to the user. My head only has the extreme cases running through it, like running out of ROM completely, programs with open file handles for reading, etc..
43
« on: December 13, 2011, 07:44:11 pm »
One of the issues that will pop up in GlassOS is flash fragmentation. I already have a routine that will defragment flash pages and sectors. The only issue is that I can't just defragment whenever. So, opinions are needed... I have a couple of ways to go about this. - If a file IO fails due to out of space, it should defragment a sector so that it can write. It will fail completely if no flash can be freed. Warns if other programs are running.
- If a file IO needs space, it should ask the user what type of defragment should be done. A quick or a long defrag. Also warns for other programs.
- File IO would simply return a no memory error.
The issue with defragmenting on the spot is that FILE* structs in any process will not be changed to reflect the moved data. The last one, well, you might loose your data, but if done right, you can simply close other programs, defrag, then swap back to that task to save. But :-\ I can see the first 2 being available if I keep track of file structs, but that would be... odd. There would be a max open files per-process (read and write) so that I can change the data when defragmenting without the user program knowing. I would like to see the 2nd, but that could get ugly with the fs code. 3 is more controlling as you can delete files that you don't want before defragmenting, thus letting you free up space whereas 1&2 would just fail. But 3 isn't straightforward coming from TIOS... :w00t:
44
« on: November 30, 2011, 07:39:29 am »
Ah. That will part of the OS prefs. You can run a tuning wizard in the Launcher to fine tune the greyscale, and all programs that use greyscale will use the frequency that you chose. The firstrun setup wizard will also do the tuning, but right now it only gets the hostname. (last page of the setup right now)
45
« on: November 29, 2011, 11:48:46 pm »
There was probably a better way to get a font than open a text editor, type all characters, set the font, scale it down until it is the right size, then use a text editor and type out the binary sprites for all characters and symbols... twice for both sizes. It took hours to get it right, months to fix bugs in the drawing routines... :'(
|
Show Posts