Stella Development screen...

[+stephena]

How is binary formed?

 

how is binary formed

how programer get ROMs

 

They need to do way instain programer> who execute thier binarys. becuse these binary cant dissasemble back?

it was on the forum this mroing a programer in Homebrew Discussion who had execute his three ROMs. they are taking the three binarys back to Atari 2600 Programming forum too disgust further

my post are with the programer who lost his code ; i am truley sorry for your lots

The worst thing about this is, as I'm reading it I'm 'hearing' the voices used in the Flash video!

A simple fix to the min size issue in stella is to add horizontal and vertical scrollbars if the window won't fit in the minimum space. I could see the min size being a real problem on netbooks.

I also see the problems for netbook users. The problem is that the UI in Stella is homegrown and doesn't currently support scrollbars in that fashion. That's the part I have to think about; how to properly add support for scrolling the entire window.

[slampam]

BTW you can configure your browser to include an assembly option, so you don't even need to touch commandline. By opening up the folder options window (and adding a new action for the file type), you can instruct your OS to use Dasm with %1 for a wild card name. This is the action I use in Win98:

 

"C:\Bin\dasm.exe" %1 -f3 -o%1.bin

 

In my case, the Dasm files exist in the C:\Bin folder. By right-clicking on the file name, I just pick the added action (I named it "assemble"), and the binary file appears almost instantly.

Still, it would be nice to have a proper front end for these things. Front ends are like happy faces for otherwise scary looking programs.

[SeaGtGruff]

Still, it would be nice to have a proper front end for these things. Front ends are like happy faces for otherwise scary looking programs.

A decent IDE would be the proper front end for these things. I use Crimson Editor, because it's free, easy to use, and easy to configure. But my favorite IDE is probably Multi-Edit, which can also be configured for Atari 2600 programming-- either using 6502 assembly or batari Basic-- although it's neither free nor cheap (compared to some of the other commercial IDEs out there).

 

Michael

[Wickeycolumbus]

IMO, the development current environment is great. I dare who ever is willing to not use emulators for developing for 1 week. Very painful! when the week is over, you will never look back, or complain

[SeaGtGruff]

IMO, the development current environment is great. I dare who ever is willing to not use emulators for developing for 1 week. Very painful! when the week is over, you will never look back, or complain

Emulators are essentially essential to Atari 2600 program development, but they aren't absolutely essential. Sooner or later you need to test your programs on the real deal-- and not just on one model of the real deal, but preferably on as many different models and compatibles as possible. *I* wouldn't want to develop without an emulator; but others may prefer to use a development setup that uses the real deal.

 

Michael

[+stephena]

IMO, the development current environment is great. I dare who ever is willing to not use emulators for developing for 1 week. Very painful! when the week is over, you will never look back, or complain

Emulators are essentially essential to Atari 2600 program development, but they aren't absolutely essential. Sooner or later you need to test your programs on the real deal-- and not just on one model of the real deal, but preferably on as many different models and compatibles as possible. *I* wouldn't want to develop without an emulator; but others may prefer to use a development setup that uses the real deal.

 

Michael

I agree. There are many iterations of code/compile/test, and usually the early stages will be more dominated by programmer error/uncertainty than weird interactions of the hardware. So in my opinion, It makes sense to have the code/compile/test cycle as fast as possible early into development. This is (hopefully) where programs like Stella become useful. As you get closer to the final release, it makes sense to test on as wide a variety of hardware as possible.

 

I know you could test every single recompile on a KrokCart, but personally that would drive me absolutely nuts IMO something like that is more for the weekly/monthly hardware checkout, or when you're experimenting with some code that pushes the limits of the hardware.

 

Long story short, there's a continuum between doing everything in an emulator vs. doing everything on the real thing. My aim with the developer options in Stella is to stay close to the emulation side as much as possible. It really does speed up development.